ModeSMixer2 with USB?

[DaveReid]

I'm hoping to be able to connect to my SBS-1eR (with its u/s Ethernet port) from ModeSMixer2 using USB.

The sample batch file in the ModeSMixer2 zip features an --inSerial parameter, with 3 arguments ("COM4:3000000:none" in the example), but that's not documented in the Help so it's not clear what syntax, if any, will enable a USB connection.

Does anyone know ?

[Anmer]

Can you get raw data from an SBS-1eR?

ModeSMixer2 needs to know where it can find decoded data.  Or you need to use ModeSDeco2?

[DaveReid]

I'm pretty sure you can - for example, Piotr's sbs1xxx.exe is certainly able to connect direct to the SBS-1eR without needing BaseStation (via both Ethernet and USB) and it displays the data from the SBS as raw Mode S and ADS-B packets.

That utility can connect to the SBS using either its IP address (on port 10001) or its USB identity ("nnnnnB"), so I was kind of hoping that ModeSMixer2 could, too.   

[Anmer]

Try something like:

--inSerial Com3:3000000:hardware

But I guess you need to know the Com number used by the SBS-1eR and maybe this bit's wrong 

3000000:hardware

[DaveReid]

Try something like:

--inSerial Com3:3000000:hardware

But I guess you need to know the Com number used by the SBS-1eR and maybe this bit's wrong 

3000000:hardware

Yes, that's the crucial bit, and the one that's producing the "parameter is incorrect" error.

In my case, COM4 is the virtual comm port in question and the frustrating part is that I can point a terminal program at that port and actually see the raw data streaming past, but for some reason ModeSMixer2 doesn't want to know.

So near, and yet so far ...   



[attachment deleted reduce file load]

[Anmer]

Can you post your bat file content?

[DaveReid]

Certainly.

Command plus responses:

W:\SBShelp\ModeSMixer2>modesmixer2.exe --inSerial COM4:3000000:none --outServer sbs10001:10002
2022-04-30 22:32:49.699  INFO     ModeSMixer2 v.20190413
2022-04-30 22:32:49.730  INFO     outServer(sbs10001:10002) started
2022-04-30 22:32:49.887  ERROR    inSerial(COM4:3000000) error open The parameter is incorrect
2022-04-30 22:32:49.887  INFO     inSerial(COM4:3000000) Reconnect in 10 seconds
2022-04-30 22:33:00.046  ERROR    inSerial(COM4:3000000) error open The parameter is incorrect
2022-04-30 22:33:00.046  INFO     inSerial(COM4:3000000) Reconnect in 10 seconds
etc ...

Changing the 3000000 (the baud rate) to any other value makes no difference, but if I substitute a non-existent port (COM3, for example), I get a different error message:

W:\SBShelp\ModeSMixer2>modesmixer2.exe --inSerial COM3:3000000:none --outServer sbs10001:10002
2022-04-30 22:36:53.428  INFO     ModeSMixer2 v.20190413
2022-04-30 22:36:53.459  INFO     outServer(sbs10001:10002) started
2022-04-30 22:36:53.459  ERROR    inSerial(COM3:3000000) error open The system cannot find the file specified
2022-04-30 22:36:53.459  INFO     inSerial(COM3:3000000) Reconnect in 10 seconds
etc ...

So ModeSMixer2 recognises that COM4 is a valid port, it just won't talk to it.

It must be 30+ years since I last messed about with serial comms on a PC.   

[abcd567]

pi@raspberrypi:~ $ modesmixer2 --help

ModeSMixer2 v.20210228 RPI_x64

--inSerial arg.   Input serial.
                          Format:port[:speed[:flow_control]]
                          FlowControl:none,software,hardware




[attachment deleted reduce file load]

[DaveReid]

pi@raspberrypi:~ $ modesmixer2 --help

ModeSMixer2 v.20210228 RPI_x64

--inSerial arg.   Input serial.
                          Format:port[:speed[:flow_control]]
                          FlowControl:none,software,hardware

Thanks for that.

But, as far as I can see, that's exactly the syntax I've been using - and yet ModeSMixer2 is returning an error.

[Anmer]

I'm clutching at straws here 

What version of windows are you running and is it 32 or 64 bit?

Is the SBS-1eR just connected by USB and not have any app running?  i.e. Basestation?

Have you tried using

--inSerial COM4:3000000:software

or

--inSerial COM4:3000000:hardware

[DaveReid]

I have an extensive collection of clutched straws here 

Platform is W10 64-bit.

No other apps running (though BaseStation works fine with both SBS-1eR and SBS-3 via USB).

Results are the same with any of the 3 flow control options (software/hardware/none).

Confirmed that both boxes will connect via COM4 with RealTerm (using appropriate baud rate 921600 or 3000000, respectively).

ModeSMixer2 working fine with the SBS-3 via Ethernet - I may have to make do with that.

[Anmer]

Thanks Dave, that was my last straw.

But I'll see if I can get it to work here.

[Anmer]

OK, some progress.

With this in the BAT I get the same error 

Code Select Expand

@echo off
CMD /c I:\MSM2\modesmixer2.exe --inSerial COM1:921600:none --outServer sbs10001:10002
exit

Hmmm?

[attachment deleted reduce file load]

[egnx]

FYI, if I use modesmixer2 with my 1er connected by usb without basestation running and with the following:-
modesmixer2.exe --inConnect 127.0.0.1:10001  --outServer msg:31664

All i get is the error:-
no connection could be made because the target machine actively refused it

I am not trying to run basestion with this, merely output the msg data to a port for testing.

If I run Basestion without modesmixer it runs fine. This implies to me that modesmixer cannot decode the 10001 output from the 1er ?

egnx

[Anmer]

This implies to me that modesmixer cannot decode the 10001 output from the 1er ?

I get the same result if I connect via USB to an SBS-3 which supports raw data.