User Tools

Site Tools


second_tinypilot

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
second_tinypilot [2019/08/26 19:21]
209.42.151.109 created
second_tinypilot [2022/02/10 01:22] (current)
seandepagnier
Line 1: Line 1:
 It might be useful to use a second tinypilot to control the autopilot over wifi using the lcd/keypad and remote ​ interface. It might be useful to use a second tinypilot to control the autopilot over wifi using the lcd/keypad and remote ​ interface.
  
-Configure ​the second tinypilot ​client wifi:+Set the second tinypilot ​to use remote address for lcd interface:
  
- ​- ​boot second tinypilot keeping the first tinypilot (autopilot) powered off. +  * boot second tinypilot keeping the first tinypilot (autopilot) powered off. 
- connect to wifi access point "​pypilot" ​with device with browser +  ​* ​connect to wifi access point "​pypilot"​ 
- - navigate to http://​192.168.14.1 +  * ssh to client (remote tinypilot) 
- - click "​Configuration"​ then "​Configure Wifi"​ +  * set remote host for hat display
- - Switch ​to client ​mode (managedrather than AP+
  
 +  $ ssh tc@192.168.14.1
 +  password: pypilot
 +  $ nano ~/​.pypilot/​hat.conf
  
-Set the second ​tinypilot to use remote address ​for lcd interface:+  * Replace localhost with the ip address of the master ​tinypilot.  Typically replace  
 +"​host":"​localhost","​actions"​... with "​host":"​192.168.14.1","​actions"​... 
 +  * Save file exit nano 
 +  * Disable pypilot on boot 
 + 
 +  $ nano /​opt/​bootlocal 
 + 
 +  * scroll down to line "sv u pypilot"​ (about line 78) 
 +  * comment line out changing it to "#sv u pypilot"​ 
 +  * save file exit nano 
 +  * store boot script 
 + 
 +  $ filetool.sh -b 
 + 
 +  * navigate to http://​pypilot.io/​wifi, ​ or http://​192.168.14.1/​wifi 
 +  * Switch to client mode (managed) rather than AP, and set the correct host/ssid, by default "​pypilot"​ with no key. 
 +  * Power cycle 
 +  * Power the primary tinypilot computer 
 +  * Ensure the WIFI is displayed on both screens 
 + 
 +To take out of remote ​mode will simply reverse the above steps. ​ In client mode it may be difficult to ssh into the remote tinypilot without knowing the ip address.  This is normally listed on the wifi display (version 0.32 and newer) ​ typically pypilot.io/​wifi. 
 +It may also be found with nmap
  
- - Boot both tinypilot computers +  ​$ nmap -sT 192.168.14.0/​24
- - Connect to access point of primary tinypilot +
- - Find ip address of  client tinypilot:​ +
-$ nmap -sT 192.168.14.0/​24 +
- - ssh to client +
-$ ssh tc@192.168.14.37 +
-password: pypilot +
-$ nano ~/​.pypilot/​signalk.conf +
- - Replace contents with: +
-{"​host":"​192.168.14.1"​} +
- - Save file exit nano +
-$ sync +
-$ sudo reboot+
  
second_tinypilot.1566847281.txt.gz · Last modified: 2019/08/26 19:21 by 209.42.151.109