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
- Jmriusers
- Messages
Search
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: Cannot read, but can write, with Decoder Pro
Marc
i have changed them all to Z21 and you are correct, it works again - clearly something has changed either within JMRI or with the lat st Z21 firmware (1.33) as I haven't changed these settings since I set up DecoderPro a long time ago, and it was working. doesnt matter though - working niw thank you iain |
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
? |
Locked
Re: JMRI and Sprog nano - racing loco's
Possible CV29? is set with DC (analog conversion)? enable. This will cause engines to race off thinking they see DC on track if no DCC signal is present.
CV29, bit 2 Marc |
Locked
Re: Throttle operating in reverse
¿ªÔÆÌåÓý
On Sat, Jan 12, 2019 at 03:58 PM, Norb Schertzer wrote:I've even tried to reset the CVs to factory settings.. no dice. Other than reversed throttle direction, the engine behaves as it should. Any suggestions?If you reset to factory defaults AND TESTED BEFORE ANY OTHER CV CHANGES ? and issue still present then the motor is wired wrong.? You may need to reverse the two headlights as well. Paul |
Locked
Re: Cannot read, but can write, with Decoder Pro
If I setup defaults as you have them (all Z21Loconet),? I also end up with greyed out on New LOCO and no read.
If I set DEFAULTS to all? Z21, then the New Loco is not greyed out and read/write appear as normal. Suggest you visit the following link for what is supported in the JMRI / Roco environment. Hope this is the BLACK Z21 !... Sorry but can not be more helpful than this. Marc |
Locked
Re: Turnouts (not) updating on Panel
Hi Steve,
I thought as much, the turnout mode is set to Direct, with Feedback 1 and 2 blanked out and Turnout automation set to off, i have taken a screenshot here. I have also made another gif with the CBUS event table, turnout file and layout editior showing, this may be a bit more clear, to start i change the switch by clicking the state, the icon on the layout updates to show the change, when i send the event in the cbus table the state changes in the turnout table but the layout is incorrect. https://i.imgur.com/Cku2AJL.gif By the way, the event table has just helped understand how events are created around the servo moving, how the end points generate opposite on and off events! Cheers Tim |
Locked
Re: Configure DS64 tool trouble
Strange happening. I upgraded from JMRI 4.11.6 to 4.14 and suddenly I could program the troublesome unit completely. I thought this was strange but, I'll take it. As I had been using a home-made controller for my turnouts and routes I discovered i had to reverse the wiring on 3 of my switch machines to have them take the proper positions when using the DS64. Everything is good now, except I screwed up my Pi, but that's a whole 'nother deal. ? ?Hi Steve.
|
Locked
JMRI and Sprog nano - racing loco's
¿ªÔÆÌåÓýHi all,I have a combination of latest stable JMRI on Lubuntu (or Mac) with Sprog Nano with the following: During start up
Then the set all turnouts to closed takes a while as it works through roughly 30 switch decoder addresses. Power off and all goes quiet. If I then turn on the power again manually those loco's that raced before will do this again until you take control of them and change speed or direction. They then come under control and stay that way for the rest of the session. My Lubuntu system went into screensaver mode after 10 minutes and the same happened. Any idea what can be causing this? I don't think the problem happens when I use a Tams Command Station. Must give this a try and observe. Under some circumstances I use the Tams for providing track commands and the Sprog Nano only to control turnout/DCC decoders. Would it be possible to e.g. send a "speed zero" command similar to what a break booster does as a script file similar to setting the power on/off? This might provide a work around. Thanks, (Mr) Jan |
Locked
Re: Turnouts (not) updating on Panel
Hi Tim,
Am thinking that this isn't CBUS related Another quick thing to test, does it work when sending event 503 from the event table? What feedback mode do you have set for the turnout? Ta, Steve |
Locked
Re: Programming locos with Fleischmann Twin-Center sw ver. 2.000 and DecoderPro 4.14
I don't remember the details - I worked on this 4 years ago with @kjlisby - but there are differences in the LN implementation between IB2/IB-COM and IB 'one' (or Fleischmann TC); and a number of IB (1 or 2) messages are NOT defined in the Digitrax LN specification.
The work performed by @kjlisby focused on the IB-COM with my support for IB2 - both are sharing the same message set - but it was not completed for IB 'one'. -- Alain LM |
Locked
Re: Turnouts (not) updating on Panel
Hi Steve,?
Yes its a little unclear i will admit. basically the panel never updates the turnout position, IE the icon doesn't move? when the event "503" is sent from the CANCAB.? The turnouts table shows the change, the column labeled? "state" in the turnouts table does change when the CAB sends the 503 event, but this is not replicated on the panel image. This means that the Panel is not correct if you change the switch with the CAB.? (it is correct if you change the switch with the Panel, or click the state in the turnouts table) I am just heading out but will try to get a copy of the data later for you. Thanks for the assistance. Tim |
Locked
Re: Turnouts (not) updating on Panel
Hi Tim,
Yes, the same Steve Young! Thanks for the GIF however I found it a tad awkward to understand! The one thing I spotted was that there was an incoming short event containing a node number, this isn't an issue though. Console will report these as they are the true message, however I've tested this in JMRI, and the node number is definitely stripped out as per CBUS short-event spec. I think we need to resolve which particular link isn't working, there are 2 links in the chain. 1 - Between the panel and the turnout table 2 - Between the turnout table and the CBUS message. When the troublesome incoming CBUS message is received, the turnout table IS updating? or When the troublesome?incoming CBUS message is received, the turnout table is NOT updating? If you could post the single console log entries ( left hand side pure message please ), for the correct message sent out, also the entry for when the message is received by the CAB that would also help. Thanks, Steve. |
Locked
Re: RPi-JMRI image updated
Hi Bruno, since the autoidentify is not working, you should disable it (there's a desktop icon for that). Then open PanelPro and select a similar profile, or just create a new one.
Then set the Connection Preferences as needed. That profile will be used on restart. I don't have Lenz equipment, so I can't advise on that. -- SteveT |
Locked
Re: JMRI RailDriver In Cab Video
#raildriver
Hi again;
Regarding RailDriver support, it would be nice to have it as a Jynstrument, like I did for Wiimote, various USB pads, and even a DCC throttle, see code in jython/Jynstruments/ThrottleWindowToolBar .... just checked the code, it's actually there (in USBThrottle.jyn), I remember now, it's a sample implementation I did a while ago, but was never tested, as I don't own a Raildriver. Why using Jynstrument instead of a classical Jython script, because it will be loaded by the throttle, and the throttle will be a regular JMRI throttle with all its customization, and the Jython code doesn't have to handle the throttle creation, hence code is way simpler, and several of these Jynstruments can be loaded all together in one regular throttle. So actually, it's all there, just need to make it work! Regards; Lionel |
Locked
Re: JMRI RailDriver In Cab Video
#raildriver
Hi;
regarding video playback in a JMRI throttle frame, I had build something a while ago, I think the code is still there ( jython/Jynstruments/ThrottleFrame/VideoView.jyn ), see (at 0:40), not sure if this still works, there are some comments at the top of the Jython code on how to set it up. Regards; Lionel |
Locked
Re: Turnouts (not) updating on Panel
Hi Steve,
Thanks for the link, i did try that but to no avail, enabled or not it seems to make no difference. I can click on the panel editor and it does change the turnout, but the panel doesn't seem to update its state when the turnout is thrown outside of JMRI. I created a short GIF to show this, first i change the point in the Panel, then change the point in the turnout table, this also updates the turnout position in the Panel, then i change the turnout from the CAB, this changes the state correctly in the turnouts file but the panel doesn't follow the update. I am using 4.15.1+R4a42841 so i could get your (Assuming you are the same Steven Young :) ) improvements to the console etc, not sure if that should make any difference. Cheers Tim? |
Locked
Re: Operations Pro Roster
Thanks Dan and Peter.? Dan, I thought CSV was most likely the easier and more efficient way since the columns would be easier to manage.? I never thought of first exporting a "dummy file" with no data entered.?? Jerry |
Locked
Re: RPi-JMRI image updated
hello Steve,
First of all thanks for your hard work. I downloaded your early January 2019 version. I'm having a Lenz LZV100 and normally use my Lenz 23150 Li-USB to connect with a WIN10 to my central station. That works. But now I would like to switch to the RPI approach. What doesn't work for me is the Auto Identify of the Lenz LIUSB (23150, not the newer 23151). I looked in your script whereyou grep the lsusb output. My Lenz LIUSB is recognized as "Bus 001 Device 005: ID 1111:1234 Pandora International Ltd." I modified the SH script to start the right profile. That works now but I now get the error message "Serial Port ttyACM0 not found". From where does JRMI get this ttyACM0 serial port config ? I only have a ttyS0 and ttyAMA0 available but none of them are talking with the Lenz USB interface. Looking in /var/log/messages I found: Jan 13 11:58:00 RPi-JMRI kernel: [? ? 2.191535] usb 1-1.1.3: new full-speed USB device number 5 using dwc_otg
Jan 13 11:58:00 RPi-JMRI kernel: [? ? 2.335924] i2c /dev entries driver
Jan 13 11:58:00 RPi-JMRI kernel: [? ? 2.338990] usb 1-1.1.3: New USB device found, idVendor=1111, idProduct=1234
Jan 13 11:58:00 RPi-JMRI kernel: [? ? 2.339006] usb 1-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan 13 11:58:00 RPi-JMRI kernel: [? ? 2.339015] usb 1-1.1.3: Product: LI USB
Jan 13 11:58:00 RPi-JMRI kernel: [? ? 2.339027] usb 1-1.1.3: Manufacturer: Lenz Jan 13 12:43:16 RPi-JMRI kernel: [ 2713.359458] usb 1-1.1.3: USB disconnect, device number 5
Jan 13 12:43:19 RPi-JMRI kernel: [ 2716.216244] usb 1-1.1.3: new full-speed USB device number 9 using dwc_otg
Jan 13 12:43:19 RPi-JMRI kernel: [ 2716.364524] usb 1-1.1.3: New USB device found, idVendor=1111, idProduct=1234
Jan 13 12:43:19 RPi-JMRI kernel: [ 2716.364532] usb 1-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan 13 12:43:19 RPi-JMRI kernel: [ 2716.364538] usb 1-1.1.3: Product: LI USB
Jan 13 12:43:19 RPi-JMRI kernel: [ 2716.364541] usb 1-1.1.3: Manufacturer: Lenz
Jan 13 12:43:19 RPi-JMRI mtp-probe: checking bus 1, device 9: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.3"
Jan 13 12:43:19 RPi-JMRI mtp-probe: bus: 1, device: 9 was not an MTP device
?
The device is recognized but seems not be mapped to anything in /devAny clues how to solve this ? I assume, first by adding a new udev rule. regards, Bruno (JMRI user from Belgium) |
Locked
Re: Cannot read, but can write, with Decoder Pro
Cant seem to edit the last post and both links go to the same image - if you scroll back you can see the default preferences also
/g/jmriusers/photo/81943/1?p=Name,,iain,20,1,0,0 Might be the right link? |
to navigate to use esc to dismiss