开云体育

For each LocoNet turnout that you want to mirror over, you can do it with a logix:

*) Create a OpenLCB turnout in JMRI (_not_ an internal one) with the event IDs you want.
*) Configure a Logix so that when the LocoNet turnout goes THROWN, it sets the OpenLCB Turnout THROWN, etc.

Alternately, you could use a script to do lots of them.? The CombineTurnouts.py sample script less you set up each one with just a line of code (it’s meant to handle more complicated cases, but it can do one to one just fine)

Bob

> On Jan 14, 2019, at 10:08 AM, Paul Davidson <pdavidson@...> wrote:
>
> I would like to know how to submit a request for a new feature/capability in JMRI. The background on what I would like to see in JMRI is below.
>
> Background - I am implementing LCC controlled signals on my DCC layout. The signals are controlled by logic cells in the LCC nodes. The signal logic involves checking for turnout settings and block occupancy in the track ahead of the signal. As long as you are using LCC components for turnout control and block occupancy, you have no problem because the info you need for the logic cells is already available on the LCC network. However, if you are adding LCC to an existing layout and you want to use something like turnout position (from your Loconet controlled turnouts) in your LCC logic cells, there no easy current method to get the turnout position information from Loconet over to the LCC network. Yes - I know that I can (and have) used JMRI signal logic to set up signals but I do not want to go that route. I prefer to use the LCC Logic solution in lieu of the JMRI solution.
>? ? ?I believe a solution can be established in JMRI via edits/additions to Logix. I know JMRI can "see" the Loconet events because it uses that info to display actions on a panel. I can use JMRI Logix to create an Internal Sensor that tracks a turnout position. However, the LCC logic cells are looking for sensors and events that match its own style of "Event ID" which is a HEX number thus it never sees the Internal sensor created in JMRI. I would like to see JMRI Logix that I could use to generate a LCC Event ID (HEX number) in the same manor that it does to create an Internal sensor. For the non LCC savvy people, the Event ID is a unique HEX number that only exist one time anywhere in the LCC world thus it is used to trigger specific actions without any conflict anywhere else. Anyone can apply to get their own personal bank of 256 HEX numbers. I have mine.? That means that if JMRI Logix needed a unique Event ID to use in the Logix, anyone with a bank of ID's can provide that number and be compliant with LCC standards.
>
> --
> Paul Davidson
> Washita & Santa Fe RR
> N scale:? Southern Oklahoma circa late 70's
>

--
Bob Jacobsen
rgj1927@...