Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Locked L1USB Ethernet Adapter Error ? Help
|
I would be very grateful for some help to identify the cause of the console error below which I have been trying to resolve for many weeks:-
jmrix.AbstractMRTraffic Controller ? ERROR - Auto Recovery from Error Message: 01 01 01 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? Retransmitted 0 Times ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? [liusbethernetXnetPacketizer Receive thread]? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? INFO - Message added back to queue 52 1F 8D C1 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? liusbethernet.L1USBEthernetXnetPacketizer ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? Transmit thread This message may be repeated several times but only occurs when there is a logix. Can somebody convert this to something more understandable for the less educated !! ? The PanelPro layout which has Turnout, Sensor, Signal Head and Block Tables does not show any errors until logix is added, then when the first table entry is completed an error may appear (i.e it doesn't happen every time,? similarly when the logix state is changed an error may occur.) I have checked the adapter, i.e. the red XpressNet LED is on and the greed ethernet LED is lit.? Sensor debounce is set to global. Operating turnouts etc.,does not produce errors except when a logix is involved. I have tried to capture the console error and XpressNet Monitor events and have put the screenshot in the photo file.? (Console error-XpressNet Inf) JMRI 4.12+Rb6a99b1 ? ?? Java 1.8.0_181 Windows 10 ? HP 290 G1 MT Lenz LZV100 v 3.6 Thank you for any help or advice Alan Gibbs |
|
Alan,
toggle quoted message
Show quoted text
I don’t have any insight into the communication errors, but I am curious about the Logix correlation. Instead of the editing the Logix, select Browse. That will display the Logix in a text format. Select and copy the contents of the window and paste it in a reply. There might be something in the Logix definition that contributes to the problem. Dave Sand On Aug 5, 2018, at 3:04 PM, Alan Gibbs <buggydriver17@...> wrote: |
On Aug 5, 2018, at 4:04 PM, Alan Gibbs <buggydriver17@...> wrote:That specific message tells us that there was a communication error between the computer and the computer interface ( either a timeout or corrupt data ) and we are automatically retransmitting the data to recover. ( that first message really should be an INFO message, just like the second one ) As to why this occurs when your logix is added or updates, the most likely cause is a flood of traffic between the Computer and the LIUSB-Ethernet. Paul |
|
Hi Paul, ?? I mentioned in an earlier message that I hadn't been able to recover a largely working layout from a number of changes and updates etc., most of which were relatively minor, however it did include making a separate JK accessory bus and all solid state PC.
During this time we had a lightening strike which destroyed the router; given your comments and seeing that XpressNet Traffic Monitor shows a lot of "Normal Operations Resumed after timeout" message I think there is a possibility that the adapter was damaged by the lightening strike.? I assume that we do not have a way of testing it ?? The replacement PC is unlikely to be the cause as it was not installed at that time.? Most things I've been through in fine detail so there isn't much else other than the LZV100! Best regards, Alan |
|
Dave, ? I don't save logix if I know there are errors, but I this is one which does:-
?IX:AUTO:0001C1? C1?? ?? Antecedent: (R1 and R2) or (R3 and R4)? ??? [x]? R1? IF? Turnout "pt01" state is "Turnout Closed"?? ??? [x]? R2??? AND Sensor "senblk1" state is "Sensor Inactive"?? ??? [x]? R3??? AND Turnout "pt01" state is "Turnout Thrown"?? ??? [x]? R4??? AND Sensor "senblk5" state is "Sensor Inactive"?? ???????????? THEN?? ?????????????? On Change To True, Set Signal Head Appearance, "IH01" to Green?? ?????????????? On Change To False, Set Signal Head Appearance, "s1r/gn" to Red I am beginning to suspect its the 23151 adapter that's faulty. Regards, Alan ? |
|
Alan,
toggle quoted message
Show quoted text
I don’t see any issues with the Logix. I am assuming that IH01 and s1r/gn are the same head, that the head is defined as a turnout based signal head and the supporting turnouts are not pt01. If you can re-create the communication error by changing the head appearance in the signal head table without a Logix defined, that would eliminate Logix as a possible source of the problems. Dave Sand On Aug 8, 2018, at 12:37 AM, Alan Gibbs <buggydriver17@...> wrote: |
|
On 08/07/2018 04:49 AM, Alan Gibbs wrote:
During this time we had a lightening strike which destroyed theDon't assume that the "Normal Operations Resumed after timeout" message means there is a problem. The Lenz interfaces (all of them) send that message to the computer for any message which the XPressNet manual says the LZV100 doesn't send a response.? So it's actually normal to see that.? This is why the full message we put in the XPressNet log is: "Command Successfully Sent/Normal Operations Resumed after timeout" (we don't know what caused it, only that we received it). We do know that the command was actually received by the interface because there is a raw XPressNet response (from the command station) that triggers this.? The raw XPressNet commands include device addresses.? We never see anything but the payload of the messages addressed to the computer interface. ? I assume that we do not have a way of testing it ?If you can do things like turn the power on and off on the system or control a throttle, then there isn't anything wrong with the interface. The replacement PC is unlikely to be the cause as it was not installedAs I stated already in this thread, that "01 01 00" error you are seeing is not being generated by the LZV100.? It is generated by the computer interface. What it tells us (per the manual) is that when the computer interfaced received the last message from the computer, the message was corrupted.? Our response is to automatically send the message again (which causes the error message you posted earlier).? If this is ALL you see in the logs (and this WILL show up in the XPressNet logs), then there is something wrong on the path between the computer and the LIUSB-Ethernet. If this is only happening every once in a while, there may be some intermittent external source of interference causing this (it could be, for example, the LIUSB-Ethernet failing to see a collision on the Ethernet).? If this is the case, then there isn't anything for us to do to fix the problem.? The automatic resend is the correct recovery action. I don't believe there is anything wrong with your system. Paul |
|
Paul,
? ? ? ? ? The adapter and PC are both ethernet connected to a tp-link10/100 desktop switch by short cables, the switch is connected to the router by a good quality ethernet cable about 40 mtrs long. ? I can't see anything wrong here. Also I disconnected all other ethernet connections on the router but this has no effect on the errors. I have factory reset the adapter and set up a small table with 5 logix's which control signals, which are disabled at start up.? After opening the program and operating a few turnouts from the layout diagram the are no errors on the console. ? Enable the 5 logix? and return to the console shows:- audio.JoalAudioFactory ? ? ? ? ? ? ? ? ? ? INFO - Initialised ……… jmrix.AbstractMRTrafficController ?? ERROR - Automatic recovery from error message..... I then operated a turnout (twice) which is in a logix and got 9 errors ! Repeating this causes errors about 40% of the time so the errors build up rapidly on the console. I look forward to your response but wonder if I'd be better off using a USB adapter ? Regards, Alan |
|
Alan,
On Aug 19, 2018, at 6:26 AM, Alan Gibbs <buggydriver17@...> wrote:I don’t think there is anything wrong there. It is really hard to eliminate all possible sources of interference and data corruption which is why we implement the automatic recovery process for communication errors. I have factory reset the adapter and set up a small table with 5 logix's which control signals, which are disabled at start up. After opening the program and operating a few turnouts from the layout diagram the are no errors on the console. Enable the 5 logix and return to the console shows:-JMRI is doing what it is supposed to do here. It is recovering when the interface detects an error. Send me a copy of the panel file and I will see if there is anything in the panel that could be contributing to the number of repeated messages you are seeing. I suspect that operating that turnout generates a disproportionately large number of XPressNet messages when the logix is enabled. I look forward to your response but wonder if I'd be better off using a USB adapter ?Perhaps, but unless the recovery is impacting performance, you aren’t going to see any difference. I have found the Ethernet interface is generally the most reliable interface to Lenz systems, especially with Windows machines. Paul |
|
Paul, Just to throw in some other experiences, I have found the USB side of my interface to be more reliable. I was getting dropped connections from time to time with ethernet without any pattern to them. But I have a Mac, not a Windows machine on it. The USB has been flawless over at least several years now.
Ed Merrin Northwestern Pacific Santa Rosa. |
|
Seeking a little help on these AbstractMRTraffic Controller errors as well, but connecting using a Lenz LI100.
Is it plausible that JMRI could become so overwhelmed with these error recoveries that it would cause another network connected to it to fail? My reason for asking is this..? during my ops session this morning, the CTI/Acela signal network failed about 15 minutes into the session. I've been at the layout for over 45 minutes running a single train over the entire system and cannot cause the signal system to fail. (I went through a similar experience last year, where I spent a couple of months trying to diagnose a problem with the CTI network, only to finally discover that a loose bus wire for the Lenz DCC was the culprit.? My theory was that this loose wire was causing so many communication errors to occur that it would result in the CTI network loosing its connection to the computer.) Any help is greatly appreciated.? I can upload an excerpt from the System Console, but it sounds like my error messages with the automatic recovery are similar to those described earlier in this thread. Windows 7 Lenz LZV100 Lenz LI100 CTI/Acela Mike Carr Mike |
mopacmike
to navigate to use esc to dismiss