A variation of this issue came up about 18 months ago. See the message thread starting with #139664.

At that time, with a lot of help from Dave Sand, I was able to modify a script written by Bob Jacobsen. A copy of that file has now been uploaded to /g/jmriusers/files/ProblemsBeingWorkedOn/Master%20and%20Slave%20Turnout%20Control/TurnoutsMasterSlave.py

Some of the comments concerning the Identifier Prefix strings may be out of date.

Editing may be required at lines # 50 & 51 for the prefixes on your layout, because as-is, this script will translate an instruction to a real or hypothetical turnout LT1234 into the same instruction to a real hardware turnout NT1234.

There may be some subtle portion of the original posting in this thread that I have not picked up on, so some additional investigation may be necessary.

Cliff in Baja SoCal

开云体育

I'm preparing an update for the Athearn RTR Eco definition but I'm no longer getting replies to my emails to Soundtraxx for more info, so can only add decoders that I have or someone who does that is willing to send me info.

First reset the decoder to factory with setting CV8 to value of 8 then placing on powered track to allow the reset to happen.
Select any of the models in the "Econami Diesel OEM Athearn" family.
Read all sheets.
Once everything has been read, from file menu pick export - CSV file, give it a name and note where it is saved and send me that file.

I'll be adding the recent release SD40 and SD40T-2
And on Genesis TSU2 side, second version of SD60E decoder and GP7u.

Michael Mosher
Member SFRH&MS              
DCC Master PVSMR            

Joseph,
I use both NCE for trains and Loconet for turnouts, sensors and signalling. More info is on my web site at


As others have said, the Loconet does not connect directly to NCE. But JMRI connects to both and makes it one integrated system. In fact some of my block detectors are BD20 and AIU on the NCE cab bus. Others are BOD8 on the Loconet. JMRI integrates them into one working system.
Bob Bucklew

There are various methods of connecting Non loconet to loconet. Digitrax themselves gve circuits and there are a couple of circuits here in MRi.
Railsync from NCE controller can be found here?
igitrax manuals for the equipment you want to use are here?
If your NCE system doesn't have a ground connector and you're using BDL168 ocupancy sensors, the circuit diagram can be found here.
jmri.org/help/en/html/hardware/loconet/StandaloneLocoNet.shtml
This is probablty the best page for information as i m trying to do something similar with a Gaugemaster (MRC) Prodigy connecting to the sensors.
Have fun and happy linking
SwissChris.

How to do the connection is in the link in my prior post: but you should probably read that entire page, particularly

But you’ll never get the "Digitrax components communicate through the Loconet to my NCE Command Station”. That’s just not how it works. But that’s OK, because there’s no need for that. The LocoNet components would instead communicate to JMRI, which then handles whatever needs to be done.

Bob

On Jan 8, 2019, at 7:07 AM, Joseph Carlino <coastiejoe64@...> wrote:

Bob,
I have heard this before in some online articles. Please excuse my ignorance but, do you know where I can find anything on how to go about connecting the NCE DCC signal to the Railsync on the loconet buss? (I think this is pretty much exactly what I am trying to accomplish). What I am actually trying to do is pretty straight forward and I'm sure has been done or at least tried before. I want to use my NCE system to control my trains and leave open the option to use Digitrax components for other layout functions like switching, block detection and signaling. However, I don't want them to be two completely different systems that can't inter-operate. This way I can also power components like DS64 or SEC8 with a simple DC power supply , (not the track bus) and have the Digitrax components communicate through the Loconet to my NCE Command Station. In the most basic sense it would give me the ability to pick the components I prefer to use from both manufactures combining them sort of as one DCC system.

Thanks so much to everyone for your replies!!
This is my first experience with any kind of user group, so I'm not very sure of myself.
Best regards,
Joseph

--
Bob Jacobsen
rgj1927@...

Could you email me your panel file? (jacobsen@...) I’ll update it and send it back to you.

Bob

On Jan 8, 2019, at 3:57 AM, Jonathan Hamilton <joffham@...> wrote:

I have upgraded to JMRI Version 4.14 recently. The old DCC++ Connection prefix was DCCP, which is now showing as “This is a legacy prefix which should be migrated…” I believe that the correct Prefix is now just D, which I changed, but doing this deleted all of my Sensors. So, for the time being, I have not changed that Preferences.

Any clues?

Joff

--
Bob Jacobsen
rgj1927@...

