|
Hi John or anyone:
Bill here, the one with the problem. I've been trying to program a decoder and not having any luck. I get the "Program Error: Timeout talking to Command Station". It's trying to write CV29. This is where we left off. I get all kinds of info (don't what it is saying in the DEBUG -- LOCONET MONITOR window.
I have two leads from the PROG output on the DCS100 directly to my programming track, which with a toggle switch I can change from programming track to regular DCC track.
So I get this Program timeout error talking to command station. Can you help me with this.
Bill
toggle quoted message
Show quoted text
----- Original Message -----
From: Jon Miller
To: jmriusers@...
Sent: Saturday, November 02, 2002 10:31 AM
Subject: Re: [jmriusers] programmer error
Wendell,
I know Bob has done testing with an Empire Builder but I'm not sure what
is supposed to happen. Bob will have to comment on this.
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.
|
the "Program Error: Timeout talking to Command Station< If you can get LocoNet data I think this means that the LocoBuffer, DecoderPro, and DCS100 are talking. How are you selecting the engine/decoder? Will the DecoderPro select the decoder that is in the engine using the "ident" button associated with "Decoder installed"?
|
Jon:
WHen I use the IDENT button (middle of the screen), I get the error "stopping due to error: timeout talking to command station". Thanks.
Bill
toggle quoted message
Show quoted text
----- Original Message -----
From: Jon Miller
To: jmriusers@...
Sent: Saturday, November 02, 2002 3:10 PM
Subject: Re: [jmriusers] Program error -Timeout talking to Command Station
>the "Program Error: Timeout talking to Command Station<
If you can get LocoNet data I think this means that the LocoBuffer,
DecoderPro, and DCS100 are talking.
How are you selecting the engine/decoder? Will the DecoderPro select
the decoder that is in the engine using the "ident" button associated with
"Decoder installed"?
To unsubscribe from this group, send an email to:
jmriusers-unsubscribe@...
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
|
WHen I use the IDENT button (middle of the screen), I get the error "stopping due to error: timeout talking to command station". Thanks.< Disconnect the plug from the LocoBuffer where it connects to the DCS100 and plug the throttle in. Program with the throttle, does it work? Check the LocoNet under debug. Does the line "Programming track is available" ever come up? Does the LocoBuffer data LED flash when you attempt to identify a decoder? Are you absolutely sure the cable between the LocoBuffer and the DCS100 is good? Make sure it is a data cable! Jon Miller AT&SF For me time has stopped in 1941 Digitrax DCC owner, Chief/Zephyr systems NMRA Life member #2623 Member SFRH&MS
|
Jon:
Still trying to get pass the Timeout error.
1. Yes, I can program loco's using the throttle with the locobuffer not connected.
2. When I reconnect the locobuffer to the loconet and the PROG A&B output to the programming track I do get "Programming Track Available" under DEBUG - Locobuffer Monitor. The line of info just above this says "Track Status off".
3. Yes, the data LED flashes when I run a train and the Locobuffer Monitor window fills will data.
4. From item 3 above I would say my data cable is working fine.
5. Not sure what you mean "Make sure it's a data cable". I'm using 6 wire flat phone cable I got from Radio Shack and on which I crimped the RS232 plugs.
Thanks.
Bill
toggle quoted message
Show quoted text
----- Original Message -----
From: Jon Miller
To: jmriusers@...
Sent: Saturday, November 02, 2002 4:25 PM
Subject: Re: [jmriusers] Program error -Timeout talking to Command Station
>WHen I use the IDENT button (middle of the screen), I get the error
"stopping due to error: timeout talking to command station". Thanks.<
Disconnect the plug from the LocoBuffer where it connects to the DCS100
and plug the throttle in. Program with the throttle, does it work?
Check the LocoNet under debug. Does the line "Programming track is
available" ever come up?
Does the LocoBuffer data LED flash when you attempt to identify a
decoder?
Are you absolutely sure the cable between the LocoBuffer and the DCS100
is good? Make sure it is a data cable!
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.
|
Jon:
I forgot to say I'm trying to program a loco with a Lenz decoder and DSX sound decoder install and sitting on the programming track. I heard somewhere that I should program each separately.
Bill
toggle quoted message
Show quoted text
----- Original Message -----
From: Jon Miller
To: jmriusers@...
Sent: Saturday, November 02, 2002 4:25 PM
Subject: Re: [jmriusers] Program error -Timeout talking to Command Station
>WHen I use the IDENT button (middle of the screen), I get the error
"stopping due to error: timeout talking to command station". Thanks.<
Disconnect the plug from the LocoBuffer where it connects to the DCS100
and plug the throttle in. Program with the throttle, does it work?
Check the LocoNet under debug. Does the line "Programming track is
available" ever come up?
Does the LocoBuffer data LED flash when you attempt to identify a
decoder?
Are you absolutely sure the cable between the LocoBuffer and the DCS100
is good? Make sure it is a data cable!
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.
|
Bill,
Data cable means that the white wire goes to the white wire, in other
words one of the clips is up at one end and down at the other.
\
[_]----------------------[_]
\
Like the terrible asci drawing.
Have you tried a different decoder? Possibly just an engine with a
single decoder in it. I'm guessing you are running the Lenz decoder and DSX
sound decoder with the same engine number. This can work ok but the
decoders should be programmed separately. Try just programming a single
decoder. I can't think of anything else, it seems like it should work.
Jon Miller
AT&SF
For me time has stopped in 1941
Digitrax DCC owner, Chief/Zephyr systems
NMRA Life member #2623
Member SFRH&MS
|
Bill,
Forgot to add this check same as for Wendell,
I'm not sure what DecoderPro is supposed to read with this but try taking
the engine off the track and then attempt programming. It should read
something like "engine not on track".
I'm totally running out of ideas!
Jon Miller
AT&SF
For me time has stopped in 1941
Digitrax DCC owner, Chief/Zephyr systems
NMRA Life member #2623
Member SFRH&MS
|
Bill,
A thought occurred while grocery shopping. The DCS100 (Chief) has a
current limit on the programming track. The fact that you have two decoders
in that engine may be beyond the current capabilities of the programming
track. You can use just a decoder and clip it to the programming track. In
fact it's a good idea to have or make a decoder tester. That way you can
connect it to the programming track, test it, and program it before it ever
goes into the engine. A really good idea as some installs take a lot of
time.
Jon Miller
AT&SF
For me time has stopped in 1941
Digitrax DCC owner, Chief/Zephyr systems
NMRA Life member #2623
Member SFRH&MS
|
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
toggle quoted message
Show quoted text
----- Original Message -----
From: Jon Miller
To: jmriusers@...
Sent: Sunday, November 03, 2002 8:01 PM
Subject: Re: [jmriusers] Program error -Timeout talking to Command Station
Bill,
A thought occurred while grocery shopping. The DCS100 (Chief) has a
current limit on the programming track. The fact that you have two decoders
in that engine may be beyond the current capabilities of the programming
track. You can use just a decoder and clip it to the programming track. In
fact it's a good idea to have or make a decoder tester. That way you can
connect it to the programming track, test it, and program it before it ever
goes into the engine. A really good idea as some installs take a lot of
time.
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.
|
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)
|
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
toggle quoted message
Show quoted text
----- Original Message -----
From: Bob Jacobsen
To: jmriusers@...
Sent: Sunday, November 03, 2002 9:16 PM
Subject: Re: [jmriusers] Program error -Timeout talking to Command Station
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)
To unsubscribe from this group, send an email to:
jmriusers-unsubscribe@...
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
|
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
|
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
toggle quoted message
Show quoted text
----- Original Message -----
From: Michael Beckemeier
To: jmriusers@...
Sent: Monday, November 04, 2002 6:27 PM
Subject: [jmriusers] RE: Program error -Timeout talking to Command Station
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
To unsubscribe from this group, send an email to:
jmriusers-unsubscribe@...
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
|
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)
|
Bob Jacobsen