ODR-DabMux version and EasyDAB V2

[mike....@gmail.com]

We've bought a PCS and EasyDab V2 transmitter but have come up against the incompatibility of the current odr-dabmux versions and EasyDab. The test file from a v2.3.1 source does allow the EasyDab to transmit. I have tried to roll back to a v2.3.1 odr-dabmux but the compiling fails. Any ideas  people?

Mike

[Matthias Brändli]

Hello,

I fixed something related to easydab in v5.0.0, and I believe also the
latest release should work with the easydab. Can anybody confirm?

Regarding v2.3.1 not compiling: that's why v2.3.2 exists.

Cheers
mpb

> --
> You received this message because you are subscribed to the Google
> Groups "mmbtools" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to crc-mmbtools...@googlegroups.com <mailto:crc-
> mmbtools+u...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/crc-
> mmbtools/9cf551ba-5586-425c-8d61-9377ce08d680n%40googlegroups.com
> <https://groups.google.com/d/msgid/crc-
> mmbtools/9cf551ba-5586-425c-8d61-9377ce08d680n%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

[mike....@gmail.com]

I have successfully install v2.3.2 but....

ietf.org is no longer serving this file. Use https://data.iana.org/time-zones/data/leap-seconds.list instead. - Problem  

and it looks like the "https://raw.githubusercontent.com/eggert/tz/master/leap-seconds.list" has expired.

MD

[Nick Piggott]

Hello,

I'm successfully using

* odr-dabmux 5.0.0

* odr-zmq2edi 4.5.0 - connecting to the ZMQ output of odr-dabmux

with an easyDab v2 based transmitter. The purpose of odr-zmq2edi is to provide additional buffering locally to the transmitter, in excess of what the easyDab v2 board can accommodate.

odr-dabmux has a general configuration of

       tist true

       tist_offset 2

the ZMQ output configured with 

      allowmetadata true

Nick

[mike....@gmail.com]

Hello Nick . I can produce a working multiplex with both EDI and ZMQ  outputs with odr-dabmux 4.5.0 on separate ports and decode the EDI stream with Dablin. I think I have odr-zmq2edi running but would like some advice on the syntax. It produces buffering statistics but I can't resolve an EDI o/p with Dablin.

I somehow managed to activate the EastDAB from home on Saturday but have been unable to repeat the set up and stupidly made no records.

MD

[Nick Piggott]

Hello,

You will need to use different ports for the EDI and ZMQ outputs from odr-dabmux

The syntax for my  odr-zmq2edi is

odr-zmq2edi -w -400 -C /usr/bin/local/check-time-sync -x -Z tcp://*:9100 tcp://{odr-dabmux-ZMQ-port}

The -w 400 tells odr-zmq2edi to release the EDI packets 400ms before their ATST time (which in turn is set in the mux as now()+tist_offset)

The -C is a path to my local script that returns an error if NTP time is not locked

The -x says to drop late frames (that arrive less than local NTP time - 400ms)

The -Z is to open a local ZMQ socket for the easyDab to connect to (on port 9100)

Finally the tcp:// is the address on the mux which the ZMQ port is open on

I haven't ever tried to read the EDI out of that - I just connect an easyDab board to the ZMQ, and it seems pretty happy, and stays in the SFN

Nick

[mike....@gmail.com]

I am attempting a remote access and sending EDI data directly from odr-dabmux over the internet gets a 'Connected' green blob OK but no broadcast blob and that EDI can be monitored by Dablin(locally). Here is my result when running odr-zmq2edi:-

$ odr-zmq2edi -w -400 -C ~/check-time.sh -d 192.168.1.94 -p 9000  tcp://127.0.0.1:9990
2025-10-21Z11:40:31       ZMQ2EDI converter from ODR-DabMux 4.5.0 starting up
2025-10-21Z11:40:31       EDI disabled
2025-10-21Z11:40:31       Running startup check '/home/michael-davison/check-time.sh'
2025-10-21Z11:40:31       Startup check ok
2025-10-21Z11:40:31       Setting up Sender with delay -400 ms. Will not drop late packets
2025-10-21Z11:40:31       Opening ZMQ input: tcp://127.0.0.1:9990
2025-10-21Z11:40:40       Buffering time statistics [milliseconds]: min: 2525.11 max: 2597.64 mean: 2561.22 stdev: 26.8321 late: 0 of 250 (0%) Num ZMQ send errors: 0
2025-10-21Z11:40:46       Buffering time statistics [milliseconds]: min: 2525.05 max: 2597.59 mean: 2561.6 stdev: 26.8315 late: 0 of 250 (0%) Num ZMQ send errors: 0

The line 'EDI disabled worries me.

MD

[mike....@gmail.com]

I've just deleted the -d and -s entries and set Z tcp://192.168.1.94:9000 and bingo green blobs on both connected and broadcasting.

MD

[mike....@gmail.com]

So the unwritten rules of the syntax of ODR-ZMQ2EDI are use the -d switch for a UDP output and the -Z switch for an EDI TCP output. Is that right?

MD

[Nick Piggott]

Hello,

The primary function of zmq2edi is to generate an EDI/UDP output - the -d switch specifies the destination IP address for the UDP packets and the -p switch the port. You can use these several times on the output to specify multiple destinations to be fed in parallel. If they're omitted, no EDI/UDP is outputted.

zmq2edi also provides for a ZMQ interface. In that scenario, it opens a single socket to listen for connections from a ZMQ client. easyDab only supports ZMQ, and practically only supports ZMQ as a client device. So you're using zmq2edi in its alternative mode as a way of providing additional buffering beyond that which the easyDab can do with its own (limited) memory.

Nick

To unsubscribe from this group and stop receiving emails from it, send an email to crc-mmbtools...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/crc-mmbtools/f600878a-dad5-49ac-bdb7-5394af7fbe4dn%40googlegroups.com.