开云体育


Re: Difference Between Compare and Reset #decoderpro

 

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!


Re: Train tracking, dealing with gaps #traintracking

 

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


Re: Cars Returning to Staging #operationspro

 

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


Re: Difference Between Compare and Reset #decoderpro

 

Which decoder definition is this, exactly?

Bob


Bob Jacobsen
rgj1927@...


Re: Difference Between Compare and Reset #decoderpro

 

开云体育

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


Re: Cars Returning to Staging #operationspro

 

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


Re: Difference Between Compare and Reset #decoderpro

 

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

On Thu, 3 Apr 2025, 21:45 Phil G via , <phil=[email protected]> wrote:
After writing back to the decoder, what’s in cvs 1, 17, 18, 29 and 19??

Phil G

On 3 Apr 2025, at 21:18, Steve Haas via <Goatfisher2=[email protected]> wrote:

?

Continuing the conversation, Don responds:

?

      Are you saying that CV 19 would somehow elude the Compare?

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: Cars Returning to Staging #operationspro

 

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


Re: Difference Between Compare and Reset #decoderpro

 

开云体育

After writing back to the decoder, what’s in cvs 1, 17, 18, 29 and 19??

Phil G

On 3 Apr 2025, at 21:18, Steve Haas via groups.io <Goatfisher2@...> wrote:

?

Continuing the conversation, Don responds:

?

      Are you saying that CV 19 would somehow elude the Compare?

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: Difference Between Compare and Reset #decoderpro

 

开云体育

Continuing the conversation, Don responds:

?

      Are you saying that CV 19 would somehow elude the Compare?

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

On Thu, 3 Apr 2025 at 20:58, Dave Sand via <ds=[email protected]> wrote:
Wouter,

"salient part" is subject to missing important data.

Dave Sand



----- Original message -----
From: "whmvd via " <vandoornw=[email protected]>
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

On Thu, 3 Apr 2025, 20:26 erik via , <erik=[email protected]> wrote:
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 -----
From: "whmvd via groups.io" <vandoornw=[email protected]>
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

On Thu, 3 Apr 2025, 20:26 erik via , <erik=[email protected]> wrote:
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

 

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


On Thu, 3 Apr 2025, 20:26 erik via , <erik=[email protected]> wrote:
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

 

Erik,

Go to "Help -> System Console". ?Click on the "Copy to clipboard" button and paste into a reply.

Dave Sand

----- Original message -----
From:?erik@...
Subject: Re: [jmriusers] Cannot start to read decoders
Date: Thursday, April 03, 2025 2:25 PM

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,
can you please explain how to post the logfile here so one knows it belongs to this discussion?
Thank you
Erik


Re: Train tracking, dealing with gaps #traintracking

 

George,

Maybe you could put a long going "inactive delay" on block A. ?Or both if bi-directional.

Dave Sand



----- Original message -----
From: "George Hofmann via groups.io" <george.hofmann=[email protected]>
Subject: Re: [jmriusers] Train tracking, dealing with gaps #traintracking
Date: Thursday, April 03, 2025 1:54 PM

Dave
I think LogixNG would work here. I tried putting a dummy block in between that was constantly occupied but that did not work unsurprisingly.
?
But I'm confused about your third option. I'm already not telling JMRI that a gap exists. As far as it knows the two monitored blocks are abutting even though physically they are not. It's just that block A goes dark before block B lights up.?
?
Thanks for the help.
George
?


Re: Train tracking, dealing with gaps #traintracking

 

Dave
I think LogixNG would work here. I tried putting a dummy block in between that was constantly occupied but that did not work unsurprisingly.
?
But I'm confused about your third option. I'm already not telling JMRI that a gap exists. As far as it knows the two monitored blocks are abutting even though physically they are not. It's just that block A goes dark before block B lights up.?
?
Thanks for the help.
George
?


Re: How to delete a turnout with jython

 

Ralph,
?
In agreement with the previous posters on this thread, the concept of dynamically removing track seems like something for a bad horror movie.? Really?
?
However, since Sensors and Turnouts are both bean objects, the postings /g/jmriusers/topic/108527414#msg234620 "Deleting Objects in Scripts" seems like it has the information requested.? Of course, the "why?" was not answered there either.
?
Happy destruction.? But keep it contained to your layout.
?
Cliff in Baja SoCal


Re: How to delete a turnout with jython

 

I like the symmetry of constructors and destructors. I do understand that automatic garbage collection was a primary justification for Java (yet another programming language), and destructors per se do not exist. Fortunately I found deleteBean() and now can blow away all kinds of stuff.
?
Anytime I have to deal with a new programming or scripting language (currently python/java for JMRI) I am reminded of a truly classic article from 1982. My hard copy that I have had since then is titled "Real Programmers Don't Write Pascal." At the time I was a proficient Fortran 66 user, and yes did use punch cards and JCL on IBM 360/370 mainframes and had worked at Sandia National Labs, so I appreciated the tongue in cheek humor. The article can still be found, https://en.wikipedia.org/wiki/Real_Programmers_Don't_Use_Pascal.
--
-Ralph


Re: Train tracking, dealing with gaps #traintracking

 

George,

If you can use a test release, JMRI 5.11.2 introduced a concept called a ghost block. ?The allows Dispatcher to simulate a train going through the ghost block.

If you are just looking at train tracking, you can create a virtual block and use Logix or LogixNG to simulate occupancy. ?

Another approach is to pretend the gap does not exist. ?Don't tell JMRI about the gap. ?Of course, that will not work if the gap is a turnout.

Dave Sand


----- Original message -----
From: "George Hofmann via groups.io" <george.hofmann=[email protected]>
Subject: [jmriusers] Train tracking, dealing with gaps #traintracking
Date: Thursday, April 03, 2025 1:06 PM

I created a nice panel for the museum layout and created train tracking markers on it. It works well except for one show stopping thing. At one spot in the loop there is a detection gap between blocks that kills the tracking. The gap is only 1 or 2 seconds.?
?
Is there a workaround for this? Increasing train length is not an option. Installing a new detector is not likely either.
?
George