开云体育

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

I have checked all the manuals I can find on the command station,

xbus etc and it is as far as I can see acommand station running Ver
3.0 of the software. If it does not work it looks like I will ahve
to spend another ?150 on an LZ100!!!!!!! Not a happy prospect.
McKays who I bought the LI100F from assured me it works. Lenz
themselves sell an Xbus adapter kit specifically for the LI100F and
the Set 02.

Alex

That's interesting.

Those are messages from the LI100, so the program is successfully
exchanging messages with the LI100 over the serial link.

1 4 5 is from the LI100 itself, and means that "instruction was
successfully sent to command or normal operations have resumed

after

a timeout"

But "61 82 e3" is a bad sign. It is from the command station, and
means "Instruction not supported by command station".

It looks like everything is communicating OK, but the Set O2 is
refusing to do a programming operation from the XPressNet. I'm

not

familiar with the Set 02. Is there some option you have to set to
make it accept this? Is it a full XPressNet command station?

Bob

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

At 2:59 PM +0000 7/22/02, sotars wrote:

Further to my last post, I have been trying to download the other
tools but have been unable to find out how to!!!!!!

However while logging the xpressnet traffic when trying to
communicate with the interface the following is repeated

1 4 5
1 4 5
61 82 e3
61 1 60

these are the responses after trying to "ident the loco address and
the decoder.

That's interesting.

Those are messages from the LI100, so the program is successfully exchanging messages with the LI100 over the serial link.

1 4 5 is from the LI100 itself, and means that "instruction was successfully sent to command or normal operations have resumed after a timeout"

But "61 82 e3" is a bad sign. It is from the command station, and means "Instruction not supported by command station".

It looks like everything is communicating OK, but the Set O2 is refusing to do a programming operation from the XPressNet. I'm not familiar with the Set 02. Is there some option you have to set to make it accept this? Is it a full XPressNet command station?

Bob

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

Thanks for the reply. I have tried to send the command but there is
nothing in the monitor. However when i try to ident the loco
settings or decoder settings from the programmer the following
appears 1 4 5
1 4 5
61 1 60
61 82 e3

I have tried connecting to a laptop with XP Pro on and also another
machine with (*SE on anf the same thing happens. Can it be to do
with the Set 02 command station. I have also changed the LH200 but
no difference is made.

Alex

Is there a difference between the LI100 and LI100F?

A systematic approach to diagnosis will probably help here.

First, get a consistent set of settings. The best starting place

for

settings is 9600 baud (which should be the LI100's default) and no
flow control.

Make sure the LI100 and command station are talking to each other.
If they are, the LI100's LED will be on solid; if not, it will be
blinking.

Next, start a trace of the serial port by selecting

the "Lenz/Atlas

Command Monitor" item from the "Debug" menu. As you try to

program,

you'll (hopefully) see some traffic in that display. The command

to

start a programming operation is:

22 14 8 3e

And the LI100 will then reply with a burst of stuff. Do you see
either half of that? After a while, you'll see

21 81 a0

which is the program giving up and sending a reset command. Do

you

see this? After how long?

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

Can anyone please tell me if DecoderPro works with XP Pro?

I took delivery of the LI100F on saturday and have it connected to a
Set02. The software loads and appears to work correctly however I
have been unable to get it to talk to the interface. The message
(Programme error: timeout talking to the command station) appears, I
have changed the baud rate for com1 and in the LI100F also the flow
control in all its combinations but it is still timing out.

Is there something simple I am missing or do I have to partition my
drive and install 98SE/Me (YUK!!!!!!)

Is there a difference between the LI100 and LI100F?

A systematic approach to diagnosis will probably help here.

First, get a consistent set of settings. The best starting place for settings is 9600 baud (which should be the LI100's default) and no flow control.

Make sure the LI100 and command station are talking to each other. If they are, the LI100's LED will be on solid; if not, it will be blinking.

Next, start a trace of the serial port by selecting the "Lenz/Atlas Command Monitor" item from the "Debug" menu. As you try to program, you'll (hopefully) see some traffic in that display. The command to start a programming operation is:

22 14 8 3e

And the LI100 will then reply with a burst of stuff. Do you see either half of that? After a while, you'll see

21 81 a0

which is the program giving up and sending a reset command. Do you see this? After how long?

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

At 9:42 PM +0000 7/21/02, sotars wrote:

Can anyone tell me please if DecoderPro works under XP Pro? It
seems to load and run well but I have been unable to get it to talk
to the interface. I get Program error: talking to command station. I
have tried all combinations of speed and flow control both for the
Com port and inside the LI100F.

Is there something simple I am missing or is it just XP?

I test DecoderPro on other protocols (NCE, Digitrax) under XP Home and it works fine. Would XP Pro be different?

I can try the Lenz protocol with XP Home this evening, will let you know.

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

Can anyone tell me please if DecoderPro works under XP Pro? It
seems to load and run well but I have been unable to get it to talk
to the interface. I get Program error: talking to command station. I
have tried all combinations of speed and flow control both for the
Com port and inside the LI100F.

Is there something simple I am missing or is it just XP?

Thanks Alex

Can anyone please tell me if DecoderPro works with XP Pro?

I took delivery of the LI100F on saturday and have it connected to a
Set02. The software loads and appears to work correctly however I
have been unable to get it to talk to the interface. The message
(Programme error: timeout talking to the command station) appears, I
have changed the baud rate for com1 and in the LI100F also the flow
control in all its combinations but it is still timing out.

Is there something simple I am missing or do I have to partition my
drive and install 98SE/Me (YUK!!!!!!)

Grateful for any help

Alex Thomson

No problem Bob. Working with Robin the problem is fixed. It turned out
that the first two function lines said "forward" instead of "forward" then
"reverse". Once that was changed then the lights worked correctly.
I really wish I could help with the programming but the time I spent on
that little problem convinced me "I'm not a programmer"<VBG>.

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

Sorry for the slow reply. Were you able to get this sorted out?

I met John Forsythe of TCS today at the show. We went over his decoder line, and discovered that I had put some of his decoders in the wrong groups:

*) The TH141 is the same as the T2 except for one fewer function (I had it as similar to the TH150 line)

*) The T1 lighting is only normal, random flicker, rule 17 and dim; all the others are present in T2 but not T1

*) The TH150, T1, T2, TH141 all have a function map.

