Piping DUMP978 data to modesmixer2

Is it possible to take DUMP978 data (ADSB Receiver Project) and send it to ModeSmixer2

Yes. You need a listener for AVR, port 30001, on the ModeS2Mixer.

1 Like

–inConnectId \ doesnt work

Need more information. What is the error message?
How are you trying to feed modesmixer? Internally(from the same device) or externally (from another device).
If external, you may need to listen on the physical IP addresses, not the loopback address.

1 Like

MM2 I have set up on the same PI I have ADSB Receiver Project set up on and I used the option to install and run DUMP 978 too.

It works now. I made a small but crucial mistake in edition the mm2 script.

Is dump978 already running? If so, what are the settings? (ps -eaf | grep 978)
It is possible that dump1090 is already using port 30001. If that is the case then just get the info from dump1090.

Good to know it is working now.
What changes did you make to file mm2.sh?
Did you add this line to file mm2.sh, or did something else?

--inConnectId \

–inConnectId \

1 Like

I just did a comparison with DUMP978 MAP and MM2 and the data does not show up on MM2.
I have DUMP 978 set up on ADSB Receiver Project with DUMP 1090 mutability as per the installation of the scripts.
This is the configuration;

Start dump978 without logging.

while true; do
rtl_sdr -d 1 -f 978000000 -s 2083334 -g 48 - | /home/pi/adsb-receiver/build/dump978/dump978/dump978 | tee >(/home/pi/adsb-receiver/build/dump978/dump978/uat2json /var/www/html/dump978/data) | /home/pi/adsb-receiver/build/dump978/dum$
sleep 15

This does not show a data output for I found out the hard way you cant use this configuation;
while true; do
rtl_sdr -d 0 -f 978000000 -s 2083334 -g 48 - | /home/pi/adsb-receiver/build/dump978/dump978/dump978 | tee > (/home/pi/adsb-receiver/build/dump978/dump978/uat2json /var/www/html/dump978/data) | /home/pi/adsb-receiver/build/dump978/dump978/uat2esnt | /bin/nc -q1 30001
sleep 15

I think 30001 carries data from dongle to decoder (input).
so you need 30002 (output) AVR instead.
I tried it in VRS and modeSmixer under Win 7.
although both connect to 30001 there is no data flow.

--inConnectId [your IP ]:30002:AVR for external mm2 use.
--inConnectId [localhost or]:30002:AVR for internal (rpi) use
(this is same as inConnect localhost:30002) as mm2 defaults to AVR on this port.


1 Like

That works. The AVR is the correct one.
--inConnectId [localhost or]:30002:AVR for internal (rpi) use