开云体育

Can any of this group that have a Zephyr test the feedback for me. Mine basically doesn't work. Several calls to Digitrax and their line is I'm the only one that's unhappy, they have heard

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

The code _requires_ that echo be on. It listens to the incoming messages, including the echo'd ones it transmitted, to figure out the order in which things actually happened on the LocoNet. If you

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,

DecoderPro and the Java Comm library are trying to set the serial port to: Flow control to the LocoBuffer; don't send unless CTS (Clear To Send) is active. Ignore flow control from the

First, thanks for all the kind words. There seem to be several problems happening. 1) It appears that certain models of the Keyspan PDA adapter can't handle the LocoBuffer's 57,600 rate. This might

Perhaps something has gotten confused in the preferences file. If you search for file(s) named "DecoderProConfig.xml" on your system and remove them (while the program isn't running!), when you next

Bill, That's ok there are only four LED's on that board. If you look at the back of the small pc board you will see; RAIL- LOCO2 LOCO1 RAIL+ When you plug it in and get four LED's lit it is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello billroger, The cable should be straight through, in other words if you hold both connectors next to each other in the same orientation the wires

Jon et al: More and I believe my problem is with the cable. I have this gadget that came with my DCS100, it's a telephone jack with a circuit board attached with what looks like 6 green LED's on the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Jon, Tuesday, November 5, 2002, 11:16:21 PM, you wrote: JM> Alex, JM> ????????? This has been bouncing around on about 3 lists.???

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Alex, This is a problem with the Locobuffer. Depending on how the computer hardware deals with a unconnected signal, it can be either high or

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello vanhovem02, It is probably related to the flow control. Try 57600 baud with no flow control. I had this problem a few days ago and was able to

More on the DCS50. I finally hooked up a Lenz LE104XF and the DCS50 read the address. So downstairs and hook up to DecoderPro. It did read the basic, after many hits, so right now it's trying

Bob: I forgot to mention, this is on an Apple iMac; 233hz 256 meg of ram and System 8.6, so it's not specific to the dreaded Windows System Mike

Bob: I have followed your suggestions and set baud to 19700, disabled Flow Control and checked all the jumpers on Loco Buffer. Threw away all the DecoperProConfig.xml files and restarted. Lo!

I discovered DecoderPro just a couple days ago. After a couple false starts I got it up and running yesterday. It is on an early-Pentium laptop running W98SE. I'm using an MS100 to connect to my

No Flow Control was the setting that got mine going, too (FYI: a PII 200mhz desktop with a serial card I purchased from Loy's). Maybe anyone with com port problems should be experimenting with this

Bob, This is starting to smell like the Java Comm API is not correctly handling the hardware handshake configuration or XP is doing something different. Looking at LocoBufferAdapter.java you appear

Well a friend just got his decoder pro, so I went to help. I am a MAC guy but I am an NT Lan Admin at work :( Anyway we spent 1.5 hours changing this and that. What finally worked was resetting the