(V65) Horus V3 not transmitting on 2 QRG's

[PC9DB]

HI, I have configured this:

as well as this:

But my RS41 always transmits at 437.600 and not always once in a minute. Sometimes again after 30 seconds and a lot of times 2 packets (on the same QRG) right after each other.

What am I doing wrong here, or is there a bug present?

Regards,
Mark

[Nevvman18]

I have to check the scheduler code, I don't trust it now and I have to rewrite it.
The 2 QRG operation works by transmitting on the second QRG right after the transmission on the first one. I'll investigate it.

Thanks,
Franek

[SteveRan]

I've also encountered the scheduler doing unusual things - when set to just transmit horusV2 every 15 seconds it would often give 1 - 2 minutes gaps - sometimes sending 2 or even 3 consecutive packets when it did wake up. With the setting of Horus V2 every 10 seconds it seems much more regular - but transmissions are still occasionally late and sometimes 2 consecutive packets are transmitted.
Ive also found that if the GPS looses lock (say due to RF noise from a camera) that the sonde does not transmit any packets. I suggest the sonde keeps its own free running time which is adjusted by GPS time when available. Loosing transmissions completely provides no clue as to the failure and provides no help in finding the equipment (which could have been DFed from the transmissions even without GPS position).

[darksidelemm]

If the GPS has lock and loses it, the GPS should still continue to increment its internal time (though it will report no lock) - there should be no need for this codebase to try and maintain its own time.

[SteveRan]

OK - but the code is not transmitting when it looses lock - I assumed the GPS had lost time and and that was why the transmission scheduler was not working. My opinion is that it should continue to transmit more or less to the same schedule - even if the GPS data is rubbish. It should not give up transmitting altogether. This was driven from the experience of Z1HV3 Saturday - which was working fine until the students tied it near their payload - which knocked out the RS41's GPS until the payload batteries ran out. There were very few transmissions during the flight (often 10s of minutes of radio silence).

[darksidelemm]

@SteveRan (sorry just saw this) - yes, I agree that it should definitely continue transmitting even if there is no GPS lock, even if just to enable direction finding of the payload. The "improvedGpsPerformance" setting will make it transmit less often without gps lock (to try and let it obtain lock again), but it shouldn't ever completely stop transmitting...

If you're using the newer RS41 boards, then I would maybe suggest reverting to my original testing fork: https://github.com/darksidelemm/rs41-nfw/tree/horusv3/
This doesn't appear to have the scheduler issues, and should hopefully continue transmitting without GPS lock if the improvedGpsPerformance setting is disabled.

The KE5GDB fork of RS41ng ( https://github.com/ke5gdb/RS41ng/tree/stm32_ll ) is also coming along well, and has Horus v3 support.