In article <484f5356$0$1514$c3e8da3@[EMAIL PROTECTED]
>,
Puckdropper <puckdropper(at)yahoo(dot)com> wrote:
>I've tried isolating sections, but the problem still remains. However,
>when I disconnect the loconet cable between the command station and
>booster, the problem appears to go away.
I would double-check all of the wiring, particularly that related to
the power supply and data connections to and between the command
station and the booster. How are the reversers controlled ? Do they
receive their instructions via the DCC track power ? If not then
double-check the separate cable. Have you tried disconnecting all but
one of the reversers and seeing if the problem persists ?
Bizarre behaviour like this is often due to things like missing or
poor ground connections. I don't know what loconet is like
electronically, or what the connectors are like, but that would be a
place to start looking. If you have a spare loconet cable that should
be early on your list of things to try.
>Does anyone have any ideas what could cause this? There was no
>configuration change before the problem started that I know of. (We have
>not yet tried resetting the system.)
By `resetting' I assume you mean putting the command station, which I
assume has some nonvolatile memory for configuration etc., back to
factory settings. This will help if the fault is due to an error in
that configuration (perhaps abetted by buggy firmware).
Do you have access (perhaps via one of your members) to a spare
command station and/or booster which could be tested ? I don't know
if people conventionally build this kind of thing in in a way that
makes it difficult to remove and disconnect tem****arily; I wouldn't
but the result is that a substantial pro****tion of my not
inconsiderable electronics budget goes on connectors.
--
Ian Jackson personal email:
<ijackson@[EMAIL PROTECTED]
>
These opinions are my own.
http://www.chiark.greenend.org.uk/~ijackson/
PGP2 key 1024R/0x23f5addb, fingerprint 5906F687 BD03ACAD 0D8E602E
FCF37657
|
