|
I'm using layout editor and two-sensor feedback. When I throw a switch using the web server panel, it never changes position when the feedback event comes in. It will change if I refresh the browser. Is there a setting to allow this to happen? The Browser (client) would have to request the update from the WebServer?
Also using Entry Exit routing, the "cancel" and "stack" pop-ups don't appear on the web server
Thanks,
Dave
|
Hi Dave,
What version (exactly) of JMRI are you running? Turnout position on web panel should reflect the same state as on the JMRI panel.
Also, what browser are you using? If it does not support WebSocket, you won't get updates. Test this at:?
I've not heard of those popups. It's very likely they are not coded into the client-side web panel. If you'll post your panel and advise how to duplicate the popups on the JMRI panel, I'll take a look.
--SteveT
|
In addition to Steve's quesions, which URL are you using? (there's 2, but I dodn't remember what the /<FOO>/ is that's different between them. What browser, browser version, and OS is the browser running on?? Some browsers (mostly on phones/tablets) don't completly support websockets, which JMRI uses on one of the URLS.
Hi Dave,
What version (exactly) of JMRI are you running? Turnout position on web panel should reflect the same state as on the JMRI panel.
Also, what browser are you using? If it does not support WebSocket, you won't get updates. Test this at:?
I've not heard of those popups. It's very likely they are not coded into the client-side web panel. If you'll post your panel and advise how to duplicate the popups on the JMRI panel, I'll take a look.
--SteveT
|
I'm using Chrome, the echo link shows websocket working.
"190729 Jay Console" has been posted to the files section.?
You can make the "Stack Route" popup activate by selecting an Entry Exit route, say 15E to 4E, then select 14E to 4E - the dialogue box gives you the option to stack the route or not.
|
nnn.nnn.nnn.nnn:12080
Happens with Chrome on both iOS and Win10.
|
Hi Dave, I don't see your files (yet??). Can you post a link to them?
I think Spuds was asking about the full path, the part after the 12080. It'll be either /panel or /frame, those are very different servers.
|
|
|
Thanks, I tried to open it, but not sure what connection your "S" refers to. Can you export your config profile and post that as well?
|
|
|
Thanks Dave.
I was able to change your config to use four simulator connections and get your panel to load. I still get some errors creating sensors, but since your question is regarding turnouts, I hope I'm close enough.
What turnout(s) (specifically) are you seeing the problem with? I tried a few on your layouteditor panel (e.g NY-87), and they worked as expected, the JMRI panel and web panel looked the same after changing state from either side or from the turnout table. I tried this by manually changing the feedback sensors and by clicking after changing the turnouts to "Monitoring".
As for the NX routing, I don't know what this means: "selecting an Entry Exit route" so I couldn't duplicate it on your JMRI panel. But my guess is we do not have the underlying communication for the web panel to perform this prompt. So that may be a showstopper for you.
|
Steve, This album shows the dialog windows that can occur for NX actions. /g/jmriusers/album?id=94433NX Options.png dialog occurs when re-selecting an existing route. This makes it possible to cancel a route, simulate the train movement or stack the route for use when the current route is finished. The NX Stage.png dialog occurs when a conflicting route has been selected. If yes is selected it will be added to the stack for later execution. The NX Stack List shows the currently stacked routes. As the conflict is resolved, they will be activated and removed from the list. It is also possible to cancel a stacked route request. Dave Sand
On Aug 20, 2019, at 3:03 PM, Steve Todd <mstevetodd@...> wrote:
Thanks Dave.
I was able to change your config to use four simulator connections and get your panel to load. I still get some errors creating sensors, but since your question is regarding turnouts, I hope I'm close enough.
What turnout(s) (specifically) are you seeing the problem with? I tried a few on your layouteditor panel (e.g NY-87), and they worked as expected, the JMRI panel and web panel looked the same after changing state from either side or from the turnout table. I tried this by manually changing the feedback sensors and by clicking after changing the turnouts to "Monitoring".
As for the NX routing, I don't know what this means: "selecting an Entry Exit route" so I couldn't duplicate it on your JMRI panel. But my guess is we do not have the underlying communication for the web panel to perform this prompt. So that may be a showstopper for you.
|
Unless I'm missing something, I don't think MONITORING does what I want. When I changed NY-87 to monitoring the turnout assumes the requested position on the panel before it operates. I only want the turnout to show the position that the sensors report it to actually *be* in so I think I need to use TWOSENSOR.
Reading the help file on Monitoring it seems related to LocoNet, and there does not seem to be any apparent support for LCC - you'd have to associate the indication events with the turnout command and the sensor event fields become shaded in the edit turnout dialog when you select MONITORING.
Dave
|
Dave,
No, I wasn't suggesting you change your panel at all. I do not have your turnout sensor hardware, so I can't test exactly as you do.
I did test by manually changing the sensors and both sides changed in response has expected.
I switched the turnout to monitoring so that I could click on each of the panels. That also worked as expected, with both panels changing appearance.
It would be helpful if you could post and link a screenshot showing the panel and the web panel and highlight the difference.
|
Here are links to the videos you requested. For simplicity I used the bounce back 127.0.0.1
This shows the lack of proper indication for switches on the web server panel
This shows that the dialogue boxes don't pop up in the browser - although they do pop up on the local machine
|
Hi Dave B,
Note that there were some tweaks to improve Layout Editor supporting Turnouts, especially those with 2 sensor feedback in JMRI v 4.17.3.
See ?and?
Steve Y.
|
Steve,
Is there a safe, easy way to update JMRI on the RPi running your image without connecting it to the internet? My Pi isn't connected to the internet, it's being used as a standalone network server for the railroad. Can I download 4.17.3 to a flash drive, plug that into the Pi, and install it from there?
Don Weigt Connecticut, USA
|
Thanks, Steve.
Looks like it's time to update!
|
Don, you may have posted into a previously running thread.... but what you propose sounds like a reasonable approach to update an air-gapped Rpi.
|
On Wed, Aug 28, 2019 at 05:24 AM, Dave Barraza wrote:
Here are links to the videos you requested.
Dave,? Thanks for the videos. I tried the same turnouts you were toggling and the web panel works for me if I enable the proper sensors. Hopefully the upgrade will help, I don't recall you telling us what version of JMRI you were on. Regarding the NX prompts, the current web code doesn't come close to supporting something like that. Sorry. --SteveT
|
Please note that dialogs triggered on the JMRI native panel (regardless of what triggered them) block the panel from updating, so the web panel (from either the /panel or /frame URLs)
- does not get any updates until the dialog is dealt with
- has no way (without a significant rewrite of the native panel) to be aware of the need to display a dialog or aware of the need to notify an operator to use the native panel
- may cause that dialog to be displayed on a JMRI instance where something else is in the front (another panel perhaps)?
These are limitations of bolting a web server onto JMRI and the primary panel developers not developing with the web server in mind (I¡¯ve had one who I won¡¯t call out tell me that the only correct way to address this complexity is to remove the web server).
|
Dave Barraza