?

Terry,

With one huge paragraph to work from, multiple snippets have been isolated. It has taken more time to split out the details than to figure out if a response is needed.

Preamble, I generated a complete panel, layout, and tables for turnouts, sensors and logiX.

From what is written below, the reasonable assumption is that you are using the LocoNet Simulator when away from the layout. At least that is what I commonly do, with multiple iterations back and forth to and from the club layout.

When I put it on the working layout and made the changes in the preferences to Digitrax, PR4 and the Zephr DCS51 , I have not been able to get the switches to activate on the layout.

I have confirmed communication by running locomotives from my roster without any issue. My panel, levers, lights and code buttons all work as they had in the simulator mode. Except they do not activate the physical switches on the layout.

• What warning or error messages are showing in your session.log file or your JMRI System Console window?
• Is this true for all switches?
• Do you have the LocoNet monitor turned on,
• with both the "Show raw data" and the "Show Timestamps" turned on with the checkboxes at the bottom of the window?
• Do those switches activate correctly with your Digitrax throttle?
• If so, do you see useful information on your Tools -> Tables -> Turnouts window?

I have been working on this for a couple of days and consequently already done a lot of different things. The most drastic action was moving my functioning JMRI to a different file name, the uninstalling all JMRI short cuts and then completely reinstalling JMRI (4.19).

It is not at all clear that the heaviest tool in your toolbox was the appropriate choice, but other than delay, no harm is likely to have been done.

This clean setup allowed me to load my new files. Nothing changed though, still no control of the physical switches.

This result is not surprising, the cause of your problem has not been identified.
If none of the other JMRI features were working properly, or if specifically identified in the release notes, maybe....

I have looked through all other the tables for sensors, turnouts and signal. Then confirmed the names of the turnouts listed as closed or thrown in the actions, reprogrammed the DS64's to insure they matched what the program was calling for. Still no worky.

All of the tables defining the levers are (IT) sensors are (IS) and I can't remember the code buttons but they are ( something).

The description of your Turnouts table and what happens when you click on UNKNOWN, ACTIVE, or INACTIVE is still unknown to us.

My physical turnouts are (LT101-108).

I hope this is enough information to help with the diagnosis as I am running out of things to try. I have a gut feeling that the easy answer would be to start from scratch and recreate my project not as a simulation. Thanks in advance for the help!

If the answers to the above questions do no supply enough clues, please provide us with more explicit detail about the turnouts.

Also, in the future, it would be much safer to make minor changes and then verify the results with the layout hardware, rather than make a huge investment of time and effort between testing events.

Cliff in Baja SoCal