There is a tool that comes close to this. It is under the 'OS Tools' item
and is a 'Follower'. If it was generalized to work as anything following
anything, it would cover the bill. Right now it only works for turnouts to
follow a sensor or some restrictive mapping. So if it could work for
watching turnouts, sensors, lights, blocks, and then drive the same or
longer list, it would work. It would also make it handy for anyone else with
multiple systems and needing to have something on one system follow
something on another system.

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

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@...

Bob H,

My main JMRI computer is a laptop connect to a NCE USB card.? I have added a turnout table that has 16 entries with matches my Tam Valley Octopus controllers.? I have started to work on creating panels to utilize the turnout tables.? Rather than continue to design my panels on the laptop I would rather use my desktop computer that has multiple monitors connect to it.? When I save the current panel that I am working, have not attached the turnouts just yet, I don't see the table information being saved.? Is there a different file being created?? I want to be able to move between the two computers without have to go out an buy another NCE USB card.

David,
I have 60 turnouts so converting from DCC Loconet controlled turnouts over to LCC controlled turnouts is not economically feasible. I know how to set up the signal logic in JMRI and have already experimented with it. However, I prefer to set up the logic in the LCC nodes. This is about more than signals. It is about creating this bridge between any DCC network and the LCC network.
I know I am not a JMRI programmer but (on the surface to me) it seems like a straight forward task for someone who maintains the Logix section of JMRI. Currently, I can set up Logix to set a conditional to evaluate a turnout then set a sensor as active/inactive according to the turnout position. instead of setting a sensor, let me create an Event ID and set it to active/inactive and let me insert a HEX code from within the range I have assigned. I know the devil is in the details but this capability is desperately needed as a bridge between the DCC and LCC world....even if/when someone creates a hardware bridge.?
--
Paul Davidson
Washita & Santa Fe RR
N scale:? Southern Oklahoma circa late 70's

Before you switch to a PR4, be aware that it is also not 100% reliable. We have a number of group members who are having problems making the PR4 work with Win10, as well as a bunch for whom it does work.

I had some issues when I first started with my PR3, but after a few tries and re-installing the drivers it now works VRY reliably

Stefan
--
Stefan Bartelski

Home layout: The Blue Ridge Line, an HO representation of the L&N Etowah Old Line from Etowah to Elizabeth, set in 1986 9under construction)
Modular Layout: Shoofly module of the Country RRoads Modular group

Paul
I believe what you are asking for is a Loconet to LCC gateway to be built into JMRI.? It would certainly be a useful tool, but I don't think it will sole your Signal conversion problem.? When I converted from Loconet to LCC I converted the Turnouts first, then the Sensors and finally the Signal Masts.? The signal logic is still mostly in JMRI and will not be moved to the nodes until some future node firmware from RR-Cricuits makes that possible.? It is now theoretically possible for some elementary signal logic to be wholly contained in the RR-Circuits LCC nodes.? However, you will find that for the time being JMRI Logix is a much easier alternative, even if someone should develop the Loconet to LCC general purpose Gateway.? If you should decide to convert the Turnouts to LCC that data will become available to the nodes directly without the gateway.? I'm not depreciating the value of the proposed gateway, just suspecting that for the immediate future you will still need to use the JMRI Logix to compute the necessary Signal Aspects.
David PARKS
Los Altos, CA

No, I did not have the Start Menu properly set up but I'm still stuck. My attempts to save my Turnout Table and Route Table are all failing, Java says it can't find them. ?I didn't see an Open Panel command but I do see Open File. I tried adding that to the Startup /home/pi/JMRI_UserFiles/Turnout List. Turnout List is an xml. file. Nothing. Starting from scratch, what is the proper way to save a Turnout Table and a Route Table created in PanelPro and make the proper entries in the Startup Menu so they can work with WiThrottle? ?Please do not assume knowledge on my part.?

Hi Steve,

Thanks, the Panel is uploaded to?/g/jmriusers/files/ProblemsBeingWorkedOn/Hampsford_Layout.xml

I also created a brand new instance and new panel and it still had the issue, i assume that your panels update as one would expect? (i did upgrade to this version of JMRI recently but had the same behaviour previously)

Cheers
Tim

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

Peter

i upgraded as I couldn’t connect and had assumed that it was something to do with the update of the Roco firmware - seems the issue was simply down to the defaults having changed.

however I now have the latest version and it’s working - happy days :)

Hi Tim,

Good to hear the event table has been of use :-)

If you could upload your panel to the /g/jmriusers/files/ProblemsBeingWorkedOn?folder,
( or even just a really simple panel with a single turnout which has the issue )
I'll see if I can reproduce / spot anything, unable to recreate the issue locally,

Steve

Thanks Bruno.

Your earlier question - From where does JMRI get this ttyACM0? ?- that is how the newer Lenz USB appears on the RPi when you plug it in.
To make the autodetect work a bit smoother, there are two options:
1.? alter the code you have done so that it comes up as ttyACM0 instead of? ttyUSB0 .? I don't know how to do that or if it's possible.??
2.? create an extra profile by copying the?LENZ_USB profile, perhaps call it? LENZ_USB0 and alter the device name in the connection. Use that profile (with the new id reference after it)?in the section of code you added.
The first option would be better if someone knows how to do it.?

- Dave Mc.

开云体育

Chuck,

?Make sure your PR3 has the Version 1.0 firmware update. It contains a fix for using the PR3 on 64-bit OS's.

HTH,
Steve
"Breezlys"

Donwload links now OK. Thanks

alain

hi Paul,

You're right, I should consider to make my life a bit easier and invest in the latest Lenz 23151 Ethernet-USB device and simply use the Ethernet connection. Would make my life much easier.

Thanks all for your feedback !

regards, Bruno

hi David,

That's the output I have:

Could you try again please?

Looks like I didn’t wait long enough for all the various parts to get into their final places before sending out the email.

Sorry for the confusion.

Bob

On Jan 14, 2019, at 3:01 AM, alain c via Groups.Io <acarasso_fr@...> wrote:

Hi Bob,

The release note page doesn't include any download links, it just forward us to the Jenkins built (thus 4.15.3). Is that the new way to update to test versions ?

Thanks and HAPPY NEW YEAR to all team members

--
Bob Jacobsen
rgj1927@...

Hi Bob,

The release note page doesn't include any download links, it just forward us to the Jenkins built (thus 4.15.3). Is that the new way to update to test versions ?

Thanks and HAPPY NEW YEAR to all team members