开云体育

Yes Dave, that is exactly how I have always wired the feedback for points and when I get to wiring for JMRI will continue to do so. Tony https://ozfreemo.com

In our club, QSI was notorious for this. Even with DC off, still happened. Someone puts a steam Lok on the layout (Beep, Beep, shorts) and any QSI decoder is scrambled. Sometimes a reset did not bring

Jerry, It is not possible to set Unknown directly, but you can indirectly using a script action: IX:AUTO:0001C1 C1 [x] R1 IF Sensor "DOIT" state is "Sensor Active" THEN On Change To True, Execute

A month ago I posted and got no response. ?Do any of the Logix experts or developers out there have any thoughts on my post: My first try at LOGIX...I'm trying to set up a LOGIX to check a sensor for

Mike, - When JMRI opens, it looks for a "roster.xml" file in the "Roster Location" (refer Help->Locations). This purportedly contains an index of all ".xml" files in the "roster" folder at "Roster

For those that want to follow along: https://github.com/JMRI/JMRI/issues/7259 -- Peter Ulvestad JMRI Users Group Moderator - http://www.jmri.org ( http://www.jmri.org ) Tam Valley Group Moderator -

Bob, Since I don't know the circumstances prior to the loco not responding to the 4-digit address, I will make some observations based on personal experiences with Digitrax DCC systems . This is not

While you could rewire the usual position indicating switches in series to AND them, I'd recommend keeping all turnout wiring the same, and using logic, either hardware or better yet, software, to

OK, this is strange.? I know stuff happens.? I put my engine(Walthers Proto GP-60) on an isolated programming track and started DP.? I went in and read CV 29 and lo and behold it was 2.. It was

Hi Peter/Bob Many thanks. I have produced a worked example panel showing the problem and created an issue on github and uploaded the panel with it. Nigel

Most of these responses are doing nothing to help the OPs problem. Please try and stick to the topic. Nigel, As Bob J. has suggested, create an issue in github and upload your panel for a developer to

I understood that error condition was defined by the poster as the "unknown" situation, not the the "inconsistent" situation. If the turnout doesn't have a known safe settling time, presumably defined

This is not prototypical, but it works and is fairly simple. When I have a configuration that requires multiple turnouts I arrange the feedback so that it is wired through all of the switch contacts.

Nigel, Try thinking through the problem as a switch position problem and not JMRI. You have two switches, one at each end of the throw bar fitted to both turnouts. You will only have a condition where

Since something like that Really Should Work, if you open a new Issue at GitHub ( https://github.com/JMRI/JMRI/issues/new ) and attach your panel file (might have to add .txt to the name) and

Hi Dave From what I think you are saying is that the feature of supported turnout (eg crossover) with full feedback does not actually work in JMRI. Logically it could work if the code was sufficiently

Nigel, From what you have said there could be a conflict. If both turnouts are powered as one and work as one then you only need an input from one turnout for the actual crossover route because it is

If you always knew that the points are going to get to their commanded end point in a certain time, you wouldn’t need feedback hardware. People install feedback hardware (in part) to catch the case

If JMRI needs to know that a turnout is an inconsistent (traversing) state, but doesn't also know the intended result, or the safe settling time to get there, there is something wrong with that logic.

Hi Dave When you put a crossover on the layout you have the option of using two individual turnouts. The first turnout system name goes in the first box. If you tick the "supporting" turnout box the