开云体育

?My question is this: is it better to 'Read All Sheets' first or read each sheet individually?

I have been reading each sheet by sheet. Is there an advantage doing it that way or reading all sheets at once?

Look forward to all of the replies,

William

I actually prefer to do the basic set up (road name, etc.), auto find the decoder if it will read it, or manually select if it does not, and then go to the CV tab and read the entire sheet. ?Once you pull all the CVs in you have the entire program that is in the decoder. ?If I end up with a couple of CV that did not read properly (generally shown as unknown in the list) I manually read those one at a time until the sheet is free of errors. ?Then I save it to JMRI. ?From there if I want to make changes to the speed table, the address, or other settings, I do it at then and save the changes.

George

William,

On 25 May 2019, at 7:10 AM, William Warren <fec449@...> wrote:

My question is this: is it better to 'Read All Sheets' first or read each sheet individually?

I have been reading each sheet by sheet. Is there an advantage doing it that way or reading all sheets at once?

In theory it shouldn't matter. However in practice, read on:

Because of a known (but as yet unresolved) issue in JMRI code, it is better to use "Read Full Sheet" on the CVs pane instead of "Read All Sheets". It is less likely to cause errors when reading a decoder with lots of CVs.

Once finished, some may be missed (displayed in red). Use "Read Changes on Sheet" as many times as needed until no red items remain.

Hint: Click on the Status column in the CVs pane until you see a down arrow. All the Red items will then be at the top.


Dave in Australia

Based on what I have previously read on this forum the recommended option would be to:
1. Read sheets one at a time, or
2. Go to the CVs tab and read all CVs in one pass there

there has been previous advise that using the Read All Sheets option on the other tabs cabling result in errors/problems -at least for some decoders.

Bob,

Power Pro (PP) is presound decoders, PP has trouble programming them.

There is a mod that can be don to increase the current on the PP, involves two
light bulbs I believe.

Or you could get one of the programming boosters (PowerPax ot the Soundtraxx
unit).

Rumour has it NCE is working on a new command station to address this and other
things like USB, etc., I may be too old by the time it hits the market though.

John

Bob and Jon,

On 25 May 2019, at 11:30 AM, Robert Schworm <rkschworm@...> wrote:

I have jmri connected serial to NCE Power Pro. The decoder is a tsunami2 - diesel for Alco-PA1. When I attempt to write all sheets on a programming track, jmri stalls out at 1.127 which is in the area of a feature called Digital Dynamic Exhaust. Anyone know why this is happening. When programming this with the NCE throttle, it states "WAIT" for several seconds and then completes. Jmri 14.

This particular problem has no connection with the known older Power Pro programming track circuitry deficiency.

Instead it relates to a Power Pro firmware issue that affects program track operations with both JMRI and the NCE throttle.

If you, by any means, attempt to write a value to any CV>256 in Program Track mode using an NCE Power Pro, the firmware will instead write to a CV<257, possibly corrupting your decoder.

For, example, if you use the NCE throttle to write a value to CV275, that value will be written to CV19 (the consist address) instead, making your decoder appear non-responsive to its normal address!

If you attempt use JMRI to write a value to CV275, JMRI intercepts that request (to protect your decoder) and instead throws an error (unfortunately not gracefully, but the error can be seen in the JMRI system console).

The DDE and other advanced panes in the TSU2 use CVs>256 so are affected.

The only workaround for these decoders is to read the decoder on the Program Track, then save and reopen in Program on Main mode. Attempting to use the NCE throttle as a workaround will simply corrupt other CVs in your decoder.

( The ESU decoders are not affected because ESU provides an in-decoder workaround that doesn't involve writing to CVs>256 so JMRI intercepts the write command and uses that workaround.)

If you have TSU2 decoders, your only choices are to use Program on Main or to get another programmer (such as a SPROG or an NCE Power Cab/NCE USB combination). JMRI can easily be configured to use two connections in the same session, with Program on Main, throttles, turnouts etc. being directed to the Power Pro and Program Track commands being directed to the SPROG/Power Cab.

Don't try other means to cheat around the firmware limitation in the Power Pro, it will inevitably lead to tears.

Dave in Australia