开云体育

?I have just spent hours trying to get a Digitrax reverse module to report occupancy via Loconet. It works correctly with a Digitrax command station. Luckily, I was able to get a refund on the module.

I now find out this is a known problem with Digitrax Loconet items not working correctly DR5000 and YD7001.

I thought the whole idea of Loconet net was you could buy any Loconet item and it should work.

?

Shouldn’t this problem have been solved with a hardware update to the YD7001?

?

Also a list of incompatible items would be very handy?

?

Alec

On Tue, Aug 20, 2024 at 12:45 AM, Alec Hudson wrote:

Shouldn’t this problem have been solved with a hardware update to the YD7001?

I beg your pardon ? :O

What's the logic when replacing the Network module (with no link whatsoever with LocoNet), any hardware LocoNet problems would/should/must be "solved"....

Mostly "some every other time"? message of stuff not working ( no I don't keep track of them ) was either solved by turning-off RailCom on the DR5000/YD7001 or change the DCC wire polarity...

Greets,
Karst

Karst

?

Sorry about that I used the wrong word it was meant to be software update.

?

It was daisy chained with YD6016LN/YD6016ES. These all work ok. I tried different cables and tried the unit directly into the YD7001 to no avail.

?

Thanks

Regards

Alec

No problem, can happen ?

?

But I start to be curious WHAT did not work, and WHICH module we are talking about.

As i wrote below, it IS known that some/many Digitrax modules cannot cope with RailCom Cut-Out being present in DCC and/or RailSync.

Greets,
Karst

It was a Digitrax BXPA1 Loconet DCC Auto reverse with detection.

It excepted the board I.D. ok. But never reported occupancy high or low over Loconet.

This was monitored with the jmri Loconet monitor and also the Loconet feedback monitor on the YD7001. Railcom is off on the YD7001.

?

When the unit was returned the dealer tested it with a Zepher and it worked ok.

?

Regards

Alec