Bob,
I have heard this before in some online articles.? Please excuse my ignorance but, do you know where I can find anything on how to go about? connecting the NCE DCC signal to the Railsync on the loconet buss? (I think this is pretty much exactly what I am trying to accomplish).? What I am actually trying to do is pretty straight forward and I'm sure has been done or at least tried before.? I want to use my NCE system to control my trains and leave open the option to use Digitrax components for other layout functions like switching, block detection and signaling.? However, I don't want them to be two completely different systems that can't inter-operate.? This way I can also power components like DS64 or SEC8 with a simple DC power supply , (not the track bus) and have the Digitrax components communicate through the Loconet to my NCE Command Station.? In the most basic sense it would give me the ability to pick the components I prefer to use from both manufactures combining them sort of as one DCC system.

Thanks so much to everyone for your replies!!
This is my first experience with any kind of user group, so I'm not very sure of myself.
Best regards,
Joseph

Bob:

My example RR is old enough that the host computer that it started with was back in the dark ages... processors with clock speeds in Mega Hertz... So as the computer evolved the C/MRI bus speed never changed... We just redid the computer using a "baby" box a Minix NeoZ83-4 Pro not that high powered but more than sufficient for the task.

So if I were starting out now I would go to at least 19,200 or 28,800 given a 1+ GHz system clock...

RS485 is rather bullet proof and unless you really do something really strange with the wiring those speeds should be good even with some wiring issues... The history of 422/485 was with *big* washtub disk drives with very long 60 conductor cables under the raised computer room floor... noisy environment you bet.

Just re-read Bruce's manual section on 485 and I think we're in agreement.

Where I see a genuine concern was raised, one I haven't considered is the modular world, termination. When you build a RR in the "basement" you tend to start in one place and work out from there. So yes a terminated to the computer interface but that's normally at one end... Is there an issue if the nodes are rearranged and the interface is in the middle? Shouldn't but in our DCC world of applied witchcraft?

I can't see where there needs to be any order to the node addresses. You send the node address out over the entire C/MRI bus, all nodes listen, so where they are doesn't matter. Same for the node talking that's on the entire bus...

Jim Albanowski

开云体育

Graham,


Please see my answers below.


Am 07.01.2019 um 22:03 schrieb SettleDown:

Is it really the case that it's not possible to "save" the multiple decoders/profiles/VSDfiles in the VSDecoder Manager window for future sessions ?? I currently only have a small number of locos so it doesn't take that long to rebuild the Manager window for my fleet, but I imagine this is an issue for modelers with a large fleet.? The only option I can see at the moment is to keep the session running overnight if I want to go back to the layout with all sounds active the next day.? Is this on the to do list ?? If it's going to be possible in " "VSDecoder faceless", to skip the dialog and load the Rosters automatically", why isn't it possible to do that in the standard VSD UI ?

Because building the GUI is skipped too. I have to look closer on this to understand, whether there is a solution to go. For now I'd like to recommend to use a roster per VSDecoder and setup "Start Virtual Sound Decoder Manager" at startup. I counted four clicks to have a VSDecoder up and running.

Yesterday I worked on "VSDecoder faceless" and I'm preparing a JMRI change request shortly.

Q2. i have Class64.vsd file assigned to one of my locos but when it appears in the Manager it always shows the same layout of buttons as in the GenericSteam.vsd without the combination of whistle sounds as shown in the document ?which you referenced in the post above.? The problem may be caused by the fact that even if I choose Class64 as the profile and then as the VSD file, it always appears as GenericSteam profile in the Manager.? Is this a known issue?? Similarly I can't get Class94 to work as I've only ever seen the decoder for this once - it always reverts to GenericSteam.

I haven't seen this behavior before. It is possible to assign a profile multiple times to different rosters or numeric addresses. But to get this I have to select the same profile always.

I do not understand...

"I choose Class64 as the profile and then as the VSD file"

Selecting the profile should always be the last step before clicking the OK button.


Regards,
Klaus

Don,

In that layout we moved the RS-485 and the terminator to trade them. So now
the terminator is at node 0 and the RS-485 serial is at the end past node 4.
The way Bob had worded his statement of things it seemed to me he had a
concern if the order of the node ids has some possible issue. His later
message seemed to say there isn't any sensitivity to the order of the nodes.

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

The SD60E that is in the released version is based on the decoder that was in the NS 9-1-1 SD60E and other numbers released at the same time.? The just released NS 6920 Veterans unit has different ID number and a few changes compared to 9-1-1.? Definition is being updated.

Michael Mosher
Member SFRH&MS
DCC Master PVSMR

Is the idea to create a standalone (no command station) LocoNet?

Then you might not need JMRI for it. LocoNet contain a Railsync (RailSynch?) signal that’s a copy of the DCC signal. The DS64, along with most, maybe all, LocoNet connected components, can take their instructions from that.

So you can connect your NCE-generated DCC signal into the Railsync of your standalone LocoNet and you should be able to get things to work without going through JMRI or any other software.

See along with the rest of that page.

Bob

