开云体育

Here it is after dispatcher runs

Hello Friends I would describe myself as a beginner when it comes to JRMI,been working on it around a week The end goal is to automate a train. As you see above i have entered Turnouts sensors and

Interesting.? Thanks Trevor.? I'll go back and look at my udev rules again tomorrow.? Maybe I'm doing something that is causing it to link to the usb bus device rather than the tty. Joel

I should also mention that I didn't manually set any options in jmri.conf or elsewhere when I set this up.? I just added the udev rules, then went in to JMRI and the DCCEX serial port was there for

OK, I should have checked first, and typed later... I've just checked my laptop, and the DCCEX symbolic link *isn't* as I remember it.? It is just like Dave Sand's example.? Possibly I saw the

I tried this again with the symlinks prefaced with "tty", but I still see the same behavior.? From the log it looks like the code is trying to connect to the devices before the additionl device names

Thank you Noel and Pete! Noel - that’s pretty much how I have it set up. Pete - thanks for jogging my memory about putting 5# of coffee in a 3# can. ?I’ve done that before, just forgot. ?I

How is JMRI seeing 7.3.0 on a New System? That's seem its on the old system. Inobu

I have put all four of the jumpers back on the board and changed to 19,200 in the advanced section. I got a normal startup, I will monitor. Thanks for the great

I'm not sure if this will assist, but on my Linux laptop, I added udev rules to give my DCC-EX system a name that doesn't changed based on order of connecting USB devices, or which port it gets

Inobu, Yes, the NCE USB device can only talk to a old command station like the PH1 or CS02 using the commands that throttles can do. Those command stations never had things like memory commands

I think Its from the Upgrade thread a few days ago. Instead of hijacking the thread a new one was started which is this one. Same person (Georgia). I vaguely remember there is a command structure

Joel, A previous message had some list commands. The symbolic link looks strange. Here is what I see on a Raspberry Pi. This is the udev rule: SUBSYSTEM=="tty", ATTRS{interface}=="LocoBuffer-USB",

Inobu, This case is a bit more involved or has mixed two different end users. I'm not 100% sure any more. One case was about a user with a PowerCab and SB5. The other case was a user with a

Bill S, The 7.3.0 in the log says you have no jumpers on the NCE USB. That code tells JMRI that the system is a PowerCab and it has the old 1.28 firmware.. The error message says that's not what

One thing I noticed is that if I define the devices in the udev rules as lower case names (dccex, tchlcc), then the names show up in the jmri config menu for the serial ports, but jmri still can't

No good.? I tried changing just the config file to use ttyDCCEX and ttyTCHLCC, as well as changing the udev rules to create ttyDCCEX and ttyTCHLCC.? The devices get created as defined, but still

Joel, Try including "tty" at the beginning of the device name, i.e. ttyDCCEX. Dave Sand

Thanks Dave.? Unfortunately, that didn't work either.? According to the comments in jmri.conf, for linux I don't need that path "/dev/", but I tried it both ways, using /dev/DCCEX as well as DCCEX,

Joel, Try using jmri.conf. Copy the installed version to ~/.jmri and modify it. default_options="--serial-ports=/dev/ttyUSB_NCE_PH_Pro, /dev/ttyUSB_PowrCab” Dave Sand