Nerdy Camelopard

@Cloedu72Thanks for the advice! Everything is in Public scope, debugging is disabled and there is no broken code since I have the same issue with the simple NI code that is quite minimalistic. I also followed the checklist. Thanks for the link though, this one is really helpful. @ak_nzThanks for clarification. This way it works perfectly and this is also my workaround for now. Using async calls with "override module" seems not possible. I will report to NI and keep you updated...

Hi ak_nz and thanks for our reply. Yes, I used the really simple example of the ni forums article, added it to a lvproj and packed it to a lvlibp. The behaviour remains exactly the same when I call it via the project and the override settings (adaptor configured as RTE). Interesting behaviour: If i call the vi from the lvlibp directly, it works as expected (-> Called via RTE). I added the example...one sequence working, the other not... Example.zip

Hi there, I am using Teststand 2020 together with LV 2020 SP1 since a while. My framework contains a HAL with several modules that I use with lvlibp (override module settings) and RTE for production. This works pretty well and we are happy with it so far. For one of our sequences we need to make asynchronous VI Calls now. There is an NI Code example and knowledge article about asynchronous calls in general: https://forums.ni.com/t5/Example-Code/Run-a-LabVIEW-VI-Asynchronously-from-TestStand/ta-p/3834066 and https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000g0sqSAA&l=de-DE Both solutions explained work perfectly with the LabVIEW Development Environment. When switching to packed libs and RTE on our production Teststations, it won't work anymore. Also if I try to force using lvlibp and rte in Teststand on my development machine it will always open the LV Development and not use RTE. Did anyone use asynchronous vi calls in Teststand and had the same issues with lvlibp and the RTE?