Wow, after a hundred billion years, and a lot of effort in the last 12 hours, AV3's comm gear is finally up and running. Thanks to Theo, Glenn, Richard, Frank, and Bart for getting this all done today.
- Crescent GPS is wired into the FC, and the FC is running Ian's small C program that parses the output so we can see what's going on with the GPS (lock, SNRs, etc)
- from the event-driven-fc repo:
gcc crescent.c -o crescent - ssh to the FC, run it with the FTDI device connected to the GPS serial port:
./crescent /dev/ttyUSB0
- from the event-driven-fc repo:
- USB 802.11A adapter is wired into the FC and the FC has control over the WiFi power amp via it's GPIO.
- FC has control over the ATV system via it's GPIO.
- Temporary power distribution board on the top plate distributes battery power for now.
- Temporary battery pack Just Works.
Wireless configuration of the Ralink RT2860:
# iw reg set US
# iw list (to find the physical name of the device and confirm channel 36 is usable in ad-hoc mode)
# iw phy2 interface add adhoc0 type ibss
# iwconfig adhoc0 mode ad-hoc essid LV2 freq 5180M
# ifconfig adhoc0 up
# ifconfig adhoc0 10.1.1.2
Wireless configuration via Network Manager for a development laptop:
- right-click tray icon > Edit Connections...
- wireless > Add
- Wireless tab
- Connection name: rocket
- Mode: Ad-hoc
- Band: A (5 GHz)
- Channel: 36 (5180 MHz)
- Mac addr: fill it in so this config isn't used for your built-in wireless
- IPv4 tab
- Method: Manual
- Add: 10.1.1.2, mask 255.255.255.0
- Save
Also:
- More?
- Pictures?
To do:
- GPIOs are always high on boot and no longer go low without direct commands. Remove MOSFETs from RF power board to make it an active-low system.
- Rewire ATV signals to header on temp distribution board for debugging camera signals.
- Wire FC's ttyS0 to a serial-level header on the temp distribution board so we can get reliable communication to the FC when it's put together.
- Get the Ethernet to come up in some kind of known state so we can use ethernet for coms if we want to.
- Get the USB WiFi up and running in Ad Hoc mode - this seems to be difficult on the FC?
- Since 2005, Linux has added a regulatory database (crda) for which regions are allowed to use which frequencies in various modes, such as ad-hoc/ibss. The default worldwide region blocks use of channels 36 (the one our antenna is best at) and above. On our Linux laptops, we can use
iw reg set USto set the appropriate region and open up a dozen channels. This fails on the rocket's monolithic 3.4.3 kernel with the error "Failed to set regulatory domain: -7". Others who got this error suggest that this only works if your wireless drivers are built as modules. Other workarounds are to set the region in the device's firmware and constructing a replacement regulatory database giving the default 00 region unrestricted access.
- Since 2005, Linux has added a regulatory database (crda) for which regions are allowed to use which frequencies in various modes, such as ad-hoc/ibss. The default worldwide region blocks use of channels 36 (the one our antenna is best at) and above. On our Linux laptops, we can use
- Make temporary battery setup less hacky
- All Systems Go for flight computer development, so time to bring the software team page up-to-date.
- remove obsolete LV2 links
- instructions and kernel config for building FC kernel
- userspace configuration, like wireless and event-driven-fc installation
- LV2c equivalent of the old FlightComputerSoftware page