Hi
I was viewing a layout editor panel via the webserver and noticed that the crossover was showing the incorrect occupation status. Only a change to Block 1 of the crossover is recognised, and this shows all 4 areas of the crossover as occupied. Changes to Blocks 2 - 4 make no difference on the web panel. This is the case whether it is closed or thrown.
I was initially using v4.16 on a raspberry Pi. However, I've since recreated the problem on 4.16 and 4.17.3 running on Ubuntu 19.04, java 11.0.4.
Showing the problem is very simple:
- Create a layout editor panel
- Put a crossover on the panel (using created turnout)
- With the Tables
- Create 4 Blocks
- Create 4 Sensors
- Link sensors 1-4 to blocks 1-4
- Create 1 turnout
- Edit the crossover and assign the blocks and turnout to it
- Start webserver and view panel
- Alter state of sensor 1 using Sensor Table
- Notice the native panel shows only top left quadrant as occupied
- Notice that the web panel shows all 4 quadrants as occupied
- Changing sensors 2-3 gives correct occupation on native panel but does not change the web panel.
- Notice that web 'preview' panel (on the web home page) always shows the correct occupation (page refresh needed between each change)
I've created a simple panel using the above steps and uploaded to
/g/jmriusers/files/ProblemsBeingWorkedOn/Andy%20Brown%20-%20161045/CrossoverBlockOccupancyIssue.xml In my current application I have blocks 1 & 2 with one sensor and 3 & 4 with another. Hence, when in the crossed state the problem is not so obvious, but when closed it's really obvious.
The same issue is visible when the blocks are set to reserved (white). It is also the same with a double crossover. Slips only have one block so the problem does not occur.
Regards
Andy
