开云体育

Dave Falkenburg wrote:

A quick question for any Zephyr owners out there-- does it behave like
the DCS 100 or DB150?

(It does have a Loconet connection, right?)

Yes. It has the standard two ports.

I just not sure you can talk to it with Decoder pro. In other words,
but for reasons that I cannot recall, I believe the programming track is
not accessible via Loconet. But that is the question at hand? It would
be great if we can.


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)

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

A quick question for any Zephyr owners out there-- does it behave like

the DCS 100 or DB150?<

I have one but haven't hooked it up to DecoderPro yet. It should behave
just like a DCS100 as it has a programming track. DecoderPro does have a
different selection for it but I don't think there are any differences. I
have programmed with it using the programming track and it works just like
the Chief.

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

A quick question for any Zephyr owners out there-- does it behave like the DCS 100 or DB150?

(It does have a Loconet connection, right?)

-Dave

It seems that most are associated with using the DIY loco buffer device ..... but I would not draw any conclusion fron that as there is no way of knowing how many users have no problems at all ... regardless of which connection / system they are using.

John


John and Sandi Deecker jdeecker@...
Hemlock Junction Railroad 150 Mill St Milton ON L9T 1S2
DCC, HO, N & G model railroad supplies

Bob J,

The DN121 has a value of 1 for CV7 (Number appears in list and was
verified by a re-read.)

I'm at odds with this issue now as when testing the CV29 theory my
findings matched yours. The problem stated earlier did not recur!

I'm now rethinking the previous programming session to determine
what other actions might have been performed prior to programming
the DN121. Given this change (or rather normal operation!), I
wouldn't spend time trouble shooting the issue. I'll advise if I'm
able to replicate it again.

Bob

P.S. The decoder doesn't have a speed table thus this segment of the
pane should not appear.


--- In jmriusers@y..., Bob Jacobsen <Bob_Jacobsen@l...> wrote:

At 7:57 PM +0000 11/3/02, Bob Blackwell wrote:

During reprogramming of min/mid/max voltages for a Digitrax DN121
decoder, I ran into a situation where DecoderPro set the address

of

a previously programmed and functional decoder to 03. This

occurred

even though I had entered a short address of 86 and a long address
of 1586. I've been able to replicate this twice through the
following steps;

(Very nice description of how to repeat the problem omitted)

I just tried to reproduce this with a couple of different types of
decoders and failed. Unfortunately, it might be specific to the
DN121, or at least the DN121's programming definition.

What CV7 value does that have? (It doesn't appear in the listing)
It might be in the wrong family, as you mention that speed tables

are

showing up, but it doesn't have them.

It could be that the program is doing something to inadvertently

set

the decoder back to defaults. Or there could be a bug in how we
re-write the values. Or, somehow the software default of 03 is

not

getting changed, even though you edited the field.

I'll start looking at that last possibility. That code was

changed

in a recent test version (1.0.8, I think, but I'd have to check)

so

that if you re-wrote the short address, CV29 would also be forced

to

be re-written. This was to cope with the odd DZ121 and NMRA spec
behaviour. But perhaps a bug was introduced.

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@l..., 510-486-7355, fax 510-495-2957)

Is it just me, or are virtually all of the communications problems being seen unique to the various Digitrax systems?

Are other systems (Lenz, NCE, etc) having problems?

Mike B

Bob I see All of The statement s but this one;Write Programming Track: Write Byte in Paged Mode on Service Track
Setting CV29 to 2 (0x2)

From: Bob Jacobsen
Sent: Sunday, November 03, 2002 9:35 PM
To: jmriusers@...
Subject: Re: [jmriusers] programmer error

Sorry to come late to this.

At 3:33 PM -0500 11/2/02, Wendell Camp wrote:

Bob I am getting time out talking to station Its adb150 I know I
can't read the cvs but understood can write cvs

As far as I know, the DB150 should work fine. I don't have one to
test with, but other people use them routinely.

At 8:18 AM -0500 11/3/02, Wendell Camp wrote:

Jim I did the down load and installed still no joy decoder pro
starts up showing 1.0.6 don't if this right ,still get error time
out talking to command station, still didn't see where to choose pro
gram track Wendell

This is saying that there's something quite odd about how things are
arranged in your PC. You've downloaded the most recent version,
which definitely doesn't say it's version 1.0.6. Version 1.0.6
should work OK, but the fact that the download isn't correctly
updating to the most recent version seems to mean that there's
something missing.

If it's still not showing "Version 1.1", I think you should try
removing the program completely, then reinstalling it. To do this on
Windows:

1) In your Start menu you should find a "JMRI" group, which contains
an uninstall option. Pick that, and say OK ot any prompts.

