¿ªÔÆÌåÓý

Date

Locked Re: Exception while setting Signal Logic attempting to set invalid aspect

 

Just for grins, I changed the file appearance-SL-2-high-absolute.xml to include an aspect called Diverging Approach which was a copy of Approach Diverging.? I also removed the aspect mapping for Diverging Approach at the same time.? After this, JMRI no long threw the Exception while setting Signal Logic exceptions.? This looks to me like there is a bug in the aspect mapping code somewhere.? Any other ideas?

Thanks,
Jack


Locked Re: NCE GET Macro caused loss of existing Macros and loss of existing consists

 

¿ªÔÆÌåÓý

With the NCE Power Pro, the NCE recommended ?"Clear All Advanced Consists" command (Pro Cab, under Setup Command Station) is better, much easier, safer and more thorough than trying to fix things manually in the event of problems with consists.

NCE?Clear All Advanced Consists Command:
1) Clears and resets the Consist Table in the Power Pro command station.
2) Sends an NMRA Consist Control Instruction (remove loco from consist) to short address 1 (the broadcast address). All locos currently on the layout should obey this command to the broadcast address.
3) The NMRA Consist Control Instructions are not the same DCC instruction as "Program on Main CV19", but the result in the decoder is the same. Many locos will not obey Program on Main commands to the broadcast address.
4) Should be done at least twice because some decoders (e.g. SoundTraxx and QSI) go into a slumber mode and miss the first command.
5) Some decoders (e.g. early MRC) don't support the?NMRA?Consist Control Instructions at all and need manual cleanup.
6) Some decoders (e.g. LokSound V3.5 and early V4 firmware versions) don't support the?NMRA?Consist Control Instructions sent to the broadcast address and need manual cleanup.
7) Obviously, locos currently on dead track or off-layout are not cleaned up.

--?
Dave in Australia


On 22 Nov 2018, at 3:29 AM, Wain Schroeder <niaw1@...> wrote:

