Log In
Register
Forum
Topic RSS
2:47 am
April 19, 2015
Offline
how does one debug compiler errors? I have been using the latest version of the compiler with Arduino 1.6.1 and LabVIEW 2014. Often, upon making changes to a wiring diagram with several nested structures, I get compiler errors, but with obscure references to node numbers, along with scope errors related to misplaced brackets or parens. I have been able to back out the wiring diagram changes up until this recent instance where I cannot tell what is causing the error.
The VI runs in LabVIEW without errors....
thanks, jjwebster
2:50 am
March 12, 2015
Offline
Hi there,
Yes, we have been reviewing your error logs, thank you for submitting them. The issues you are having are due to a small defect in the compiler handling nested structures. Luckily we have ran your code through the latest version that is about to release (probably early next week) and everything compiles. So hopefully your issues will be resolved soon. Its hard to debug these things on your end so that's we we implemented the ability to send errors to us and it has been very helpful. If you have registered your product, you will get a notice when the next version is available for download, which you can get for free if you have already purchased a license.
2:59 am
April 19, 2015
Offline
Thanks for the quick reply. I'm glad a fix is imminent. Is there anything I can do to keep making progress until the next release?
3:50 am
March 12, 2015
Offline
One thing you can try is converting some of the contained functional blocks into subVIs and replacing code with those. That will help narrow down where the issue is and may even be a workaround as it simplifies deep nesting of structures within one VI. If you do this, you can also compile the SubVIs by themselves to make sure you don't hit any compilation issues on the smaller blocks of code before integrating back into your larger application.
Sorry for the inconvenience. We are working to get this next release out soon with several fixes and additional features.
10:38 pm
March 12, 2015
Offline
jjwebster,
Just FYI Version 1.0.0.14 is up on NIs FTP. Although it may not appear in VI Package Manager for a few days, you can download it directly here if needed. Just find the 1.0.0.14 Home package.
8:24 pm
April 19, 2015
Offline
Steffan, I upgraded to 1.0.0.13 through VI PM, but that didn't address the problem I'm having (sent another error report in the case it is helpful). When will 1.0.0.14 be up on VI PM? I'd much rather manage through the package system than D/L directly.
edit ** Just realized the link was to a VI package. Installed 1.0.0.14... WORKS! Thanks for the fixes!
8:32 pm
March 12, 2015
Offline
jjwebster said
Steffan, I upgraded to 1.0.0.13 through VI PM, but that didn't address the problem I'm having (sent another error report in the case it is helpful). When will 1.0.0.14 be up on VI PM? I'd much rather manage through the package system than D/L directly.
Thanks for the additional report. I have confirmed it does compile with 1.0.0.14. And we have a request into NI as to why it is not visible in VIPM yet. For some reason there is always a few days lag until it shows there so by the time I hear back it may be up already. Just keep checking. As you know you can download the package through the ftp but I understand you want to manage it directly in VIPM.
1:48 pm
March 19, 2015
Offline
Hello, the compiler doesn't accept the wired "N"-connector of the for-loop. Strange error message
2:31 pm
March 12, 2015
Offline
viwoi said
Hello, the compiler doesn't accept the wired "N"-connector of the for-loop. Strange error message
It should accept the N-connector but the compile error is probably due to another reason. Can you please send the error report within the compiler when prompted or post your VI here and indicate what version of the Compiler you are using?
2:59 pm
March 19, 2015
Offline
Steffan said
viwoi said
Hello, the compiler doesn't accept the wired "N"-connector of the for-loop. Strange error message
It should accept the N-connector but the compile error is probably due to another reason. Can you please send the error report within the compiler when prompted or post your VI here and indicate what version of the Compiler you are using?
here are the screenshots of the error message and the VI. I use the 1.6.1-compiler
3:52 pm
March 19, 2015
Offline
@ viwoi,
Tested your vi,
When you connect the output of the "serial length" to an indicator and connect a local variable of this indicator to the "N-connector" the vi will compile without failures.
Perhaps this info will help Steffan.
4:29 pm
March 19, 2015
Offline
John said
@ viwoi,Tested your vi,
When you connect the output of the "serial length" to an indicator and connect a local variable of this indicator to the "N-connector" the vi will compile without failures.
Perhaps this info will help Steffan.
thanx John, currently I am using the auto-indexing function of for loops. In case of strings I convert them to a byte-array first. Then pass it to the for loop. Not fine, but works.
I also noticed, that the error-wire should not be connected to a "?"-connector of the case-structure. It provides also some "strange" errors.
5:08 pm
March 12, 2015
Offline
viwoi said
thanx John, currently I am using the auto-indexing function of for loops. In case of strings I convert them to a byte-array first. Then pass it to the for loop. Not fine, but works.I also noticed, that the error-wire should not be connected to a "?"-connector of the case-structure. It provides also some "strange" errors.
We are analyzing your VI, thanks for posting it. As John noted, you can use that as a workaround. Thanks John for posting it.
I have created Case 90 for this issue and hopefully it will be fixed in the next release.
Also, yes, you cannot wire error wires to case selectors. Please refer to the "Important Considerations" section of the user manual for more details. Error clusters are used for flow control only and not intended for functional use.
45
1 Guest(s)
