meteohub.de

Sandaysoft are working on a new version of Cumulus - called Cumulus MX.

I am trialing this software and have run into issues where Cumulus MX does not seem to communicate properly with Meteobridge.
Communicated with Steve the software developer on the Cumulus forums.

Basically all I see when I connect to the IP address of my Meteobridge and use port 22222 are zeros in the display.

Communication diagnostics (output from the diags file in Cumulus) shows:

It expects to get an 'ACK' (0x06) back when its sent the date and time, but it's getting an assortment of other characters:

2015-01-22 19:50:32.958 Received response to DMPAFT, sending date and time
2015-01-22 19:50:32.959 36-1E-9E-07-18-11
2015-01-22 19:50:33.459 Received 0x0A
2015-01-22 19:50:33.459 Received 0x0D
2015-01-22 19:50:33.459 Received 0x29
2015-01-22 19:50:33.459 Received 0x3A
2015-01-22 19:50:33.459 Received 0x0A
2015-01-22 19:50:33.459 Received 0x0D
2015-01-22 19:50:33.459 Received 0x0A
2015-01-22 19:50:33.459 Received 0x0D
2015-01-22 19:50:33.459 No ACK

Any suggestions or thoughts?

Guy

When the PC program takes over, the console might still be in an mode triggered by Meteobridge to report some type of data (LOOP packets etc.). So Cumulus cannot not expect that it will find an empty receive queue where only data it has requested will be there. After a few more couple of seconds, no more Meteobridge requested data will come in, as Meteobridge stops requesting from the console when the PC program has made a connection.

So consuming data not requested before starting its own protocol and doing some initial looping on false tries might be a good idea for Cumulus and this is not just something that can happen in context of Meteobridge. When another PC program (or previous call of Cumulus) has requested 100 LOOP packets and terminates then. The PC program started next also has to handle this situation.

Will Cumulus MX make use of the LOOP2 packets as well or is it still stuck to the antique LOOP protocol only (makes a difference in pressure readings etc)?

Steve (Cumukus MX author) has built in a delay (configurable, default 200ms) before connecting to the console via port 22222. Actually 5000ms seems to work well but the system does not seem to update after that.

Guy