|
Locked
Test version 4.15.2 of JMRI/DecoderPro is available for download
Test version 4.15.2 of JMRI/DecoderPro is available for download.
This is the next in a series of test releases that will culminate in a production release, hopefully in early Summer 2019. If you are currently using JMRI 4.9.6 or earlier, we strongly recommend that you first update to JMRI 4.12 and make sure that's running OK before updating to this test release. There have been a number of changes in serial port support, panel file format and configuration options since those earlier releases, and moving to the stable JMRI 4.12 release is a good way to work through any possible problems. <> If you use JMRI on Linux or Mac and are updating from JMRI 4.7.3 or earlier, there¡¯s a necessary migration step. (Not needed on Windows) Please see the JMRI 4.12 release note for details: <> For more information on the issues, new features and bug fixes in 4.15.2 please see the release note: <> Note that JMRI is made available under the GNU General Public License. For more information, please see our copyright and licensing page. <> The download links, along with lots of other information which we hope you'll read, can be found on the release note page: <> Bob -- Bob Jacobsen rgj1927@... |
|
Locked
Re: Saving files / RasPi / TightVNC
Have you set the ¡°Startup¡± part of the Preferences to load your file?
Bob On Jan 13, 2019, at 7:40 PM, Bob Hall <Olmanhall@...> wrote:-- Bob Jacobsen rgj1927@... |
|
Locked
Re: JMRI is broken (?)
Open the preferences, then pick ¡°Defaults¡± in the left to get to the default pane. Make sure that the radio buttons are selected in the NCE line all the way across, not the Internal line. Save and restart.
Bob On Jan 13, 2019, at 9:48 PM, gwi8251315 via Groups.Io <gwi8251315@...> wrote:-- Bob Jacobsen rgj1927@... |
|
Locked
Re: Cannot read, but can write, with Decoder Pro
Defaults changing were issues in the previous 2 JMRI production releases. Make sure you are using at least JMRI 4.14.
-- Peter Ulvestad JMRI Users Group Moderator - ( ) Tam Valley Group Moderator - ( ) Sprog-DCC Group Moderator - ( ) Edmonton Model Railroad Association - |
|
Locked
Re: RPi-JMRI image updated
hi Steve,
No worries. I have some Lenz equipment and can help with testing. It seems some of these older Lenz 23150 USB Connectors where kind of sample devices which aren't that easily recognizable by Linux. Anyways, I found a workaround, documented it and was able to run my LGB locs over the RPI. Good feeling ! Here are my notes and if you want, you can publish them on your website.? Why the Lenz 23150 shows a vendorID of 1111 in "lsusb"command output.
?
"According to Lenz, an LIUSB with a product ID of 1111:1234 was an early?sample model. Lenz's advice at that time was to contact them for?exchange, although there is nothing actually wrong with the unit you
have.
For some reason, these sample devices can be made to behave on windows,?but they don't behave correctly on Linux. (I do all of my development?on Linux, and the normal production version works just fine)." (dixit Paul Bender, source: https://forum.beneluxspoor.net/index.php?topic=52593.0)
?
?
**
WORKAROUND STEPS:
?
Load kernel module ftdi_sio:
sudo vi /etc/modules
add new line at the end of the file: ftdi_sio
?
Modify /home/pi/PanelPro_autoIdentify.sh to autodetect the Lenz 23150 Li-USB device.
If I'm correct, the?"04d8:0721 Microchip Technology, Inc."?is linked to the Lenz 23151 (which has USB and Ethernet): ?
copy the existing profile settings:
?
result=$(lsusb | grep -e "04d8:0721 Microchip Technology, Inc.")
if [ $? -eq 0 ]; then
? printf "Found LENZ USB hardware\n"
? /home/pi/JMRI/PanelPro -p LENZ_USB.3efdbd7f
? exit 0
fi
?
and add a new set like, this set will find the USB Hardware, load the correct profile and also link the USB Hardware to the ttyUSB0 serial port
?
result=$(lsusb | grep -e "1111:1234")
if [ $? -eq 0 ]; then
? printf "Found LENZ 23150 USB hardware with vendorID 1111 and productID 1234\n"
? sudo chmod 777 /sys/bus/usb-serial/drivers/ftdi_sio/new_id
? sudo echo 1111 1234 > /sys/bus/usb-serial/drivers/ftdi_sio/new_id
? /home/pi/JMRI/PanelPro -p LENZ_USB.3efdbd7f
? exit 0
fi
?
?
The first time the LENZ_USB profile is loaded, the wrong serial port might be selected (ttyACM0).
click Edit Connections and select ttyUSB0.?
Restart JMRI.
?
**
?
Remarks:
?
sudo chmod 777 /sys/bus/usb-serial/drivers/ftdi_sio/new_id
sudo echo 1111 1234 > /sys/bus/usb-serial/drivers/ftdi_sio/new_id
?
This command will trigger the link between the USB driver and the creation of the USB Serial port ttyUSB0
example output via "dmesg":
Jan 13 17:38:41 RPi-JMRI kernel: [? 291.776447] ftdi_sio 1-1.1.3:1.0: FTDI USB Serial Device converter detected
Jan 13 17:38:41 RPi-JMRI kernel: [? 291.777062] usb 1-1.1.3: Detected FT232BM
Jan 13 17:38:41 RPi-JMRI kernel: [? 291.787562] usb 1-1.1.3: FTDI USB Serial Device converter now attached to ttyUSB0
before that, you only found in /var/log/messages (or dmesg) this example output:
Jan 13 17:33:46 RPi-JMRI kernel: [? ? 2.181552] usb 1-1.1.3: new full-speed USB device number 5 using dwc_otg
Jan 13 17:33:46 RPi-JMRI kernel: [? ? 2.329251] usb 1-1.1.3: New USB device found, idVendor=1111, idProduct=1234
Jan 13 17:33:46 RPi-JMRI kernel: [? ? 2.329272] usb 1-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan 13 17:33:46 RPi-JMRI kernel: [? ? 2.329285] usb 1-1.1.3: Product: LI USB
Jan 13 17:33:46 RPi-JMRI kernel: [? ? 2.329302] usb 1-1.1.3: Manufacturer: Lenz
? |
Bob Jacobsen
Peter Ulvestad
Bruno De Graeve