09-26-2023 05:45 AM
Going through the initial description of the issue:
are the other VIs you are refering to as woirking also called from a lvlibp? If so, are they also using DLLs ?
09-26-2023 05:52 AM
Yes, all the VI's are called by the packed library like the DLL. No, for the PDF there is only one DLL (the one we talked about before).
09-27-2023 01:17 AM
Just to throw in different ideas, getting more creative:
have you been able to build a deployment using the configuration as it is?
09-27-2023 02:14 AM
Well, i've already built the packed library and used it, it works fine except for the first run as i told you before.
This is the reason why i'm going crazy on this... it return error only the first time, it doesn't make sense to me since if i try to run it again (without closing TestStand, just by ending that execution and starting a new one) it does everyting perfectly...
Is this what you meant or something else?
09-27-2023 02:24 AM
I was actually thinking of creating a deployment of your TestStand project using the TestStand Deployment Tool
09-27-2023 03:14 AM
Could this fix my problem somehow?
09-27-2023 03:35 AM - edited 09-27-2023 03:36 AM
Not neccessarily.... yet it might help for diagnosis
Actually clutching at straws.....
Though I am wondering, how you want to deploy your code to the actual TestBench
09-28-2023 09:44 AM - edited 09-28-2023 09:49 AM
What is the LV version of the code creating the PDF ?
TestStand doesn't like to cross LV versions in the same execution unless a check box is checked in the adv options (I need to find which one it is).
If you LV version for you own code is LV2021 but the code for the PDF generation is compiled with another LV runtime, it will generate such issues.
If your code to generate the PDF is a PPL compiled to work on 'newer version of LV', this is not sufficient, you'll still have to set TS to allow loading different versions of the LVRTE.
EDIT :
So the options is actually in the LV adapter options -> Advanced
Try with this setting checked, and let us know if it resolves the issue.
09-29-2023 05:23 AM
Yeah unfortunately the LabVIEW and TestStand versions are different, is not my choice, both 64bit but LabVIEW is 2021 and TestStand 2020 (i have installed the 21.0 runtime).
I've tried to enable the option that you talked about but nothing changes, still pops up error at the beginning of the first execution.
09-29-2023 06:59 AM
Sorry to hear that!
Just to make sure, did you restart TS after applying the option?