squawk not always read from SBS JAERO inputs about readsb HOT 9 CLOSED

That would be the thing to do for now at least.
I'll think about making an exception for jaero when i get the chance.

from readsb.

you can always recompile with local changes

from readsb.

From SBS the squawk should be accepted.

Are you sure it's in the data stream?

from readsb.

Squawk has some logic to require the squawk to be received twice before the change is accepted.
I'm not sure if that applies to SBS input as well though. ... .don't think it does.

from readsb.

number of messages might be it... looking at the current tar1090 list I only have squawks for targets with >2 messages. Possibly a separate issue, I've never seen a target listed as only having 1 message.

Squawk is definitely in the input SBS messages, I can actually monitor the SBS output port and see the squawk forwarded on all messages there as well.

from readsb.

also, I didn't look too hard at the code, what causes blank lines to be output on the SBS output port? Invalid/old messages?

from readsb.

https://github.com/wiedehopf/readsb/blob/dev/track.c#L2013

Yeah i believe that's what is happening.
The squawk will only change after receiving the same squawk twice.
For actual ModeS / ADS-B data that's a sane approach.

I don't know if i want to change it even for SBS to be honest it's a good thing most of the time.
An exception for SBS jaero input might be possible as it's an input that only gets messages very rarely.

from readsb.

thanks. if you don't want to add an exception i can just send messages twice lol

from readsb.

ah sending twice doesn't work, looks like there's a wait period. Not sure if the 15 second or 750 ms wait period is the relevant one.

from readsb.