Glenn, Theo and Andrew finally got everything pulled together:
- Temporary battery in the battery box
- 4S1P pack @ 1 AHr (?) and it lasted a little less than an hour.
- Power draw with PAs off is 15V @ 1.2 - 1.7 A (Why is it so high?)
- Power draw with PAs on is 15V @ 1.7 - 2.3 A
- ttyS1 port on top of AV3
- Put AV3 into avionics module and hooked up antennas
- With Josh and Joe's help, got Andrew's laptop to be an AP on CH36 and have the FC associate with it.
wifi-on/offto control PAs from the command line.
crescentprogram in the event-driven-fc repo let us look at the GPS sats.
We got great results on the GPS:
- Turning on and off all PAs didn't seem to affect GPS lock or satellites at all.
- Even turning on the Trackmaster 2000 PAs didn't affect GPS lock.
- It kept grabbing lock within a few seconds of being turned on.
- Don't forget to run
stty -F /dev/ttyUSB0 115200 raw
- Just worked.
WiFi Networking Testing
- Andrew used
hostapdon the RALINK adapter as an AP.
- Ran the
/usr/local/sbin/psasscript to associate the RALINK on the FC with the psas network.
- Had to run
ip addr add 172.17.0.1/20 dev wlan0on the FC in order to get a static route.
- Andrew had to run
ip addr add 172.17.0.2/20 dev wlan2to get the static route on his laptop.
- FC dissociates from psas network after about 30 feet or so, and then you have re-run the psas script. We're thinking we've misconfigured the network somehow, and made it brittle? Also, we hope this problem goes away in ad-hoc mode?