(He's also got a new lighting-only decoder that looks pretty interesting.)

I'm willing to make these changes, but it might take a week or two to get time (I've fallen pretty far behind)

Bob

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

I'm still working the issue (at my "day job"), but it won't be fixed for "Jaguar"...

-Dave

The issue is the same issue that was the problem on the PC-- the serial javacomm package for Mac OS X doesn't support the LocoNet baudrate quite right.

If you run Mac OS 9, MS-100 should work OK, but I'd recommend a snagging locobuffer on what I've heard over lunches with Bob...

-Dave Falkenburg

Everyone,
What do you think about an information pane? [Info] One pulldown where
we could just put text as to what we know about that decoder and what
versions might do what. That way the programmer could look at that pane and
determine or at least help him with what that decoder might do. This would
help until we can get the 3rd CV! We could also note there to program a
number into CV105 or 106 (if those are available for the given decoder) to
further define the decoder he's using. Those 2 CV's then would further
identify the decoder only after it was programmed the first time.
Is this a difficult task? I am finding out creating these "text only"
programming items are not easy<VBG>.

It wouldn't be hard to display some info from the decoder definition file. Where/when would you like it displayed?

I could put an area on the "select loco/decoder" window that would show info from the decoder when you select it. You could then just click along through the decoder tree, reading what pops up in the box. Or I could put it in a "tooltip" that comes up when you rest the cursor on a decoder name.

The hardest part is probably writing good comments for all those decoders...

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

The following information is from John Jabour. Email at address give by
Bob.

"LocoBuffer and LocoIO kits are still available. All prices are in US
dollars.
Shipping quoted is to the US. Shipping and PayPal charges outside the US
are slightly more.
Kits include all the parts except a case or a wallwart power supply.
LocoBuffer is $27.25 and shipping for 1 - 3 units is $3.85 using
priority mail.
LocoIO is $21.00 for an "A" kit and $19.60 for a "B" kit and shipping for
1 - 3
units is $3.85 using priority mail.
Assembled is $10.00 extra.
You can pay with cash, check or money orders. You can also pay with PayPal
(which is the prefered method). If you pay with PayPal please add 2.9%
plus $.30 cents."

