search

Mictronics / readsb-protobuf

Readsb is a Mode-S/ADSB/TIS decoder for RTLSDR, BladeRF, Modes-Beast and GNS5894 devices. Future development version with protocol buffer storage.
Other
90 stars 25 forks source link

General help and or forum? #29

Closed JBKingdon closed 9 months ago

JBKingdon commented 9 months ago

Hi, Sorry to use an issue for this general question, I couldn't find a forum for discussion and new user questions.

I'm working on a simple ADSB receiver (https://github.com/JBKingdon/ADSB_Alert) and a friend suggested that I use this project to validate the output while I'm working on the protocol decoding stage. I implemented the beast AVR format output via usb vcp, currently for df17 and df18 messages only. The output data decodes with pyModeS and looks reasonable. I've confirmed that reading from the port with cat /dev/ttyACM1 shows the expected output.

Running readsb with ./readsb --device-type modesbeast --beast-serial=/dev/ttyACM1 --beast-mlat-off --interactive starts successfully, shows the header bar with a rotating | symbol at the end, but never populates with any entries. Any suggestions for what I'm doing wrong would be great. Is there any debug I can enable to confirm what readsb is seeing from my device? I was wondering if there is any start-up handshake between readsb and the device that I need to support, or if more message types than just df17 * 18 are needed?

Regards and thanks!

JBKingdon commented 9 months ago

Ah, I see - there's a configuration step and readsb wants binary format. Ok, sorry for the noise, I'll update my output stage. https://github.com/Mictronics/readsb-protobuf/blob/51304bcbda95aef4df1345428f3a4ac82db02756/sdr_beast.c#L141

JBKingdon commented 9 months ago

All working nicely now. I made a mess of generating the binary format but got it sorted eventually.

Many thanks for readsb, it's going to be very useful to have a known standard to validate against.