Closed jrobinson-uk closed 7 years ago
rc.local is probably the best place to start it from.
Is RTTY definitely not starting? Or is it possible it's still on the MTX2's default frequency? Something I had to do in PITS and I've noticed I'm not doing in pytrack is to call the frequency-setting routine twice. Not sure why that's needed exactly but it seems the MTX2 doesn't always see the first command, though it's fine after that. Duplicating line 18 in rtty.py - this line:
self._set_frequency(frequency)
would sort that.
Can't think why LoRa wouldn't start. Is it possible that the entire program isn't starting?
On 29 March 2017 at 15:46, James Robinson notifications@github.com wrote:
Dave, how would you start pytrack on boot, I'm sporadically getting it booting, running but not transmitting. Usually Rtty is the issue but sometimes Lora too
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/raspberrypi/pytrack/issues/3, or mute the thread https://github.com/notifications/unsubscribe-auth/ABBodFz-GkDMOj2kcqbIfprE97hU4GI1ks5rqm66gaJpZM4MtFqb .
Yeah I had an rc.local script setup much like yours.
Adding a 2nd self._set_frequency(frequency)
line worked
Thanks
Now added that MTX2 frequiency-setting line to master, plus instructions for autostart to the readme file.
Dave, how would you start pytrack on boot, I'm sporadically getting it booting, running but not transmitting. Lora always works, but rtty often fails. If I log in and re-run the program it suddenly works.