And just for kicks. Since those dev messages look like it needs to be a fork that supports --mlat. I fired it up to compare the difference on my test stick.
Dump1090 windows compile Ver : 1.09.0608.14
./dump1090.exe --help
--mlat display raw messages in Beast ascii mode
When run with --mlat --net:
30002 format:
@00000224999A8DC8276C2204E6B3DF5360F845A4;
@000002F62ACA02A186111F58FA;
@000003357F0002A186111F58FA;
30005 format: (certainly binary)
ÛCì╚'lÛÞê0å3xÂ░\Nì╚'lÖÆô8H
┴~╠2yÛF┴åö(~3y-ènMì╚'l°#I©hM3y4█ÄJì╚'lX5GO╠ÛL┌3yfKÿKì╚'lÖæô8 H ─a×3yv╚Æ=ì╚'lß║ØBY3y█}Gì'lÛÞê0å2yß▀ªRÑåô/%3z¦{■Bì╚'lÖæôH
When run with only --net:
30002 format:
*02A184B6FA5473;
*8DC827B1EA30E894013C08F9A8A6;
*8DC827B19908602610540C7CE0EA;
30005 format:
28ê2b─2ì3¿2ÿ"ì╚'▒t╠
ô2®]ý5]╚'▒ç═3®ÃS┬)ì╚'▒uð
╔ÎJ3¬┐ýì╚'▒XË<à¹W3¬═(ý%ì╚'▒uÈ
Guess that's why it's always preferred avr/30002 then?
Though I would have thought with it happy with Binary Beast format (just like the Radarcape and F- produce) it shouldn't be as clear cut as 'only use DVBT with direct connection'
Here's my current status (mode-s beast behind beast-splitter, And fr24feed is using one of beast splitter ports on beast-tcp even!)
Figure this one out.. (beast-tcp like this is malformed essentially the same no matter the receiver?)
pi@raspberrypi:~ $ sudo fr24feed-status
[ ok ] FR24 Feeder/Decoder Process: running.
[ ok ] FR24 Stats Timestamp: 2021-04-29 06:42:20.
[ ok ] FR24 Link: connected [TCP].
[ ok ] FR24 Radar: T-NZCH1.
[ ok ] FR24 Tracked AC: 14.
[ ok ] Receiver: connected (5494652 MSGS/0 SYNC).
[ ok ] FR24 MLAT: ok [UDP].
[ ok ] FR24 MLAT AC seen: 13.
mlatbeast.JPG
fr24feed 27037 27067 th_master fr24 29u IPv4 1091682373 0t0 TCP localhost:43918->localhost:30005 (ESTABLISHED)
fr24feed 27037 27068 th_reader fr24 29u IPv4 1091682373 0t0 TCP localhost:43918->localhost:30005 (ESTABLISHED)
fr24feed 27037 27069 th_socket fr24 29u IPv4 1091682373 0t0 TCP localhost:43918->localhost:30005 (ESTABLISHED)
fr24feed 27037 27070 mlat_thre fr24 29u IPv4 1091682373 0t0 TCP localhost:43918->localhost:30005 (ESTABLISHED)
Dump1090 windows compile Ver : 1.09.0608.14
./dump1090.exe --help
--mlat display raw messages in Beast ascii mode
When run with --mlat --net:
30002 format:
@00000224999A8DC8276C2204E6B3DF5360F845A4;
@000002F62ACA02A186111F58FA;
@000003357F0002A186111F58FA;
30005 format: (certainly binary)
ÛCì╚'lÛÞê0å3xÂ░\Nì╚'lÖÆô8H
┴~╠2yÛF┴åö(~3y-ènMì╚'l°#I©hM3y4█ÄJì╚'lX5GO╠ÛL┌3yfKÿKì╚'lÖæô8 H ─a×3yv╚Æ=ì╚'lß║ØBY3y█}Gì'lÛÞê0å2yß▀ªRÑåô/%3z¦{■Bì╚'lÖæôH
When run with only --net:
30002 format:
*02A184B6FA5473;
*8DC827B1EA30E894013C08F9A8A6;
*8DC827B19908602610540C7CE0EA;
30005 format:
28ê2b─2ì3¿2ÿ"ì╚'▒t╠
ô2®]ý5]╚'▒ç═3®ÃS┬)ì╚'▒uð
╔ÎJ3¬┐ýì╚'▒XË<à¹W3¬═(ý%ì╚'▒uÈ
Guess that's why it's always preferred avr/30002 then?
Though I would have thought with it happy with Binary Beast format (just like the Radarcape and F- produce) it shouldn't be as clear cut as 'only use DVBT with direct connection'
Here's my current status (mode-s beast behind beast-splitter, And fr24feed is using one of beast splitter ports on beast-tcp even!)
Figure this one out.. (beast-tcp like this is malformed essentially the same no matter the receiver?)
pi@raspberrypi:~ $ sudo fr24feed-status
[ ok ] FR24 Feeder/Decoder Process: running.
[ ok ] FR24 Stats Timestamp: 2021-04-29 06:42:20.
[ ok ] FR24 Link: connected [TCP].
[ ok ] FR24 Radar: T-NZCH1.
[ ok ] FR24 Tracked AC: 14.
[ ok ] Receiver: connected (5494652 MSGS/0 SYNC).
[ ok ] FR24 MLAT: ok [UDP].
[ ok ] FR24 MLAT AC seen: 13.
mlatbeast.JPG
fr24feed 27037 27067 th_master fr24 29u IPv4 1091682373 0t0 TCP localhost:43918->localhost:30005 (ESTABLISHED)
fr24feed 27037 27068 th_reader fr24 29u IPv4 1091682373 0t0 TCP localhost:43918->localhost:30005 (ESTABLISHED)
fr24feed 27037 27069 th_socket fr24 29u IPv4 1091682373 0t0 TCP localhost:43918->localhost:30005 (ESTABLISHED)
fr24feed 27037 27070 mlat_thre fr24 29u IPv4 1091682373 0t0 TCP localhost:43918->localhost:30005 (ESTABLISHED)
Comment