05-03-2012 04:59 AM
This indeed is a strange error.
I found multiple threads handling this issue and all states that it's not the hidden front panel that has an undefined type.
Check the other errors that are reported by LabVIEW and fix those - this will fix the error.
In my case I had this ugly cluster with all refnums being reported as faulty. In the end I noticed that one of the sub-VIs had a CIN referring to a non-existing function in my .dll. I removed an option from my DLL (Visual Studio project) which made the sub VI fail.
After replacing the .dll the 'undefined type' error magically disappeared ...
So the fix is simple: just fix all the other errors and this one is gone too.
But the error reported by LabVIEW is just wrong and it kept me busy for some time ![]()
Needs to be fixed - I'm using LV2009 but this still is wrong in the 2011 version.
I don't have 2012 (beta) - it might be worth to check this in the new beta ...
Rob
05-04-2012 12:05 PM
This issue is filed under Corrective Action Report (CAR) #220595. R&D knows about the misleading error message and it may be remedied in a future version of LabVIEW.
07-28-2017 11:35 AM
@JaredRo wrote:
This issue is filed under Corrective Action Report (CAR) #220595. R&D knows about the misleading error message and it may be remedied in a future version of LabVIEW.
Eureka! I've fixed it! I've recently come across the same issue in LV2016. I have multiple clusters of RefNums, and if I get an error on any other part of my code, it produces the same error.
The issue (for me, and likely others) is that the cluster has an array refnum, but the type of array is not defined. To solve, drag and drop a control/constant/etc of the array type into the RefNum in the cluster on the FP.
Solved!