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