Locked
Vmid/Vmax feature of DH121 Restricted to 14/28 SS'
Bob J,
I caught the following message in the Digitrax NG and thought it
might have an impact on DecoderPro. The DB has been updated
accordingly. I'm off now to check out the DN121 instruction card to
see if it suffers from the same limitation?
Bob B
toggle quoted message
Show quoted text
--- In digitrax@y..., "digilox1" <digilox1@y...> wrote: --- In digitrax@y..., "Jason Chenard" <jwchenard@y...> wrote: Jason, According to the instruction card that comes with the DH121, the decoder supports CVs 2/5/6, but is restricted to 14/28 ss operation with this features ON - like older Digitrax premium decoders,DH 150s for example. This limitation is not listed in the instruction card however.
I just spent some time programming the Vmax (CV5) and Vmid (CV6)
all the way down to 100d and 40d respectively. (Atlas RS1, Big Boy
system.) Even with these low values, which should have limited to
units to low speed, the decoder steadfastly continued to operate at the same speeds.
Do these CV's work on the DH121? I recall Loy's Toys saying that the feature is 'flawed'... --- End forwarded message ---
|
Stony, Would you be kind enough to verify the model number of your friends Soundtraxx decoder ? I'm maintaining a database (DB) of decoders supported by DecoderPro but don't see the model you reference listed. There is a DSD-AT100LC listed, however it may be different then the one mentioned. I'd like to make sure before there is a differnce before adding this unit to the DB. Also, if you find the model number is different, please provide a value for CV8. Thank You Bob --- In jmriusers@y..., "Rick C. Stone" <stony611@c...> wrote: All
I ws programming some locomotives at a friend's operating session last night and found a couple of anomolies.
One friend had just gotten a brand new DSD-100LC-AT from Soundtrax
and it has software version 35 which DecoderPro said it didn't recognize. Snip ... Stony
|
All the Atlas decoders I have work fine on four digit address. I have some
from the very first run of the Master GP38, number 340 as well as the later
version numbered 341 (don't yet have a four function number 342 decoder). I
don't think Atlas ever said the decoders did not support four digit, they
did say there system did not support four digit.
Did you also set CV29 to allow for four digit addressing? A value of 34
decimal sets CV29 to be four digit, 28/128 speed step, no analog conversion,
no speed tables, forward direction. There's no special config needed, just
set CV17/18 (long address) and CV29.
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
toggle quoted message
Show quoted text
----- Original Message ----- From: "Rick C. Stone" <stony611@...> To: <jmriusers@...> Sent: Sunday, November 10, 2002 6:54 AM Subject: [jmriusers] Anomolies All
I ws programming some locomotives at a friend's operating session last night and found a couple of anomolies.
One friend had just gotten a brand new DSD-100LC-AT from Soundtrax and it
has software version 35 which DecoderPro said it didn't recognize.
The second one is a little more complicated. He has amassed quite a few
Atlas GP-38s. Without trying he ended up with two road names that had the same last two digits of the road number. He asked me to find a way to give them different but easily recognizable numbers. I took the first one and fired up DecoderPro and promptly changed it to a four digit number. I was elated, this was going to be easier than I though and Atlas has been lying to us about the decoder's capability.
The second locomotive would appear to take a four digit address but when
you tried to operate it, it was still responding to the two digit address. When I went back and read the CVs, sure enough it was only two digit capable.
So the question becomes, did I get an Atlas decoder with an Easter Egg?
Or is there some special configuration that will allow an Atlas decoder to accept four digit addressing? Both decoders report the same software version (45).
Any ideas?
Stony
To unsubscribe from this group, send an email to:
jmriusers-unsubscribe@...
Your use of Yahoo! Groups is subject to
|
Locked
Re: Question on Loconet Tools
William - Thanks! I should have thought about looking in the start menu. Everything was there. Mike In a message dated 11/11/2002 5:28:38 AM Central Standard Time, hunk@... writes: Mike,
When you downloaded Decoder pro and installed it, it put a link on your
desktop for decoder pro. Don?t use that, go to the start menu->JMRI-> Loconet
Tools When you get there you can see all of the options and you can also
access Decoder Pro. If you do not have it under the start menu you probably
didn?t D/L the whole tools program. [Non-text portions of this message have been removed]
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Wendell,
I had this exact issue. Try running DecoderPro without hardware
handshaking.
If that works, you can either just run it that way, or jumper pins 5,6 &
8 on the RS2342 port.
JBB
Sunday, November 10, 2002, 8:53:34 AM, you wrote:
WC> Jon I tried this it didn't work still get program error talking to command station writing cv29
toggle quoted message
Show quoted text
WC> ----- Original Message ----- WC> From: Jon Miller WC> Sent: Tuesday, November 05, 2002 10:58 PM WC> To: jmriusers@... WC> Subject: Re: [jmriusers] programmer error WC> Wendell, WC> ????????? The following was posted on the Loco_Net hackers group. WC> first message; I just got the Locobuffer kit assembled.??? I've hooked it up to my laptop
WC> and to the Loconet. WC> Lights flash properly, the JMRI software monitor can show traffic on WC> Loconet. WC> The RRctrl program is able to grab a loco and control it. WC> However, the DecoderPro software is unable to do any programming.?????? It WC> keeps giving a message about being unable to contact the control WC> station.< WC> second message; Here is another piece of info:
WC> I tried putting the Locobuffer into MS100 mode, and set the DecoderPro WC> to talk to an MS100.??? With these settings, it worked!!!!!< WC> ????????? You might try the above. WC> Jon Miller WC> AT SF WC> For me time has stopped in 1941 WC> Digitrax DCC owner, Chief/Zephyr systems WC> NMRA Life member #2623 WC> Member SFRH MS WC> To unsubscribe from this group, send an email to: WC> jmriusers-unsubscribe@... WC> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.??? WC> WC> To unsubscribe from this group, send an email to: WC> jmriusers-unsubscribe@... WC> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. JBB - -- Best regards, Jonathan mailto:linuxgurugamer@... -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (MingW32) iD8DBQE9z89N8frsPBZFgFcRAsmKAJ0UUTGRmxEmxt83Wxj2p0EGFzGV4gCfVZtr iHAMgSxHTwcxSP0Z5igu55Q= =kYrw -----END PGP SIGNATURE-----
|
Locked
Re: Question on Loconet Tools
Mike,
When you downloaded Decoder pro and installed it, it put a link on your
desktop for decoder pro. Don?t use that, go to the start menu->JMRI->Loconet
Tools When you get there you can see all of the options and you can also
access Decoder Pro. If you do not have it under the start menu you probably
didn?t D/L the whole tools program.
-- William, Charleston, SC N scale & Digitrax Chief Great Model train Forums! www.hipple.com/forums
I've downloaded DecoderPro 1.1 and it seems to work well with my MS100 and
DCS100. However, I've seen mentioned some Loconet tools, such as a Command
Station Slot Monitor, and Send Loconet Packet, etc. There is a Loconet
monitor under the Debug heading in DecoderPro, but how do you get these other
Loconet tools. I've been to the jmri.sourceforge.net page, and while the
Loconet tools are talked about, none of the links on the page take me
anyplace that they can be downloaded. Any info on this would be appreciated.
Thanks
Mike K.
[Non-text portions of this message have been removed]
To unsubscribe from this group, send an email to:
jmriusers-unsubscribe@...
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
<> .
[Non-text portions of this message have been removed]
|
Locked
Re: USB-to-Serial converters handshake line termination
Any chance you could try the latest FTDI driver and temporarily remove
handshake line jumpers you added on the LB? I was hoping to find out if the handshake problem was in the FTDI hardware/driver or in the SDK/ JavaComm
software. I suspect software since it also has been reported on native
serial ports, but thought the test would be worthwhile. Well I removed the resistor and it works with my FTDI based USB to Serial converter, but does NOT work with the local hardware COM2. So it looks like the problem is definitely to do with DTR/DSR and maybe DCD on some systems but DCD on mine is open. When I run DecoderPro with debug enabled in JBuilder it reports the following: 0 locobuffer.LocoBufferAdapter DEBUG - configureBaudRate: 57,600 baud (J1 on 2&3) [main] 0 locobuffer.LocoBufferAdapter DEBUG - configureOption1: hardware flow control (recommended) [main] 16 locobuffer.LocoBufferAdapter DEBUG - configureOption2: DCS100 (Chief) [main] 187 locobuffer.LocoBufferAdapter DEBUG - Found flow control 2 RTSCTS_OUT=2 RTSCTS_IN= 1 [main] 187 locobuffer.LocoBufferAdapter DEBUG - Serial timeout was observed as: -1 false [main] 187 locobuffer.LocoBufferAdapter DEBUG - input stream shows 0 bytes available [main] 187 locobuffer.LocoBufferAdapter INFO - COM2 port opened at 57600 baud with DTR: true RTS: true DSR: false CTS: true CD: false [main] 437 locobuffer.LocoBufferAdapter DEBUG - port flow control shows hardware flow control [main] 26234 jmrit.AbstractIdentify WARN - Stopping due to error: timeout talking to command station [AWT-EventQueue-0] Alex
|
Locked
Re: USB-to-Serial converters handshake line termination
Any chance you could try the latest FTDI driver and temporarily remove
handshake line jumpers you added on the LB? I was hoping to find out if the handshake problem was in the FTDI hardware/driver or in the SDK/ JavaComm
software. I suspect software since it also has been reported on native
serial ports, but thought the test would be worthwhile. I will try and do the two tests tonight Alex
|
Locked
Question on Loconet Tools
I've downloaded DecoderPro 1.1 and it seems to work well with my MS100 and
DCS100. However, I've seen mentioned some Loconet tools, such as a Command
Station Slot Monitor, and Send Loconet Packet, etc. There is a Loconet
monitor under the Debug heading in DecoderPro, but how do you get these other
Loconet tools. I've been to the jmri.sourceforge.net page, and while the
Loconet tools are talked about, none of the links on the page take me
anyplace that they can be downloaded. Any info on this would be appreciated.
Thanks
Mike K.
|
Locked
Re: FAQ/Trouble Shooting LOG
OK! Then... I'll browse through the archives, but it would also be helpful
if people sent me some solutions (or at least the problems - I can try and
find the solutions in the archives). Michael.maloney@[no_spam]verizon.net
If you will be e-mailing me, please put JMRI FAQ in the subject line.
Thanks,
Mike M.
toggle quoted message
Show quoted text
-----Original Message----- From: Bob Jacobsen [mailto:Bob_Jacobsen@...] Sent: Saturday, November 09, 2002 2:11 AM To: jmriusers@... Subject: RE: [jmriusers] FAQ/Trouble Shooting LOG That would be great! There are lots of people here willing to help with details, etc, but if you could pull things together that would be a big help. Bob At 3:01 PM -0500 11/8/02, Maloney, Michael wrote: I don't have a tons of time myself, but would be willing to give it a
whack...
-----Original Message-----
From: Bob Jacobsen [mailto:Bob_Jacobsen@...]
Sent: Friday, November 08, 2002 2:18 PM
To: jmriusers@...
Subject: Re: [jmriusers] FAQ/Trouble Shooting LOG
At 1:34 PM -0800 11/6/02, Mark Gurries wrote:
Should someone be keeping a FAQ/Trouble shooting Log for each thing we
learn in terms of system setup? Take error messages and translated
them into check actions ect.... I hate to see BOB spend lots of time
in the future addressing common communication problems.
The log should include accessories Q&A such a Locobuffer setup info and
checks. Same with USB to Serial Adapters. You get the ideas.
Personally I do not have the time, but maybe others do. In the end I
hope that this file be included with the install as part of the
documentation.
Just an Idea... And a _very_ good idea. I've put a little of this info onto the web
pages, but if somebody wanted to write a section of the manual on
troubleshooting, it would help a bunch of people.
Unfortunately, I'm having trouble even keeping up with the email, as
this late reply attests. There's this blasted day job....
-- -------------- 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
|
All
I ws programming some locomotives at a friend's operating session last night and found a couple of anomolies.
One friend had just gotten a brand new DSD-100LC-AT from Soundtrax and it has software version 35 which DecoderPro said it didn't recognize.
The second one is a little more complicated. He has amassed quite a few Atlas GP-38s. Without trying he ended up with two road names that had the same last two digits of the road number. He asked me to find a way to give them different but easily recognizable numbers. I took the first one and fired up DecoderPro and promptly changed it to a four digit number. I was elated, this was going to be easier than I though and Atlas has been lying to us about the decoder's capability.
The second locomotive would appear to take a four digit address but when you tried to operate it, it was still responding to the two digit address. When I went back and read the CVs, sure enough it was only two digit capable.
So the question becomes, did I get an Atlas decoder with an Easter Egg? Or is there some special configuration that will allow an Atlas decoder to accept four digit addressing? Both decoders report the same software version (45).
Any ideas?
Stony
|
Jon I tried this it didn't work still get program error talking to command station writing cv29
toggle quoted message
Show quoted text
----- Original Message ----- From: Jon Miller Sent: Tuesday, November 05, 2002 10:58 PM To: jmriusers@... Subject: Re: [jmriusers] programmer error Wendell, The following was posted on the Loco_Net hackers group. first message; I just got the Locobuffer kit assembled. I've hooked it up to my laptop and to the Loconet. Lights flash properly, the JMRI software monitor can show traffic on Loconet. The RRctrl program is able to grab a loco and control it. However, the DecoderPro software is unable to do any programming. It keeps giving a message about being unable to contact the control station.< second message; Here is another piece of info: I tried putting the Locobuffer into MS100 mode, and set the DecoderPro to talk to an MS100. With these settings, it worked!!!!!< You might try the above. Jon Miller AT&SF For me time has stopped in 1941 Digitrax DCC owner, Chief/Zephyr systems NMRA Life member #2623 Member SFRH&MS To unsubscribe from this group, send an email to: jmriusers-unsubscribe@... Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
|
Locked
Re: USB-to-Serial converters handshake line termination
Alex,
Any chance you could try the latest FTDI driver and temporarily remove
handshake line jumpers you added on the LB? I was hoping to find out if the
handshake problem was in the FTDI hardware/driver or in the SDK/ JavaComm
software. I suspect software since it also has been reported on native
serial ports, but thought the test would be worthwhile.
Robin
toggle quoted message
Show quoted text
-----Original Message-----
From: Alex Shepherd [mailto:ashepherd@...]
Sent: Saturday, November 09, 2002 3:42 AM
To: jmriusers@...
Subject: Re: [jmriusers] USB-to-Serial converters handshake line
termination
The DecoderPro install instructions don't talk about Windows drivers.
Should they?
Well I'm not really sure you could say much generally except for known bad
hardware/software combinations.
So far what I have seems to work with the simple test I gave it,
but I only
got it recently as I am running out of serial ports.
I think if we go with a note to say that you should link the appropriate
pins either in the cable or on LB and run at 19200 then this should suit
most systems.
People can try the faster baud if they want, but it won't make much
difference as it still has to dribble out at 1666 onto the LN, but I guess
the latency is a fraction less :-)
Alex
To unsubscribe from this group, send an email to:
jmriusers-unsubscribe@...
Your use of Yahoo! Groups is subject to
|
Locked
Re: Roster order (was Re: Soundtraxx DSD-AT100LC)
At 2:27 PM -0800 11/4/02, Mike Davison wrote: 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. OK, done. It'll be in the next test version released, and is in CVS now. At 11:59 AM +1300 11/5/02, Alex Shepherd wrote: 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? It (is supposed to) notice that the file already exists and pick a different name. It's also supposed to prevent you from changing the ID of a roster entry to one that already exists. I haven't really tested that in a long time, however. Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
|
Locked
Re: USB-to-Serial converters handshake line termination
The DecoderPro install instructions don't talk about Windows drivers.
Should they?
Well I'm not really sure you could say much generally except for known bad hardware/software combinations. So far what I have seems to work with the simple test I gave it, but I only got it recently as I am running out of serial ports. I think if we go with a note to say that you should link the appropriate pins either in the cable or on LB and run at 19200 then this should suit most systems. People can try the faster baud if they want, but it won't make much difference as it still has to dribble out at 1666 onto the LN, but I guess the latency is a fraction less :-) Alex
|
Locked
Re: USB-to-Serial converters handshake line termination
At 4:17 PM -0700 11/8/02, Robin Becker wrote: Ok, so I can see a potential problem under the following circumstances:
If:
the USB-to-Serial device mfr has provided an RS232 connection to the DSR and
DCD pins on the FTDI device (quite possible),
and
if the dataset (LocoBuffer) isn't driving those lines (which we know - the
LB only supports CTS),
and
if those lines float at the "wrong" level,
and
if the device driver software enables those control inputs,
then
the PC driver would think that the LocoBuffer is not ready to receive and
the serial data output from the PC would not be transmitted.
This is all consisted with the reported behavior, namely that wiring the DSR
and DCD pins to the CTS pin on the LocoBuffer fixes the problem. The open
question is whether the device driver provides any means of disabling the
DSR and DCD via software while still enabling CTS, which would be the most
desirable solution. Sounds like that's definitely what's going on. The LocoBuffer driver code tells the Java comm library to set hardware flow control outbound (to the LocoBuffer), and not to set it outbound. But we don't have the source for that library, and I don't know whether it actually keeps those two separate directions when talking to Windows. Some of the reported problems have been with native serial ports on laptops, but the logic is probably similar. If the Java comm library or the OS isn't keeping the two directions separate, the missing control leads from the LocoBuffer will cause a problem. Setting "no flow control" will bypass it for DecoderPro, as DecoderPro only sends individual messages (e.g. sends the message and waits for the reply). The LocoBuffer shouldn't get stacked up. But other JMRI programs aren't that simple, and a lot of the LocoBuffer's advantages will be lost if we can't be sure it won't lose messages. Don't know if this affect anything but the drivers on the FTDI website are
more recent than those at the DSE link you provided. (FTDI says they are
now WHQL certified for WinXP) Anyone having problems with a USB-serial
device using an FTDI chip might want to check this site for the latest
driver.
The DecoderPro install instructions don't talk about Windows drivers. Should they? Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
|
Locked
Re: Program error -Timeout talking to Command Station
At 5:27 PM -0600 11/4/02, Michael Beckemeier wrote: 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? Unfortunately, yes. Right now, I'm working a problem with a Wangrow unit that talks to one Macintosh and not another, a Lenz system that programs once but requires power-cycling the LI100 interface to program again, and an EasyDCC system that doesn't turn the track power back on properly. But LocoBuffer problems have recently been causing a lot of traffic. In part that's because they've been hard to figure out, so they make a lot of emails go back and forth. And we used to have _lots_ of problems with the MS100 until we got that sorted out with the help of a bunch of people. I don't know that the Digitrax system has more or less problems per user than the others. It's hard for me to know how many people are using DecoderPro with which system, because I don't tend to hear when it just works. As the program moves forward, features tend to be present in the Digitrax code first. For example, the "speedometer" is still LocoNet-specific, the throttle that Glen Oberhauser is working on is being written for the LocoNet first, etc. That's mostly because people vote with their feet, and work on code for the system that's most directly useful to them. And so far, most of the people who've contributed code have Digitrax systems. (Although people with NCE and EasyDCC systems have also made important contributions, and I don't even know what system some of the people who have contributed decoder files use) Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
|
Locked
Re: FAQ/Trouble Shooting LOG
That would be great! There are lots of people here willing to help with details, etc, but if you could pull things together that would be a big help.
Bob
toggle quoted message
Show quoted text
At 3:01 PM -0500 11/8/02, Maloney, Michael wrote: I don't have a tons of time myself, but would be willing to give it a
whack...
-----Original Message-----
From: Bob Jacobsen [mailto:Bob_Jacobsen@...]
Sent: Friday, November 08, 2002 2:18 PM
To: jmriusers@...
Subject: Re: [jmriusers] FAQ/Trouble Shooting LOG
At 1:34 PM -0800 11/6/02, Mark Gurries wrote:
Should someone be keeping a FAQ/Trouble shooting Log for each thing we
learn in terms of system setup? Take error messages and translated
them into check actions ect.... I hate to see BOB spend lots of time
in the future addressing common communication problems.
The log should include accessories Q&A such a Locobuffer setup info and
checks. Same with USB to Serial Adapters. You get the ideas.
Personally I do not have the time, but maybe others do. In the end I
hope that this file be included with the install as part of the
documentation.
Just an Idea... And a _very_ good idea. I've put a little of this info onto the web
pages, but if somebody wanted to write a section of the manual on
troubleshooting, it would help a bunch of people.
Unfortunately, I'm having trouble even keeping up with the email, as
this late reply attests. There's this blasted day job....
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
|
Locked
Re: LocoBuffer/Decoder Pro Problem
Thanks Bob:
Hopefully, Robin Becker can help me out when I get back on Nov 12 Tuesday. I'm in Phoenix, AZ. Thanks again.
Bill
toggle quoted message
Show quoted text
----- Original Message -----
From: Bob Jacobsen
To: jmriusers@...
Sent: Friday, November 08, 2002 12:26 PM
Subject: Re: [jmriusers] LocoBuffer/Decoder Pro Problem
At 6:40 AM -0700 11/8/02, billroger wrote:
>And of course I have never been able to program a decoder.
You've been incredibly patient through all this.
Do you happen to be located in California? If so, maybe I should
drop by with some test equipment and try to figure out what's going
wrong.
I live in Berkeley, and get around most of Northern California for
work. And this weekend I'll be in Anaheim, and could free up a
couple hours if you're somewhere in the southern part of the state.
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.
|
Locked
Re: LocoBuffer/Decoder Pro Problem
Jon:
I have to go away for a few days will return and pick this up on Tuesday Nov 12.
Bill
toggle quoted message
Show quoted text
----- Original Message -----
From: Jon Miller
To: jmriusers@...
Sent: Friday, November 08, 2002 12:49 PM
Subject: Re: [jmriusers] LocoBuffer/Decoder Pro Problem
I wish he was Bob but Bill's in AZ!
Jon Miller
AT&SF
For me time has stopped in 1941
Digitrax DCC owner, Chief/Zephyr systems
NMRA Life member #2623
Member SFRH&MS
To unsubscribe from this group, send an email to:
jmriusers-unsubscribe@...
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
|
Bob Jacobsen