I would like to clarify:

AVR-MLAT format does not provide data about the level of received signal. His format is: <@><6 byte MLAT counter><7 or 14 byte Mode-S><;><CR><LF>. The signal level is the invention of Gunther and is only present in BEAST binary format: <0x1a> <"3"> 6 byte MLAT, 1 byte signal level , 7 or 14 byte Mode-S.



When the data is output in the AVR-MLAT format, are they suitable for MLAT or Beamfinder? Or they are not suitable as BEAST binary also?



Now the MLAT counter has a resolution of 83.333 ns for Mode-S, not 500 ns. It is possible that the reason is this. I'll try to find out.



Thanks,

Sergsero



Hi Sergsero,Yes AVR-MLAT seems good for mlat but I have to get a mlat fix since using your software as I think there were not sufficient data when I tried it to have good results and Beamfinder is OK like with RTL1090. But in Beast output format, the beams in Beamfinder are pointing almost anywhere and when I test in Planeplotter with the option Test Networking-->Check GS/MU status, the graph that is displayed with the dots at the bottom of the page print randoms dots instead of the oblique and nearly aligned dots with RTL1090 or Modesdeco in AVR-MLAT. So there's something wrong with your implementation of the Beast output format in Modesdeco.I like to have the signal level of the signals I receive that if the Beast output format is fixed with good timings and/or reliability, that would be great because I would have best of both worlds.BTW, I don't have too much traffic and especially this week so I cannot tell how it's doing with high packets rate but last sunday, it was stable with 75 packets/sec and it never crashed since I first tried it last saturday night.Regards,Luc Fontaine+qX