Iain,

The Logix actions all occur one after another with no delays. When delay is specified, the action is assigned a timer which will eventually execute the action.

You need to stagger the delays: T1 - 1sec, T2 - 2 secs, T3 - 3 secs, etc. This results in them going 1 second apart.

Dave Sand

Hello,

This email message is a notification to let you know that a file has been uploaded to the Files area of the [email protected] group.

File: Pennsy_West_Yard.xml

Uploaded By: Scott Walton

Description:
Panels (two) with missing sensors and logix

You can access this file at the URL:
/g/jmriusers/files/ProblemsBeingWorkedOn/Scott_Walton_Panels/Pennsy_West_Yard.xml

Cheers,
The Groups.io Team

Thanks Steve,

Now is there anyone out there who can tell me how to increase the throw delay on a turnout using any part of the user interface.

Routes allows me to set a delay of a maximum of 1.25 secs, and I have that working -- but I need more.

I have tried Logix, but (see above?#153323) set delayed does not do what you (I?) would expect - it add all the delays together.

Iain

Hi Iain,?

I code Java, php, Python + xml with notepad++ , it's whatever you're most comfortable with :-)

As long as you take a backup of the layout xml before having a play you should be fine, you'll need to restart JMRI for any changes to have effect,
I'd strongly recommend 1 change at a time!

Not sure about editing turnout settings in the xml, I'd say the User Interface will steer towards getting towards what you want than editing the xml,
others may be able to advise more on this.

As I'm using the MERG CBUS kits I can sense a point position ( via micro-switch ) for about 60p each ;-)
I think you'd be surprised how many people have block? + point detection, it's not particularly difficult to setup ( especially if using Servo's ).

I'm not advocating in any way that you rip up your existing layout though, there should be an easy-ish way to do what you want,

Steve.

开云体育

Steve

Roland:

Matt will need to sort this out but... I have two of the MCII throttles one the first one I had only "one shots" the horn button though the screen F2 holds until you stop touching it. The other throttle has the button work like the touch screen.

I do not see any preference to change this so I have to assume some change in the hardware since both throttles are running the same firmware, OS and WiThrottle...

Stay tuned sports fans...

Jim Albanowski

Hi Peter,

I've done this via Memory Variables so the count will be maintained between sessions.

I've got 6 memory variables for this,
IMSESSIONCLOCKWISE
IMSESSIONBOTH
IMSESSIONANTICLOCKWISE
IMALLTIMECLOCKWISE
IMALLTIMEANTICLOCKWISE
IMALLTIMEBOTH


For my test loop, when a train enters a block in clockwise direction then it calls a script which has the following Jython script :

#session clockwise

?

sessionclock=memories.provideMemory("IMSESSIONCLOCKWISE")

sessionclockvalue=int(sessionclock.getValue())+1

sessionclock.setValue(sessionclockvalue)

?

#session both

sessionclock=memories.provideMemory("IMSESSIONBOTH")

sessionclockvalue=int(sessionclock.getValue())+1

sessionclock.setValue(sessionclockvalue)

?

?

#alltime clockwise

?

alltimeclock=memories.provideMemory("IMALLTIMECLOCKWISE")

alltimeclockvalue=int(alltimeclock.getValue())+1

alltimeclock.setValue(alltimeclockvalue)

?

#alltime both

?

alltimeclock=memories.provideMemory("IMALLTIMEBOTH")

alltimeclockvalue=int(alltimeclock.getValue())+1

alltimeclock.setValue(alltimeclockvalue)

Hope this helps,
Steve.

Greetings all.?Here is a picture of my first go at a layout for my dining room table top. It's not immediately clear from the picture but the Upper East/West Loop is elevated above the yard and main.

I'm wondering if the blocks make sense? I'd like to get to a point I can automate the simultaneous running of 3 trains using block detection for collision avoidance using the NCE BD20s (plus PowerCab, NCE USB/AIU.) JMRI runs on an RPI3. I do have an Arduino loaded with DCC++ and am waiting on a motorshield but so far I appreciate the low barrier to entry with the NCE stuff if it will work for me.

Couple of questions:

1) Do I need to add physical signals right off the bat to achieve this or is that more of an element for realism I can add down the line??

