LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How can I run dynamic reentrant VIs in EXE Applications?

It crashed for me when I tried your exe.

I changed "SimpleTestVI.vi" to "normal prority" and now no more crashing. I do not know of any rule against a dynamic re-entrant being set to sub-routing priority in a exe.

I suspect there something wrong here ( should I utter the B word? Smiley Wink ).

Why did you have the VI set for sub-routine?

That setting is generally used for VI's that are shared amoung many callers and should execute promptly to minimize bottle-knecks. Since you are doing re-entrant calls there can not be simultaneous call issues.

Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 11 of 16
(2,520 Views)

OK this has been confirmed by NI and it looks like a BUG.

Service Request # = 730889

I will post latter if a CAR is filed and the results of testing this in LV 8.0.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 12 of 16
(2,507 Views)

Updating my previous:

A new CAR (corrective Action Report) has been filed on this BUG.

The CAR# = 3QGE3KUF

Preliminary tests indicate this may not be an issue in future releases.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 13 of 16
(2,495 Views)
Smiley Surprised That was my fault with the exec-level, I just played around with the option and forgot to rewind the settings. I wasn't really aware about meaning of the executionlevel.

Thanks to your afford

I'm little surprised, that it is possible to report bugs to NI :smileyhappy ... can I also post a CAR ?


0 Kudos
Message 14 of 16
(2,482 Views)
"can I also post a CAR ?"
 
Yes, but it takes some doing.
 
First you have to come up with a clean cut set of steps that results in the "bad thing".
 
Then you call NI at 800 433 3488 and tell them you are calling to report a possible bug. This goes easy if you have a support cotract but in theory they want to know about all bugs (with the current version of the code).
 
At that point you work with the application engineer and they will confirm that they see the same behaviour.
 
If they agree that it is a bug and not just an un-expected result they will then search the internal knowledge-base to see if the problem has already been reported.
 
If it has not been reported they will then check with the product support engineer to confirm all of the previous work.
 
If all of this falls out, the AE will then file the CAR.
 
 
I have a collection of CAR's but the real question is "Who will be the first to win a shiny new CAR for LV 8?"
 
Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 15 of 16
(2,480 Views)
This was reported to R&D (# 3QGE3KUF) and was fixed in LabVIEW 8.0. Here is a link to the current evaluation software download for LabVIEW.

Thanks!
Travis H.
LabVIEW R&D
National Instruments
Message 16 of 16
(2,345 Views)