Cyril Gambini

Hi Pablo, We develop the tool on our spare time, and backing saving it is a bit too much work. LV2020 comes with valuable ressources (such as maps) and has a community edition. That is why we use this version for the TSifier. Most of our own customer who had a SSP migrated to 2020 anyway, so our own bank of customer using LV2017 is very low now. Sorry, but I have to decline this request

We tried to reproduce it with TS/LV 2022 without success. I think this is related to TS ActiveX registration : https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YGxHCAW&l=en-CA

Hi Maurizio ! I've never seen this one yet ! The error seems to point onto an ActiveX problem. Moreover, the output shows that the PPL was built. After the PPL is built, the TSifier tries to connect to TestStand to build the sequence file. It seems that your TestStand API was not located / registered correctly. Do you also have a 64 bit TestStand installed on the same machine ?

Hi, Thanks for the feedback ! I cannot really help here ! We noticed few erratic bugs with LV when working with unicode related langages (we have a Korean employee and it is often a problem when his PC is set in Hangul). For the moment, due to very low request to support Chinese characters and diffculties to investigate on such issues, I will simply note this behavior as a bug. And there is a great chance that we will not investigate further. Sorry to be very direct here, but I prefer not to give false hopes !

Hi @Jim Kring thanks for pointing the message to me ! @Pablo J Bames sorry I wasn't notified by this message. The usual support forum for the TSifier is on NI.com website. I believe the problem you are facing is resolved in the latest version of the TSifier. Did you try again lately with the last version ?

Hi, I built a VIP Package for a library that I designed. The code within my library uses the Timekeeper.livlib as a dependency (which is a locked (by password) lib that you can find on NI website). I added Timekeeper.lvlib to my project so that I can ensure that it will be put into the VIP file. Everything works fine until I run the VIP installation on a new computer. In the fresh install, my lvlib code refers to the Timekeeper.lvlib but expect it to be on a path that is related to my dev computer (instead of the destination set in the VIP build). Any idea on how I can prevent that ? Cyril