Keyboard Shortcuts
Likes
Search
Locked No NCE connection
I copied the following thread from my system console while in Panel Pro.? I have a Keyspan serial to USB connector and when I go to Device Manager on my laptop it says device is working properly. I have NCE power pro command station and pro cab throttle.? When I start up Panel Pro the NCE on COM3 goes red and the data light on the keyspan serial adapter goes solid green.? I see in below thread that the EPROM is not being echoed back.? In Panel Pro preferences I have tried both serial and NCE to USB option on connections screen.? My baud rate is 9600.? I have my pro cab turned off.What is wrong with my configuration? 2018-12-05 11:30:24,158 util.Log4JUtil??????????????????????? INFO? - This log is appended to file: C:\Users\Admin\JMRI\log\messages.log [main] 2018-12-05 11:30:24,174 util.Log4JUtil??????????????????????? INFO? - This log is stored in file: C:\Users\Admin\JMRI\log\session.log [main] 2018-12-05 11:30:24,190 apps.Apps???????????????????????????? INFO? - PanelPro version 4.12+Rb6a9bb1 starts under Java 1.8.0_101 on Windows 10 x86 v10.0 at Wed Dec 05 11:30:24 MST 2018 [main] 2018-12-05 11:30:27,632 apps.Apps???????????????????????????? INFO? - Starting with profile PBJ_RR.3de2a322 [main] 2018-12-05 11:30:27,945 node.NodeIdentity???????????????????? INFO? - Using jmri-jlKwQdXLGhNiaaJeYKUITG-3de2a322 as the JMRI Node identity [AWT-EventQueue-0] 2018-12-05 11:30:28,117 xml.AbstractSerialConnectionConfigXml INFO? - Starting to connect for "NCE" [main] 2018-12-05 11:30:28,550 usbdriver.UsbDriverAdapter??????????? INFO? - NCE USB COM3 port opened at 9600 baud [main] 2018-12-05 11:30:29,019 util.FileUtilSupport????????????????? INFO? - File path program: is C:\Program Files (x86)\JMRI\ [main] 2018-12-05 11:30:29,019 util.FileUtilSupport????????????????? INFO? - File path preference: is C:\Users\Admin\JMRI\PBJ_RR\ [main] 2018-12-05 11:30:29,019 util.FileUtilSupport????????????????? INFO? - File path profile: is C:\Users\Admin\JMRI\PBJ_RR\ [main] 2018-12-05 11:30:29,019 util.FileUtilSupport????????????????? INFO? - File path settings: is C:\Users\Admin\JMRI\ [main] 2018-12-05 11:30:29,019 util.FileUtilSupport????????????????? INFO? - File path home: is C:\Users\Admin\ [main] 2018-12-05 11:30:29,019 util.FileUtilSupport? ????????????????INFO? - File path scripts: is C:\Program Files (x86)\JMRI\jython\ [main] 2018-12-05 11:30:30,269 PanelPro.PanelPro???????????????????? INFO? - Main initialization done [main] 2018-12-05 11:30:38,676 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 0 in nce.NceTrafficController [nce.NceTrafficController Transmit thread] 2018-12-05 11:30:38,786 nce.NceConnectionStatus?????????????? WARN? - Incorrect or no response from NCE command station [nce.NceTrafficController Transmit thread] |
Check...9600, 8, N, 1
toggle quoted message
Show quoted text
John ---------- Original Message ---------- |
Changing the device baud rate etc. settings in Windows Device Manager has absolutely no effect and is a waste of time. JMRI overrides those settings when it opens the port.
toggle quoted message
Show quoted text
The log reveals that the Baud Rate in JMRI is correct. -- Dave in Australia On 6 Dec 2018, at 12:23 PM, John <jonie41@...> wrote: |
Thanks John and Dave for your prompt responses.? John, I presume 9600 is the baud rate to be checked?? If that is your intent, as stated before, my baud rate is confirmed at 9600.? I have read Dave's earlier posts about baud rate and I do not intend to change it through his firm guidance.? I have checked "N" for my connection prefix and that is confirmed.? John - how do I check for "8" and "1"?? Am I correct that the system console echo should state something about the EPROM? in response to the the?nce.NceConnectionStatus statement after the statement containing NCE USB COM3 port opened at 9600 baud [main]?
Thanks for any and all help, Stan Mattingly ProPanel 4.12+Rb6a9bb1 Java Version 1.8.0_101 |
Thanks for the console log. Here is a checklist.
toggle quoted message
Show quoted text
1) Make sure the port that appears/disappears in Windows Device Manager when you plug/unplug the Keyspan cable is actually COM3. If not, change the JMRI setting to match the actual port appearing/disappearing. 2) Since you have a Keyspan cable, you need an adaptor lead due the binding post issue. Did you get a straight-through one? If you got a crossover one (usually called a Null Modem cable) it won't work. I prefer the FTDI cables from ESU or RRCirKits as they don't need an adaptor, are cheaper and have other advantages. 3) On the Power Pro under Setup Command Station, make sure AIU broadcasts are disabled and baud rate is set to 9600. 4) You quite possibly have the connection post issue documented at the link below. 5) The link below also explains how to do a loopback test. The loopback test eliminates JMRI, Windows and Keyspan issues. If the loopback test returns the expected result (as documented), your problem is probably either (2) or (4) (there are other less likely possibilities, such as a Power Pro fault - mine had one). <> -- Dave in Australia On 6 Dec 2018, at 11:31 AM, stanbmattingly@... wrote: |
Well, Dave, you know more about this stuff than I.
toggle quoted message
Show quoted text
John ---------- Original Message ---------- |
Dave knows more about this than I, just thought you should check those is all,
toggle quoted message
Show quoted text
best do as Dave says after all, he works with this stuff. Over to you Dave. John ---------- Original Message ---------- |
¿ªÔÆÌåÓýSee my other post for further information. In response to your specific questions: Thanks John and Dave for your prompt responses.? John, I presume 9600 is the baud rate to be checked?? If that is your intent, as stated before, my baud rate is confirmed at 9600. ? I have read Dave's earlier posts about baud rate and I do not intend to change it through his firm guidance.? I have checked "N" for my connection prefix and that is confirmed.? John - how do I check for "8" and "1"? ? Am I correct that the system console echo should state something about the EPROM? in response to the the?nce.NceConnectionStatus statement after the statement containing NCE USB COM3 port opened at 9600 baud [main]? Yes, it should, and that's not what it is doing at present. Timeout indicates no connection. Flushing unexpected response indicates mismatched baud rate, unless you are doing a loopback test (in which case flushing "AA" indicates a successful loopback - "AA" is the Get EPROM Version command JMRI sends out. Dave in Australia |
Thanks again for the incredibly prompt response Dave. Items #1 and # 3 in your above 5 item checklist have indeed been checked and confirmed.? Regarding Item #2, my Keyspan cable is a USB A to USB B.? I do not know if I have a "straight through" as you are asking and ask that you advise me how to tell.? Could you provide a weblink to purchase the ESU or RRCirKits cable? I will in the meantime check the helpful link in checklist Item #5.
|
The "Keyspan serial to USB connector" must have a 9-pin serial connector, otherwise it wouldn't be "USB to Serial" . In the case of the Keyspan, (at least the previous models) won't plug directly into the Power Pro's serial port because of fouling issues and need a 9-pin M-F straight-through cable between the Keyspan and Power Pro.
As far as alternatives are concerned:, see the document lower down in this post. Dave On 6 Dec 2018, at 1:18 PM, stanbmattingly@... wrote:Do not try to use an NCE USB with JMRI Decoder Pro and a PH Pro system. The PH Pro firmware does not support decoder programming with the NCE USB. <> You need a third-party USB-Serial adaptor. Ignore the el-cheapo RS232 to USB connectors you see at office supplies and computer stores and buy a reliable genuine FTDI chipset-based one such as these two ~$30 solutions: <> <> The UN8-BE is the item you want. <> <> (Also ESU dealers in the UK and Australia can supply.) Both these adaptors have the correct screw terminals rather than binding posts and the USB cables are 1.8m long, so you do not need an extension cable. I use my ESU one regularly on a 10m Active USB extender as well. Both work well with JMRI and have unique IDs so will not change COM ports capriciously. Drivers download from: <> There are Windows 10 drivers on this site. I have found them very stable with JMRI on Windows, Mac and Linux. There are problems with many USB-Serial adaptors readily available in retail outlets: 1) The older PL2303 chipset version does not work with Windows 7 or 8. 2) Both thePL2303 and FTDI chipsets have been counterfeited and there are numerous non-genuine devices out there in the market place. 3) Many of the cheaper devices do not incorporate a unique serial number on-board so are likely to capriciously appear at different COM port numbers when plugged in to Windows or Mac computers. Another problem with the USB-Serial adaptors is that many units readily available have binding posts attached to the male RS-232 plug rather than lock-down screws. This requires either physical modification of the adaptor (sometimes impossible) or the purchase of an RS-232 straight-through extension cable. However many RS-232 male-female extension cables come with null modem or crossover wiring rather than straight through. The often-recommended Keyspan adaptor does have a genuine chipset, but it does need the extension cable in order to be able to be connected. It ends up costing considerably more than the FTDI-based cables I recommend above. |
OR if you have a motor tool with a cutoff disk, then cut some of the DB9 nuts on
toggle quoted message
Show quoted text
the Power Pro. Up to the owner...I use a DB9 M/F cable. John ---------- Original Message ---------- |
You often need to trim the posts with any sort of adaptor, see:
toggle quoted message
Show quoted text
<> But with some USB to Serial adaptors you'd have to cut the whole post off and that won't do because they hold the board to the front panel and prevent physical stress damage when plugging or bumping the adaptor. -- Dave in Australia On 6 Dec 2018, at 2:51 PM, John <jonie41@...> wrote: |
A timely warning, which Marcus does mention at:
toggle quoted message
Show quoted text
<> Removal of the posts for testing needs to be done with command station cover removed to ensure no loose hardware and the posts must be replaced after testing/modification in order to avoid stress failure of solder connections etc. on the top board. Leaving them off permanently is not a viable option. -- Dave in Australia On 6 Dec 2018, at 11:42 PM, Ken Cameron <kcameron@...> wrote: |