开云体育

Locked Coping with the user-fiendish features of the DZ121


 

At 3:15 PM -0700 7/31/02, Jon Miller described a nasty feature of the DZ121:
It basically says that anytime you reprogram CV01 (the 2digit address), the
DZ121 automatically resets several CVs. The key here is the reset doesn't
happen during programming, it happens the first time the DZ121 powers up on
the layout in normal mode. So if you use the PR1 to program your values and
change CV01, using the PR1 to read back the data shows everything as you
would expect. In other words, it confirms everything was programmed as you
requested. But when you carry the loco to the layout and place it on the
track, the DZ121 powers up, detects the CV01 change and resets the following
CVs ...
The nasty thing about this is that there's no way for DecoderPro to fix it while the decoder is on the programming track; the CVs are changed when you _later_ power the decoder. At that point, it's too late for the program to fix the values.

Can anybody think of a good way to cope with this?

The best idea way that I've thought of is to have the short address be a read-only variable on the programming screen. You then can't change the short address value, so you can't trip the "feature". I'd add a tooltip that says why this value is held read-only, and suggests that sequence that you need to set the short address.

Yes, that's ugly. I'm hoping that somebody has a better idea.

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
At CERN until August 10, replies may be slow.


Jon Miller
 

The best idea way that I've thought of is to have the short address
be a read-only variable on the programming screen.<

The PR1DOS software has a special DZ121 program button. I would suspect
the way that's done is to lock out programming CV01, basically what you are
suggesting. I think it's the only way to do it with a DZ121.
I weird thing about this is I understand it's a NMRA legal feature. It
seems it's one that should be changed!

Jon Miller
AT&SF
For me time has stopped in 1941
Digitrax DCC owner, Chief system
NMRA Life member #2623
Member SFRH&MS


Mark Gurries
 

Bob Jacobsen wrote:

At 3:15 PM -0700 7/31/02, Jon Miller described a nasty feature of the DZ121:
It basically says that anytime you reprogram CV01 (the 2digit address), the
DZ121 automatically resets several CVs. The key here is the reset doesn't
happen during programming, it happens the first time the DZ121 powers up on
the layout in normal mode. So if you use the PR1 to program your values and
change CV01, using the PR1 to read back the data shows everything as you
would expect. In other words, it confirms everything was programmed as you
requested. But when you carry the loco to the layout and place it on the
track, the DZ121 powers up, detects the CV01 change and resets the following
CVs ...
The nasty thing about this is that there's no way for DecoderPro to
fix it while the decoder is on the programming track; the CVs are
changed when you _later_ power the decoder. At that point, it's too
late for the program to fix the values.

Can anybody think of a good way to cope with this?
I guess the problem solution depends on the command station.

With NCE, you can cycle power on the programming track allowing you to
work around this.

I cannot say absolutely about the others but it should be possible too
since the service mode programming track is supposed to be unpowered when
you put the locomotive on it and then enable the programing. Clearly
this will not work with a system that do not support service mode tracks.

This get things complicated since now we have a decoder pane response
that depends on a command station.

Maybe what you do is define a command that called reset that can be added
to the XML files as part of the script in some way. When the command is
called, a dialog box pops up and says resetting the programming track and
goes away when it is done. But if the command cannot be implemented
because the command station does not support it, it tells the user what
to do manually instead.




Best Regards,

Mark Gurries
Linear Technology
Power Supply & Battery charger Applications Engineer/Manager
---------------------------------------------------------
Model Railroad Club and NMRA DCC presentations are at:

--------------------------------------------------------
Audio Enthusiast (Love SAE equipment)


----------------------------------------------------------


 

I tried a test with my Digitrax DCS100 - the programming track is
unpowered until a read or write operation is done. Then the power
comes on, the action is performed and the power goes off. So I would
assume the DZ121 power up reset would take place on the next
read/write. (unless there is a difference in powering on the
programming track compared to the running track).

This would mean that if DecoderPro followed the write with a read or
a second write action, it would force the reset.

A few caveats:
I was using the throttle, not DecoderPro. (I havne't got my
Locobuffer built yet).
This wouldn't work with Ops mode programming as the power is not
cycled.
I haven't yet tried one of my DZ121's to see if I can force the reset
on the programming track using a read command. Maybe I'll have time
tomorrow.

Dennis

--- In jmriusers@y..., Mark Gurries <gurriesm@m...> wrote:
Bob Jacobsen wrote:

At 3:15 PM -0700 7/31/02, Jon Miller described a nasty feature of
the DZ121:
It basically says that anytime you reprogram CV01 (the 2digit
address), the
DZ121 automatically resets several CVs. The key here is the
reset doesn't
happen during programming, it happens the first time the DZ121
powers up on
the layout in normal mode. So if you use the PR1 to program your
values and
change CV01, using the PR1 to read back the data shows everything
as you
would expect. In other words, it confirms everything was
programmed as you
requested. But when you carry the loco to the layout and place
it on the
track, the DZ121 powers up, detects the CV01 change and resets
the following
CVs ...
The nasty thing about this is that there's no way for DecoderPro
to
fix it while the decoder is on the programming track; the CVs are
changed when you _later_ power the decoder. At that point, it's
too
late for the program to fix the values.

