On Nov 17, 2018, at 11:21 AM, paul@... wrote:

Dave,

Thanks. Will the structural changes impact any timetable data I create with the 4.13.4 version of the tool?

Regards

Paul

On Nov 17, 2018, at 10:14 AM, paul@... wrote:

I've just started playing with this and it looks potentially really useful. According to the help page there's a sample script TimeTable.py to show how to open the manager and navigate the structure but I can't find it at JMRI/jython or by searching. Has it not made it into the release?

Thanks

Paul

Hi Dave,

What you need is? YAAT!
The following is clipped from a document I started.
It may be sufficient to wet your appetite!
Regards
BrianW

YAAT in control of your JMRI layout

What is YAAT?

YAAT is an acronym for Yet Another Auto Train. It is a piece of software written by Dave Sand and written in? Jython . But that is irrelevant as you can use it with no Jython knowledge at all.

?It brings writing scripts for ?layout automation to all!

I have knowledge of programming especially in machine code but I find the Jython language very unfriendly and very unforgiving .

In the past I used the BASIC programming language for my user interfaces. ?

BASIC is another acronym Beginners All-purpose Symbolic Instruction Code developed in 1964 at Dartmouth College USA.

Now with YAAT we have our own BASIC language for JMRI.

Lets leap in with a simple script:-

Assume we have a working JMRI layout, a piece of straight track, a sensor at each end named LEFT and RIGHT and ?loco with long address 7331.

??????????????????????????????? Assign long address 7331

??????????????????????????????? Set direction to forward

??????????????????????????????? Set speed to .10

??????????????????????????????? Wait for sensor RIGHT to become active

??????????????????????????????? Set speed to 0

??????????????????????????????? Wait for 5 seconds

??????????????????????????????? Set direction to reverse

??????????????????????????????? Set speed to .10

??????????????????????????????? Wait for sensor LEFT to become active

??????????????????????????????? Set speed to 0

??????????????????????????????? Wait for 5 seconds

Set the YAAT script running just like any other script. I do it with a button on the JMRI main menu.

Drive the loco with any throttle forwards over the RIGHT sensor and the script will take over from there.

Unless instructed to STOP this script will just keep repeating.

The script is written as you would any JMRI script using your favourite text editor but is ?saved as a We have written a shuttle script as easy as writing a simple BASIC program .

txt ?file. It is then placed in the YAAT.py file.

Here is a snip from a working program

trainList = {}

trainList['CoalExchange'] = 'preference:YAAT\Schedules\CoalExchange.txt'

trainList['FyardC-GoodsB'] = 'preference:YAAT\Schedules\FyardC-GoodsB.txt'

trainList['Plat1FyardB'] = 'preference:YAAT\Schedules\Plat1FyardB.txt'

trainList['YAATblock'] = 'preference:YAAT\Schedules\YAATblock.txt'

The YAAT program then compiles the script into something Jython and JMRI will understand!

?

YAAT allows us to use blocks, signals, sensors, turnouts, function keys.

There are special commands for decision making

YAAT will spot errors in syntax and highlight them when you try to run the program

The following is an extract from the start of one of my programmes.

?

# Coal Road to and fro

# Takes empty wagons and replaces with full between fiddle yards F&G

# Position loco facing South in Coal Road over IRD42

# Loco No 47331 or D3002

?

Loop

???? Start when sensor YAATsens41 is active

?

???? If sensor YAATsens1 is active

??????? Assign long address 7331?????

???? Else

??????? If sensor YAATsens11 is active?

?????????? Assign long address 3002

??????? Endif

???? Else

?????? Set sensor YAATsens41 inactive

???? Endif

?

Repeat if sensor YAATsens41 is inactive

????????

???? If sensor YAATsens31 is inactive

?????? Set function key 1 on????????????????????????? # Sound on

???? Else

?????? Set function key 1 off???????????????????????? # Sound off

???? Endif

?

