I just updated my two DR5000's to YD7001. The DR5000 used to have this issue until Digikejs fixed it in the very last firmware release. Now the YD7001 has exactly the same problem. I have about 50 blocks, on first connect it report just 4 of them, then after pressing the green button a few more report, I end up having to press it 5-6 times to get all blocks to report. I have reached out to?Karst Drenth (and he just replied saying he hasn't heard of this before) but was wondering if anyone else has seen this. My setup uses all Digikejs gear (DR5088RC) and Traincontroller with Railcom. Thanks Eddie

Yes this problem has carried over from the DR5000 to the updated YD7001. ?I have a Digikeijs Loconet Digihub with connections to 3 groups of DR4088LN block detectors. ?On start up I simply unplug then reconnect each loconet cable from the Digihub and all zones are detected. Attached is a screenshot of my setup.

Alex Thomson

On Wed, Mar 20, 2024 at 12:14 PM, sotars wrote:

Yes this problem has carried over from the DR5000 to the updated YD7001.

Of course it did. That is because the problem originates in the DR4088LN, not in the command station !! Indifferent of the command station, Z21, IntelliBox, Digitrax, in fact any LocoNet command station show the same behaviour !!

?

?to 3 groups of DR4088LN block detectors

And luckily for you you have less than the problematic 10 Modules on each group. Already back in 2019 we discoverde empiricly that there seems to be a maximum of 9-11 Modules on one LocoNet bus causes the DR4088LN to lockup. In the worst situation, they completely lockup the whole LocoNet.

?

?(and he just replied saying he hasn't heard of this before)

And has offered you full investigation...?

Anyhow, you seem to have DR5088RC only, so I suspect we are looking at a completly different phenomena.

?

Although I usually do not answer the same problem in twoo different systems/fora etc.

?

Here is a suggestion: "The report delay after PowerOn" is just meant for that: set it differently ( 250ms difference should do )? between all your feedback modules and all should be fine.

However...

I have about 50 blocks, on first connect it report just 4 of them, then after pressing the green button a few more report

This is completely weird. 4 only means that not even 1 complete module is reporting... So again, I suspect we are looking here at a completly different beast.

==> Only the YD7001 Logging can tell you what is coming in from the LocoNet. So please provide such Screenprint and or a Logging.txt

?

?(he hasn't heard of this before)

I know of customers having over 10x DR5088RC on their layout and no problems getting the data in.

?

Greets,

Karst

Here's a diagram of my system. As I start to remove modules from the far end it gets more reliable. with only two left connected it works the first time as expected. I have changed the cables to rule those out. After 5-6 presses of the green button?and they all have reported, the system and Traincontroller function fine, so it's really just an inconvenience, but I like things to work well. Here's a link to what's happening.?

Sotars, what version of the DR5000 software were you on. The very last release from Digikijs make this way better.

Reded
think it was 1.6.3 or something like that, certainly was the last available version. ?Apart from the lack of detection on start up I didn't suffer any other of the glitches reported for the last firmware version. ?Funnily enough when I first did the conversion to YD7001 the blocks or least most of them did show up so I thought the problem was solved but it did not last. ?The fact that Karst has identified the problems with the DR4088LN makes sense now I just assumed it was a problem with the DR5000. ?That comment from Karst was the first time I had heard of the limitations on the number of DR4088LN units. Other than having to remove and replug the 3 Loconet cables at startup I have suffered no other glitches or problems. ?I have since the last post added a Hornby HM7040 dongle to the system yet another control method!!! ?The YD7001 handles all of these connections effortlessly. I have added an updated System Diagram.

Alex

开云体育

Your remedy of multiple resets or limiting loconet connection effects the polling time.

Chances are Digikeijs extending the polling time or number of polls to capture all the devices.

Try powering the devices in stages or groups. This will create a delay the reporting window.

Inobu

On Fri, Mar 22, 2024 at 08:29 AM, sotars wrote:

That comment from Karst was the first time I had heard of the limitations on the number of DR4088LN units

That is incorrect quoting ! ? I was referrring to you, mentioning that you had all DR5088RC !!! when I wrote that I never had seen the problem before.

?

Eddie Jones	Wed, Mar 20, 12:47?AM (3 days ago) ?	?
?

?

?

?

?

?

5088RC and I use railcom if that matters.

?

Thanks Eddie

?

From:?Karst Drenth [Drenth Design & Consulting B.V.] <drenth.design.consulting@gmail.com>
Sent:?Tuesday, March 19, 2024 2:59 PM
To:?Eddie Jones <smartfxsoftware@...>
Subject:?Re: Request Activation Code for: 5000D0011927

?

What type of feedbask units do you have ?

?

It was the first time I heared about DR5088RC problems in this context.

The DR4088LN problem is already known for more than 5 years.... That also the DR5033 suffer from the same dissease (hanging up LocoNet on high trafic) became aparent quite soon after that 4088LN problem was discovered.

?

But looking at your schematic... There is some things I would do differently.?

?

First: give each DR5088RC a different "Report Delay"( start with 750 or 1000 and then increment by 130 on each subsequent DR5088 )

Second: consider your DR5033 to operate from them as CDE device behind the DR5039

Third: get rid of the 5099. One direct LocoNet cable from YD7001 LocoNet-B to DR5039 will do.

?

Since you now effectively only have left 3x DR4099LN, thy should report just fine.

?

Further, you may want to switch on this:

?

Greets,

Karst

?

?

?

On Fri, Mar 22, 2024 at 01:20 PM, Inobu One wrote:

Your remedy of multiple resets or limiting loconet connection effects the polling time.

Chances are Digikeijs extending the polling time or number of polls to capture all the devices.

Try powering the devices in stages or groups. This will create a delay the reporting window.

There is no polling .... Neither in the DR5000, nor in the YD7001.

LocoNet devices "just send" on input-change and/or power-up.

?

On Wed, Mar 20, 2024 at 09:47 AM, Reded wrote:

I have about 50 blocks, on first connect it report just 4 of them, then after pressing the green button a few more report, I end up having to press it 5-6 times to get all blocks to report.

With what Software do you monitor the reporting ??

Greetz,

Karst

Polling is the process where the computer or controlling device waits for an external device to check for its readiness or state, often with low-level hardware.

Stationary Broadcast and Interrogate Commands is basically the "Polling Process" for Loconet.

The issue is most likely Transmit Echo data being triggered due to the number of devices trying to register at the same time.


Inobu







Inobu

开云体育

Hi there?

On Sun, Mar 24, 2024 at 06:45 AM, John Critchley wrote:

1 - 8 via the Loconet T on the Z21

2 - 8 via the RoSoft (1) stand-alone USB?

3 -?8 via the RoSoft (2) stand-alone USB?

No second thoughts about that (y) should work nicely !

?

Very nice cabinets by the way !!

?

Greets,

Karst

On Sat, Mar 23, 2024 at 02:21 PM, sotars wrote:

Karst I am confused by your comment below as I do not have any DR5088C units. ?That is Reded

Sorry, excuse me. I read it wrongly.

?

Greets,

Karst

Thanks Karst.

Kind Regards
Alex

开云体育

Thank you Karst?

John
Do you not get any feedback problems due to cable lengths with the? 4088s being so far from the track berths?
Andrew

开云体育

No Andrew