Keyboard Shortcuts
Likes
Search
Locked NCE AUI Sensors not detecting active or inactive - timeout message
|
All my track detectors are working with proper lights on the AUIs ( I have three # 50, 51 and 53). All the sensors are properly defined with the correct JMRI addresses? (785..etc. ) in the Sensor Table. The turnout table works fine. However, I am not getting the detections and therefore occupancies reflected in the sensor table. The console error messages that come up indicate a "timeout" problem on getting a return signal from the AIUs (see snapshot of message below. 2018-11-21 01:26:12,096 jmrix.AbstractMRTrafficController???? WARN? - timeout flushes receive buffer: 30 [nce.NceTrafficController Receive thread] 2018-11-21 01:26:51,921 nce.NceSensorManager????????????????? WARN? - timeout awaiting poll response for AIU 51 [NCE Sensor Poll] 2018-11-21 01:26:51,921 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: 9B 33 consecutive timeouts = 0 in nce.NceTrafficController [nce.NceTrafficController Transmit thread] 2018-11-21 01:26:52,125 jmrix.AbstractMRTrafficController???? WARN? - timeout flushes receive buffer: 30 [nce.NceTrafficController Receive thread] 2018-11-21 01:27:31,950 nce.NceSensorManager????????????????? WARN? - timeout awaiting poll response for AIU 53 [NCE Sensor Poll] 2018-11-21 01:27:31,950 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: 9B 35 consecutive timeouts = 0 in nce.NceTrafficController [nce.NceTrafficController Transmit thread] 2018-11-21 01:27:32,154 jmrix.AbstractMRTrafficController???? WARN? - timeout flushes receive buffer: 30 [nce.NceTrafficController Receive thread] I am running Windows 10 and JMRI 4.12 and Java 1.8 on an Acer desktop with 1 Terabyte of storage. My NCE system is a Powerhouse with eprom 7.3.2 My connection is thru a NCE USB Interface Adapter.. Has anyone had a similar issue? If yes, what was the resolution? Any help would be appreciated as I plan to add signaling using NCE Lighi-its decoders as soon as I can get the occupancy detection to work in Panel Pro. Regards Mike |
|
Hi Mike, Although I am not sure that this is the actual cause of what you are experiencing, the choice of using an NCE-USB with a PH-Pro is most definitely incorrect(*). That device is specifically for the PowerCab and causes severe limitations with a PH-Pro. What you need is a serial connection to the computer. If your PC has a serial port, you can just get the simplest of cables, but if you are stuck with just USB, as most are these days, then you need to get a USB to serial connector, which will involve installing a driver. The recommended ones have an FTDI chipset, and it's not advisable to get something different. (*) Whether the NCE-USB supports AIUs at all depends on the version - V6 does not, V7 does with the right command station software version. Bottom line: do not go this way - get a serial connection, as decoder programming is notsupported whatever the version. You simply have a pointlessly crippled system. Wouter On Wed, 21 Nov 2018 at 10:50, <michelplouffe4748@...> wrote:
|
开云体育Wouter, thanks for the guidance. I will try that connection type. Mike ? From: [email protected] <[email protected]> On Behalf Of whmvd ? Hi Mike, ? Although I am not sure that this is the actual cause of what you are experiencing, the choice of using an NCE-USB with a PH-Pro is most definitely incorrect(*). That device is specifically for the PowerCab and causes severe limitations with a PH-Pro. What you need is a serial connection to the computer. If your PC has a serial port, you can just get the simplest of cables, but if you are stuck with just USB, as most are these days, then you need to get a USB to serial connector, which will involve installing a driver. The recommended ones have an FTDI chipset, and it's not advisable to get something different. ? (*) Whether the NCE-USB supports AIUs at all depends on the version - V6 does not, V7 does with the right command station software version. Bottom line: do not go this way - get a serial connection, as decoder programming is notsupported whatever the version. You simply have a pointlessly crippled system. ? Wouter ? On Wed, 21 Nov 2018 at 10:50, <michelplouffe4748@...> wrote:
|
开云体育Mike, Wouter ?is correct. I need to update this page: <> Also, as Wouter has said, 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.) These don't need a 9-pin to 9-pin adaptor cable (some brands do). Also be aware that there is a potential poor contact issue involving the Power Pro socket and any adaptor, due to an engineering issue. If you have problems with getting a response from the Power Pro, see this page: <> --? Dave in Australia On 22 Nov 2018, at 3:16 AM, michelplouffe4748@... wrote:
|
开云体育Thank you again. I purchased the serial to USB cable and had to buy a PD9 male to male adaptor cable because the Power Pro is a female plug and the serial - USB ?cable was PD9 female plug as well. ?I was able to get the sensors to detect occupancies using NCE, COM4, SB5 settings. However, I have to use COM4 which is what the disk installed and that created a conflict with my Internet port resulting in a loss of internet.. Tomorrow I will try to resolve the conflict. Cheers. Mike ? From: [email protected] <[email protected]> On Behalf Of Dave Heap
Sent: Wednesday, November 21, 2018 5:56 PM To: [email protected] Subject: Re: [jmriusers] NCE AUI Sensors not detecting active or inactive - timeout message ? Mike, ? Wouter ?is correct. I need to update this page: <> ? Also, as Wouter has said, 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.) ? These don't need a 9-pin to 9-pin adaptor cable (some brands do). ? Also be aware that there is a potential poor contact issue involving the Power Pro socket and any adaptor, due to an engineering issue. If you have problems with getting a response from the Power Pro, see this page: <> ? --? Dave in Australia
|
开云体育Mike, Those settings will get you into trouble with other features (like programming) The correct settings for a Power Pro system via the Serial Port ?are: - On the Power Pro, Set Up Command Station -- AIU Broadcast must be Disabled. -- ?RS232 Port Baud Rate must be set to 9,600 - JMRI preferences are: -- System manufacturer: NCE -- System connection: ?Serial -- Serial port: <whatever is appropriate for your setup, as per Windows Device Manager> -- Additional Connection Settings checkbox ON --- Baud rate: 9600. --- Command Station EPROM: 2006 or later (unless you have a very old system). The JMRI console log should then report V6.2.x (where "x" is most likely "1"). When you install the USB-Serial driver, the Windows installer should take care of avoiding COM port conflicts. If you bought other than the recommended USB-Serial cables, you may find that Windows capriciously changes the COM port later and you'll have to change JMRI settings to match. This is because many cables do not have a unique serial number, and is most likely to happen if you plug into a different USB port on your computer. --? Dave in Australia
|
开云体育Thanks Dave, All works fine now. Mike Canada ? From: [email protected] <[email protected]> On Behalf Of Dave Heap
Sent: Thursday, November 22, 2018 1:53 AM To: [email protected] Subject: Re: [jmriusers] NCE AUI Sensors not detecting active or inactive - timeout message ? Mike, Those settings will get you into trouble with other features (like programming) ? The correct settings for a Power Pro system via the Serial Port ?are: - On the Power Pro, Set Up Command Station -- AIU Broadcast must be Disabled. -- ?RS232 Port Baud Rate must be set to 9,600 - JMRI preferences are: -- System manufacturer: NCE -- System connection: ?Serial -- Serial port: <whatever is appropriate for your setup, as per Windows Device Manager> -- Additional Connection Settings checkbox ON --- Baud rate: 9600. --- Command Station EPROM: 2006 or later (unless you have a very old system). ? The JMRI console log should then report V6.2.x (where "x" is most likely "1"). ? When you install the USB-Serial driver, the Windows installer should take care of avoiding COM port conflicts. ? If you bought other than the recommended USB-Serial cables, you may find that Windows capriciously changes the COM port later and you'll have to change JMRI settings to match. This is because many cables do not have a unique serial number, and is most likely to happen if you plug into a different USB port on your computer. ? --? Dave in Australia ? ? On 22 Nov 2018, at 5:20 PM, michelplouffe4748@... wrote:
|
|
Windows changing the COM Port number when different USB ports are used is often an issue on portable systems where different people might plug the system together. Generally have to choose a physical USB port for the USB to serial convertor and then mark it and always use it.
You can usually change the COM port that WIndows assigns to a USB to serial convertor in the driver porperties. That might be useful if you have to use a different USB socket due to damage and dont want to change the setup on JMRI. Open Device Manager, Select Ports(COM&LPT) and double click your device e.g. "USB Serial Port(COM6)". Then in the Properties that opens select the Port Settings Tab, then the Advanced button and in there you can change the COM port number assigned to that device plugged into that USB socket. Dave |