You? can see that I have a JMRI internal sensor ( YAATsens41 ) which starts the script when active.

I have 2 locos which can be on roster for this duty ?and YAATsens11 or YAATsens41 will select which.

You will also notice that if a start is attempted without selecting a loco the active starts sensor? is made inactive.

When the routine starts YAATsens31 active puts the loco sound ON or OFF.

On my layout the internal sensors are all displayed on a JMRI control panel using standard JMRI icons.

The YAAT kill button will KILL all running scripts.

The Block Release button runs my script YAATblock which clears all my blocks to unoccupied and free. Both these buttons have proved most useful while writing interactive scripts.

I have a sensor in each routine to determine if it is to repeat.

?

By careful use of the block control system you can run multiple scripts without collisions!

I have trains slowing at distant signals and stopping at Home signals.

I have trains making decisions as to which YARD to pick up from or drop off at.

I have automatic switching of routes after the program has made sure the route is free and unoccupied.

It is possible to interact manually by setting? signals or using a throttle.

?

The following are snips from one of my routines showing how I have? dealt with signals.

?

?

Wait for sensor IRD11 to become active???

???????

??????? If signal head UpScissorDistant does show Yellow???????????????

?????????? Set speed to .20?????????????? # slow towards signal at red

??????? Else??

?????????? If block PLATFORM2 is free

?????????? Set block PLATFORM2 reserved

?????????? Set turnout Lever SHED Coal thrown

?????????? Set turnout Lever XOVER\ thrown????

?????????? Set speed to .40

????? Endif

?

Wait for sensor IRD12 to become active

???????

????? ??

??????? If signal head UpScissor does show Red???????

?????????? Set speed to 0???????????????????????????? ?? # STOP at red

??????? Wait for block PLATFORM2 to become free

?????????? Set block PLATFORM2 reserved

??????? Wait for block PLATFORM2 to become unoccupied

?????????? Set turnout Lever SHED Coal thrown??????? # Switch siding

?????????? Set turnout Lever XOVER\ thrown??????????? ? # Switch crossing?

??????? Wait for signal head UpScissor to show Green #Wait for feedback

?????????? Set speed to .10

????? ?? Wait for 5 seconds???????

?????????? Set speed to .35

??????? Endif

?

Find YAAT1.6 with all you need to know on the JMRI user group site:-

[email protected] examples..YAAT1.6.zip

?

Dave,
You could probably do it either way. I have two trains that run under script during my open house. They each have their owns script but interact with each other through use of a sensor that indicates both are ready for the meet. The robot throttle is another approach and you can have multiple instances running.
Bob Bucklew

----- Original Message -----
From: "David Slipper" <softfoot@...>
To: "jmriusers" <[email protected]>
Sent: Friday, November 16, 2018 6:21:05 PM
Subject: [jmriusers] Scripting - a general question ....

Probably a rather newbie question ...

If I have (say) 3 trains on a layout would I expect to have a single
script that controls all 3 (I can see this would rapidly become very
complex),? or would I be better off running 3 scripts (say one per loco)
... assuming this is even possible ... or is there a better approach??

TIA
Dave







.

Thanks Klaus. That helped.

I have a NCE Power Pro, running 2 AIU’s, and a switch it mk2. Thanks to this forum I now have a working panel and would like to start adding signals to my small layout. I would like to keep everything NCE. I have a light it, already wired with leds and a signal address of 100. I’m able to change the signal from the NCE handheld. I’ve also tried several different ways of adding a signal to the panel such as a mast and as a signal and even added as a sensor but to no avail. What am I missing? Or is it really that hard? ?Each main line has 8 blocks and there is one crossover. Do I need to add at least 2 more light it’s to get the R,Y,G? Or does it work off block occupancy? ?Would it be something to do with the fact that when I check the NCE log, I see the 2 AIU’s #50 and #51 that I programmed for BD20’s, but now there is also a AIU #63?