consists were recreated, but not without quite a few decoders having to be placed on the Programming track to set their CV19 to 0 (wouldn't work on the Main).? It was my stupidity for forgetting the "NCE Users - don't use Macros" warning in this forum from last year, but want to relay some information that might prove helpful going forward .


Locked C/MRI serial connection issues

 

Our club has a C/MRI maxi-node with a SUSIC, eight DOUT24 output cards four DIN 24 input cards.

It is connected to a Lubuntu 18.04 system using a two port 16550 based RS-232 serial card.

While I was working with the layout editor to sequence the signals some time ago, everything was working fine.

Then my attention was diverted to other projects.

Recently, I noticed most of the signals were held at 'stop' and many of the block detectors were shown as 'active' in JMRI despite nothing in the blocks.? I don't know when the problem started.

After installing an SSD as the system drive, I have been unable to get JMRI to properly connect to the maxi-node.

The results of my troubleshooting are as follows:

1/ Lubuntu serial connection to C/MRI
  • JMRI 4.13.5
  • no activity on RX or TX indicators on SUSIC
  • slow flash on green 'heartbeat' indicator on SUSIC
  • C/MRI Monitor shows repeating sequence of INIT's followed by several polls.

2/ WIndows 10 laptop with USB - RS-232 connection to C/MRI (connected at computer end of cable)
  • JMRI 4.12
  • RX and TX indicators active
  • slow flash on green 'heartbeat' indicator on SUSIC
  • able to set signal aspects
  • all sensors show as 'unknown'
  • C/MRI Monitor shows repeated polls without replies and signal aspect messages when signal table value changed

3/ Lubuntu with connection via USB - RS-323 adapter to C/MRI (as in 2 above)
  • reverted to JMRI 4.12
  • RX and TX indicators on SUSIC active
  • slow flash on green 'heartbeat' indicator on SUSIC
  • able to set signal aspects
  • all sensors show as 'unknown'
  • C/MRI Monitor shows repeated polls without replies and signal aspect messages when signal table value changed
Any suggestions on resolving this problem would be appreciated.



Tom


Locked Exception while setting Signal Logic attempting to set invalid aspect

 

JMRI version: 4.13.4 and 4.12
Java version:?1.8.0_171
MacOS: Version 10.13

I've been working on a small physical layout connected to JMRI to understand signaling and LCC.? I've been using SML with Signal Masts assigned to turnouts.? I've used the Autogenerate features of SML logic to generate mast pairs, logic, and sections.? The layout includes 12 turnouts.? The turnouts operate in pairs of crossovers.? The problem is when I exercise the turnouts, under certain situations, I get an exception like "19:42:45.476 (246382) ERROR [AWT-EventQueue-0] DefaultSignalMastLogic.java:974? - Exception while setting Signal Logic attempting to set invalid aspect: Diverging Approach on mast: Turnout Left Near 2A".

Turnout Left Near 2A is a Signal Mast using N&W 1981 Signal System with Mast Type: Color Light 2 Arm Absolute Mast Signal.? The Mast Driver is currently Virtual Mast because I have no hardware at the moment.?

The Mast Type supports aspects: Clear, Approach Diverging, Advance Approach, Diverging Clear, Approach, Restricting, and Stop and Stay.? When I look at the JMRI/xml/signals/NW-1981/appearance-SL-2-high-absolute.xml, I see that the file has an aspectMapping for "Diverging Approach" that maps to "Approach Diverging".? I would expect this mapping to take care of setting the Mast to state Approach Diverging when JMRI sends it state "Diverging Approach".? Am I missing something?? Why is JMRI throwing this exception?

I've copied my Main Yard panel file here:?/g/jmriusers/files/Exception%20while%20setting%20Signal%20Logic/Main%20Yard.xml

Thanks for your help.


Locked Re: Caboose load status not printing

 

David,

In the next test release 4.13.5, I've added check boxes to the "Manifest Print Options" window that will allow you to the show caboose and passenger car loads .

Dan


Locked Re: NCE GET Macro caused loss of existing Macros and loss of existing consists

 

Wain,

It looks to me that the NCE command station crashed. Other than the Macro tool, was anything else communicating with the NCE command station?? The console shows a timeout to a valid macro memory address in the command station.? I don't see anything wrong with the message.? However, the NCE command station might have seen something else, as the message timed out, which means the command station failed to response to our request to write to macro memory.

Dan


Locked what is needed for seeing a train running on a physical layout through the computer?

 

Dave?
I have been using JMRI for a while now, but I cannot seem to get where I want to be. I have a Digitrax system, DCS50, Windows Vista RR-Cirkits and loconet. I believe Dave has my layout (George Layout) information that I sent to him several weeks back. I have some blocks, but I do not know whether they are working or not. I have a BD1 connected through a DS64 and when I run an engine around, only one LED stays lit and none of the other 4 come on or go off. I understand that is a problem as it shows that my blocks are not yet right.
What I want to do is be able to run my trains, and see the train locations on the computer by the track going occupied. What do I need to do to get this going? I am hoping that Dave can help me get going since he has already helped me with the layout.
Thanks,
George Pendergraft


Locked Re: Problem exporting and importing the roster

 

Your fallback method (copying the "roster" folder) is the one I prefer.

The Export Complete Roster option takes a long time to complete (with no busy/completed feedback) and actually produces a ZIP file. If you manually give it a ".zip" extension you can look inside it. It's also very tedious to import a large roster as it prompts for each entry.

Some useful information links about JMRI file structure:
<>
<>
--
Dave in Australia

On 22 Nov 2018, at 9:05 AM, Marshall <readingrr2103@...> wrote:

Eventually, I gave up and copied all the files in the roster folder to the flash drive and on the new Windows system, copied them into the roster folder. I then did the option the Rebuild the Roster. Everything worked and all of the engines were in the roster on the new system.

There were over 300 engines that needed to be exported to the new windows 10 system

I either was doing something wrong when exporting the roster or there is a "bug".


Locked Re: Caboose load status not printing

 

/g/jmriusers/message/153685

There are only 4 messages in the original thread. Your answer is in the second message.

/g/jmriusers/message/153695

--
Peter Ulvestad

JMRI Users Group Moderator - ( )
Tam Valley Group Moderator - ( )
Sprog-DCC Group Moderator - ( )
Edmonton Model Railroad Association -


Locked Re: 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

On 22 Nov 2018, at 3:16 AM, michelplouffe4748@... wrote:

Wouter, thanks for the guidance. I will try that connection type. Mike

?

From: [email protected] <[email protected]> On Behalf Of whmvd
Sent: Wednesday, November 21, 2018 7:13 AM
To: [email protected]
Subject: Re: [jmriusers] NCE AUI Sensors not detecting active or inactive - timeout message

?

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.


Locked Re: Caboose load status not printing

 

Greetings all;

My first note of this snag seemed to have been co-opted to the discussion of some other problem - so I'm re-printing it.

------------------------------------------------------

Another very minor bug I've been experiencing:
When a caboose is assigned to a train, the car shows on the 'Cars' page with
the load status I have set - normally either 'E', or the custom load 'Crew'.
However, when the manifest is previewed or printed, the 'load' column is always
blank.

David


Locked Logix Change Doesn't Always Trigger Signal Head Change

 

I have numerous logix running on my layout and have for years.? I recently have added several signal heads and more logix to go with them.? Every once in a while, when the logix controlling a signal head changes state (for example, calculating that the signal should be green when it had been showing red previously), the signal head doesn't make the change.? In other words, the logix calculates the proper change and the conditional that triggers the change to green shows true in the logix (and is the only "true" in the logix), but the signal head table doesn't get the message and continues to display red.? Eventually, something eventually tirggers the signal head to make the change, but it seems to require some other event on the layout to occur before that happens.? I haven't been able to figure out what eventually gets the change to happen.

For the most part, this signal head is working properly.? It's just on rare instances that it doesn't seem to get the message to the signal head table.

Any ideas on why the signal head table doesn't always reflect the change calculated by the logix?

I believe that I am using the latest production version of JMRI.


Locked Problem exporting and importing the roster

 

Hi,
Today I attempted to export the roster from one computer to a new computer.? They are both Windows 10 and JMRI on both is 4.12.

I used the "Export Roster" option and the "Import Roster" options.

Although the Export seemed to work, here is what I observed:

1.? A window came up with a blank line to enter a file name (I'm assuming).? I entered one, Roster1.? On the flash drive I go Roster1roster. ?? Using a Windows window to rename the file, Windows say no way as something in JMRI did not release the file.? I think it was the Java run time library.? Not until I exited the Export window was I able to rename the file.? I tried it again giving a filename of roster.xml as mentioned on the JMRI.ORG web pages.? What I got was roster.xmlroster.? I renamed the file to roster.xml.
2.? The import failed telling me the file was basically "garbage". I edited the file with notepad++ and it was unintelligible.? There were errors in the console log related to this problem, but I had do way of capturing it as it was a club computer.
3.? I tried exporting a single roster entry and that worked as one would expect.? Also I did not get the problem the the export window has not "released" file, like I got on export of the roster.

Eventually, I gave up and copied all the files in the roster folder to the flash drive and on the new Windows system, copied them into the roster folder.? I then did the option the Rebuild the Roster. Everything worked and all of the engines were in the roster on the new system.

There were over 300 engines that needed to be exported to the new windows 10 system

I either was doing something wrong when exporting the roster or there is a "bug".

Have a Happy Thanksgiving and don't forget to roll back the scale 10lbs.

Marshall


Locked Re: Is there any way to add time stamp to SensorLog.py? #scripting

 

Dave and Cliff,

I was having some issues finding the lines you suggested Cliff, then saw Dave's suggestion and followed that.? It works as requested!!? Thank you for the quick reply and help, both of you!!

Regards,
Wain


Locked Re: Is there any way to add time stamp to SensorLog.py? #scripting

 

Wain,

An alternate solution to Cliff¡¯s approach.

Add "import time¡±

Change the print line:

print time.strftime("%Y-%m-%d %H:%M:%S"), mesg


Dave Sand

On Nov 21, 2018, at 9:09 AM, Wain Schroeder <niaw1@...> wrote:

Hi,

I have recently started using SensorLog.py as a tool to validate block assignments on our layout and it works quite well, thank you. The only change I would like to see would be to add a time stamp to the output line when a sensor is triggered (ACTIVE/INACTIVE). I'd be more than glad to do this modification myself, but am not familiar with coding of py-type scripts and am afraid I'd really mess things up if I do attempt it without guidance.

Here is an example of how I would like to see this enhancement:

2018-11-20 18:53:17, Sensor LS123 from INACTIVE to ACTIVE
2018-11-20 18:53:52, Sensor LS123 from ACTIVE to INACTIVE

BTW - using PanelPro version 4.12+Rb6a9bb1 under Java 1.8.0_151 on Windows 7 amd64 v6.1

Thanks in advance,

Wain Schroeder


Locked Re: Is there any way to add time stamp to SensorLog.py? #scripting

 

The Preview seen on my screen prior to sending is not always in agreement with what is reported at the groups.io website

2018-11-21 09:24:41,939 script.SensorLog INFO - Sensor NS550 (East Yard) from INACTIVE to ACTIVE [AWT-EventQueue-0]

2018-11-21 09:24:52,235 script.SensorLog INFO - Sensor NS550 (East Yard) from ACTIVE to INACTIVE [AWT-EventQueue-0]

Double blanks and double CR characters seem to be squeezed. Maybe the snip from the log file will work better this time??

Cliff in Baja SoCal (still having mistakes with the markdown features)


Locked Re: Is there any way to add time stamp to SensorLog.py? #scripting

 

Wain,

The modifications suggested here approximate what you asked for and were developed several months ago. The only tests that I have performed were on Digitrax DCS200 and NCE simulator. These modifications assume that you are comfortable editing a script. If not, then I can send a complete SensorLogMod.py file off list.

Immediately after the line:

import java.beans

copy these lines:

import org.apache.log4j

LogfileWrite = org.apache.log4j.Logger.getLogger("jmri.jmrit.jython.exec.script.SensorLog")

then at what was line # 41 change from:

        print mesg

to:

#        print mesg
        LogfileWrite.info ( mesg )

After that is saved with a new name and in your local jmri\python folder then executed, you should see something like:

2018-11-21 09:24:41,939 script.SensorLog INFO - Sensor NS550 (East Yard) from INACTIVE to ACTIVE [AWT-EventQueue-0]
2018-11-21 09:24:52,235 script.SensorLog INFO - Sensor NS550 (East Yard) from ACTIVE to INACTIVE [AWT-EventQueue-0]

on your System Console and you Session.log file.

Cliff in Baja SoCal (still having mistakes with the markdown features)


Locked Re: Question about defining double crossovers

 

I may be totally off base since I am a newbie.? It was my understanding that (when using 4 motors) the "supporting turnout" was used to indicate the "pair" to select a route across the crossover.? Maybe if you remove the "supporting turnout" on one route, that the other may be able to be defined correctly.
Just a thought, Woody


Locked NCE GET Macro caused loss of existing Macros and loss of existing consists

 

Hi,

The use of macros in JMRI with the NCE PowerHouse command station has been a problem for several years and even as late as last year it was advised not to use the feature.? Last night, in preparation for our upcoming Open House sessions starting Tuesday, we had some new macros that needed adding and while attempting to use the NCE Macros "Get" feature, our entire set of macros (60+) and all existing consists (20+) were? wiped out, much to my chagrin.? All macros have been restored manually, and consists were recreated, but not without quite a few decoders having to be placed on the Programming track to set their CV19 to 0 (wouldn't work on the Main).? It was my stupidity for forgetting the "NCE Users - don't use Macros" warning in this forum from last year, but want to relay some information that might prove helpful going forward .

Details:? As the log shows below, I was doing some work on sensor assignments and was using the?SensorLog.py to log sensor activity in the System Console.? A co-worker asked if we could modify existing macros and add new ones using JMRI in our NCE PowerHouse environment; since I was able to read macro assignments using the NCE/Edit Macro feature in JMRI, I said "sure" and proceeded to attempted a new macro.? It appeared that I was able to successfully add a new macro, but when I went back to modify it, the System Console started spitting out errors? and I heard a steam engine on the layout start up at full speed. We ran up to the layout and shut the power off to the layout immediately.? It was after we turned the power back on that we realized that all our macros were no longer in the NCE Command Station.? Based on that discovery, we checked a couple of consisted engines and found that they were no longer consisted.? Bottom line:? the command station lost all macro and consist data.? Quite a few locos no longer responded to their address, even though we set Program on the Main CV19 to 0.? We had to take those locos (non-LokSound decoders)? to the Programming track, then were able to reset CV19 to 0, AND reset their road number to its respective value (didn't check, but I suspect they had been returned to "3" default by the system burp).? Two of us were able to re-input all existing macros and all new ones using our NCE hammerhead throttles (there's more discussion on restoring macros in this forum either early last year or earlier).

Bottom line:? if you don't want to risk losing your macro and consist data in your NCE system, don't use the NCE macros feature in JMRI!? I hope the info above and the log below will help the macro developer in determining what the problem is.? Any and all help in resolving the long standing macro issue will be greatly appreciate going forward, but we already know how to avoid having another incident like last night -?don't use the NCE macros feature in JMRI.

Thanks in advance,

Wain Schroeder

JMRI?PanelPro version 4.12+Rb6a9bb1 with?Java 1.8.0_151 on Windows 7

Happened to have System Console on at the time to track sensor activation.? I have opened a different topic in this forum to add a time stamp to the SensorGroupAutoItem.py script which might have been helpful in the log below.? Here is the entire log - the problem started at?2018-11-20 19:20:18 and we immediately shut the layout down once we saw the errors and heard one engine start up that had previously not been running:

2018-11-20 18:52:58,751 util.Log4JUtil??????????????????????? INFO? - * JMRI log ** [main]
2018-11-20 18:52:58,766 util.Log4JUtil??????????????????????? INFO? - This log is appended to file: C:\Users\Owner\JMRI\log\messages.log [main]
2018-11-20 18:52:58,766 util.Log4JUtil??????????????????????? INFO? - This log is stored in file: C:\Users\Owner\JMRI\log\session.log [main]
2018-11-20 18:52:58,766 apps.Apps???????????????????????????? INFO? - PanelPro version 4.12+Rb6a9bb1 starts under Java 1.8.0_151 on Windows 7 amd64 v6.1 at Tue Nov 20 18:52:58 EST 2018 [main]
2018-11-20 18:52:58,969 apps.Apps???????????????????????????? INFO? - Starting with profile My_JMRI_Railroad.3f7af828 [main]
2018-11-20 18:52:59,094 node.NodeIdentity???????????????????? INFO? - Using jmri-msZGsckaWhNiaaDcUlQUS5-3f7af828 as the JMRI Node identity [AWT-EventQueue-0]
2018-11-20 18:52:59,219 xml.AbstractSerialConnectionConfigXml INFO? - Starting to connect for "NCE" [main]
2018-11-20 18:52:59,390 serialdriver.SerialDriverAdapter????? INFO? - NCE COM1 port opened at 9600 baud [main]
2018-11-20 18:52:59,437 xml.AbstractSerialConnectionConfigXml INFO? - Starting to connect for "LocoNet" [main]
2018-11-20 18:52:59,546 locobufferusb.LocoBufferUsbAdapter??? INFO? - LocoBuffer-USB adapter set hardware flow control, mode=2 RTSCTS_OUT=2 RTSCTS_IN=1 [main]
2018-11-20 18:52:59,546 locobuffer.LocoBufferAdapter????????? INFO? - COM3 port opened at 57600 baud with DTR: true RTS: true DSR: true CTS: true? CD: false [main]
2018-11-20 18:52:59,562 nce.NceConnectionStatus?????????????? INFO? - NCE EPROM revision = 6.2.1 [AWT-EventQueue-0]
2018-11-20 18:52:59,609 loconet.LnPacketizer????????????????? INFO? - lnPacketizer Started [main]
2018-11-20 18:52:59,874 apps.PerformFileModel???????????????? INFO? - Loading file C:\Users\Owner\JMRI\CCMR.xml [main]?
2018-11-20 18:53:11,333 util.FileUtilSupport????????????????? INFO? - File path program: is C:\Program Files (x86)\JMRI\ [main]
2018-11-20 18:53:11,333 util.FileUtilSupport????????????????? INFO? - File path preference: is C:\Users\Owner\JMRI\ [main]
2018-11-20 18:53:11,333 util.FileUtilSupport????????????????? INFO? - File path profile: is C:\Users\Owner\JMRI\My_JMRI_Railroad\ [main]
2018-11-20 18:53:11,333 util.FileUtilSupport????????????????? INFO? - File path settings: is C:\Users\Owner\JMRI\ [main]
2018-11-20 18:53:11,333 util.FileUtilSupport????????????????? INFO? - File path home: is C:\Users\Owner\ [main]
2018-11-20 18:53:11,333 util.FileUtilSupport????????????????? INFO? - File path scripts: is C:\Program Files (x86)\JMRI\jython\ [main]
2018-11-20 18:53:12,565 PanelPro.PanelPro???????????????????? INFO? - Main initialization done [main]
2018-11-20 18:53:17,136 script.JmriScriptEngineManager??????? INFO? - python 2.7 is provided by jython 2.7.0 [AWT-EventQueue-0]
2018-11-20 18:53:17,151 script.JmriScriptEngineManager??????? INFO? - ECMAScript ECMA - 262 Edition 5.1 is provided by Oracle Nashorn 1.8.0_151 [AWT-EventQueue-0]
226 turnouts found, 50 changed to CLOSED
Sensor LS123 from INACTIVE to ACTIVE
Sensor LS123 from ACTIVE to INACTIVE
Sensor LS123 from INACTIVE to ACTIVE
Sensor LS123 from ACTIVE to INACTIVE
Sensor LS123 from INACTIVE to ACTIVE
Sensor LS123 from ACTIVE to INACTIVE
Sensor LS123 from INACTIVE to ACTIVE
Sensor LS145 from INACTIVE to ACTIVE
Sensor LS145 from ACTIVE to INACTIVE
Sensor LS123 from ACTIVE to INACTIVE
Sensor LS145 from INACTIVE to ACTIVE
Sensor LS123 from INACTIVE to ACTIVE
Sensor LS123 from ACTIVE to INACTIVE
Sensor LS123 from INACTIVE to ACTIVE
Sensor LS123 from ACTIVE to INACTIVE
Sensor LS147 from INACTIVE to ACTIVE
Sensor LS145 from ACTIVE to INACTIVE
Sensor LS145 from INACTIVE to ACTIVE
Sensor LS147 from ACTIVE to INACTIVE
Sensor LS147 from INACTIVE to ACTIVE
Sensor LS145 from ACTIVE to INACTIVE
2018-11-20 19:06:19,089 palette.ItemPalette?????????????????? ERROR - getIconMap failed. family "UTCS" not found in item type "IndicatorTrack" [AWT-EventQueue-0]
Sensor LS146 from INACTIVE to ACTIVE
Sensor LS147 from ACTIVE to INACTIVE
Sensor LS146 from ACTIVE to INACTIVE
Sensor LS146 from INACTIVE to ACTIVE
Sensor LS147 from INACTIVE to ACTIVE
Sensor LS146 from ACTIVE to INACTIVE
Sensor LS146 from INACTIVE to ACTIVE
Sensor LS147 from ACTIVE to INACTIVE
Sensor LS146 from ACTIVE to INACTIVE
Sensor LS128 from INACTIVE to ACTIVE
Sensor LS113 from INACTIVE to ACTIVE
Sensor LS114 from INACTIVE to ACTIVE
Sensor LS115 from INACTIVE to ACTIVE
2018-11-20 19:20:10,567 jmri.Block??????????????????????????? WARN? - count of 2 ACTIVE neightbors with proper direction can't be handled for block LS116 but maybe it can be determined when another block becomes free [AWT-EventQueue-0]
Sensor LS116 from INACTIVE to ACTIVE
Sensor LS117 from INACTIVE to ACTIVE
Sensor LS119 from INACTIVE to ACTIVE
Sensor LS120 from INACTIVE to ACTIVE
Sensor LS121 from INACTIVE to ACTIVE
Sensor LS123 from INACTIVE to ACTIVE
2018-11-20 19:20:10,738 jmri.Block??????????????????????????? WARN? - count of 3 ACTIVE neightbors with proper direction can't be handled for block LS124 but maybe it can be determined when another block becomes free [AWT-EventQueue-0]
Sensor LS124 from INACTIVE to ACTIVE
Sensor LS126 from INACTIVE to ACTIVE
Sensor LS146 from INACTIVE to ACTIVE
Sensor LS147 from INACTIVE to ACTIVE
Sensor LS148 from INACTIVE to ACTIVE
Sensor LS151 from INACTIVE to ACTIVE
2018-11-20 19:20:11,518 jmri.Block??????????????????????????? WARN? - count of 2 ACTIVE neightbors with proper direction can't be handled for block LS152 but maybe it can be determined when another block becomes free [AWT-EventQueue-0]
Sensor LS152 from INACTIVE to ACTIVE
Sensor LS153 from INACTIVE to ACTIVE
Sensor LS154 from INACTIVE to ACTIVE
Sensor LS155 from INACTIVE to ACTIVE
Sensor LS156 from INACTIVE to ACTIVE
Sensor LS157 from INACTIVE to ACTIVE
Sensor LS158 from INACTIVE to ACTIVE
Sensor LS159 from INACTIVE to ACTIVE
Sensor LS160 from INACTIVE to ACTIVE
Sensor LS145 from INACTIVE to ACTIVE
Sensor LS95 from INACTIVE to ACTIVE
Sensor LS96 from INACTIVE to ACTIVE
2018-11-20 19:20:11,955 jmri.Block??????????????????????????? WARN? - count of 3 ACTIVE neightbors with proper direction can't be handled for block LS81 but maybe it can be determined when another block becomes free [AWT-EventQueue-0]
Sensor LS81 from INACTIVE to ACTIVE
Sensor LS82 from INACTIVE to ACTIVE
Sensor LS83 from INACTIVE to ACTIVE
2018-11-20 19:20:11,955 jmri.Block??????????????????????????? WARN? - count of 5 ACTIVE neightbors with proper direction can't be handled for block LS84 but maybe it can be determined when another block becomes free [AWT-EventQueue-0]
Sensor LS84 from INACTIVE to ACTIVE
Sensor LS85 from INACTIVE to ACTIVE
Sensor LS86 from INACTIVE to ACTIVE
Sensor LS87 from INACTIVE to ACTIVE
Sensor LS88 from INACTIVE to ACTIVE
Sensor LS89 from INACTIVE to ACTIVE
Sensor LS90 from INACTIVE to ACTIVE
Sensor LS107 from INACTIVE to ACTIVE
Sensor LS91 from INACTIVE to ACTIVE
Sensor LS92 from INACTIVE to ACTIVE
Sensor LS110 from INACTIVE to ACTIVE
2018-11-20 19:20:12,174 jmri.Block??????????????????????????? WARN? - count of 2 ACTIVE neightbors with proper direction can't be handled for block CP LK - CP Riverside EB but maybe it can be determined when another block becomes free [AWT-EventQueue-0]
2018-11-20 19:20:12,174 jmri.Block??????????????????????????? WARN? - count of 2 ACTIVE neightbors with proper direction can't be handled for block LS93 but maybe it can be determined when another block becomes free [AWT-EventQueue-0]
Sensor LS93 from INACTIVE to ACTIVE
Sensor LS111 from INACTIVE to ACTIVE
2018-11-20 19:20:12,174 jmri.Block??????????????????????????? WARN? - count of 2 ACTIVE neightbors with proper direction can't be handled for block LS94 but maybe it can be determined when another block becomes free [AWT-EventQueue-0]
Sensor LS94 from INACTIVE to ACTIVE
Sensor LS112 from INACTIVE to ACTIVE
Sensor LS97 from INACTIVE to ACTIVE
2018-11-20 19:20:12,252 jmri.Block??????????????????????????? WARN? - count of 2 ACTIVE neightbors with proper direction can't be handled for block CY-EB-3 but maybe it can be determined when another block becomes free [AWT-EventQueue-0]
Sensor LS99 from INACTIVE to ACTIVE
Sensor LS144 from INACTIVE to ACTIVE
Sensor LS129 from INACTIVE to ACTIVE
Sensor LS130 from INACTIVE to ACTIVE
2018-11-20 19:20:12,439 jmri.Block??????????????????????????? WARN? - count of 2 ACTIVE neightbors with proper direction can't be handled for block LS131 but maybe it can be determined when another block becomes free [AWT-EventQueue-0]
Sensor LS131 from INACTIVE to ACTIVE
Sensor LS132 from INACTIVE to ACTIVE
Sensor LS133 from INACTIVE to ACTIVE
2018-11-20 19:20:12,517 jmri.Block??????????????????????????? WARN? - count of 2 ACTIVE neightbors with proper direction can't be handled for block Main Rear WB but maybe it can be determined when another block becomes free [AWT-EventQueue-0]
Sensor LS134 from INACTIVE to ACTIVE
Sensor LS135 from INACTIVE to ACTIVE
Sensor LS136 from INACTIVE to ACTIVE
Sensor LS137 from INACTIVE to ACTIVE
Sensor LS138 from INACTIVE to ACTIVE
Sensor LS139 from INACTIVE to ACTIVE
2018-11-20 19:20:18,492 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: 99 CE 28 00 00 00 00 consecutive timeouts = 0 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:20:28,495 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AD 02 58 04 00 consecutive timeouts = 1 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:20:38,510 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AD 02 58 04 00 consecutive timeouts = 2 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:20:48,728 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 3 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:20:48,931 nce.NceConnectionStatus?????????????? WARN? - Incorrect or no response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:20:58,933 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 4 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:20:59,136 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:21:09,136 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 5 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:21:09,339 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:21:19,354 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 6 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:21:19,557 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
Sensor LS156 from ACTIVE to INACTIVE


Locked Re: NCE AUI Sensors not detecting active or inactive - timeout message

 

¿ªÔÆÌåÓý

Wouter, thanks for the guidance. I will try that connection type. Mike

?

From: [email protected] <[email protected]> On Behalf Of whmvd
Sent: Wednesday, November 21, 2018 7:13 AM
To: [email protected]
Subject: Re: [jmriusers] NCE AUI Sensors not detecting active or inactive - timeout message

?

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:


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