开云体育

Hello all,

It seems I want to do something that's not intended, and I'm wondering if
there's a way to do this neatly. I'm trying to use JMRI (decoderpro)
4.0-r29647 to program a speed curve in a Massoth Emotion L decoder. The
required values are:
0 for step 0
100 for steps 1-5
0 for all higher steps.
(I'm perfectly willing to explain why, but I don't think that's very
relevant now).

Using the CV tab to program the individual steps in individual CVs works,
and I have got the decoder working the way I want. But. I can't load the
decoder and have it display this information. It will simply revert to an
incorrect table where no value is lower than the one for the previous step,
showing adapted values in orange (that I absolutely don't want to store).
Nor can I fool JMRI into ever displaying what I want via manual changes.

It seems as if the curve I'm looking for is not displayable. Am I missing
something? Is this doable?

Wouter

There’s actually a bunch of complicated code in JMRI to _prevent_ what you want to do. The reason dates back 15 years to some NMRA dicta. It might be time to get past that and add a checkbox to the DecoderPro speed table pane that says “Allow speed steps to decrease” or something that.

In the mean time, it’s possible to make a custom decoder definition to do what you want, if it’s worth the effort. You just replace the speed table element with a bunch of individual CV elements, which can take any value you want.

Bob

On Oct 10, 2016, at 6:30 AM, Wouter van Doorn vandoornw@... [jmriusers] <jmriusers@...> wrote:

It seems I want to do something that's not intended, and I'm wondering if
there's a way to do this neatly. I'm trying to use JMRI (decoderpro)
4.0-r29647 to program a speed curve in a Massoth Emotion L decoder. The
required values are:
0 for step 0
100 for steps 1-5
0 for all higher steps.
(I'm perfectly willing to explain why, but I don't think that's very
relevant now).

Using the CV tab to program the individual steps in individual CVs works,
and I have got the decoder working the way I want. But. I can't load the
decoder and have it display this information. It will simply revert to an
incorrect table where no value is lower than the one for the previous step,
showing adapted values in orange (that I absolutely don't want to store).
Nor can I fool JMRI into ever displaying what I want via manual changes.

It seems as if the curve I'm looking for is not displayable. Am I missing
something? Is this doable?

--
Bob Jacobsen
rgj1927@...

I have done omething like that, sing the single CV programerto write the speed step. Walt

Hi Walt,

Yes, that's what I did (except I didn't use the right term for it). Glad to
see I'm not the only one to have run into that little difficulty.

Wouter

On 10 October 2016 at 15:06, walter.stanley.thompson.3@...
[jmriusers] <jmriusers@...> wrote:

I have done omething like that, sing the single CV programerto write the
speed step. Walt

[Non-text portions of this message have been removed]

I'd caution that depending on the code in the decoder, some may not do what
you want when the next speed step is a lower value from the prior speed
step. And I've heard that some will not accept the value during programming.
But most don't have those extra precautions.



-Ken Cameron, Member JMRI Dev Team

www.jmri.org

www.fingerlakeslivesteamers.org

www.cnymod.com

www.syracusemodelrr.org