Page 2 of 2
Re: <#rmonth> no returning correct value
Posted: Wed 18 Mar 2020 12:50 pm
by TheBridge
Thanks Mark,
I have found my MX keeps 'stalling' in on-line updates (it goes ok for a bit then stops). Debug log says '*** Data input appears to have stopped' over and over again'. The system (Davis VP) runs fine under Cumulus 1. The Davis Datalogger is connected to host via serial at 9600 baud. Does MX have a serial speed setting I can check (didn't find any in the webpage station setup section). Latest MX log attached.
20200317-083957.txt
Re: <#rmonth> no returning correct value
Posted: Wed 18 Mar 2020 1:32 pm
by mcrossley
I'm surprised it works at all if the comm port speeds don't match!
Why have you changed it from the default 19,200 baud?
You can add an entry to the Cumulus.ini file in the [station] section to override the default...
Re: <#rmonth> no returning correct value
Posted: Wed 18 Mar 2020 3:30 pm
by TheBridge
Mark,
Baud rates now all set 19200. Restarted MX. It's not updating website. Some obscure setting i have in my MX? (Culumus I runs fine)
I still see a lot of '
WaitForAck TimeOut' occurrences in the most recent debug log.
20200318-080840.txt
Re: <#rmonth> no returning correct value
Posted: Wed 18 Mar 2020 3:58 pm
by mcrossley
It sort of looks like there is a loopback on the serial connection. When it should be just getting a 0x06 character back for a ACK command, it is getting 0xA,0xD = CRLF
Re: <#rmonth> no returning correct value
Posted: Wed 18 Mar 2020 4:50 pm
by water01
Has he set the serial port up correctly in MX?
Re: <#rmonth> no returning correct value
Posted: Wed 18 Mar 2020 5:04 pm
by mcrossley
water01 wrote: ↑Wed 18 Mar 2020 4:50 pm
Has he set the serial port up correctly in MX?
Not much to set really, it Windows, so COM4, 19200, is there more?
Re: <#rmonth> no returning correct value
Posted: Wed 18 Mar 2020 5:07 pm
by TheBridge
Settings for MX station connection are pretty basic. Station settings in MX same as Cumulus 1 which ran very well. But Mark is seeing 0xA,0xD = CRLF instead of 0x06 back for an ACK command. Don't know how to adjust that within MX or why it needs adjustment given it is the same hardware is working well (for years) under Cumulus 1. As is said 'it is getting curiouser and curiouser'
MX Station setting screen shot.png
Re: <#rmonth> no returning correct value
Posted: Wed 18 Mar 2020 5:47 pm
by mcrossley
Have you set the VP2 console to 19,200 as well?
Re: <#rmonth> no returning correct value
Posted: Fri 20 Mar 2020 8:28 pm
by TheBridge
Hi Mark, I have Cumulus 1 running like a watch. But when I make a separate install for using the Cumulus 1 'Cumulus.ini' file and making necessary directory name changes, still seeing 0xA,0xD = CRLF instead of 0x06 (ACK) root in debug log. Davis says there is no way to change (or have caused it to change) the Envoy datalogger device it yet fine under Cumulus 1. I guess this will be a mystery left unsolved.