Youssef Menjour

Dear Jim, Could you please delete HAIBAL package from your platform. We never give autorisation of this upload. This version is also outdated, and the only official version is downloadable on our website.(www.haibal.com) We have decided to stop to work with VIPM and we launch our own distribution solution next month. Thank you to do it now.

Dear jim, Can i have an answer please ? We can't finish the NI partnership process because of a bug inside VIPM. What do I have to do to get something done ? Can you take your responsibility ? It is March 1, we reported the problem on January 11. As a reminder, we pay for a VIPM license, I find this way of treating your customers simply shameful. We bought a license because we thought you were a serious company. Telling us that we are not a priority in a private message by asking us how many customers we have while you block our growth potential is simply shameful. As you seem overwhelmed, I offered you my help, if you can't fix your bugs my engineers can do it for you. Now it's time to do something, I don't feel like writing to Eric Starkloff to ask him what to do, we all have other things to do than getting into a conflict.

Dear Jim, Now we are blocked with the NI partnership to distribute HAIBAL because of the bug of desactivation from VIPM. That mean we can't sell HAIBAL on NI shop till this bug is not fixed. Could you please do something ?

I

Hi Jim, It seems building one package for 2021-2021 / 2022 / 2023 is no more possible because of broken dependancy. We had this problem on our package forced us to make two compilation for "2020 - 2021" --> no broken and 2022 alone. We just tested our package for 2023 with the 2022 built and it's totally broken. That mean if we want to make a package for these differente version of LabVIEW we need to build separatly for all of them. Seems "LabVIEW XXX and later" functionality in install requirement no more works since LabVIEW 2021. Do you have any information and preconisation ? Thank you

Please find the issue here

Already tested ... that's not the problem

I found the problem. The project is compatible 2020 - 2021 - 2022. But as we want to protect our code and we build a project without diagram before to construct it in VIPM. (Because this functionality does not exist on VIPM --> it would be really useful) When we build the new project with LV2020 --> LV2020 - LV2021 are ok and broken dependancy appear for LV2022. So that mean it's not possible to build a library 2020 - 2021 - 2022 if diagram is erased. So now i resign to build two package, one for 2020 - 2021 and one for 2022. But now a new problem appear, TPLAT could not be installed on LV2022 ... So hope someone can help me to propose my package on LV2022.

[VIPM TEAM UPDATE: NI has been informed and we are working to test possible fixes. See bug tracker issue #19 for up-to-date information.] Hi, I have an issu when i try to install TPLAT with LabVIEW 2022 (22.3.1f8) I just installed it with LabVIEW 2020 with no problem. Without TPLAT on LV2022 i can't try to build licenced package ... is this problem known? is there a solution ? blem

Hi, Our project was developped with LabVIEW 2020. We can open it with LabVIEW 2021 and LabVIEW 2022 without any error but when we build it The librarie work without any problem with LabVIEW 2020 The problem appear with LabVIEW 2022 version (LabVIEW 2021 is ok) I 'm not sure but i think you have an issu on your LabVIEW XXX or later function since LabVIEW 2022 because you package one solution for different LabVIEW and LabVIEW VI hierachie seems to have changed. I bet if i compile only on LabVIEW 2022 it will work. Is this issu will be fixed ? We will propose on NI shop the HAIBAL deep learning toolkit and we would like to propose it for 2022 (NI feedback --> The product satisfy the requirements. This completes the review process. We will continue with market submission.) --> it seems they does not see this big issu ! I need JKI answer to adapt my response to NI.

Is someone can help me about this problem ?

Any news ?

Sent in PM all the element.

Is someone can make the test in your side (could be more easy to find the issu) ? I put in attached the "test project", you just have to put your own LF file and use your own keys. test.zip

To facilitate communication i put fake Client Key (XML): (truncatenate some parts) So i put off <RSAKeyValue> <RSAKeyValue><Modulus>3JuXicNIj4pLHCtYFeWkRvd15soeUxO0yxR0VK8rXs8W4mhSMpZF2peevqLrGYYTLFPDznCbdMRcow6WRSsLiG1QGCHYCi9xpkjrnANp12wRReAIdiVsukFzqT0hEMpXqHj0oxCuimk=</Modulus><Exponent>AQAB</Exponent><P>4lvoZiUcc0Q5lBpAMZS0vZwVVuu5Gm0Y2WOcbSQZZcfD8MyvPOefjtBYGswxz+Ah0ET6xI9w5szGxHDi8twXuw==</P><Q>+X7jnKu3QfmPXzaTZ/7Zuuxj2UEZZRGgrYKfKKw==</Q><DP>UUfpaoxW6/kKwvpsxhra+rpFR3gz6+mjDFw/P4VMw==</DP><DQ>ChSuba4igW/r8xTpb9Iu9QAGNDa7HpwwNQQBfFYN8D+h/9k3U9Y4+oDH1wq16OAB9uNpSIicQ==</DQ> <InverseQ>uImLwSN4EhDuHQ==</InverseQ><D>Iq53SVohCyfjnP8XbwHWLK30pB68W7UqZA7IJxQOzm3iHB/uxx+vFqxilwidv9Cgh1Nnrzn9pVd5I96SZNmn4GwZ2FKH2SKoBvY203NhtosMbMBPn0h9XGH0=</D></RSAKeyValue> Tried and same result 🤔 strange ....