User Tools

Site Tools


second_tinypilot

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
second_tinypilot [2022/02/10 01:16]
seandepagnier
second_tinypilot [2022/02/10 01:22] (current)
seandepagnier
Line 2: Line 2:
  
 Set the second tinypilot to use remote address for lcd interface: Set the second tinypilot to use remote address for lcd interface:
- - boot second tinypilot keeping the first tinypilot (autopilot) powered off. 
- - connect to wifi access point "​pypilot"​ 
- - ssh to client (remote tinypilot) 
- - set remote host for hat display 
-$ ssh tc@192.168.14.1 
-password: pypilot 
-$ nano ~/​.pypilot/​hat.conf 
- - 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 
  
 +  * boot second tinypilot keeping the first tinypilot (autopilot) powered off.
 +  * connect to wifi access point "​pypilot"​
 +  * ssh to client (remote tinypilot)
 +  * set remote host for hat display
 +
 +  $ ssh tc@192.168.14.1
 +  password: pypilot
 +  $ nano ~/​.pypilot/​hat.conf
 +
 +  * 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. 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 +It may also be found with nmap 
-$ nmap -sT 192.168.14.0/​24+ 
 +  ​$ nmap -sT 192.168.14.0/​24
  
second_tinypilot.1644455773.txt.gz · Last modified: 2022/02/10 01:16 by seandepagnier