On Jan 7, 2019, at 9:06 AM, Joseph Carlino <coastiejoe64@...> wrote:

When creating a simplified Loconet bus on a non-Digitrax layout, can both systems (in my case NCE & Digitrax Loconet bus) connect to JMRI at the same time through separate USB ports? Can the Digitrax components be accessed from the home system. For example can I throw turnouts with my NCE Cab through a DS64 connected to the Loconet?

--
Bob Jacobsen
rgj1927@...

Joseph,

When creating a simplified Loconet bus on a non-Digitrax layout, can both systems (in my case NCE & Digitrax Loconet bus) connect to JMRI at the same time through separate USB ports?

Yes.

Can the Digitrax components be accessed from the home system. For example can I throw turnouts with my NCE Cab through a DS64 connected to the Loconet?

Maybe. Without some "magic", the NCE cab contols ONLY those turnouts which are on the NCE system.

I am not very "NCE literate" so I cannot state this conclusively, I _believe_ that it is possible for JMRI to "see" NCE turnout commands, for at least some NCE systems and at least some NCE-to-computer interface connections. With this JMRI visibility to NCE turnout commands, it would be _possible_ to configure JMRI to watch certain NCE turnouts and send "turnout messages" to LocoNet when appropriate. This is not something that JMRI can do by clicking a few buttons. But it ought to be "rather easy" to configure using JMRI Logix.

Note that not all NCE systems and NCE-to-computer interfaces are created equally. This may limit the ability to implement this for some NCE hardware.

There may be another way to achieve what you are trying - simply connect the DS64s to the NCE track bus via the DS64 track connections. That way the DS64 would get the NCE turnout commands directly from the NCE command station! Be aware that DS64s tend to become "forgetful" of programming when connected to a DCC track signal, so if you want to set this up once and never have to reprogram it later, then the DS64 "track connections" are _not_ recommended.

Regards,
Billybob

Hi Klaus

I'm back looking at VSD again having been diverted by having to learn some Ubuntu command line skills as part of moving to JMRI4.14. I've got a couple of VSD questions:

Q1. In the second post of this topic #155052 you wrote:

On problem 2.The VSDecoder Manager always comes up empty. What you are looking for might be "VSDecoder faceless", which skips the dialog and loads the Rosters automatically. This is doable, but I'm not sure how to quit JMRI later. For now it is not implemented.As you mentioned you can create a roster and associate the VSD file with that roster. Please see (section "Configuration Dialog"), how to achieve this. This will save some clicks and you can "Auto load" the VSD file as well, see .

Is it really the case that it's not possible to "save" the multiple decoders/profiles/VSDfiles in the VSDecoder Manager window for future sessions ?? I currently only have a small number of locos so it doesn't take that long to rebuild the Manager window for my fleet, but I imagine this is an issue for modelers with a large fleet.? The only option I can see at the moment is to keep the session running overnight if I want to go back to the layout with all sounds active the next day.? Is this on the to do list ?? If it's going to be possible in " "VSDecoder faceless", to skip the dialog and load the Rosters automatically", why isn't it possible to do that in the standard VSD UI ?

Q2. i have Class64.vsd file assigned to one of my locos but when it appears in the Manager it always shows the same layout of buttons as in the GenericSteam.vsd without the combination of whistle sounds as shown in the document???which you referenced in the post above.? The problem may be caused by the fact that even if I choose Class64 as the profile and then as the VSD file, it always appears as GenericSteam profile in the Manager.? Is this a known issue?? Similarly I can't get Class94 to work as I've only ever seen the decoder for this once - it always reverts to GenericSteam.

Regards

Graham - @SetleDown

When creating a simplified Loconet bus on a non-Digitrax layout, can both systems (in my case NCE & Digitrax Loconet bus) connect to JMRI at the same time through separate USB ports?? Can the Digitrax components be accessed from the home system.? For example can I throw turnouts with my NCE Cab through a DS64 connected to the Loconet?

Thanks Dave. That was exactly what I needed.
Cheers / Sven

Dave R,

I have created a script which will move the user names from the ITnnn turnouts to XTnnn turnouts. There is NO capability for changing the turnout address assignments. The user name for IT123 is moved to XT123. When the hardware is implemented, the real address may end up as XT321.

/g/jmriusers/files/ProblemsBeingWorkedOn/dsand/mass-move.py

Add a "Lenz/XpressNet Simulator" connection to your profile.

After you re-start JMRI, load the panel xml file, run the script, save the panel xml file to a different name. Stop and start JMRI and load the updated file and verify the results.

This is a "one off" script. The scope is specific and running it twice will probably blow up the world.

I agree with the comments made by Bob and Ken. It would have been faster and safer to manually move the turnout names.


Dave Sand