Nelson,
That was a good explanation.
To eliminate the network and Rpi nodes, what happens if you connect to the web server using a Windows browser at localhost:12080? ?I assume you have not change port numbers.
Are there any unexpected messages in the JMRI system console?
You might also try doing a clean JMRI install. ?Remove JMRI using the Windows control panel, delete any residual JMRI install directories in C:\Program Files (x86) or C:\Program Files. ?This assumes that any custom components (icons, etc.) are in the user files location and not in the JMRI install location. ?
Dave Sand
----- Original message -----
From: Nelson <nelson.allison@...>
Subject: Re: [jmriusers] Test version 4.17.7 of JMRI/DecoderPro is available for download
Date: Saturday, December 14, 2019 5:25 PM
Dave:
The system that our JMRI resides on is a Windows system, the JMRI is I believe? installed over the previous release.
Let me explain how our system works.
We have a windows box which runs JMRI and talks by Chubbnet to a number of CpNodes.
It is also connected to a ethernet hub and wifi router.
The windows box runs withrottle and JMRI webserver with frames disabled.
We have created a number of panels in panel pro on the windows box and they are shared on the web server.
On the wifi network are a number of raspberry pi boxes with either a touch screen or a regular monitor and a mouse. The Raspberry Pies boot up and launch the web browser in kiosk mode and connect to a panel that is predetermined as part of the launching script. This allows an operator to control the area where they are running.
We have a master CTC board but at this time don't use it due to a lack of a communications system.?
Our operators where able to connect by pad or phone to the panels (we discourage this, preferring them to use the glass panels instead).
This works with 4.17.6
When I upgraded to 4.17.7 the panels on the web server stopped working and would only display question marks for sensors (unknown) and X for lights (unknown). Note that this only occurred on the web based panels, the panels worked fine on the windows box running panel pro.
Nelson
This has nothing to do with browser caches the reason I know this is that the cache is cleared everytime the pi restarts and when I reinstalled 4.17.6 the panels all came back.
