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
|
JMRI and LogicX driving Signals
#signals
Wanting to drive a Signal based on a decision 'to set green / red' from a LogicX - already set a sensor 'light' on the screen and switch turnouts,, looking for guidance to then set a dwarf signal.
听
unable to use turnout motor switches as there are two x three-way turnouts used.
听
If there is a write up or Youtube I would appreciate in pointer, all i have seen so far are track sensor based and switched from a single turnout motor.
听
Happy to answer any questions...
听
thanks
Randall |
|
Signal Controller Board Suggestions
I have JMRI LogicX working through a tree/ladder of turnout to set 'a road in a yard' to the 'Main' from a touch sensor on a Panel.听 Due to space, I am using two x three-way turnouts meaning I cannot use the turnout motor internal switches to switch leds on the Dward Signals on each road.
听
On the screen, I have a 'sensor' light next to the Road when it is clear to the Main.听 All good so far and works fine.
听
Looking now for an addressable signal controller board to receive a JMRI command to turn a 'dwarf' signal from 'red' to 'green' when the sensor on the panel is selected (when it sets the required road to main).听 听The signal controller will connect to an AUX bus connected to, in this case, a NCE PowerPro Controller.听
听
What Signal Controller Boards are you using to take the command to change the LEDs from JMRI?
听
happy to answer any clarifying questions!
听
Thanks
Randall
听
听
听
听 |
|
Re: JMRI & Engine Driver Issue
#enginedriver
Richard,
Please post a screenshot of the About screen from EngineDriver while connected.
What address (exactly) are you typing in? NCE has some odd addressing, IIRC.
Also, try turning off the track power from EngineDriver and controlling Turnouts from EngineDriver. All of these will help narrow down the problem.
--SteveT听 |
|
Re: Difference Between Compare and Reset
#decoderpro
Testing the brake is simple. F11 is the default for these decoders. Make sure F11 is off.
-- Peter Ulvestad Linux Mint 22.1, JMRI 5.11.4plus, Java 21.0.6 JMRI Users Group Moderator ( /g/jmriusers ) JMRI Developers Group Moderator ( ) Tam Valley Group Moderator ( ) Sprog-DCC Group Moderator ( ) Edmonton Model Railroad Association ( ) |
|
Re: Difference Between Compare and Reset
#decoderpro
toggle quoted message
Show quoted text
On 4 Apr 2025, at 11:46, Don Shroyer via groups.io <Donshroyer@...> wrote:
|
|
Re: Train tracking, dealing with gaps
#traintracking
The 'delay to inactive' technique worked. I'm glad that I was made aware of these 'debouncing delays'. I think they might be useful to clean up some flaky sensor data that we have been dealing with.
听
George |
|
Re: Experimental "Flatpak" distribution of JMRI
I understand that. The "tricky bit" for both MS-Windows and MacOS installs is
getting and installing the "proper" JAVA JRE, not actually installing JMRI itself. That seems to be what non-techies seem to have the most trouble with. And probably the most confusing thing is that the version of Java at java.org -- Oracle's JAVA -- is the wrong one. This is where something like a "Flatpak" type of install might be helpful. Getting the correct version of JAVA for *Linux* is pretty trivial, by comparison, since almost all Linux distros have OpenJDK in their repo. Here having a RPM or DEB package with a proper depenency for OpenJDK could be helpful, eg: sudo apt install ./jmri-5.12.deb would then go after openjdk-17-jre (and openjdk-17-jre-headless) automagically. At Fri, 04 Apr 2025 10:29:53 -0500 "Dave Sand" <ds@...> wrote: -- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services -- Linux Administration Services heller@... -- Webhosting Services |
|
Re: Sensor Query wrong for Digitrax BDL716 in 5.11.4
I don't think the BDL's have the ability to respond to a query.
听
It would imply that the BDL has the ability to read an translate a query message and the perform a status lookup
on a particular detection port.
听
The BDL creates messages based on trigger events. Only when a unit enters a block or exits a block will a message be generated.
听
Inobu听 |
|
Sensor Query wrong for Digitrax BDL716 in 5.11.4
Version 5.11.4+ R87a9dadc80 (Java 17.0.13)
The BDL168 is discontinued and replaced with BDL716 which I have two installed on LocoNet.
听
Upon starting JMRI,
During use the sensors correctly show inactive and active so changed states work correctly.
I don't recall this behavior using version 5.10 but I could be mistaken and I also added a second BDL716 at the same time I upgraded JMRI.
The problem is JMRI doesn't "see" the trains sitting in the yard although the LT5C clearly shows high/active so I have to run the train out of the block and back in to initialize the sensor at the correct level.
听
//stevemac |
|
Re: Experimental "Flatpak" distribution of JMRI
Robert,
toggle quoted message
Show quoted text
The macOS install is essentially the same as the Linux install. Download a DMG, open it and drag "JMRI" to "Applications". Dave Sand ----- Original message -----
From: "Robert Heller via groups.io" <heller@...> To: [email protected] Subject: Re: [jmriusers] Experimental "Flatpak" distribution of JMRI Date: Friday, April 04, 2025 8:34 AM This seems like a "solution looking for a problem", at least for *Linux*. Since JMRI is in JAVA and requires nothing outside of JAVA's JRE and installing a suitable JRE under Linux is "trivial" (compared to MS-Windows or MacOS), I am not sure how truely useful or needful this is. I can see a flatpak (or similar) for MS-Windows or MacOS, since it appears that those two O/S's have the greatest problems with installing JMRI, mostly caused by confusion about installing the proper version of a JRE. *I* would find a Linux "Flatpak" distribution of JMRI to be far more hassle to deal with than the current Linux distribution methodolgy of JMRI. Actually, I expect that the current Experimental "Flatpak" distribution of JMRI won't work on my machine(s) anyway -- I expect it is a x86_64 Flatpak and all of my machines use ARM processors. And this brings up a *new* issue that will complicate things: there would need to be *four* Linux flatpaks: ix86, x86_64, armv7l, and aarch64. My only thought about "improvements" in the Linux distribution of JMRI would be the creation of .deb and .rpm distrubutions of JMRI. I realize that JMRI will never be in any Linux distro repo and I understand why that is, but a self-made .deb and .rpm with a proper openjdk-XX-jre depenency could be helpful. *I* could probably help with creating the necessary control files to help with this, if anyone is interested. At Fri, 4 Apr 2025 08:19:38 -0400 "Bob Jacobsen via groups.io" <rgj1927@...> wrote: -- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services -- Linux Administration Services heller@... -- Webhosting Services |
|
Re: How to delete a turnout with jython
I note that scripting and Java is listed in the layout automation section of the JMRI website. Perhaps that is why I am sensing discomfort with regard to what I thought was a simple programming question. No I do not intend to run scripts to operate an actual layout that would involve deleting turnouts or anything else. However, I do find that working with the layout editor and Panel Pro in general is frustrating and I am exploring alternative approaches to getting things done. For example I have used the AnyRail scripts to set up initial panels and found that the exported file from AnyRail has seemingly added tiny track segments with the incorrect block assignments around turnouts and that requires painstaking editing before signal masts can be placed easily. Additionally, part of the AnyRail to JMRI process involves using a script to place sensor icons. It places them directly over a track segment selection circle, making it almost impossible to select the icon to move it. I have not looked yet but have to believe it is relatively easy to iterate over the sensor icons and change their coordinates. Probably easier to edit the existing script for my own use to permit an offset when adding the sensor icons. But it might turn out to be useful to know how to delete things as part of an editing procedure and that is basically all I was thinking about.
--
-Ralph |
|
Re: Cannot start to read decoders
Thank you , here is a detailed problem description logfiles are saved in director EAR /g/jmriusers/files/EAR
听
.started completely from scratch. Deleted all remnants from previous installs.
.Installed java 17 as suggested in windows installation
.installed jmri - no problem so far.
.Before using DecoderPro I verified connection with the central unit and programming track with loko placed on it
.Started up DecoderPro with empty roster/lokpark- clicked on New loko
.New loko window came up (it is rather small if that is of any significance - see later)
.Klicked read decoder type
.came back with list of decoders (where 4 zimo decoder)
. selected correct decoder (highlight took some seconds!)
. Then entered the id name on the right side - took another 2-4 seconds until decoder address was read and displayed
.Saved the loko to the roster / lokpark
.Status line: Pause
.Exited new lok window - clicked on "Identify"
.correct entry in the Roster (there is just one) is highlighted.
.Klicked exit and save!
.Restarted DecoderPro and klicked new loko
. This time a almost double wide New loko window came up
."Read decoder type" grayed out as well as "open detailed programmer" !
.Staus line: Pause
.Klicked exit and save the log files
Notes:
1) This is windows 11 24H2 all updates applied, iTrain, Central sation Mgmgt software, Anyrail all are working ok.
2) I tried English language as well as my own German - no difference
3) I have tried with the JMRI 5.11.4 test release as well as the current release
4) I have the same JMRI installation runing on another laptop听 - Windows Version听 is Windwos 11 22H2
Thanks for your patience - if you need more info/tests just let me know
Erik
听 |
|
Locked
2 files uploaded
#file-notice
Group Notification
The following items have been added to the Files area of the [email protected] group. By: @EAR <erik@...> Description: |
|
Re: Experimental "Flatpak" distribution of JMRI
Bob and everyone,
I have no strong feelings about adding a flatpak (and my Linux distribution does not have great support for it, so I won't test - plus I prefer spending my development time on other parts of JMRI which I've been neglecting far too long already). I'm just slightly wary of either dropping behind java releases or adding more flatpak releases to the JMRI schedule (i.e. 5.10-java17.0.13 on 5.10 release in Dec 2024, 5.10-java17.0.14 on Jan 21, 2025, 5.10-java17.0.15 on Apr 15, 2025 if things go as planned at Oracle). OTOH, I don't know if this is of any real concern, considering we are already shipping dozens (?) of libraries which also may go out of date in between production releases, and it's not system java but JMRI java :) Heiko -- eMails verschl眉sseln mit PGP - privacy is your right! Mein PGP-Key zur Verifizierung: |
|
Re: Experimental "Flatpak" distribution of JMRI
This seems like a "solution looking for a problem", at least for *Linux*.
Since JMRI is in JAVA and requires nothing outside of JAVA's JRE and installing a suitable JRE under Linux is "trivial" (compared to MS-Windows or MacOS), I am not sure how truely useful or needful this is. I can see a flatpak (or similar) for MS-Windows or MacOS, since it appears that those two O/S's have the greatest problems with installing JMRI, mostly caused by confusion about installing the proper version of a JRE. *I* would find a Linux "Flatpak" distribution of JMRI to be far more hassle to deal with than the current Linux distribution methodolgy of JMRI. Actually, I expect that the current Experimental "Flatpak" distribution of JMRI won't work on my machine(s) anyway -- I expect it is a x86_64 Flatpak and all of my machines use ARM processors. And this brings up a *new* issue that will complicate things: there would need to be *four* Linux flatpaks: ix86, x86_64, armv7l, and aarch64. My only thought about "improvements" in the Linux distribution of JMRI would be the creation of .deb and .rpm distrubutions of JMRI. I realize that JMRI will never be in any Linux distro repo and I understand why that is, but a self-made .deb and .rpm with a proper openjdk-XX-jre depenency could be helpful. *I* could probably help with creating the necessary control files to help with this, if anyone is interested. At Fri, 4 Apr 2025 08:19:38 -0400 "Bob Jacobsen via groups.io" <rgj1927@...> wrote: -- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services -- Linux Administration Services heller@... -- Webhosting Services |
|
Re: Experimental "Flatpak" distribution of JMRI
As long as it is an additional option for Linux users.听 I run RPi and it is super easy right now to rename the existing JMRI folder and extract the replacement.听 Yes, I do have to handle Java separately, but then how often is the Java requirements changed.听 I would hate to see the existing process changed and/or complicated by something called Flatpak.
--
-splasher in somd -NCE PowerCab with Raspberry Pi 3b+ and JMRI -DCC-EX with Arduino Mega听w/motor shield, Raspberry Pi 3b+ and JMRI -Using听听Engine Driver with both -Generally running the latest dev version of JMRI & Engine Driver |
Peter Ulvestad
George Hofmann
splasher
to navigate to use esc to dismiss
One for the more learned amongst us to have a look at.
听
I have the following set up听:
听
NCE Powercab, JMRI running on a Raspberry Pi via NCE USB using M Steve Todd's files, Panel Pro with a touchscreen panel to operate turnouts, turnout motors are DCC Supplies Cobalt Digital IP.
听
The touchscreen panel works exactly as intended to control the turnouts.
听
I would like the ability to use my phone to become a second throttle.
听
With Wi-Throttle server running, I connected my phone to the WiFi network created by the Raspberry Pi, opened up the Engine Driver app & connected to the server.
听
And here is where it goes wrong. Typing a loco address and then trying to move something , absolutely no response from the loco. If I try to operate a turnout motor via the accessory address , it works perfectly. The loco isn't stuck in consist mode as it works off the bat from the NCE handset using the same DCC address so as far as I know I'm not using the wrong address.
听
On the Wi Throttle server screen I can see the phone throttle is connected and even the address of the locomotive I'm trying to control. The Track power is on.
听
Can anyone give any pointers here?
听
thanks in advance