windigipet.de

Win-Digipet - english forums => Win-Digipet Forum English => Thema gestartet von: Rupert van Swol am 19. Februar 2021, 14:18:50

Titel: How to fit BIDIB Feed back Nodes
Beitrag von: Rupert van Swol am 19. Februar 2021, 14:18:50
Hello Forum Members,
I am not succeeding in entering the feedback nodes in Windigipet 2018c that the feedback works.
I am using the Fichtelbahn RS READY interface,  which has 7 nodes internally.
The numbering of the nodes is 0 to 7.
Each node has 128 positions for feedback.
So the RS Ready interface controls a maximum of 8x128= 1024 feedback positions.
I have been working on implementing RS Ready in WDP 2018.c for some time now. Without of succes.

If I keep it to 1 node, in this case node 4, and determine the range from 1 to 16 modules, I get the correct count, namely 1 to 128, including the active feedbacks in the feedbacks monitor.
But if I add the previous node,  node 0, to Node 4,  then it goes wrong, the subsequent count is correct, but there is no active message on the Feedback monitor.

What am I doing wrong, can I still add other fichtelbahn  feedback modules.

The feedback address 513 matches the Lenz feedback module with address 65, the first contact.
What am I doing wrong in my thinking and input?

Thanks in advance for the feedback.

Rupert van Swol
Titel: Re: How to fit BIDIB Feed back Nodes
Beitrag von: Markus Herzog am 19. Februar 2021, 17:04:16
Hello Rupert,

The feedback module assignment table in the last picture can not work.

First of all BiDiB distinguish between the following types of inputs:
-Track modules (e.g. occupancy detectors, regular feedback modules, feedback caused by trains)
-Port modules (simple logic inputs etc. without security function)
-Position reports (car system)

As far as I see the screenshot from the BiDiB monitor the ReadyRS reports as Track/feedback modules, thus in the colums "from Module" and "To Module" only selections starting with Track M. are right the choice

Then you need to be aware of the fact, that every BiDiB node starts internally counting the track modules each with 0, port 0 to 7 will then be appear in WDP as Track module 1, 8 to 15 as track module 2.

If you have e.g. a BiDiB node VFB P66002D00 reporting at ports 0 to 23 in the BiDiB-Monitor and a second BiDiB node VFB P66002E00 reporting at ports 0 to 31 in the BiDiB-Monitor, then you would have to register them in the system settings as follows:
-BiDIB-Interface From Track M. 1 to Track M. 3  P66002D00  Start Module WDP x
-BiDIB-Interface From Track M. 1 to Track M. 4  P66002E00  Start Module WDP y

So every BiDiB node starts internally with Module Number 1 and only the Start Module column determines where these modules will appear in the WDP in the WDP sphere.

If you set for example the value in the config above x to 1 then the 24 ports of P66002D00 will appear in WDP as Feedback number 1 to 24.
And if you set in the config above x to 126 then the 24 ports of P66002D00 will appear in WDP as Feedback number 1001 to 1024
And if you set in the config above y to 251 then the 32 ports of P66002E00 will appear in WDP as Feedback number 2001 to 2032.
Your responsibilty is just to manage that no feedback numbers in WDP are assigned twice.

Regards
Markus
Titel: Re: How to fit BIDIB Feed back Nodes
Beitrag von: Rupert van Swol am 20. Februar 2021, 12:50:28
Hello Markus,
Thanks for your detailed explanation,
I have printed it out and put it in the documentation folder BIDIB section WDP .
 I assumed too much that each Node as a separate collection of feedback (max 128 ) and the ID of the node would act as a distinguishing part.
See first picture.
However, the internal numbering turned out not to be correct.

When mutating the "START MODULE WDP ", the numbers remained  red and were also not sequentially increased.

Only at START MODULE 49, the numbers went back to black and the numbering also sequentially increased.
At the end of the range  Start module WDP ( number 113 )  was everything filled in black with the corresponding numbering. See Picture.
After that I removed the unused nodes and it's works as it should.

Thank you for your help.
Rupert van Swol