I connected my JMRI through NCE USB to NCE Powercab.?
I can see the Powercab on my JMRI NCE -> NCE show cabs
In NCE -> Show NCE cabs, when I refresh, I see commands in NCE: Command monitor and also see the status of the Powercab - e.g. speed = 020 or 024
This tells me that a read communication between NCE Powercab and JMRI has been established
How can I control my locomotive from JMRI -> send control commands to the Powercab?

In Create New Loco, when I "Read type from decoder, it says "Found mfg 123 (Massoth Elektronik GmbH) version 123; no such decoder defined". What do I need to do?

As I recall notepad should work, turning off line wrap helps.
Otherwise there is notepad++ that can be found here

On Nov 9, 2018, at 4:00 PM, Iain <iain@...> wrote:

Thanks Dave. I have found the box on the Route table. It's obvious when you know to look for it!

Using that will provide me with a sensor set, then I write the next Logix for the block setting triggered by that sensor. But that too will need to point to yet another Logix to set the signal, otherwise the signal may be set before the route is illuminated fully (longest is 8 blocks at the moment). Unless there is a similar trigger that I haven't yet seen, I can only do that by making the signal trigger sensor a delayed set? Maybe just a couple of seconds?

Basically you are saying my interpretation of what I have read and what you have said is correct??

Iain

On Nov 9, 2018, at 2:56 PM, Iain <iain@...> wrote:

I have an understanding problem. It has been clarified to me (and the manual does say it!) that Logix actions are NOT necessarily performed in a strict order, and will be executed "as convenient".

My problem is in route (note little "r" not meaning use of Routes) setting for my layout panel. May I please pick brains to get to the most effective way for my layout and current equipment.

I seek to have a process whereby three separate but tightly related activities take place in sequence, with each step being completed entirely before the next is commenced.

When a sensor is set (a button click on the panel) the Logix conditions will ensure that the process cannot start unless certain sensors (from blocks) are inactive (I.e. the route is free)

If true (1) THEN the necessary turnouts are set (I use a Route for this so I can have an Additional Delay" between turnout commands - technical problem of possible bus overload so this is a workround which works for me).

When (and only when) the turnouts have completely set (I do NOT have feedback so I rely on delay), (2) THEN the blocks which the route will follow will be set active (note these are those very sensors from the fist condition above so the first condition test will fail subsequently)

(3) THEN when all is complete the signals controlling the route are set.

My logical problem is this. The Logix does not maintain a sequence, so what is below does not work but it expresses what I need if the sequence were strictly followed: [comments not in the original]

IX:AUTO:0011C1 C1
[x] R1 IF Sensor "RQL1toP1a" state is "Sensor Active" [button on panel
[x] R2 AND Sensor "SP1a" state is "Sensor Inactive" [block on route which needs to be clear
[x] R3 AND Sensor "SLa" state is "Sensor Inactive" [block on route which needs to be clear
THEN
On Change To True, Set Sensor, "RQL1toP1a" to Inactive [reset button
On Change To True, Set Signal Mast Aspect, "P1aS" to Danger [signal on clashing route - should be Danger but do it just in case
On Change To True, Set Signal Mast Aspect, "P1aSf" to Zero [signal on clashing route
On Change To True, Set Turnout, "Crossover" to Thrown [turnout movement which needs additional delay - use a Route
On Change To True, Set Turnout, "QL1" to Thrown [turnout movement which needs additional delay - use a Route with above
On Change To True, Set Sensor, "SP1a" to Active [set block to be used
On Change To True, Set Sensor, "SLa" to Active [set block to be used
On Change To True, Set Sensor, "SQL1" to Active [set block to be used
On Change To True, Set Signal Mast Aspect, "QL1toP1ag" to Off [set signal controlling route - at the very end when all else is complete

Currently even if the "set turnout" operations were set to "delayed set turnout" the blocks would be set active, and even the signal, before the turnout operations are complete.
Moving the turnouts into a Route helps to keep the turnout sequence separate - but the sequence still continues on whilst the Route is executing, and some routes have 10 turnouts.

I cannot move the sensor setting into the Route because they will be set asynchronously to the turnouts, so the route will be coloured in before the turnouts are correctly set.

There is no way to delay a signal mast setting.

I need a foolproof way of identifying that the turnout switching is complete before moving on to set the block sensors as occupied. It was suggested that another sensor could be defined and when that was set another Logix would fire up which would contain the route sensor setting and signals. But since the new sensor will be set immediately after the Route is activated, this won't help me. I could perhaps call the Route from a Logix and do a delayed sensor set at an appropriate delay for all the turnout operations to be complete. Crude but may be all I can do.

The problem with delaying the signal setting would need to be met in the same way - several sensor sets for the blocks - followed by a delayed sensor setting for another new sensor which would then fire another Logix to set the signal(s).

I now have something like 2 extra Logix, a Route and 2 extra sensors to meet what seemed to me to be a fairly straightforward requirement.

Have I analysed this right or am I an idiot?

Your thoughts and suggestions are humbly requested. Solutions requiring changing hardware, wiring, new equipment are not likely to be acted on. I just want to use JMRI software effectively to meet my needs if that is at all possible.

Many thanks for taking the time to read this.