![]() ![]() Hence if you are using COM7 under Windows, this is the third emulated serial port, and so under Linux the equivalent should be /dev/ttyACM2. If under Windows the COM ports are COM5, 6, & 7, under Linux they then would be /dev/ttyACM0, 1, & 2, as you saw. When you plug in the DR5000, the three serial ports should get listed by the device driver in the same order under both Windows and Linux, every time. The exact name used under Linux depends on the device driver and the type of device, but for you it looks like they are called /dev/ttyACM*. ![]() The DR5000's USB interface emulates three old-school RS232 serial ports, these are called COM ports under Windows and TTY's under Linux. You're on the right track with the files under /dev - in Linux, all hardware devices that Linux detects appear as files under that directory. I use Linux as well, and while I haven't gotten talking to my DR5000 via the serial port yet, that's the next step in my plan. Rocrail is set up in locobuffer mode, listening on that com7 com port which doesn't seem to mean too much in the linux world I have tried various suggestions I've seen online such as adding my linux user id to the dialout group, and I have observed an entry for /dev/ttyACM0, 1 and 2 appears when I plug in the usb cable from the DR5000. I am fairly new to Linux and I'm wondering how the windows configuration on the DR5000 telling it to use loconet on COM7 "translates" to the linux system. Maybe it's worth asking on a Rocrail-specific forum, since there might be some more people there with Rocrail experience? I've also looked at the RocRail trace files but I don't see any meaningful error messages in thereWell, it is indeed working for me via the USB connection using JMRI. I cannot connect it to my router because that is downstairs so my only options are WiFi or USB I am having a hard time believing that no one has managed to configure RocRail (or indeed JMRI) to work on Linux communicating (with the USB cable) to the DR5000. I'm pretty sure the first one is always LocoNet, the second always XpressNet, and the third Digikeijs's own protocol. Happily, it does work fine for running trains.Īnyway, unlike for the LAN and WiFi, I'm not sure it is actually possible to reconfigure the protocols that the DR5000 speaks on the serial ports. I hear Digikeijs is working on Linux & Mac configuration support, hopefully it's not too far off. Unfortunately it's not yet possible to configure the DR5000 without Windows at the moment, which means either having a computer that is able to boot Windows hanging aroud still or (as I do), run Windows in a virtual machine such as Virtual Box. ![]() I think where I am having a hard time trying to understand all this is that I suppose its possible to reconfigure my DR5000 with my old Win 7 machine to use a different COM port for locobuffer, and thus maybe have it match better to what my Linux machine provides. ![]() Maybe try configuring Rocrail similarly? That wiki page the other Mike pointed seems to have the right details. I tried your suggestion of substituting /dev/ttyACM0 (and ACM1 and ACM2) in the controller setupof Rocrail - substituting for COM7.But that didn't end up working? For what it's worth, I fired up my DR5000 today and I was able to get JRMI talking to it fine when configured using a Digitrax Loconet LocoBuffer connection on /dev/ttyACM0. Thank you Mike That does help in the sense that I'm learning about the representation of serial ports in Linux Mint. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |