开云体育

Larry, Focus on getting the turnouts working right from the turnout table first. Each turnout is a pair of events, thrown/closed. The feedback is normally MONITORING. Once that is correct, then the

Larry, Turnouts should never use 'toggle'. They should always use two events, one for normal and the other for reverse. The only time you would use 'Toggle' (alt action) is if you are controlling

No. JMRI routes set JMRI Turnouts to a specific direction. There’s no need to create a workaround to do that, that’s what they should already be doing. If you’re not getting consistent operation

I suggest you open an issue on Github https://github.com/JMRI/JMRI/issues you need to create an account to do so. It would also be helpful to provide an updated definition if possible. -- Peter

A few years ago I reported an error in the light function settings in the TCS function decoders, today I found the same error is still in place so am reporting it once again. I don't remember if at

So I’ve figured out that if I want to build a route that I want to *always* go a certain way, that I almost need to configure a turnout as two separate turnouts. One for each route that I want the

OK… so that may have resolved the startup issue. But when I build a route and click on the route all the turnouts just change to their opposite state. I was thinking this has something to do with

Steve, I have done some searching and cannot find the test files that I was using to verify what follows.? So, here are a couple of answers, starting with the one I am most confident about. Since the

There aren't many sounds on a trolley, that couldn't just as easily be played on speakers hidden at trolley stops. The running motor noise might be able to be simulated by amplifying and playing the

My node is 02.01.57.00.00.DD I just updated it. I will see what happens. Larry

I just described how I used LCC to control a staging yard over on layoutcommandcontrol here on groups.io, but it's only 3 tracks and 2 turnouts and doesn't use JMRI, so I'm not sure it would be any

Larry, I'm not sure why Turnouts shouldn't be called Turnouts and entered in the JMRI Turnout table. There is a button in the CDI to do just this. Your friend is correct that there is no actual

I actually think it’s more likely that he’s thinking about the grand scheme of things as it were. The Person I’m usually talking to installed and programmed layout command control for the entire

Perhaps you misunderstood what your friend said, or you got some not-so-good advice. The Tortoises on your layout should be controlled by Turnouts in JMRI, i.e. via the Turnout table. Yes, there are

The thing that is more concerning to me is - the system won’t set a turnout consistently with it’s status. IOW, it could say “Active” and be Thrown or Closed. How do your program a route if

Hi Larry. on Start-up, JMRI doesn't remember the status of anything.There are a couple of scripts which set switches and sensors but it's all one way or the other. I don't know if anybody has written

Ken: Perhaps stating the obvious but having selected a decoder that seems like it might be close and thus "checked the box", it is a good idea to read all the CV values and save them as the default.

Hi all, I’m working on implementing LCC on some modules I have, where I have an auto delivery facility. I have a Tower LCC, and an SMD8 connected to Tortoises. I was told by a friend who knows a lot

That’s not hard. It’s already in the JMRI block tracking. It follows a single mainline train well. But it’s not always sufficient for more complicated things without lots of detected blocks. For

Thank you all. I forgot to mention, as I did in my last post, how absolutely? great I think the tutorials are. And I apologize that, as another poster from Quebec (who for some reason no longer