Jump to content

Youssef Menjour

Members
  • Posts

    26
  • Joined

  • Last visited

Everything posted by Youssef Menjour

  1. 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.
  2. 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.
  3. 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 ?
  4. 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
  5. 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.
  6. [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
  7. 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.
  8. 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
  9. 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 ....
  10. Hi Jim, Yes it works with TPLAT but i want to use VIPM Bind licence to library at build (more convenient) I'll try your solution and make feedback. (If it works you'll have to update your documentation)
  11. Hi Jim, I followed instruction to enable desactivation from Bind licence to library at build time from "Licensing &Activation" help documentation Encryption Key ID: Specifies the Encryption Key ID associated with your Instant SOLO Server account. Client Key: Specifies the Client Key (XML) associated with your Instant SOLO Server account. Server Key: Specifies the Server Key (XML) data associated with your Instant SOLO Server account. Then I tested the desactivation licence and the feedback is "one or more required input elements are missing. what is this error ? I would like to desactivate my haibal licence to verify security but i can't for now ... (before the release...)
  12. Here is my contribution for the ideas of functionalities which would be frankly useful to integrate in the future on VIPM - an automatic generator of BIN3 for the examples folder (the current system is not practical). --> currently you have to create a tree structure and then copy and paste the files inside to finally generate the bin3 in an exbins directory (category that you have to create in VIPM) At the time of setup before construction it is necessary to point the directory examples towards another treesecence (Name of the company / project) which is absolutely not native in a LabVIEW project (nobody makes that...) In short it is too complicated. - the possibility to delete the diagram of the VI that we want. --> currently one is obliged to create a distribution to make that before building the distribution. It is too laborious. With just these two features we would save a lot of time.
  13. The problem is the context. I would use a tick to activate or not the licensing & activation page. Inside this "licensing & activation" page i would put a tab with 2 pages (normal // advanced). Normal as already exist. Advanced with the good name and the other context.
  14. Tested and works ! What could confuse custom is "licenced library" term --> mean already licenced ... Thanks Jim
  15. i have to understood You mean VIPM + LF file will automatically licenced the library with bind system ? (Library file must be unlicenced yet and VIPM will manage to licence it during the construction) I'll give it a try but if so it's just a great feature!
  16. I also tested on last version of VIPM, the result is the same ... Is someone can help me ?
  17. Hi Jim, We have another bug with VIPM 2020 when we try to package this example with a purchase url we have a proxy error. License ID: 3380916 Activation Password: 358SZ333 It's a big issu for us because we want to redirect to our shop on our website. I tested with no proxy --> error, use system proxy settings --> error What should i have to do ? Best regards, test.rar test.zip
  18. OK thank you JIM for your feedback. A simple way to fix this issu could be to recommand custom to not remove blockdiagram and to add this option directly in VIPM as suggested upper.. This will have two big advantage, custom win time to not multiply steps and in side of JKI engineers it just a simple script at the end of packaging that remove block diagram (no need to make big changement in your source code, execute it as usual and last step remove block diagram with scripting). About this issu is someone at your company will work on it ? Thank you for the github link but since three week nothing happen. (If you don't have actually the ressource to do it internally, one of my engineer can fix it fast because we really need it, it will take maximum a day). It's important for us to have a visibility because our custom (HAIBAL) already ask on LabVIEW 2022. For now we are blocked by this JKI issu because if we change our HAIBAL code in LV2022 we will no longer be able to protect our code effectively. So we are obliged to stay in LV2020 for the moment. https://haibal.com/support-community/topic/how-could-i-run-haibal-in-cpu-mode/ Thank you for your help, Youssef
  19. Dear Jim, I'm compiling a library with all diagram deleted. With LabVIEW 2020 and VIPM 2020 it works. When i do the same manipulation with LabVIEW 2022 and latest VIPM there is a Traverse Failed error (coming from scripting of VIPM). This problem is known since 2 years (https://forums.vipm.io/topic/4008-error-1012-dependency-bd-not-found/#comment-13562 ) and has not yet fixed, and no one at JKI made any feedback about it. Is someone can answer if this bug will be fixed ? This is a big issue. We release deep learning library 5 days ago and NI is now reviewing our distribution but for now we are forced to stay in 2020 because of this bug. (www.haibal.com) Suggestion for the future, it could be good to integrate remove block diagram fuctionality in the next version of VIPM (very useful) Thank you, Project.rar
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.