ManuBzh

Yes, Diagram property exists, and as a reference, since at least 8.5, I've checked. Edit : and ... I put here a simple VI containing the following code. It's saved in LV2015 version, if someone can tell me with which version it won't be broken... Thanks ! value of wire classe reference.vi

Thank you ensegre ! Very strange that diagram property does not appear in LV2019/2021 ! it's the basis for scripting...

And so the question is : is there different subVI refnum[] for each clone... I guess yes but note sure and can't figure how to reach them.

Yes, I agree with this (That's what I saw after in the heap). There's only one diagram for all, but you can set breakpoints or probe on each instance "diagram",(it's only images ?) However, it would be enough for me to be able to do the same : programmaticvally put BP or read wires values on them. I don't really know where to go now clone DS... if ever I can do something (But I think yes).

It's the Top Level Diagram reference... no the clone diagram reference (if ever this has sense) (If you look at the exact name on the property node linked to your diagram ref, you'll see : TopLvDiag )

I took a look to everything but seen no mentions about clone Diagram refnum...

You're talking about VI ref ? If you do an open VI Reference using the Clone name, you get the clone ref, don't you ? Here, I need The clone diagram reference... But any help is appreciated, let me know what you find !

## Accessing Breakpoints and Wire Values in Preallocated Clone VIs (LabVIEW Scripting) Hello, As part of automating certain debugging workflows, I’m looking to programmatically: - Place breakpoints on SubVIs, or - Read values flowing through wires (yes, I’m aware this involves using private properties — if anyone knows from which version of LabVIEW these became accessible, I’d be glad to know!). This is trivial when working with **non-reentrant VIs** via the `Diagram` property. However, things get complicated with **reentrant VIs** (specifically *preallocated clones*): Accessing the `Diagram` property on such a clone returns the **top-level VI’s diagram reference**, not the actual clone's diagram. As a result, I can’t access the relevant references for SubVIs or wires within that clone instance. ### Why I believe it’s still possible: - The **Breakpoint Manager** correctly detects and removes breakpoints on objects *inside* clone diagrams. 👉 This implies it has access to these internals and may be able to **set** breakpoints programmatically too — which is exactly what I’d like to do. - The **Probe Watch Window** can read values from wires within clone diagrams. 👉 Again, this confirms some internal visibility and access. I’m fully aware this might involve using **undocumented or unsupported LabVIEW features** (e.g., hidden `.ini` keys, private scripting APIs, or heap introspection). --- If anyone has insights, experience, or any direction to offer, I’d greatly appreciate your help! Thanks in advance!