Page 1 of 1

Bug report (solved)

Posted: Fri 14 Jan 2022 11:04 pm
by mimo57
Hello,
Today I changed my local network.
I configured the connection with the Davis station in TCP/IP like this: 192.168.1.101
Problem, by entering this IP address format, the VP2TCPPort=22222 parameter changes to VP2TCPPort=0 in cumulus.ini :bash:
This prohibits the connection during a next restart.
According to my tests, this happens when there are 3 digits at the end of the IP address.
Please consider this issue.
Cumulus MX 3.14.1 b3160

Re: Bug report

Posted: Sat 15 Jan 2022 10:41 am
by mcrossley
I cannot reproduce this. Using the IP address you posted it saves OK and the Port is left at 22222?

Re: Bug report

Posted: Sat 15 Jan 2022 10:43 am
by mcrossley
Before you save, check under your Davis Advanced Options - is the port there set to 22222?

Re: Bug report

Posted: Sat 15 Jan 2022 4:06 pm
by mimo57
Hello,

when I use an IP address with two digits at the end, (example: 192.168.1.10) no problem, when saving the settings, the connection port does not change in cumulus.ini and the IP address is fine saved.
When I use an IP address with three digits at the end (example: 192.168.1.110) the connection port (22222) changes to 0 when saving in cumulus.ini.
I also just noticed that I can't find where the port number is set. In Davis advanced options there is nothing (see screenshot).

Re: Bug report

Posted: Sat 15 Jan 2022 4:20 pm
by mcrossley
And there is your problem. Have you upgraded CMX since last altering the settings?

It likes like you may not have copied the entire contents of the new zip file to your installation when upgrading?

If you have try forcing a refresh of the page in your browser with Ctrl-F5.

Re: Bug report

Posted: Sat 15 Jan 2022 11:11 pm
by mimo57
Hello,
I found the problem.
I have an extension in Firefox that prevents the display of the parameters in question. No doubt others too. :bash:
This extension is: http://jgoudey.free.fr/highlightall/ :evil:
Why I don't know, but it solves the bug, which is not due to cumulus.
Thanks for putting me on the track. :P

Re: Bug report (solved)

Posted: Sun 16 Jan 2022 2:17 pm
by mcrossley
Well, that's a new one! Glad it is sorted though.