Can anybody think of a good way to cope with this?
I guess the problem solution depends on the command station.

With NCE, you can cycle power on the programming track allowing you
to
work around this.

I cannot say absolutely about the others but it should be possible
too
since the service mode programming track is supposed to be
unpowered when
you put the locomotive on it and then enable the programing.
Clearly
this will not work with a system that do not support service mode
tracks.

This get things complicated since now we have a decoder pane
response
that depends on a command station.

Maybe what you do is define a command that called reset that can be
added
to the XML files as part of the script in some way. When the
command is
called, a dialog box pops up and says resetting the programming
track and
goes away when it is done. But if the command cannot be
implemented
because the command station does not support it, it tells the user
what
to do manually instead.




Best Regards,

Mark Gurries
Linear Technology
Power Supply & Battery charger Applications Engineer/Manager
---------------------------------------------------------
Model Railroad Club and NMRA DCC presentations are at:

--------------------------------------------------------
Audio Enthusiast (Love SAE equipment)


----------------------------------------------------------


Michael Mosher
 

I haven't tried it but: The DCS100 can make the program track outputs into
a broadcast brake generator (still low current). This should provide power
to the decoder when not programming, then switch to program insturction
packets during programming then back to boradcast stop packets to keep power
to the decoder. DecoderPro could then set and clear OpSw47 as needed for
power / no power to the program track for the needed power cycle.

From the Super Chief manual page 119 (pdf page 61)

"OpSw47: Program track is brake generator when not programming. Braking is
DCC set to speed 0 (not Emergency stop) for address 0, light ON, broadcast
to all addresses"

More info at:


Michael Mosher
Webmaster
Daylight Division PCR/NMRA www.trainweb.org/daylight
Golden Empire Historical & Modeling Society www.trainweb.org/gehams
San Luis Obispo Model Railroad Club www.trainweb.org/slomrc
Personal
Member
Kern County Live Steamers www.trainweb.org/kernctyls

----- Original Message -----
From: millerdlca
To: jmriusers@...
Sent: August 06, 2002 08:24 PM
Subject: [jmriusers] Re: Coping with the user-fiendish features of the DZ121


I tried a test with my Digitrax DCS100 - the programming track is
unpowered until a read or write operation is done. Then the power
comes on, the action is performed and the power goes off. So I would
assume the DZ121 power up reset would take place on the next
read/write. (unless there is a difference in powering on the
programming track compared to the running track).

This would mean that if DecoderPro followed the write with a read or
a second write action, it would force the reset.

A few caveats:
I was using the throttle, not DecoderPro. (I havne't got my
Locobuffer built yet).
This wouldn't work with Ops mode programming as the power is not
cycled.
I haven't yet tried one of my DZ121's to see if I can force the reset
on the programming track using a read command. Maybe I'll have time
tomorrow.

Dennis

--- In jmriusers@y..., Mark Gurries <gurriesm@m...> wrote:
Bob Jacobsen wrote:

At 3:15 PM -0700 7/31/02, Jon Miller described a nasty feature of
the DZ121:
It basically says that anytime you reprogram CV01 (the 2digit
address), the
DZ121 automatically resets several CVs. The key here is the
reset doesn't
happen during programming, it happens the first time the DZ121
powers up on
the layout in normal mode. So if you use the PR1 to program your
values and
change CV01, using the PR1 to read back the data shows everything
as you
would expect. In other words, it confirms everything was
programmed as you
requested. But when you carry the loco to the layout and place
it on the
track, the DZ121 powers up, detects the CV01 change and resets
the following
CVs ...
The nasty thing about this is that there's no way for DecoderPro
to
fix it while the decoder is on the programming track; the CVs are
changed when you _later_ power the decoder. At that point, it's
too
late for the program to fix the values.

Can anybody think of a good way to cope with this?
I guess the problem solution depends on the command station.

With NCE, you can cycle power on the programming track allowing you
to
work around this.

I cannot say absolutely about the others but it should be possible
too
since the service mode programming track is supposed to be
unpowered when
you put the locomotive on it and then enable the programing.
Clearly
this will not work with a system that do not support service mode
tracks.

This get things complicated since now we have a decoder pane
response
that depends on a command station.

Maybe what you do is define a command that called reset that can be
added
to the XML files as part of the script in some way. When the
command is
called, a dialog box pops up and says resetting the programming
track and
goes away when it is done. But if the command cannot be
implemented
because the command station does not support it, it tells the user
what
to do manually instead.




Best Regards,

Mark Gurries
Linear Technology
Power Supply & Battery charger Applications Engineer/Manager
---------------------------------------------------------
Model Railroad Club and NMRA DCC presentations are at:

--------------------------------------------------------
Audio Enthusiast (Love SAE equipment)


----------------------------------------------------------

Yahoo! Groups Sponsor
ADVERTISEMENT



To unsubscribe from this group, send an email to:
jmriusers-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.