开云体育

Dick, I get what your saying and that does make sense. However, I still have the initial problem I started with and only a couple cables had four lights. As you mentioned LocoN

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

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.

Have a few routers and other stuff laying about so might give that some consideration. Thanks for replies. Regards, CFJ

One third-party wireless LocoNet connection device is a LocoNet-Bluetooth "smartphone interface" device from Mollehem. An english web page for this device is at

CF: There's a lot of other information going across the LocoNet interface using the LocoBuffer than a WiFi throttle uses. The LNWI is designed solely for WiFi throttles, though very flexible working

Yes.

CFJ, You want to substitute a WiFi connection between your computer and LocoNet instead of a LocoBuffer connection? Remember, the LNWI is primarily intended to provide a mechanism for phones to

Currently I have JMRI (on laptop with a loconet cable) working with loconet via a locobuffer. Is it possible to have JMRI (on laptop with a wifi connection) working with loconet by substituting a LNWI

Thanks to everybody for all the help on this. Lot’s of interesting tests. It’s clear that programming isn’t always reliable, but there didn’t seem to be a case where Paged mode worked and

Ken, No, I have not tried 4.12 as the documentation recommends.? Should have read that instruction more closely. I will set a restore point on my PC and then give 4.12 a shot tomorrow. There was some

I've not used Layout Editor for a while. Just before I stopped working with it, I had an odd problem. The scroll bars disappeared. I set the option to have both vertical and horizontal scroll bars,

OK, I've created https://github.com/JMRI/JMRI/issues/7335 ( https://github.com/JMRI/JMRI/issues/7335 ) to proceed with approach #3 for layoutturnout. If someone can identify similar warnings for other

Gary H. Thanks for the update I have run into problems trying to do this same thing. I've figured work arounds still not quite what I'm wanting it to do. I just watch to see if someone comes up with a

Bill (or anyone), could you say a bit more about how you handle this?? I am a modestly experienced CATS and TrainStat user, but I'm just starting to use Operations.? I'm generally curious about how

Ok, there is one little twist I didn't appreciate when I wrote the previous post: if the spurs and interchange siding are in the same Location, then Ops will not request moves between the two for the

Jim, This document is also helpful with speed matching, particularly if locos have a mixture of brands of decoder, as different manufactures have minor differences in the way settings interact:

The general approach for XML persistence of NamedBeanHandles is to store the name the user provided originally: If the user selected which Bean to use via a user name, persist that, otherwise persist

I’d use #3. That maintains the panels as they are and allows any web/json client to get the data it needs to “just work”. Although every client I am currently aware of uses the panel.js for

Dan Thank you for sharing the Speed Matching link Very useful guide John Pearson Sent: 18 August 2019 20:16 To: [email protected] Subject: Re: [jmriusers] Speed Matching Jim, The document at this