开云体育

On Aug 28, 2019, at 8:39 PM, Scott Pandorf <spandorf55@...> wrote:

I am running JMRI on a Windows 10 machine talking to an NCE system (9600 baud), and CMRI (19,200 baud). Although it's not clear to me that there is linkage, I recently upgraded to JMRI 4.16, I didn't notice immediately but a couple of days later it became obvious that the CMRI wasn't initializing. I checked the serial interface, even purchased a USB to RS485 cable in case my Chubb RS232 to RS485 converter card was the source of the problem. Nothing worked, then I looked at the JMRI log (except below):
2019-08-28 18:32:15,741 util.Log4JUtil INFO - * JMRI log ** [main]
2019-08-28 18:32:15,787 util.Log4JUtil INFO - This log is appended to file: C:\Users\scott\JMRI\log\messages.log [main]
2019-08-28 18:32:15,787 util.Log4JUtil INFO - This log is stored in file: C:\Users\scott\JMRI\log\session.log [main]
2019-08-28 18:32:15,803 apps.Apps INFO - PanelPro version 4.16+R6f9aced starts under Java 1.8.0_221 on Windows 10 x86 v10.0 at Wed Aug 28 18:32:15 EDT 2019 [main]
2019-08-28 18:32:23,897 apps.Apps INFO - Starting with profile WVOMCMRI.3f24bebf [main]
2019-08-28 18:32:24,100 node.NodeIdentity INFO - Using jmri-jWj6rcoHWhNiaaabL3psy8-3f24bebf as the JMRI storage identity for profile id 3f24bebf [AWT-EventQueue-0]
2019-08-28 18:32:24,412 xml.AbstractSerialConnectionConfigXml INFO - Starting to connect for "C/MRI" [main]
2019-08-28 18:32:24,944 serialdriver.SerialDriverAdapter INFO - COM6 port opened at 9600 baud with DTR: true RTS: true DSR: true CTS: true CD: true [main]
2019-08-28 18:32:24,991 xml.AbstractSerialConnectionConfigXml INFO - Starting to connect for "NCE" [main]
2019-08-28 18:32:25,819 serialdriver.SerialDriverAdapter INFO - NCE COM3 port opened at 9600 baud [main]
2019-08-28 18:32:25,928 nce.NceConnectionStatus INFO - NCE EPROM revision = 6.2.1 [AWT-EventQueue-0]
2019-08-28 18:32:28,741 util.FileUtilSupport INFO - File path program: is C:\Program Files (x86)\JMRI\ [main]
2019-08-28 18:32:28,756 util.FileUtilSupport INFO - File path preference: is C:\Users\scott\OneDrive\Ohio & Mississippi\WVO&M\ [main]
2019-08-28 18:32:28,756 util.FileUtilSupport INFO - File path profile: is C:\Users\scott\JMRI\WVOMCMRI\ [main]
2019-08-28 18:32:28,756 util.FileUtilSupport INFO - File path settings: is C:\Users\scott\JMRI\ [main]
2019-08-28 18:32:28,756 util.FileUtilSupport INFO - File path home: is C:\Users\scott\ [main]
2019-08-28 18:32:28,772 util.FileUtilSupport INFO - File path scripts: is C:\Program Files (x86)\JMRI\jython\ [main]
2019-08-28 18:32:29,741 PanelPro.PanelPro INFO - Main initialization done [main]
2019-08-28 18:32:39,037 withrottle.FacelessServer INFO - Published ZeroConf service for 'west virginia ohio & mississippi._withrottle._tcp.local.' on 2600:6c4a:417f:f396:4015:7731:a9ce:b142:12090 [WiThrottleServer]
2019-08-28 18:32:41,819 withrottle.FacelessServer INFO - Published ZeroConf service for 'west virginia ohio & mississippi._withrottle._tcp.local.' on 2600:6c4a:417f:f396:b4e0:18a:cb98:73f9:12090 [WiThrottleServer]
2019-08-28 18:32:44,475 withrottle.FacelessServer INFO - Published ZeroConf service for 'west virginia ohio & mississippi._withrottle._tcp.local.' on 192.168.1.146:12090 [WiThrottleServer]
2019-08-28 18:32:47,194 withrottle.FacelessServer INFO - Published ZeroConf service for 'west virginia ohio & mississippi._withrottle._tcp.local.' on fe80:0:0:0:b4e0:18a:cb98:73f9%eth1:12090 [WiThrottleServer]
2019-08-28 18:32:49,803 withrottle.FacelessServer INFO - Published ZeroConf service for 'west virginia ohio & mississippi._withrottle._tcp.local.' on 2600:6c4a:417f:f396:d51d:12e3:1d0c:d14:12090 [WiThrottleServer]
2019-08-28 18:32:49,803 withrottle.FacelessServer INFO - Creating new WiThrottle DeviceServer(socket) on port 12090, waiting for incoming connection... [WiThrottleServer]

Note that COM6 was opened at 9600 baud, now COM6 is the new USB cable and was set up at 19200 baud and the setting in JMRI is 19200, however JMRI is insisting on opening at 9600. To test I set all my CMRI boards and COM6 to 9600 baud and the system does initialize.

Anyone have an idea why the setting of 19200 is not being honored?

Thanks for your help, Scott.

Scott Pandorf
Ohio and Mississippi Railroad