Pass the module ID as an output from request VIs to simplify wiring.

[MichaelAivaliotis]

I've been using cloneable modules on a regular basis. Wiring consecutive request VI calls become tedious with regards to the module ID. Having that as a pass-through makes so much more sense. This is kind of like a reference to the cloneable module if you think about it. So that wire should be treated as such on the connector pane.

[Ludwig72]

@MichaelAivaliotis your For-Loop is also silly. Can you tell me the reason why you are wiring the module ID through a shift register? The ID should never change inside the loop. And I think the same idea is the base for the complete design as it is: function over form. There is no reason to tunnel an only-input as an output.

[MichaelAivaliotis]

A shift-register is required when passing a value through a loop to prevent a zero value if the loop does not iterate. This was just a quick mock-up to demonstrate a use-case. However, the pass-through of the ID is very convenient. Similar to the passing of various other IO references provided by NI.

[Ludwig72]

I would wire the ID around the loop 😉

---

[MichaelAivaliotis]

Our styles are clearly different. But instead of focusing on the while loop. The point is the bigger picture of treating the ID just like any other reference in LabVIEW. Because essentially that's what it is.

[Ludwig72]

I understand. To follow your logic: nothing is stopping you from designing your own request-VIs as needed and passing the references through. I assume your suggestion is to have the (generated) standard requests include an ID output from the start, correct?