Paul; thank you for inquiring regarding this topic;
I am using a LZV100 3.6 version command station with software version 3.6 & an LV102 properly hooked up with 2 separate sMg AC-AC power packs supporting the LVZ100 & LV102 for more power the layout & my LIUSB-Ethernet being the only thing plugged into my command station &my software version is macOS High Sierra; version 10.13 Beta (17A330h); I was wondering if this Beta version was maybe a cause for the problems!
Thanks for any assistance that you can provide me:
Bill; the latest System Console is as follows:
2017-08-13 14:32:58,537 util.Log4JUtil INFO - * JMRI log ** [main]
2017-08-13 14:33:01,973 util.Log4JUtil INFO - This log is appended to file: /Users/williamseabrooke/Library/Preferences/JMRI/log/messages.log [main]
2017-08-13 14:33:01,974 util.Log4JUtil INFO - This log is stored in file: /Users/williamseabrooke/Library/Preferences/JMRI/log/session.log [main]
2017-08-13 14:33:02,016 apps.AppsBase INFO - DecoderPro version 4.9.2ish+jenkins+20170804T0543Z+Reaaaf8a starts under Java 1.8.0_144 on Mac OS X x86_64 v10.13 at Sun Aug 13 14:33:01 EDT 2017 [main]
2017-08-13 14:33:03,233 gui3.Apps3 INFO - Starting with profile wmseamac.3f48e951 [main]
2017-08-13 14:33:03,868 node.NodeIdentity INFO - Using jmri-28F0761979C8-3f48e951 as the JMRI Node identity [main]
2017-08-13 14:33:05,461 liusb.LIUSBAdapter INFO - cu.usbmodem1411 port opened at 57600 baud with DTR: true RTS: true DSR: false CTS: false CD: false [main]
2017-08-13 14:33:05,643 jmrix.AbstractMRTrafficController ERROR - Automatic Recovery from Error Message: 01 08 09. Retransmitted 0 times. [liusb.LIUSBXNetPacketizer Receive thread]
2017-08-13 14:33:05,643 jmrix.AbstractMRTrafficController INFO - Message added back to queue: 21 21 00 [liusb.LIUSBXNetPacketizer Transmit thread]
2017-08-13 14:33:35,674 lenz.XNetInitializationManager WARN - Command Station disconnected, or powered down assuming LZ100/LZV100 V3.x [main]
2017-08-13 14:33:38,650 util.FileUtilSupport INFO - File path program: is /Applications/JMRI/ [main]
2017-08-13 14:33:38,651 util.FileUtilSupport INFO - File path preference: is /Users/williamseabrooke/Library/Preferences/JMRI/wmseamac/profile/jmri-28F0761979C8-3f48e951/ [main]
2017-08-13 14:33:38,651 util.FileUtilSupport INFO - File path profile: is /Users/williamseabrooke/Library/Preferences/JMRI/wmseamac/ [main]
2017-08-13 14:33:38,651 util.FileUtilSupport INFO - File path settings: is /Users/williamseabrooke/Library/Preferences/JMRI/ [main]
2017-08-13 14:33:38,651 util.FileUtilSupport INFO - File path home: is /Users/williamseabrooke/ [main]
2017-08-13 14:33:38,652 util.FileUtilSupport INFO - File path scripts: is /Applications/JMRI/jython/ [main]
2017-08-13 14:33:40,665 jmrix.AbstractMRTrafficController WARN - Timeout on reply to message: 21 21 00 consecutive timeouts = 0 in liusb.LIUSBXNetPacketizer [liusb.LIUSBXNetPacketizer Transmit thread]
2017-08-13 14:34:15,687 jmrix.AbstractMRTrafficController WARN - Timeout on reply to message: 21 24 05 consecutive timeouts = 1 in liusb.LIUSBXNetPacketizer [liusb.LIUSBXNetPacketizer Transmit thread]
---In jmriusers@..., <paul.bender@...> wrote :
On 08/09/2017 09:47 AM, Paul Bender wrote:
>> On Aug 8, 2017, at 6:53 PM, wmseapc@... mailto:wmseapc@... [jmriusers] <jmriusers@... mailto:jmriusers@...> wrote:
>> Here is my System Console below; is this what you are referring to as the "log"?
>
> That information is also stored in a log file ( see below). So yes that was what I needed.
>
>> 2017-08-08 18:32:55,715 util.Log4JUtil INFO - This log is stored in file: /Users/williamseabrooke/Library/Preferences/JMRI/log/session.log [main]
>
> Now to the important bits of the log.
>
>> 2017-08-08 18:32:59,359 liusb.LIUSBAdapter INFO - cu.usbmodem1411 port opened at 57600 baud with DTR: true RTS: true DSR: false CTS: false CD: false [main]
>> 2017-08-08 18:32:59,522 jmrix.AbstractMRTrafficController
>>
>> ERROR - Automatic Recovery from Error Message: 01 08 09. Retransmitted 0 times. [liusb.LIUSBXNetPacketizer Receive thread]
>> 2017-08-08 18:32:59,522 jmrix.AbstractMRTrafficController
>
> This is actually an improvement. This indicates your Mac is talking to your LIUSB, but it is sending back an error message ( one we should be able to recover from ).
>
> This particular error message says the command station isn't giving the LIUSB a communication time slot. I am not sure why you are seeing this on startup.
>
> Let me investigate and see what we can do to fix this.
I've been looking at this over the last couple of days, and the only way
I have been able to replicate what you are seeing is by connecting a
Roco Z21 command station to the LIUSB-Ethernet.
Connecting a version 3.6 LZV100 caused no issues.
Can you tell me a little more about your setup?
What command station are you using?
What software version is the command station?
What else is connected to the command station?
Have you tried your LIUSB-Ethernet with it being the only thing plugged
into the command station?
What version of MacOS X do you have installed?
Thanks,
Paul
wmseapc