2) Search for folders named "JMRI" and remove them.

3) Empty your recycle bin.

Then try to redownload the 1.1 version and run the installer. Keep a
careful eye out for any error prompts while running the installer,
too.

At 6:10 PM -0500 11/3/02, Wendell Camp wrote:

I have a loco buffer and I do see Programming track is available on
loco monitor Wendell

This is good! Since you're seeing traffic on the LocoNet monitor,
you're attached to the right port, the LocoBuffer is connected OK on
both ends, and data is getting into the PC. Periodically, you should
be seeing something that looks like this:

Request data/status for slot 123
Read Fast Clock: (Data is Invalid - ignore)
Running, rate is 4:1. Day 39, 3:44. Last set by ID 0x00
Master controller implements LocoNet 1.1,
Track Status is Off,
Programming Track is Available

That's the fast clock broadcasting on the Loconet.

When you click write, you should see something like:


(The CV number and value might vary)

Is that what's happening?

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

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



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

Hi,
This thread went from amusing me to frightening me.

Mike Davidson made a sensible suggestion for the entry names.
Convert the letters a...z to Upper Case.

Why did I get concerned?
Some of us have lived through the efforts of well meaning people trying to
solve the problem of the "correct" lexical order.
Of course, "they" universally only knew one way and usually refused to
admit to problems with code value based sorting.

For instance, ignoring case, how do you properly rank?
Saint
Ste.
St.
Sainte
San
Santa

Am I breaking through?
Do we modelers really care?

In short, on the nit picks, write your own formatter!

Regards,
===============
Chuck Card in sunny Arizona
Unlimited Sunsets

The "Java Human Interface Guidelines" recommend this order, but I
really don't know why. Does anybody? If people would prefer the
usual alpha order (AaBbCc etc), let me know. It's easy to change.

How about forcing to all key names to UPPER, lower case or do a case
independant sort. Then you don't have to worry about having the same name
but with different case causing problems with Windows file names. UNIX (and
your Mac) knows about the differences between upper and lower case names but
Windows thinks they are the same.

Does DecoderPro do anything to avoid upper/lower case filename issues now
for filenames? What happens if I save a decoder under a different case
name - do both entries try and share the same filename?

Alex

Note that all the upper-case letters are before all the lower case letters.

The "Java Human Interface Guidelines" recommend this order, but I
really don't know why. Does anybody? If people would prefer the
usual alpha order (AaBbCc etc), let me know. It's easy to change.

I vote that one use the usual Alpha order for it easier to understand and
is more importantly, more natural in terms of expectations.

The Java guidelines were probably written by unix geeks, rather than humans.
(Insert smiley face - I confess to being a unix geek) I too suggest simple
alpha ordering. In fact, it would be a good idea to completely ignore alpha
case in roster entry names. ie.: SoundTraxx == soundtraxx == SOUNDTRAXX...
This would keep me from creating a roster entry named xyz-123 and XYZ-123 for
the same locomotive/decoder.

Mike Davison

Bob Jacobsen wrote:

At 8:46 PM -0800 11/2/02, Michael Mosher wrote:

Also, how do I get the loco table to be sorted in Ver 1.1?

That should happen automatically. I'm a little surprised if it's not
being sorted, but a bug like that is certainly possible.

Note that it's a "lexical" sort. That means the sort-order is:

1
A
B
C
a
b
c

Note that all the upper-case letters are before all the lower case letters.

The "Java Human Interface Guidelines" recommend this order, but I
really don't know why. Does anybody? If people would prefer the
usual alpha order (AaBbCc etc), let me know. It's easy to change.

