¿ªÔÆÌåÓý

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


 

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


 

¿ªÔÆÌåÓý

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 .


 

Dan,

I agree with you on the fact that the command station crashed.? Trying to think of what else was going on at the time other than JMRI monitoring turnout status (all turnouts are set to "monitoring") and as you can see in the log, we have over 225 turnouts being monitored.? We also have Digitrax connections with JMRI for signaling and block detection.? No one was running any locos on the layout at the time, although at least 10 to 15 engines were sitting on powered tracks, a lot with sound functions on.; BTW - we have 3 or 4 power boosters on the layout.

I just noticed that my initial post didn't contain the entire grouping of errors, which I will include in this reply, but the errors appear to be the same as what show up above.? If we hadn't been playing with the macro editor at the time, I would feel a lot more paranoid about the crash because we WERE adding new block detection in JMRI panels, but that would only be in JMRI and not in the command station IMHO.? I'm hoping it was my Impatient User actions on the macro editor screen that caused the command station to time out, along with the belief that the NCE macros to JMRI interface still has a problem.

Thanks for the reply!
Wain

Sensor LS121 from ACTIVE to INACTIVE
2018-11-20 19:21:29,559 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 7 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:21:29,590 jmrix.AbstractMRTrafficController???? WARN? - timeout flushes receive buffer:? [nce.NceTrafficController Receive thread]
2018-11-20 19:21:29,637 jmrix.AbstractMRTrafficController???? ERROR - unsolicited character received: 0 [nce.NceTrafficController Receive thread]
2018-11-20 19:21:29,637 jmrix.AbstractMRTrafficController???? ERROR - unsolicited character received: 0 [nce.NceTrafficController Receive thread]
2018-11-20 19:21:29,793 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:21:39,794 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 0 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:21:39,997 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:21:50,012 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 1 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:21:50,215 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:21:50,246 jmrix.AbstractMRTrafficController???? WARN? - timeout flushes receive buffer:? [nce.NceTrafficController Receive thread]
2018-11-20 19:22:00,216 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 2 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:22:00,419 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:22:10,420 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 3 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:22:10,623 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:22:20,638 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 4 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:22:20,841 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:22:20,872 jmrix.AbstractMRTrafficController???? WARN? - timeout flushes receive buffer: 00 00 [nce.NceTrafficController Receive thread]
2018-11-20 19:22:30,843 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 5 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:22:31,045 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:22:41,047 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 6 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:22:41,250 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:22:51,265 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 7 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:22:51,468 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:23:01,483 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 8 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:23:01,686 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:23:11,689 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 9 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:23:11,892 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:23:11,923 jmrix.AbstractMRTrafficController???? WARN? - timeout flushes receive buffer: 00 00 [nce.NceTrafficController Receive thread]
2018-11-20 19:23:21,908 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 10 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:23:22,110 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:23:32,126 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 11 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:23:32,328 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:23:42,332 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 12 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:23:42,535 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:23:52,550 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 13 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:23:52,753 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:24:02,768 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 14 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:24:02,971 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:24:12,972 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: AA consecutive timeouts = 15 in nce.NceTrafficController [nce.NceTrafficController Transmit thread]
2018-11-20 19:24:13,175 nce.NceConnectionStatus?????????????? WARN? - No response from NCE command station [nce.NceTrafficController Transmit thread]
2018-11-20 19:24:13,206 jmrix.AbstractMRTrafficController???? WARN? - timeout flushes receive buffer: 00 00 [nce.NceTrafficController Receive thread]


 

Dave,

Thanks for the info on the?NCE?Clear All Advanced Consists Command

We obviously don't want to execute this now that we've rebuilt all the consists after the crash, but will keep it in mind should something like this happen again (praying that it doesn't).? I, personally didn't go through any single locos to see if they were impacted, just the consisted ones.? I'll try to get out to the club on Friday or Sunday and do that.? I do know that the loco that "ran away" during the crash did respond ok afterwards though.? I will be checking its CV29 for NMRA Digital Only.

Wain


 

The prior behavior of the macro editor, while it was broken, fit your
description. What would happen is it would effectively wipe the memory in
the command station. What I don't recall is which version JMRI was the first
one with the fix. So that is the thing to confirm, when was it fixed and
which version you had. I think you said 4.12.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org


 

Ken,

Good catch, the NCE macro was fixed in 4.13.1.

Dan


 

Ken and Dan,

Yes, we are running 4.12 currently.? I see that there is a 4.13.5 test release, but do not see a 4.13 production release (I see it might be a December release time frame though).? I can try to load 4.13.5 but we are just starting our 2018/2019 Open House season -we're located near Lock Haven, PA if anyone is interested (www.ccmrr.org/events.html) - and I don't think the club would like to try anything new right now.

Ken - thanks for confirming the symptom(s) - first and last time I remember seeing this behavior, so hoping nothing similar occurs during Open House (yes - I WILL stay away from macros in JMRI 4.12!).

Regards,
Wain Schroeder


 

Wain,

The 4.13.* series is our beta versions that will turn into 4.14 coming out
in December. We figured out the fix just after the 4.12 production version
was released. The bug was known, but not the fix.

Right now the 4.13.5 is close to what will be 4.14 in another month. Either
make completely sure to not try the macro command or update to 4.13.5. I
would update, it means you don't have to worry about somebody trying it.
Also there are the usual new decoders that would be found that have been
created since the beginning of summer.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org


 

PS: Our number system is that even numbers, like 4.10, 4.12, 4.14 are
production versions. 4.11.* was the beta series that became 4.12, 4.13.* is
what becomes 4.14.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org


 

Ken,

I have downloaded and installed 4.13.5 on my home computer.? If time permits on or before Tuesday, I'll install it on the club's JMRI computer too.?

Thanks for your help!

Wain Schroeder

Clinton Central Model Railroad

www.ccmrr.org