At 11:53 AM -0700 7/18/02, Mike Davison wrote:

A friend would like to use DecoderPro on his Macintosh laptop running MacOS
9.1 to program decoders on his Digitrax system. I use Linux and EasyDCC so am
not able to be very helpful. Anything he should be concerned about?

Which laptop?

if it's got USB, a Keyspan PDA adapter and MS100 will work. That's an off-the-shelf solution, though a little more expensive than a LocoBuffer.

If it doesn't have USB, but rather has the DIN Apple serial connectors, a LocoBuffer is the reliable solution. The MS100 can't be used directly because the port doesn't provide the needed power (this is also a problem with certain PC laptop serial ports). It is possible to wire the MS100 to + and - power supplies to correct this, but it's probably easier to build a LocoBuffer; the MS100 needs pretty clean power to be reliable.

Also, if he's thinking of moving to MacOS X at some point, the LocoBuffer is a better choice. The MS100 doesn't work with MacOS X due to hardware support issues in the kernel. That's not something I can fix, and people at Apple have told me it's not a high priority update for them.

Secondly, the web page for DecoderPro lists something called 'LocoBuffer' as a
bit of hardware that a Macintosh user with a Digitrax system needs. I looked
on the Digitrax site and didn't see such a device. Would someone point me in
the right direction?

John Jabour <jjabour@...> is the LocoBuffer's creator. He made up some boards, and has been selling them either by themselves or with kits of parts. (He'd shipped over a hundred kits a couple months ago; the number is probably much larger now)

Assembly instructions are at



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

Mike,
LocoBuffer is a kit or at least it used to be. In the files section
click on LocoBuffer (details of a hardware solution). The chip comes
already programmed. Just solder everything to the board. You need to buy a
separate "wall wart" for power!
Someone will have to comment maybe John ran out of kits. I know it's a
popular item. I will comment on the LocoNet Hackers group and see what the
response is!

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

Jon,

The DecoderPro instalation notes suggest that the MS100 will not work with a
Mac, at least without tinkering. I didn't see any sort of kit or instructions
in the loconet hackers files section. It may all be there in the form of
board artwork, schematics and microcode, but I'm not sure my friend would
want to go down that path.

Thanks,
Mike

Everyone,
What do you think about an information pane? [Info] One pulldown where
we could just put text as to what we know about that decoder and what
versions might do what. That way the programmer could look at that pane and
determine or at least help him with what that decoder might do. This would
help until we can get the 3rd CV! We could also note there to program a
number into CV105 or 106 (if those are available for the given decoder) to
further define the decoder he's using. Those 2 CV's then would further
identify the decoder only after it was programmed the first time.
Is this a difficult task? I am finding out creating these "text only"
programming items are not easy<VBG>.

Comments?

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

Mike,
DecoderPro will now work with the Digitrax MS100 (at least for PC's) but
the LocoBuffer is a better device. Information will be found on the
Loconet_Hackers Yahoo group in the files section. It's sold by John Jabour
for cost but you have to assemble it.
Bob or another Mac user will have to comment on that part of the
question as I use a PC.

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

A friend would like to use DecoderPro on his Macintosh laptop running MacOS
9.1 to program decoders on his Digitrax system. I use Linux and EasyDCC so am
not able to be very helpful. Anything he should be concerned about?

Secondly, the web page for DecoderPro lists something called 'LocoBuffer' as a
bit of hardware that a Macintosh user with a Digitrax system needs. I looked
on the Digitrax site and didn't see such a device. Would someone point me in
the right direction?

Thanks,
Mike

Robin,
I having trouble modifying an xml file. Probably because I don't know
what I'm doing. Both of my Windows programs (98 first and second edition,
different computers) will open the files. My second edition comes up with
an error message but opens the file anyway. But when I change the data
(simple changes) and put that file back into DecoderPro it won't open the
programmer. I can put the old file back and everything is ok.

The file I am trying to change is the TCS_Tx.xml file as there are some
minor problems. In the lights (CV's 49 & 50) it shows forward for both
choices. Also the default for CV 50 is 16 not 1. I would guess the first
problem would effect CV's 51 and 52 also (T2 decoder, four function) but I'm
working with a T1.

I think somehow my wonderful Windows is not saving the xml file
correctly but I have no idea how to make it save correctly!

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