--

If you’ve selected “LocoNet LocoBuffer-USB” and “DCS240+ (Advanced Command Station)” and you’ve still having _no_ communications at all, then I suspect that your settings are not the problem.

Let’s move on to debugging that.

1) When you open the LocoNet monitor and do something else on the layout, e.g. use a real Digitrax throttle, do you see any LocoNet traffic?

2) Open the JMRI Power Control from the Tools menu, and try turn the layout power on and off. Does that work? Do you see any LocoNet traffic on the LocoNet monitor?

For this next step, leave the layout power on. Or turn it on from a Digitrax throttle

3) If you have a LocoNet-connected turnout, open the JMRI Turnout Control from the Tools menu, enter the number of a turnout on the layout (Just the number, like 23) and see if you can throw and close the turnout.

These details may help us track down the problem.


4) As an experiment, you can also try setting the command station selection to “DCS100 (Chief)”, save and restart, then see if the connection works.

Bob

On Apr 1, 2025, at 6:27?PM, Dale Gloer via groups.io <dale.gloer@...> wrote:

Here are the choices I have in the Connections panel. This is JMRI 5.4 but 5.10 shows the same panels. This was captured on a Windows 10 machine and I know how to determine the correct serial port for a Pi. So please advise which selection is correct in each box so that I can communicate with the DCS240+ from the computer. I can sort out the serial port stuff.

—
Bob Jacobsen
rgj1927@...

On 4/1/2025 11:42 AM, Dale Gloer via groups.io wrote:

I assume this is because specifying DCS240+ implies a USB connection regardless of what I input in the System connection box.

That is an incorrect assumption! JMRI can be configured to use the LocoBuffer-NG to talk to the LocoNet of a DCS240+. I have been doing exactly that for a couple of YEARS (with a Windows O/S machine)!

You should ignore your incorrect assumption, and configure JMRI "properly". I will give three pieces of info that you will need to configure.

JMRI's "connection settings" allow configuration of how JMRI can connect to the LocoNet, and if/how JMRI _assumes_ that it can talk to a command station _if_ there is a command station connected to that LocoNet.

For your case, you will NEED to configure these THREE different things on the "Connection" in JMRI:

1: Define how JMRI can talk to the LocoNet. This is the "System Connection" setting. Note that you _DO NOT want to select_ "DCS2401_ USB Interface" in this case! In your case, it should set for "LocoNet LocoBuffer-NG".

2: Define how your computer talks with the LocoNet interface device. This will be set up in the connection, and varies depending on what type of interface you are using. For a LocoBuffer-NG, the connection will require a "Serial Port", to be entered in the "Settings" portion of the "LocoNet" "tab" on the "Connection" selection in the "Preferences" window.

The "serial port" setting for _your_ installation will look differently depending on which operating system you are using. Since you are using a Raspberry Pi, I would suggest that you get someone who uses a Raspberry Pi with JMRI. I do not use a Raspberry Pi, and do not really understand the "tricks" to figuring out the "serial port" name that will work with the Raspberry-Pi. And I understand that the Linux O/S may have changed recently for Raspberry Pi devices.

3: The last item in the "Preferences"->connections"->(typically) "LocoNet" "Tab" is the "Command station type" entry. For you, select "DCS240+ (Advanced Command Station)".


These things are necessary for you to achieve what you are trying to do.

开云体育

--