No interface device. The Zephyr Express is connected to a printer cable directly plugged into my computer. Windows 11
Open Device Manager on your computer, expand the “Ports” section, and with your Zephyr powered up, plug/unplug the USB cable.
As you do so, you should hear the “beep/boop” Windows tones, and a COM port should appear/disappear. (It may take a couple seconds to appear/disappear, so give it time.) That COM port will be the one you select in JMRI.
I would try a different cable.
That would be my next suggestion, after verifying the correct COM port is assigned, because even a good cable won’t fix a bad port assignment.
Another printer cable or Ethernet? I tried Memes trick. It was using Com3 and 4 (each time it would let me pick the one available). Now they’re both red in the port field (I’ll attach a picture).
I’m guessing you misspoke. A good cable won’t fix a bad port assignment? I tried a 2nd printer cable “timeout talking to command station (306)”. Is buying a new printer cable going to help or do I need to connect it another way?
It looks to me like the cable is good: the COM port is using DigiTrax’s Loconet.
The problem seems to be convincing JMRI to use the correct COM port, which is beyond my competence. (I use a Macintosh.)
Here is the JMRI page regarding the Zephyr Express:
https://www.jmri.org/help/en/html/hardware/loconet/DCS52.shtml
Hope that helps, Ed
No, I didn’t misspeak at all.
Did you confirm the correct COM port as I suggested? Your screen capture shows that both COM3 and COM4 are available. Which one appears/disappears when you plug/unplug the cable to your DCS52?
That’s the COM port you need to use, but if you pick the wrong one, changing the cable won’t fix it. You need to specify the correct COM port or JMRI will try communicating with whatever (if anything) the “wrong” COM port is connected to!
But your screen capture also shows that you have a bigger issue with your JMRI preferences - Why do you have LocoNet LocoBuffer selected when you are using the DCS52’s built-in interface? That will never work…
Thanks I’ll check it out
Your right I misread what you said. My picture isn’t that good ( both coms were in red letters so I think that means they’re bad…at the time). The device manager detected Com3 when I plugged it back in. Ok I’ll try another network connection since the loco buffer won’t work. Thanks
Don’t just " try another network connection", reference the JMRI page Ed (gmpullman) referred to above and set all your JMRI preferences correctly for your DCS52 and how you plan to use it. Otherwise, you’ll continue to have issues.
Also, that isn’t a “network connection”, it’s a “system connection”. In addition to connecting to your DCC system, JMRI can also connect to the outside world via Ethernet, WiFi, etc for other purposes so that’s an important distinction.
Thanks for the help guys. That Zephyr Express page helped alot. I managed to get a couple of functions working. Others I think I have to tweak some network settings or they aren’t on my decoder. Idk why my long address doesn’t work, but I’ll try again later.
One of the JMRI/Digitrax ‘quirks’ that even stumps me occasionally is the Loconet drop down menu to select “Programmer Mode” or “Interface Mode” for your Digitrax interface selection.
I often ‘monitor slots’ or ‘monitor Loconet commands’ and forget to set the mode selection back to the programmer mode . It really takes some frequent use in order to get acquainted with the user interface.
I’m sure you’ll get it figured out eventually and you have to follow the JMRI instructions to the letter but once it is set up and you start to get familiar with Decoder Pro you’ll see just how valuable a tool it is.
Good Luck, Ed
1 Like
Ok thanks for the info and thanks again
That’s very simple - The interface has two modes of operation: A LocoNet pass-thru mode (Interface Mode) and a stand-alone programming mode (Programmer Mode).
When in Interface Mode, it passes commands, and listens to, the LocoNet. In this mode, the programming outputs are not active.
In Programmer Mode, it only does programming, and does not listen to, or send anything to, the LocoNet.
A little background: That behavior is due to the fact that they basically incorporated the functionality of their discreet device, the PR4, directly into the command station itself.
Again, unless you’re using something like WiThrottle or LocoNet over TCP, you DO NOT have “network settings” you need to tweak. You have a system connection!
And if you have been able to read/write any CV’s, the settings for that system connection are correct and shouldn’t be changed!
Did you use DecoderPro’s “Read type from decoder” function to identify the decoder family, then drill down and select your specific decoder?
Did you then open the programmer for that specific decoder (which will only show the functions available on that decoder), set a long address, tell it to use that long address, and write the changes to the decoder?
Did you then read back that page to ensure that the changes were actually written?
Did you (Optional, but highly recommended - Go to the CV pane and read all CV’s) and save the roster entry future use?
Edit: Link to the DecoderPro Quick Tour: JMRI: DecoderPro - Tour
I probably should reset it back to the defaults. I was trying to set up all 6 functions with different light effects. I opened the roster and I think I’m in the comprehensive programmer. I’ll see if I can find the decoder specific programmer (or the CV pane).