This 'ghost' still holds the com port and prevents any new JMRI from opening it.
It seems that on rare systems, one session of JMRI will not totally exit when you close it. One possible case might be the mystery 'ghost session' holding the com port. This is typical if theĭevice uses an FTDI driver, but there are other chips as well that can be USB-Serial chip, and so the baud rate is still important.
The other aspect, if the control unit has a USB connector on the side, is However IĪm not familiar with that particular cable.
SERIAL TO USB GIGAWARE DRIVER SERIAL
USB to serial cable, described as a " Gigaware" USB-A Serial Cable. If the connection is via USB, the baud rate is irrelevantĮven if it uses a virtual COM port.Not totally true, especially in this case as I understood he is using a Keeping that USB port for the locobuffer USB
SERIAL TO USB GIGAWARE DRIVER DRIVER
My guess was that the other device driver caused When they were reset to the digitrax baud rateĮverything returned to normal. Port changed when a different device was plugged into a port that had been Although not NCE, I've seen 2 cases where the baud rate on a USB Checking it will do no harm and eliminate a possible We have found the same thing about baud rates on the serial adaptors, someĭon't make a difference and some do. USB/Serial cable was still registering on the same port (itĬOM port diagnostic to ensure that port was still showing Now when I start it up, it starts fine but after However, after entering about 8 locomotives, Decoder Pro
AllĪs I read out these locomotives and added them to my Decoder XP and connecting thru a "Gigaware" USB-A Serial Cable. Have installed decoders in several locomotives (sound and I have an NCE Power Pro hooked up via a PowerPax to my Make sure that Decoder Pro, your command station, and yourĬomputer com port are all set to operate at 9600 baud rate.
0 kommentar(er)
