Bob,
Can physical decoder data be included.
It does not seem to work.
Sibbo
|
Locked
Re: No such decoder defined...
On Friday 04 October 2002 04:46 pm, Bob Jacobsen wrote: At 3:55 PM -0700 10/4/02, Mike Davison wrote:
In each decoder file mfg is "Throttle-Up (SoundTraxx)" while in
decodersIndex.xml it is "Throttle-Up".
That's probably the problem.
In an effort to fix the problem I changed the string in decodersIndex.xml to match the decoder files. Then I restarted DecoderPro. Now I see this error:
Found mfg 141 (Throttle-Up) version 14; no such decoder defined
So now DecoderPro has the string 'Throttle-Up' in spite of the fact that
the index and the decoder files have 'Throttle-Up (SoundTraxx)'. Weird. Ideas? It probably uses the one in your preferences (which I think is in
~/.jmri on Linux). Which one did you edit?
~/.jmri/... did the trick. Without reading the code, I'm note sure which one is used when making
a new decoder index. It could be the original (distributed) file, or
it could be the local copy.
Once you get this fixed, could you commit your changes? If I can recall the CVS magic. I'll bug you if I can't figure it out. Thanks, Mike
|
Locked
Re: LocoBuffer difficulty (continued)
You mention you have software set on lowest baud rate but my assembled
Locobuffer came default at 57,600 (The higher baud rate) You need to download
the docs in the file section, that will list which set of jumpers are for what
and what each one does.
Try that first and we will go from there...
William
Thanks for your forbearance while I learn to use the system.
Earlier I was helped along with a basic question about LocoBuffer, and that
help I got allowed me to get it working (it just needed power, which gives
you an indication of my skill set). I'm now at the point where I'm getting
an error message (once connected - I think - to the specific decoder
installed in a locomotive) that says: "Programmer error: timeout talking
to command station."
I'm using a Digitrax Radio Chief with a DT400R throttle, and have tried both
the programming track and the main track option in Decoder Pro 1.0.7. Com
port seems to be working (software set on lowest baud rate), but my laptop
(where I suspect the problem lies) is a very old one with 32MB of memory.
I'm trying to avoid lugging my desktop into the train room. I've gone
through the LocoBuffer documentation in the Digitrax list help files (and
must admit I'm in over my head when reading much of that), and don't seem to
get the programming I'm selecting onscreen to work - I get the
aforementioned error message.
Any suggestions or pointers as to my next step?
It's a beautiful system, by the way, and the user interface is very easy to
follow.
Thanks in advance for any help.
Michael McCaffery
|
Locked
Re: No such decoder defined...
Looks like the naming change to "Throttle-Up (SoundTraxx)" occurred at V1.22
of decoderIndex.xml
Robin
toggle quoted message
Show quoted text
-----Original Message-----
From: Bob Jacobsen [mailto:Bob_Jacobsen@...]
Sent: Friday, October 04, 2002 4:46 PM
To: jmriusers@...
Subject: Re: [jmriusers] No such decoder defined...
At 3:55 PM -0700 10/4/02, Mike Davison wrote:
>
>
>In each decoder file mfg is "Throttle-Up (SoundTraxx)" while in
>decodersIndex.xml it is "Throttle-Up".
That's probably the problem.
>In an effort to fix the problem I changed the string in decodersIndex.xml
to
>match the decoder files. Then I restarted DecoderPro. Now I see this
error:
>
> Found mfg 141 (Throttle-Up) version 14; no such decoder defined
>
>So now DecoderPro has the string 'Throttle-Up' in spite of the fact that
the
>index and the decoder files have 'Throttle-Up (SoundTraxx)'. Weird.
Ideas?
It probably uses the one in your preferences (which I think is in
~/.jmri on Linux). Which one did you edit?
Without reading the code, I'm note sure which one is used when making
a new decoder index. It could be the original (distributed) file, or
it could be the local copy.
Once you get this fixed, could you commit your changes?
Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
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.
|
Locked
Re: LocoBuffer difficulty (continued)
At 3:30 PM -0700 10/4/02, Michael McCaffery wrote: I'm now at the point where I'm getting
an error message (once connected - I think - to the specific decoder
installed in a locomotive) that says: "Programmer error: timeout talking
to command station." This means that the round-trip from program -> comm port -> LocoBuffer -> LocoNet -> command station and back didn't work. Unfortunately, there are a lot of steps in that... A couple of things to check: 1) Does the LocoBuffer LED flash when there are packets on the LocoNet? (Try selecting a loco address and twirling the speed knob, which sends lots of packets) 2) Do those messages come through to the program? To check this, open a "LocoNet monitor" from the debugging window. You'll get a window that will display all the messages received. 3) Can the program send a message to the LocoBuffer and see the echo? With a monitor window open, try programming. You should see a couple of messages. That's a start, and will probably help narrow down the problem. Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
|
Locked
Re: No such decoder defined...
At 3:55 PM -0700 10/4/02, Mike Davison wrote:
In each decoder file mfg is "Throttle-Up (SoundTraxx)" while in
decodersIndex.xml it is "Throttle-Up".
That's probably the problem. In an effort to fix the problem I changed the string in decodersIndex.xml to
match the decoder files. Then I restarted DecoderPro. Now I see this error:
Found mfg 141 (Throttle-Up) version 14; no such decoder defined
So now DecoderPro has the string 'Throttle-Up' in spite of the fact that the
index and the decoder files have 'Throttle-Up (SoundTraxx)'. Weird. Ideas? It probably uses the one in your preferences (which I think is in ~/.jmri on Linux). Which one did you edit? Without reading the code, I'm note sure which one is used when making a new decoder index. It could be the original (distributed) file, or it could be the local copy. Once you get this fixed, could you commit your changes? Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
|
Locked
Re: No such decoder defined...
On Friday 04 October 2002 02:40 pm, Bob Jacobsen wrote: At 1:56 PM -0700 10/4/02, Mike Davison wrote:
I am running DecoderPro 1.0 on Linux with EasyDCC and SoundTraxx DSD-150
Diesel decoder. When I click the ident button I get
Found mgr 141 (Throttle-Up) version 14; no such decoder defined
However, looking at xml/decoders/SoundTraxx_DSD_Diesel.xml I see:
<family name="DSD diesel" mfg="Throttle-Up (SoundTraxx)">
<model model="DSD diesel" numOuts="4" numFns="8">
<versionCV lowVersionID="9" highVersionID="14"/>
<versionCV lowVersionID="21"/>
.... so on
This looks to me like version 14 should be recognized. Further, this has
worked in the past so I've missed something. I did run 'Tools -> Create
Decoder Index', but that didn't change the behavior. What am I doing wrong? Could you check that the String for the manufacturer name is the
exact same between the mfg="" part of the "family" element (the
snippet above), and the listing of manufacturer codes at the start of
the decoderIndex.xml file? It first associates the CV8 number ->
manufacturer name using the elements at the start of the index, then
uses a String match to find all the decoders with the same
manufacturer name. In each decoder file mfg is "Throttle-Up (SoundTraxx)" while in decodersIndex.xml it is "Throttle-Up". In an effort to fix the problem I changed the string in decodersIndex.xml to match the decoder files. Then I restarted DecoderPro. Now I see this error: Found mfg 141 (Throttle-Up) version 14; no such decoder defined So now DecoderPro has the string 'Throttle-Up' in spite of the fact that the index and the decoder files have 'Throttle-Up (SoundTraxx)'. Weird. Ideas? Thanks, Mike
|
Locked
LocoBuffer difficulty (continued)
Thanks for your forbearance while I learn to use the system.
Earlier I was helped along with a basic question about LocoBuffer, and that
help I got allowed me to get it working (it just needed power, which gives
you an indication of my skill set). I'm now at the point where I'm getting
an error message (once connected - I think - to the specific decoder
installed in a locomotive) that says: "Programmer error: timeout talking
to command station."
I'm using a Digitrax Radio Chief with a DT400R throttle, and have tried both
the programming track and the main track option in Decoder Pro 1.0.7. Com
port seems to be working (software set on lowest baud rate), but my laptop
(where I suspect the problem lies) is a very old one with 32MB of memory.
I'm trying to avoid lugging my desktop into the train room. I've gone
through the LocoBuffer documentation in the Digitrax list help files (and
must admit I'm in over my head when reading much of that), and don't seem to
get the programming I'm selecting onscreen to work - I get the
aforementioned error message.
Any suggestions or pointers as to my next step?
It's a beautiful system, by the way, and the user interface is very easy to
follow.
Thanks in advance for any help.
Michael McCaffery
|
Locked
Re: No such decoder defined...
Bob,
Just checked my decoderIndex.xml file.
near the top of file:
<mfgList>
<manufacturer mfg="Throttle-Up" mfgID="141" />
further down:
<family name="DSD diesel" mfg="Throttle-Up (SoundTraxx)" type="locomotive"
file="SoundTraxx_DSD_Diesel.xml">
Robin
Robin Becker
Tucson, AZ D&RGW Model Railroad Layout
toggle quoted message
Show quoted text
-----Original Message----- From: Bob Jacobsen [mailto:Bob_Jacobsen@...] Sent: Friday, October 04, 2002 2:41 PM To: jmriusers@... Subject: Re: [jmriusers] No such decoder defined... At 1:56 PM -0700 10/4/02, Mike Davison wrote: I am running DecoderPro 1.0 on Linux with EasyDCC and SoundTraxx DSD-150
Diesel decoder. When I click the ident button I get
Found mgr 141 (Throttle-Up) version 14; no such decoder defined
However, looking at xml/decoders/SoundTraxx_DSD_Diesel.xml I see:
<family name="DSD diesel" mfg="Throttle-Up (SoundTraxx)">
<model model="DSD diesel" numOuts="4" numFns="8">
<versionCV lowVersionID="9" highVersionID="14"/>
<versionCV lowVersionID="21"/>
.... so on
This looks to me like version 14 should be recognized. Further, this has
worked in the past so I've missed something. I did run 'Tools -> Create
Decoder Index', but that didn't change the behavior. What am I doing wrong? Could you check that the String for the manufacturer name is the exact same between the mfg="" part of the "family" element (the snippet above), and the listing of manufacturer codes at the start of the decoderIndex.xml file? It first associates the CV8 number -> manufacturer name using the elements at the start of the index, then uses a String match to find all the decoders with the same manufacturer name. Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
|
Locked
Re: No such decoder defined...
At 1:56 PM -0700 10/4/02, Mike Davison wrote: I am running DecoderPro 1.0 on Linux with EasyDCC and SoundTraxx DSD-150
Diesel decoder. When I click the ident button I get
Found mgr 141 (Throttle-Up) version 14; no such decoder defined
However, looking at xml/decoders/SoundTraxx_DSD_Diesel.xml I see:
<family name="DSD diesel" mfg="Throttle-Up (SoundTraxx)">
<model model="DSD diesel" numOuts="4" numFns="8">
<versionCV lowVersionID="9" highVersionID="14"/>
<versionCV lowVersionID="21"/>
.... so on
This looks to me like version 14 should be recognized. Further, this has
worked in the past so I've missed something. I did run 'Tools -> Create
Decoder Index', but that didn't change the behavior. What am I doing wrong? Could you check that the String for the manufacturer name is the exact same between the mfg="" part of the "family" element (the snippet above), and the listing of manufacturer codes at the start of the decoderIndex.xml file? It first associates the CV8 number -> manufacturer name using the elements at the start of the index, then uses a String match to find all the decoders with the same manufacturer name. Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
|
Locked
No such decoder defined...
I am running DecoderPro 1.0 on Linux with EasyDCC and SoundTraxx DSD-150
Diesel decoder. When I click the ident button I get
Found mgr 141 (Throttle-Up) version 14; no such decoder defined
However, looking at xml/decoders/SoundTraxx_DSD_Diesel.xml I see:
<family name="DSD diesel" mfg="Throttle-Up (SoundTraxx)">
<model model="DSD diesel" numOuts="4" numFns="8">
<versionCV lowVersionID="9" highVersionID="14"/>
<versionCV lowVersionID="21"/>
.... so on
This looks to me like version 14 should be recognized. Further, this has
worked in the past so I've missed something. I did run 'Tools -> Create
Decoder Index', but that didn't change the behavior. What am I doing wrong?
Thanks, Mike
|
Thanks to those who generously pointed me in the right direction.
I appreciate your prompt response.
Michael McCaffery
___________________
toggle quoted message
Show quoted text
Do I need another source of power to my LocoBuffer? Is that what
the two wires sticking out are for? What would work for that source
of power, if that is the problem? And where did I miss this in the
instructions? If that's not it, any suggestions?
|
Locked
Re: LocoBuffer difficulty
Michael,
LocoBuffer information is contained in the files sections of either the
Digitrax list or the Loco_Net Hackers list. It shows the connections and
the jumpers.
Jon Miller
AT&SF
For me time has stopped in 1941
Digitrax DCC owner, Chief/Zephyr systems
NMRA Life member #2623
Member SFRH&MS
|
Locked
Re: LocoBuffer difficulty
At 6:51 PM +0000 10/3/02, Michael McCaffery wrote: all I have connecting to it is the cable to/from my serial port
(COM1) and the LocoNet cable running directly (and temporarily) to
the DCS100. The DT400 throttle is currently unplugged, with the
Program button pressed initially, and the programming track is
connected to the program A and B connections on the DCS100 through
the usual toggle switch setup so the track can also be switched to
normal mode. ...
Do I need another source of power to my LocoBuffer? Is that what
the two wires sticking out are for? What would work for that source
of power, if that is the problem? And where did I miss this in the
instructions? If that's not it, any suggestions?
You do need an external source of power for the LocoBuffer. I haven't looked at the instructions for a while, so am not sure now much they say about it. I use a 9V AC "wall wart" transformer, which seems to work fine. Also, you can leave the DT400 throttle plugged in. There's no need to disconnect it or press any of it's buttons. Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
|
Locked
Re: LocoBuffer difficulty
Michael, The LocoBuffer interface requires its own power supply in order to work. Can't say for sure what the two wires that stick out of the unit are for as I assembled mine. As you suspect, they could be for the external power supply. If you haven't already done so, you'll need to connect a 7 to 15 volt, 100 ma AC or DC power supply to the printed circuit board at the points marked Pad1 and Pad2. If this is where the two wires emanate from on your LocoBuffer, then yes, connect your power supply to these leads. If not, then find the pads mentioned above and connect the leads of your power supply to those points. Once you have a power supply connected, I'm sure all will work as expected. Feel free to write me off list should you require additional information. Bob --- In jmriusers@y..., "Michael McCaffery" <mdmccaf@d...> wrote: As a newbie to both DCC and Decoder Pro, please make the usual
allowances for my questions, which may have been covered earlier.
I'm attempting to set up a LocoBuffer (just purchased assembled from John Jabour) with my Radio Chief using a programming track. I've
read the website instructions, downloaded version 1.0.7 of Decoder
Pro, and am getting a message on my laptop (a very slow laptop) that indicates the LocoBuffer is unable to accept data. In addition, the LEDs on my LocoBuffer are on (and the message says they should be
off). There is a reference to recycling power to the LocoBuffer,
but all I have connecting to it is the cable to/from my serial port (COM1) and the LocoNet cable running directly (and temporarily) to
the DCS100. The DT400 throttle is currently unplugged, with the
Program button pressed initially, and the programming track is
connected to the program A and B connections on the DCS100 through
the usual toggle switch setup so the track can also be switched to
normal mode. Everything seems to be working fine, except I cannot
get past the message.
Do I need another source of power to my LocoBuffer? Is that what
the two wires sticking out are for? What would work for that source of power, if that is the problem? And where did I miss this in the instructions? If that's not it, any suggestions?
Thanks for any help. I'm incredibly excited about my first two
sound decoder installations - it's a whole new area of the hobby for me, and I'll rapidly convert my roster once I learn how to do it
the "easy way" with LocoBuffer.
Michael McCaffery
Davis, CA
|
As a newbie to both DCC and Decoder Pro, please make the usual
allowances for my questions, which may have been covered earlier.
I'm attempting to set up a LocoBuffer (just purchased assembled from
John Jabour) with my Radio Chief using a programming track. I've
read the website instructions, downloaded version 1.0.7 of Decoder
Pro, and am getting a message on my laptop (a very slow laptop) that
indicates the LocoBuffer is unable to accept data. In addition, the
LEDs on my LocoBuffer are on (and the message says they should be
off). There is a reference to recycling power to the LocoBuffer,
but all I have connecting to it is the cable to/from my serial port
(COM1) and the LocoNet cable running directly (and temporarily) to
the DCS100. The DT400 throttle is currently unplugged, with the
Program button pressed initially, and the programming track is
connected to the program A and B connections on the DCS100 through
the usual toggle switch setup so the track can also be switched to
normal mode. Everything seems to be working fine, except I cannot
get past the message.
Do I need another source of power to my LocoBuffer? Is that what
the two wires sticking out are for? What would work for that source
of power, if that is the problem? And where did I miss this in the
instructions? If that's not it, any suggestions?
Thanks for any help. I'm incredibly excited about my first two
sound decoder installations - it's a whole new area of the hobby for
me, and I'll rapidly convert my roster once I learn how to do it
the "easy way" with LocoBuffer.
Michael McCaffery
Davis, CA
|
Locked
Re: interfacing with a mac
I am using a G3 Powerbook and want to connect to a Lenz
system using the LI100. Is there an RS232 to USB adapter
cable I can use? Or is ther some other way to connect a mac to
the Lenz system?
I've used a Keyspan PDA adapter to do this with MacOS 9 and MacOS X. Works fine! What type of Lenz system do you have? There's been some confusion about whether a Compact (which I think is quite similar to an Atlas Commander) can program decoders via a LI100. The Commander can't. Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
|
I am using a G3 Powerbook and want to connect to a Lenz
system using the LI100. Is there an RS232 to USB adapter
cable I can use? Or is ther some other way to connect a mac to
the Lenz system?
|
Test done with fresh T1 decoder.
Use programming track.
Paged Mode
Decoder installed, Ident.
Found mfg 153 (TCS) version 22 not defined
Changed to T1 and opened Programmer
In roster Entry changed ID to 1234 and did a save.
Went to Basic pane and changed long address to 1234, checked Extended
Addressing and did write sheet.
Colors changed from yellow to red to white as normal.
Went to roster entry and did a save.
When I tried to exit program got the ???some changes have not been written"
window.
Closed window anyway!
--closed the program.
Reopened the program.
Went through the above steps except didn???t do roster entry.
1234 showed in Long address but not in DCC Address and Extending addressing
box was not checked, tried to exit but program hung.
Reopened the program and went through above step except for two differences;
used 1235 number and did a read of all panes. This time program closed as
it should.
When I reopened program old message was at the bottom found mdg 153 etc.
I 'quit' the program and reopened. Now it came up in idle. Went through
the same above and went to basic pane, the address had not changed.
At this point I decided to reload the program.
Went through above steps but this time used engine number id, it was there
and showed engine 1235.
?? It's not working like it did but I can't exactly define what's wrong
other than above comments.
Jon Miller
AT&SF
For me time has stopped in 1941
Digitrax DCC owner, Chief system
NMRA Life member #2623
Member SFRH&MS
|
At 9:35 AM -0700 9/30/02, Jon Miller wrote: Bob,
Reading one panel is fine. It will also write one pane. But then I
used to (change one pane) go to the Roster Entry pane, do a save and exit.
Now when I try and exit it tells me I didn't save. If I read the entire
group, do a save (without any changes to "other" panes), and then exit
everything is fine. Sounds like I might have broken the logic that keeps track of changes. I'll check. Just to make sure I understand: It prompted you that there were changes that had not been stored to a file, right? And it didn't warn you about changes that had not been written to the decoder? Also, do you recall which pane and which decoder type this was? It also 'seems' different in the way it writes. I was changing an
address and it appeared to change, lights flickered on the tester, but
didn't seem to change the address. But I was testing a new FX3 Digitrax and
not really sure what was happening. I need to do a careful test here as I
was trying to do something else at the time and not paying much attention to
the DecoderPro actions.
(Shows how reliable it has become)
This and the above statement may have to do with the Digitrax FX3
decoders and nothing to do with DecoderPro so will do more testing today.
Has anyone else been programming the new FX3 series and noticed anything
different? I haven't tried one of those directly. Perhaps there's something wrong in the definition file Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
|
Bob Jacobsen