Create Callback VI for IMAQdx Event -> Broken Wire

[rolfk]

Is the Image Acquisition Software license properly activated in the license manager?

[approximately_whatever]

The licenses are ok.

License Manager screenshot

According to NI Updates and NI Package Manager, my LabVIEW install is up to date.

[approximately_whatever]

@FireFist-Redhawk

Sorry, it may be lost in translation for me, but did you mean that you also get the broken wire?

[FireFist-Redhawk]

---

@approximately_whatever wrote:

@FireFist-Redhawk

Sorry, it may be lost in translation for me, but did you mean that you also get the broken wire?

---

No worries. Yeah, I was able to replicate [the issue] on my own setup.

[billko]

---

@FireFist-Redhawk wrote:

---

@approximately_whatever wrote:

@FireFist-Redhawk

Sorry, it may be lost in translation for me, but did you mean that you also get the broken wire?

---

No worries. Yeah, I was able to replicate [the issue] on my own setup.

---

I wonder why no broken wire for me?  I followed the instructions carefully.  I wish it didn't work for me so there would be some consistency here.

[approximately_whatever]

I can replicate this on my LV2018 installation and a fresh LV2021 installation (LV installed today in new VM, no other version of LabVIEW installed).

This "bug" is ruining my project timetable, if I don't get it fixed or find a workaround. Are there any official NI channels to file a bug report and get a (timely) response?

I'm located in the EU, if it matters.

[approximately_whatever]

Just to update this thread: NI technical support informed me that it is not possible to create Event Callbacks for IMAQdx events. They said they will also check with R&D if it's actually a bug, but I wouldn't hold my breath for this.

[approximately_whatever]

Another update from NI: a bug report was created for this issue (CAR No 1753009). So hopefully it's going to be fixed some time in the (near, I hope) future.

[approximately_whatever]

Another update: according to this document (https://www.ni.com/sl-si/support/documentation/bugs/22/labview-2022-q3-bug-fixes.html) the bug was fixed in LabVIEW 2022 Q3.

Did not test it yet, but hopefully it works and this thread can now be closed.