2) Among many things I don't quite grasp yet is once block occupancy is established, how does JMRI know which train to hold to avoid a collision? Suppose train 2814 is coming clockwise along Westerly Pass. Train 3201 is approaching counterclockwise on North Main. And lets say traffic on the Main always gets the right of way. How does JMRI establish that it's 2814 it needs to address and hold till North Main is clear? Do I need additional inputs to achieve this like Transponding or RFID? Or can you just kill track power to a block with the effect of holding whatever train is on it? (In that case I'd have to modify my blocks so turnouts were isolated from power cuts.)

I started out on this a couple weeks ago for my toddler who's into trains but I've been having a ton of fun with this. Thanks in advance!

jb

Hello everyone

Has anyone produced a script for counting laps?

I would be interested if there was such a script which is triggered by a Sensor and then displaying the count on the screen

I assume a resent option would be required

Cheers

Peter

Steve,

Sorry if my childish '12" to the foot' upset you - it's the local way of saying "as per the real worlds" or "to prototype".

I don't know where you are based, but here in the north of the UK I know of no-one with large layout and turnout setting feedback - it's an expensive enough hobby and we prefer to spend the money on other types of hardware.

Anyway, enough of that irrelevance. I haven't tried your:

"In your panel xml file look out for? ?
<signalmastlogics class="jmri.managers.configurexml.DefaultSignalMastLogicManagerXml">

Mike,

Thanks very much again for your kind support.? I got that message for myself just before your's came in!? Sadly it's no use sending MORE commands - my problem is too many commands too close to each other!? The delays in switching within the stall motors that I use, and their instant power consumption, simply causes garble if you send too much at once.

I have reverted to using routes and so far with the additional amount set to its maximum of 1,000 (i.e. 1250 ms delay in total on each turnout command) the results on the layout are probably OK, but as I move on to more complex things I will probably need longer delay. At the moment I have 6 firing "at once" - my worst case will be 10 - so I'll need to break that up somehow.

Thanks again.? Without your encouragement I would have walked away (again!).

Iain

I found that each turnout has to have a different time, if the same they all repeat at the same time. Making them different spreads out the commands going to the decoder. Mine use a 3 bit BCD code to set an aspect so often all three bits would change at the same time and at least 50% of the time I would get the incorrect aspect or two colours at the same time. Even worse each decoder has 4 of these codes going to it. I only needed a 50ms gap between commands to get the decoder to respond reliably, but it meant having 12 different delay times.

You did put more than 1 repeat in the number of tries? otherwise only one command is going out at the same time as all the others. All this method does is to send all commands at the same time first and then repeat them for the set number of times with the set interval, so it is the repeats that will have gaps between transmission.

Mike

The discussion turned to if the extension method used in the roster would
work to extend the data in the Operations data for cars (and locos?).

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org

David,
Enzo is correct. I don't need to expand the LOCO roster. I need to expand the CARS roster. Is there a similar fix for the CARS roster?
Paul D

Roster Media pane.....
David, this is working for "Decoder" roster only, so not for the "majority" of CARS.
Enzo

Mike,

Thank you so much for being patient with me.? I have I think worked through what you are saying.? My turnout table has an edit button at the right.? If I press that a new box opens with a set of tabs - basic,feedback, lock ....

Taking the feedback tab I have a list of boxes: my feedback mode is direct (I have no feedback) if I go to turnout automation and set that to RAW I can set 5000 in the interval box (that seems to be the max) and "5 sec" in the name.

This does nothing for me sadly - and I think I have followed your suggestion?

Iain

I first tried doing delays in Logix but it means a lot of changing output statements and didn't always works. Putting the delay in the turnout table has solve almost all the problems to the extent that in a day operation we get ?a few missed aspect instead of 50% before.

As I said you can't change the delay in the Edit Auto unless the selection to the left does not show OFF, then you can change the times, but you have to save that time as a name or it will not take effect. Once saved the name can be selected for other turnouts. I found 50ms repeat delay was enough time delay for the decoders giving 19 different times, the decoders only needed 16 and I repeated them for each decoder. I realisied you may not be seeing the settings as I selected them a different way. They can also be selected by clicking EDIT in the turnout table and then FEEDBACK, select Turnout Automation to anything but Off, enter the Times and Interval and give it a Feedback name. This is the name you can then select in Turnout Automation.

I don't use routes for our modules, it is all done in Logix along with masts for signals, each interlocking is contained in a single logix (lots of conditionals!) to make it easy to add new modules.

Mike

I wrote a route just with the three points in it.? I tried to type into the "additional delay" box - but it won't accept it.? Keeping my finger on the up button I managed to get it to 750 - I believe (?) a total of 1 sec.? That does work - though if you want a delay of 2 seconds forget it!? THe upwards button stops at 1000.?

Progress (?) so far.? As I said - I don't have any feedback - beyond my price range.

I cannot use Routes since I need to set signal MAST aspects (not heads - head settings don't work for SE8C heads and BR2003).? I could? perhaps rewrite all my logix to use routes just for the turnouts.? Then (if my reading is right!) I can set a delay in each route for all turnouts in that route. I haven't tried that because it's labour intensive and destroys what I have done so far - I thought I would try logix first

Logix is odd.? As an example, I have one route with 3 turnouts.? Since I understood (!) that the delay is *before* throwing, I have no delay on the first and I put delays on the second and third turnout actions and a further delay on the subsequent sensor set.? 10 secs delay in each instance. Hence (I tought!) throw 1, delay 10 secs, throw 2, delay 10 secs, throw 3 delay 10 secs.? What I get is throw 1, wait total 30 delay time and then everything gets done at once!? Since that is what I wanted to avoid I am not getting anywhere.

What am I doing wrong?

开云体育

WiThrottle, points, blocks on onexAIU all working!?

Excellent.