开云体育

Hello
I was happy to have loaded the JMRI version 4.7.6 down two days ago. After the installation on my iMac with Sierra 10.12.5, I could immediately open decoder Pro and with my Lenz digital control to connect (I've noticed the Notes migration). All functions could be opened directly, such as new locomotive or train controller (throttle).
Today, the joy is already over. Decoder Pro opens though, the Windows need but a long time for changes.
In the middle of the window located above button is yellow. Usually it is green or red.
Who can help?
Thank you
with kind regards

Wolfgang Grehn

In order to help you, we need to know some more information:
- Computer operating system (Windows, Mac, Linux) and version.
- DCC hardware brand, model and connection method.
- Start JMRI and go to the Help->System Console menu item, click on Copy to Clipboard and paste into a post for us to see.

The Power button will be yellow if layout state is unknown. This is normal for some systems (e.g. NCE) but if it is abnormal for your system it indicates a connection failure.
--
Dave in Australia

Hello Dave,
Thank you for your answer.
You will find the desired information from Decoder Pro below:

1. Computer operating system: MAC OS Sierra version 10.12.5 - IMac27 "
2. DCC
Lenz LZ100 - LV101 - Version 3.6 - USB Interface 23150

Wolfgang Weil am Rhein Germany


2017-06-29 12:29:33,046 util.Log4JUtil INFO - * JMRI log ** [main]
2017-06-29 12:29:34,464 util.Log4JUtil INFO - This log is appended to file: /Users/wolfganggrehn_iMac/Library/Preferences/JMRI/log/messages.log [main]
2017-06-29 12:29:34,465 util.Log4JUtil INFO - This log is stored in file: /Users/wolfganggrehn_iMac/Library/Preferences/JMRI/log/session.log [main]
2017-06-29 12:29:34,470 apps.AppsBase INFO - DecoderPro version 4.7.6+R570b2bc starts under Java 1.8.0_131 on Mac OS X x86_64 v10.12.5 at Thu Jun 29 12:29:34 CEST 2017 [main]
2017-06-29 12:29:34,683 gui3.Apps3 INFO - Starting with profile My_JMRI_Railroad.3f09e17c [main]
2017-06-29 12:29:34,751 node.NodeIdentity INFO - Using jmri-8863DFBB063B-3f09e17c as the JMRI Node identity [main]
2017-06-29 12:29:37,006 liusb.LIUSBAdapter INFO - cu.Bluetooth-Incoming-Port port opened at 57600 baud with DTR: true RTS: true DSR: false CTS: false CD: false [main]
2017-06-29 12:30:07,034 lenz.XNetInitializationManager WARN - Command Station disconnected, or powered down assuming LZ100/LZV100 V3.x [main]
2017-06-29 12:30:08,353 util.HelpUtil WARN - JavaHelp: File help/de/JmriHelp_de.hs not found, dropping to default [main]
2017-06-29 12:30:09,080 util.FileUtilSupport INFO - File path program: is /Applications/JMRI/ [main]
2017-06-29 12:30:09,081 util.FileUtilSupport INFO - File path preference: is /Users/wolfganggrehn_iMac/Library/Preferences/JMRI/My_JMRI_Railroad/ [main]
2017-06-29 12:30:09,081 util.FileUtilSupport INFO - File path profile: is /Users/wolfganggrehn_iMac/Library/Preferences/JMRI/My_JMRI_Railroad/ [main]
2017-06-29 12:30:09,081 util.FileUtilSupport INFO - File path settings: is /Users/wolfganggrehn_iMac/Library/Preferences/JMRI/ [main]
2017-06-29 12:30:09,081 util.FileUtilSupport INFO - File path home: is /Users/wolfganggrehn_iMac/ [main]
2017-06-29 12:30:09,081 util.FileUtilSupport INFO - File path scripts: is /Applications/JMRI/jython/ [main]
2017-06-29 12:30:12,034 jmrix.AbstractMRTrafficController WARN - Timeout on reply to message: 21 21 00 consecutive timeouts = 0 [liusb.LIUSBXNetPacketizer Transmit thread]
2017-06-29 12:30:22,318 withrottle.UserInterface INFO - Creating new WiThrottle DeviceServer(socket) on port 12090, waiting for incoming connection... [WiThrottleGUIServer]
2017-06-29 12:30:47,613 jmrix.AbstractMRTrafficController WARN - Timeout on reply to message: 21 24 05 consecutive timeouts = 1 [liusb.LIUSBXNetPacketizer Transmit thread]

Am 29.06.2017 um 01:01 schrieb Dave Heap dgheap@... [jmriusers] <jmriusers@...>:

In order to help you, we need to know some more information:
- Computer operating system (Windows, Mac, Linux) and version.
- DCC hardware brand, model and connection method.
- Start JMRI and go to the Help->System Console menu item, click on Copy to Clipboard and paste into a post for us to see.

The Power button will be yellow if layout state is unknown. This is normal for some systems (e.g. NCE) but if it is abnormal for your system it indicates a connection failure.

Sent from my iPad
--
Dave in Australia

On 29 Jun 2017, at 4:23 AM, grehnwolfgang@... <mailto:grehnwolfgang@...> [jmriusers] <jmriusers@... <mailto:jmriusers@...>> wrote:

Today, the joy is already over. Decoder Pro opens though, the Windows need but a long time for changes.
In the middle of the window located above button is yellow. Usually it is green or red.
Who can help?

[Non-text portions of this message have been removed]

The presence of "cu.Bluetooth-Incoming-Port" indicates the chosen port is certainly not correct. What other choices are available in the Preferences dropdown list?

A Lenz user with a Mac should be able to indicate what the correct port name looks like.
--
Dave in Australia

Hi Dave,.
Decoder pro works quickly and well.
I think the following is important:
Start DCC station
Connect USB cable to Mac
run decoder pro
Then, following connection options appear under Preferences:
CU.usbserial...
CU.Bluetooth...
Thank you
Greetings from Weil am Rhein Germany

Am 29.06.2017 um 20:41 schrieb Dave Heap dgheap@... [jmriusers] <jmriusers@...>:

The presence of "cu.Bluetooth-Incoming-Port" indicates the chosen port is certainly not correct. What other choices are available in the Preferences dropdown list?

A Lenz user with a Mac should be able to indicate what the correct port name looks like.

Sent from my iPad
--
Dave in Australia

On 30 Jun 2017, at 3:29 AM, Wolfgang Grehn grehnwolfgang@... <mailto:grehnwolfgang@...> [jmriusers] <jmriusers@... <mailto:jmriusers@...>> wrote:

Hello Dave,
Thank you for your answer.
You will find the desired information from Decoder Pro below:

1. Computer operating system: MAC OS Sierra version 10.12.5 - IMac27 "
2. DCC
Lenz LZ100 - LV101 - Version 3.6 - USB Interface 23150

Wolfgang Weil am Rhein Germany

2017-06-29 12:29:33,046 util.Log4JUtil INFO - * JMRI log ** [main]
2017-06-29 12:29:34,464 util.Log4JUtil INFO - This log is appended to file: /Users/wolfganggrehn_iMac/Library/Preferences/JMRI/log/messages.log [main]
2017-06-29 12:29:34,465 util.Log4JUtil INFO - This log is stored in file: /Users/wolfganggrehn_iMac/Library/Preferences/JMRI/log/session.log [main]
2017-06-29 12:29:34,470 apps.AppsBase INFO - DecoderPro version 4.7.6+R570b2bc starts under Java 1.8.0_131 on Mac OS X x86_64 v10.12.5 at Thu Jun 29 12:29:34 CEST 2017 [main]
2017-06-29 12:29:34,683 gui3.Apps3 INFO - Starting with profile My_JMRI_Railroad.3f09e17c [main]
2017-06-29 12:29:34,751 node.NodeIdentity INFO - Using jmri-8863DFBB063B-3f09e17c as the JMRI Node identity [main]
2017-06-29 12:29:37,006 liusb.LIUSBAdapter INFO - cu.Bluetooth-Incoming-Port port opened at 57600 baud with DTR: true RTS: true DSR: false CTS: false CD: false [main]

[Non-text portions of this message have been removed]

Correct. The port you want will not appear on a Mac until you plug in the USB cable for the device and its driver loads. I usually find it necessary to do that before starting DecoderPro.

Another way to check what port is being loaded by your device is:

Unplug your device. Open a Terminal Window (from /Applications/Utilities), copy and paste the following command in EXACTLY (including spaces and punctuation) then press Enter.

while : ;do clear;ls -lt /dev|head;i=$((i+1));echo $i;sleep 1;done

This command should show about 10 lines of output and then sit looping, with a counter incrementing every second.

Plug your device back in and wait a few seconds. Two new items with names like cu.xxx and tty.xxx should appear in the list. They should disappear if you unplug your device. If this does not happen, you do not have the correct drivers installed for your device and you will need to solve that before proceeding further. Once you have found your device, write down the name you see.You want the cu.xxx version not the tty.xxx version.

If you have got this far you know your device is be being seen by the Mac, that it has a matching driver installed and the name of the connection port "cu.xxx" you need to select in JMRI. If you cannot get this far, there's no way JMRI can find your device until the driver issue is resolved.

Note that in the latest test versions of JMRI we have changed the external library we use for serial ports and you may not see the tty. device any more (or even the cu. prefix).
--
Dave in Australia