Rob Derstadt <[email protected]> writes: > I've been trying to setup my second Telemetrum and am not able to connect > in "idle" mode using the TeleDongle (RF connection). What's odd is that I > can connect when it's in pad/flight mode. Scanning also does not show the > Telemetrum when it's booted in idle mode.
Working backwards: Scanning only works in 'pad' mode because it's listening for the TeleMetrum to transmit. In 'idle' mode, TeleMetrum only speaks when spoken to. If you can't connect in idle mode, you need to make sure you're configured for the right frequency/channel, you must have an exact match in callsigns (including case sensitivity, trailing spaces, etc) configured in the flight computer and the ground station, and you need to be a suitable distance away... if you're within a few feet you may be overloading the receiver which causes it to not be able to copy the packets. If none of that helps, give me your TeleDongle serial number and I'll let you know if it's in the range that might have a flakey RF system on chip part thanks to what appears to have been a bad run of parts at TI. > I'm running AltOs 1.6 on OS X 10.10.3 (Yosemite) . Both units are flashed > with the latest Telemetrum 2.0 image as well. All I can think of is that > there's some OS X upgrade that it causing issues with the TeleDongle or > AltoOS software. Any ideas here? I've tried on both my desktop and laptop > with no luck. Callsigns not matching is the most common problem. Doesn't affect the ability to monitor packets in pad mode, completely kills idle mode interaction. Bdale
signature.asc
Description: PGP signature
_______________________________________________ altusmetrum mailing list [email protected] http://lists.gag.com/mailman/listinfo/altusmetrum