I vote that one use the usual Alpha order for it easier to understand and
is more importantly, more natural in terms of expectations.



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)

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

Hello,

I have followed with interest the different posts about decoders
programming by PC in the Lenz Digital Plus forum, and I have
downloaded the software DecoderPro. I have some Lenz decoders and
Intellibox as command station, but it do not run. How should I
configure the software to communicate with the IB?

Thank you for your attention.

Best regards,

Peli Martinez

Bob:
Re-set the "flow control" to No flow control but it had no effect. Still get the Timeout error. I saved and re-started the program, did not re-boot PC. Is that Right?

Bill

I hadn't heard about this.

Could you check something for me? Run the "JmriDemo" application,
and write some CVs using the "Simple Programmer" from the "Tools"
menu. That should leave the power on your main track off after
that's complete. Then, open a "Power Control" from the "Tools" menu,
and click the "On" button.

If that does what you want, then I can make it happen automagically.

It does! Automagically would be great. Thanks, Bob.

Aloha,
Jim

Bob,

Right, the whole Soundtraxx version ID mess is coming back to me now.

Diesel DSD series current grouping

LC Diesel
Version ID 34
DSD-100LC no FX1 or FX2, no hyperlight effects
Version ID 35
DSD-AT100LC/KT100LC no FX1 or FX2, do have hyperlight effects

PNP LC Diesel
Version ID 37
DSD-C628LC has both FX1 and FX2, has hyperlight
Version ID 36
DSD-LL100LC has FX2 only, no FX1, has hyperlight
DSD-LL110LC neither FX1 nor FX2???, has hyperlight
DSD-LL090LC neither FX1 nor FX2???, has hyperlight


Think we talked about how to handle the FX1 / FX2 stuff way back when for
the ID 36 group but I guess there is no way to have FX2 both on and off for
the the same ID! If I remember you were just going to leave out FX2 for
that family. In any case, it should be easy to put the other lighting
functions back in. I'll be happy to fix this up Bob. My gut would be to go
with a different file for each Version, but if you have something else in
mind I'll be happy to follow that.

Robin

At 7:57 PM +0000 11/3/02, Bob Blackwell wrote:

During reprogramming of min/mid/max voltages for a Digitrax DN121
decoder, I ran into a situation where DecoderPro set the address of
a previously programmed and functional decoder to 03. This occurred
even though I had entered a short address of 86 and a long address
of 1586. I've been able to replicate this twice through the
following steps;

(Very nice description of how to repeat the problem omitted)

I just tried to reproduce this with a couple of different types of decoders and failed. Unfortunately, it might be specific to the DN121, or at least the DN121's programming definition.

What CV7 value does that have? (It doesn't appear in the listing) It might be in the wrong family, as you mention that speed tables are showing up, but it doesn't have them.

It could be that the program is doing something to inadvertently set the decoder back to defaults. Or there could be a bug in how we re-write the values. Or, somehow the software default of 03 is not getting changed, even though you edited the field.

I'll start looking at that last possibility. That code was changed in a recent test version (1.0.8, I think, but I'd have to check) so that if you re-wrote the short address, CV29 would also be forced to be re-written. This was to cope with the odd DZ121 and NMRA spec behaviour. But perhaps a bug was introduced.

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

At 9:14 PM -0700 11/3/02, billroger wrote:

But I can't program any other decoder either. I have Loys Toys decoder tester, two clip leads to the programming track, but it won't see that either (DH121). Something is preventing it from seeing the programming track. The programming track, PROG A&B on the DCS100 are connected directly to the isolated programming track. I also have a Volt meter connected to the track and get no voltage from the DCS100. Is it possible that the DCS100 is not putting out anything? Maybe the OPS switch should be set or something.

You can check the DCS100, programming track wiring, etc, by doing a read and write operation from a throttle. I think you already said that works OK, so it seems likely that the DCS100 and downstream of that are all probably OK.

DecoderPro looks a lot like a throttle to the DCS100 once the info gets on the LocoNet. So the problem is probably between the PC and the LocoNet itself.

