Bob,
Thanks. Power On/Off is perfect. I should have thought of looking in the
Loconet Monitor for the outgoing messages myself. <sigh> I just ran the
power control here with the Loconet Monitor running and the command for ON
is 83 7c and OFF is 83 7d. That's 131 124 decimal, which I think you can
send using the numeric keypad by holding <alt> down, typing 0131 releasing
<alt>, holding <alt> down, typing 0124, releasing <alt>.
Your points about possible Java/PC/BelkinUSB issues are why I'm thought we'd
try just sending a message using HyperTerm instead of DecoderPro. I want to
narrow down the problem. At this point I _think_ the evidence tends to
indicate that his PC is sending data (blinking LED on Belkin, apparent meter
response at LocoBuffer IC2 pin 19).
(Unfortunately Bill didn't see any meter response at IC1 pin 2, the transmit
out to Loconet, but with short messages most meters wouldn't do anything.)
Robin
-----Original Message-----
From: Bob Jacobsen [mailto:Bob_Jacobsen@...]
Sent: Friday, November 15, 2002 2:09 PM
To: jmriusers@...
Subject: Re: [jmriusers] simple command to test port with hyperterm?
At 12:46 PM -0700 11/15/02, Robin Becker wrote:
So I was wondering whether there was a
simple LocoNet command that could be sent using Hyperterm to see
whether the
LocoBuffer answers. This would allow a test of the hardware without
involving the Java Comm lib. Thanks.
Probably the simplest LocoNet commands that have noticable effect are
power on and power off. I'm away from the layout, so I'm not 100%
sure of the coding, but you could open a LocoNet monitor, turn on raw
data display, and get the correct set of bytes. I think it's
something like: 0x83 0x7c, where the second byte is the error-check
code, for power on and 0x82, 0x7d for power off. Note that you _must_
have the upper bit set or the packet will be ignored.
You can also send this by clicking on the buttons in the "Power
Control" tool in the JmriDemo program.
If all you're trying to do is send _something_, without caring that
it works, see if the packets you're sending show up on the LocoNet
monitor. Everything there comes from the input; the outgoing
messages aren't shown until the LocoBuffer echoes them.
It's quite possible there's something wrong in the Java comm library,
but I doubt the problem is that simple. It's more likely to be some
interaction of the library with the specific software for the Belkin
adapter, since other USB adapters work fine, and even this one works
for a message or two before locking up and failing to transmit. The
interleaved send/receive we do is a little tricky. It might be
tickling some problem somewhere, for example there could be a
confusion if the program sends the 0x11 and 0x13 XON/XOFF codes and
the Belkin tries to act on them.
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
