Re: Experimental "Flatpak" distribution of JMRI
Bob:
Correction on the JDK... The flatpak installed 5.10 is running on JDK 17.0.11...
Mint running a java --version is reporting the 21.0.6 the Mint distro java version...
More Linux users need to check in...
Jim
|
Re: Experimental "Flatpak" distribution of JMRI
Bob:
Just happen to be sitting in the lab and saw the email...
Using Linux Mint 22.0 which uses flatpak for installs during updates so it's right there to try.
Yes... Your URL downloaded and doing a flatpak install was good, just supplying password and Y when needed. There was a 5.8 on that machine and it seems to have been found when the 5.10 installed brought prefs forward.
I didn't check logs to see if the JDK was changed, quick check is version 21.0.6.
Obviously need to run more checks... this is a test machine and not in production...
Jim Albanowski
|
Experimental "Flatpak" distribution of JMRI
A user has been interested in possibly distributing JMRI as a “FlatPak” for Linux. I don’t know much about that method, but apparently the distribution file also includes the JRE, so it’s (at least in theory) easier to install.
As an experiment, you can find a 5.10 distribution in this form at
For more on this, see JMRI/JMRI Issue 11658:
Is anybody familiar enough with this distribution method to be able to try it?
Is this something that we should do on an ongoing basis?
Bob
—
Bob Jacobsen
rgj1927@...
|
Expanding on Dave Sand's idea, assign a virtual sensor to the block.
The sensor is set occupied by Logix or LogixNG when both blocks on either side are occupied, otherwise unoccupied.
This is the way I have been indicating occupied turnouts, without hardware detection, for years (before the creation of the "ghost" block).
--
Ken NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959) Loconet * JMRI 5.11.4 * OSX,Win10,Ubuntu
Blog: ?
Youtube:
|
Phil G,
?
CV 1: 9, CV 17: 213, CV 18: 96, CV 29: 39, CV 19: 0. While there is a Primary Address of 9, I use the Long Address 5472. I ran the loco reversed.
?
And Acceleration and Deceleration are 25 and 15.
?
Regards
|
All,
?
The point about braking is certainly a good one. I've just never used anything more than braking sound effects, no actual slowing of the loco.
?
Regards
|
Bob,
?
It's in my OP.
?
Regards
|
I was suggesting one step at a time. Small ones
Phil G
toggle quoted message
Show quoted text
On 4 Apr 2025, at 07:44, Mick Moignard via groups.io <mick@...> wrote:
?
Writing CVs back to a decoder will not magically turn a function, like
brakes, back on.
I’d look at speed tables, inertia, stuff like that next if the OP is sure
his addressing is correct.
Mick
Mick
______________________________________
Mick Moignard
mick@...
p:+44 7774 652504
The week may start M, T, but it always ends WTF!
|
Writing CVs back to a decoder will not magically turn a function, like
brakes, back on.
I’d look at speed tables, inertia, stuff like that next if the OP is sure
his addressing is correct.
Mick
Mick
______________________________________
Mick Moignard
mick@...
p:+44 7774 652504
The week may start M, T, but it always ends WTF!
|
Well yeah! Delay to inactive should do the trick. I was not aware of that little tool.
I'll give it a try.
?
Tnx again
George
|
Hi folks
Well darn! As usual the answer is easy but I didn’t think of it
Thank very much! ?
John Stewart
Birmingham District MRR
|
Which decoder definition is this, exactly?
Bob
—
Bob Jacobsen
rgj1927@...
|
Wouter comments: ? “The question should really be asked as: - what does jmri write to these cvs? - what is read back on the programming track? That would rule out another type of error.” ? JMRI _should_ be writing that which is displayed on the screen when whatever command to write to the decoders is executed.? Hopefully it is either “Write all . . . “. ? Reading back the values of the CVs _after_ the “Write .? . “ to the decoder would be a good idea, but I suspect the OP has done the equivalent by using the compare process on the CV’s tab. ? Anything that sheds further light on what is occurring is a good idea. ? Best regards, ? Steve ? Steve Haas Snoqualmie, WA
|
John,
?
I would also recommend that you disable pickups on the staging arrivals track, so the program does not move the "moves" to the last movement.
?
Eric
|
The question should really be asked as: - what does jmri write to these cvs? - what is read back on the programming track? That would rule out another type of error.
Wouter
After writing back to the decoder, what’s in cvs 1, 17, 18, 29 and 19??
Phil G
?
Continuing the conversation, Don responds:
?
Not likely – CV19 is just another location in the decoder to be compared to the data stored in the record in the Decoder Pro Decoder index.
This could be tested by changing CV19 in either the decoder itself or in the record in Decoder Pro, then running the compare function on the CV page.
“You read the part where I say the settings had been working... for years in fact,
right? No mysterious brake, BEMF, consist, or the like. And
Economies don't, to my knowledge, have Drive Hold, Reverser Centered, or such features that could even accidentally
be activated.”
Yes, I did.
The symptoms are identical to those reported previously by others where the
braking functionality _has_
been revealed to be the cause.? While you are
adamant this is not the case (no reason to doubt you), the symptoms _do_
seem to match that possibility.
So, if not braking related, what is left?
From your description, a reset decoder
works fine until the values stored in Decoder Pro are written to the decoder,
at which time the decoder ceases to
respond.
I don’t recall the specifics;? Can you share the make
and model of both your DCC system and the decoder again??
After you issue the decoder reset
command, the loco/decoder responds at short address three, correct?
And after that you write the data
stored in Decoder Pro back to the decoder, correct?
Does writing the settings from Decoder Pro
back to the decoder itself result in the address being changed from short address 3 to some other address (short or long), and that is the address
the decoder is not responding to?
I’m starting to suspect some type of
potential disconnect between data loaded into the decoder
via the reset, and data the command station
has stored in regard to the address that doesn’t work after the decoder data is written to the decoder.
Various DCC systems store different pieces of data about a loco/decoder in their memory.
I’m not a specialist on the internal workings of various command stations, so folks with knowledge of your specific
system’s internal workings would have to chime in here.
Hopefully this will give you some additional
paths to explore.
Keep us posted.
Best regards,
Steve
Steve Haas
Snoqualmie, WA
?
Regards
|
On Thu, Apr 3, 2025 at 02:23 PM, John Stewart wrote:
So, my question is, "cars returning to staging used to go out on the layout, and take a ride back to staging -- can this be made to happen as it used to?"? That is, the "move" instruction would have been a "P/U" instruction for leaving staging, and a "S/O" instruction upon return instead of what I'll call a "move to remain" instruction.
Yes John, you can control how the program deals with cars out of staging.? Don't allow set outs on the staging departure track.? That will force the cars to take a ride.
?
?
Dan
|
After writing back to the decoder, what’s in cvs 1, 17, 18, 29 and 19??
toggle quoted message
Show quoted text
On 3 Apr 2025, at 21:18, Steve Haas via groups.io <Goatfisher2@...> wrote:
?
Continuing the conversation, Don responds:
?
Not likely – CV19 is just another location in the decoder to be compared to the data stored in the record in the Decoder Pro Decoder index.
This could be tested by changing CV19 in either the decoder itself or in the record in Decoder Pro, then running the compare function on the CV page.
“You read the part where I say the settings had been working... for years in fact,
right? No mysterious brake, BEMF, consist, or the like. And
Economies don't, to my knowledge, have Drive Hold, Reverser Centered, or such features that could even accidentally
be activated.”
Yes, I did.
The symptoms are identical to those reported previously by others where the
braking functionality _has_
been revealed to be the cause.? While you are
adamant this is not the case (no reason to doubt you), the symptoms _do_
seem to match that possibility.
So, if not braking related, what is left?
From your description, a reset decoder
works fine until the values stored in Decoder Pro are written to the decoder,
at which time the decoder ceases to
respond.
I don’t recall the specifics;? Can you share the make
and model of both your DCC system and the decoder again??
After you issue the decoder reset
command, the loco/decoder responds at short address three, correct?
And after that you write the data
stored in Decoder Pro back to the decoder, correct?
Does writing the settings from Decoder Pro
back to the decoder itself result in the address being changed from short address 3 to some other address (short or long), and that is the address
the decoder is not responding to?
I’m starting to suspect some type of
potential disconnect between data loaded into the decoder
via the reset, and data the command station
has stored in regard to the address that doesn’t work after the decoder data is written to the decoder.
Various DCC systems store different pieces of data about a loco/decoder in their memory.
I’m not a specialist on the internal workings of various command stations, so folks with knowledge of your specific
system’s internal workings would have to chime in here.
Hopefully this will give you some additional
paths to explore.
Keep us posted.
Best regards,
Steve
Steve Haas
Snoqualmie, WA
?
Regards
|
Continuing the conversation, Don responds:
?
Not likely – CV19 is just another location in the decoder to be compared to the data stored in the record in the Decoder Pro Decoder index.
This could be tested by changing CV19 in either the decoder itself or in the record in Decoder Pro, then running the compare function on the CV page.
“You read the part where I say the settings had been working... for years in fact, right? No mysterious brake, BEMF, consist, or the like. And Economies don't, to my knowledge, have Drive Hold, Reverser Centered, or such features that could even accidentally be activated.”
Yes, I did.
The symptoms are identical to those reported previously by others where the braking functionality _has_ been revealed to be the cause.? While you are adamant this is not the case (no reason to doubt you), the symptoms _do_ seem to match that possibility.
So, if not braking related, what is left?
From your description, a reset decoder works fine until the values stored in Decoder Pro are written to the decoder, at which time the decoder ceases to respond.
I don’t recall the specifics;? Can you share the make and model of both your DCC system and the decoder again??
After you issue the decoder reset command, the loco/decoder responds at short address three, correct?
And after that you write the data stored in Decoder Pro back to the decoder, correct?
Does writing the settings from Decoder Pro back to the decoder itself result in the address being changed from short address 3 to some other address (short or long), and that is the address the decoder is not responding to?
I’m starting to suspect some type of potential disconnect between data loaded into the decoder via the reset, and data the command station has stored in regard to the address that doesn’t work after the decoder data is written to the decoder.
Various DCC systems store different pieces of data about a loco/decoder in their memory.
I’m not a specialist on the internal workings of various command stations, so folks with knowledge of your specific system’s internal workings would have to chime in here.
Hopefully this will give you some additional paths to explore.
Keep us posted.
Best regards,
Steve
Steve Haas
Snoqualmie, WA
?
Regards
|
Re: Cannot start to read decoders
True. The complete session would be best, but that runs the risk of getting not just one session but the last - many (from the "other" file). You're right, I should have been clearer.
Wouter
Wouter,
"salient part" is subject to missing important data.
Dave Sand
----- Original message -----
Subject: Re: [jmriusers] Cannot start to read decoders
Date: Thursday, April 03, 2025 2:53 PM
Erik,
You can either do a cut-and-paste of the salient part, or add the file to directory "problemsbeingworkedon" in the file area, following that with the posting of a link to it in this thread.
Wouter
Wouter,
can you please explain how to post the logfile here so one knows it belongs to this discussion?
Thank you
Erik
|
Re: Cannot start to read decoders
Wouter,
"salient part" is subject to missing important data.
Dave Sand
----- Original message -----
Subject: Re: [jmriusers] Cannot start to read decoders
Date: Thursday, April 03, 2025 2:53 PM
Erik,
You can either do a cut-and-paste of the salient part, or add the file to directory "problemsbeingworkedon" in the file area, following that with the posting of a link to it in this thread.
Wouter
Wouter,
can you please explain how to post the logfile here so one knows it belongs to this discussion?
Thank you
Erik
|
Bob Jacobsen
Ken Heywood
George Hofmann
John Stewart