Since you're seeing messages in the LocoNet monitor window, you've got the program listening to the right comm port, got the LocoBuffer jumpers set right, etc.

But it still sounds like the PC can't _transmit_ to the LocoNet.

Could you try setting the "flow control" option in the preferences to "no flow control", then save and restart?

Bob


--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

Jon:
But I can't program any other decoder either. I have Loys Toys decoder tester, two clip leads to the programming track, but it won't see that either (DH121). Something is preventing it from seeing the programming track. The programming track, PROG A&B on the DCS100 are connected directly to the isolated programming track. I also have a Volt meter connected to the track and get no voltage from the DCS100. Is it possible that the DCS100 is not putting out anything? Maybe the OPS switch should be set or something.

Bill

At 8:46 PM -0800 11/2/02, Michael Mosher wrote:

I've noticed some omissions on the Soundtraxx DSD-AT100LC programmer. One
the light tab, there is only on/off and dimmable for light effects. The LC
decoder support 15 effects, using CV49 & CV50 bits 0 to 3. Also those CV
have other bits defined, Bit 4 selects the phase of the effect, bit 5
enables/disables grade crossing logic, and bit 6 allows the output to
respond to the FX1 or FX2 function instead of the HL and BL (respectively).
I use bit 6 of CV50 to allow independent rear light of F5. Also with bit 6,
since it allows FX1 & FX2 to be used, the function mapping tab needs to have
FX1 & FX2 in the table to allow functions to be assigned to them.

I find the Soundtraxx LC series Tech Ref Manual to be easier and more
complete over the LC Owners Manual.



Also, Soundtraxx supports CV106 & CV106, user defined CVs.

At 9:44 PM -0800 11/2/02, <rbgroups@...> wrote:

Michael,

You'll see all those lighting functions in the other SoundTraxx decoder files.
In fact they were in previous versions of the LC decoder files too. It looks
like the LC-Diesel and LC-Steam decoder files both got broken in this release.
Bob any idea what happened?

That's easy. I must have screwed up.

The history: There are two decoder definition files for Soundtrax steam "plug and play" decoders, plus another two for diesel. Roughly, one in each pair is the "early" version and the other is the "later" version. The file for the later decoders has more features.

For diesels, the "early" file is SoundTraxx_LC_Diesel.xml, which identifies decoder version 34. The "later" file is SoundTraxx_pnpLC_Diesel.xml which identifies version 36.

Just before 1.1 came out, there was a report that an DSD-AT100LC would hang DecoderPro if you tried to "read all". This was because that decoder didn't have CV51 or CV52, so when DecoderPro tried to read them, the operation failed. Since the config file _said_ they were there, DecoderPro was convinced they were there, and kept retrying. (The DSD-AT100LC was in the "later" file, which contains these CVs)

Interestingly, the version ID of the DSD-AT100LC is 35, intermediate between the 34 and 36 of the two files.

For more info on the background, see the earlier message:




I don't own any sound decoders, so can't test this directly. But it seemed clear that if the DSD-AT100LC doesn't have CV51 and CV52, it doesn't belong in the family of decoders that does.

So, I moved it back to the "earlier" family.

This was probably a mistake. There should probably be a decoder file/family that's intermediate between the "early" and "later" families, without CV51 and CV52, but with the CVs and features mentioned by Michael Mosher above.

I'd be happy to help somebody set up such a file, but I can't do it myself because I don't have one of these decoders. As we've seen from this experience, these files really do need to be tested with a real decoder.

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

At 8:46 PM -0800 11/2/02, Michael Mosher wrote:

Also, how do I get the loco table to be sorted in Ver 1.1?

That should happen automatically. I'm a little surprised if it's not being sorted, but a bug like that is certainly possible.

Note that it's a "lexical" sort. That means the sort-order is:

1
A
B
C
a
b
c

Note that all the upper-case letters are before all the lower case letters.

The "Java Human Interface Guidelines" recommend this order, but I really don't know why. Does anybody? If people would prefer the usual alpha order (AaBbCc etc), let me know. It's easy to change.

Bib
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)