Youssef Menjour Posted December 22, 2022 Report Share Posted December 22, 2022 (edited) 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 Edited December 22, 2022 by Youssef Menjour 1 Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted December 23, 2022 Report Share Posted December 23, 2022 Hi @Youssef Menjour. Thanks for posting such a detailed error report and including a sample project to reproduce the issue. There is a bug report in our public issue tracker, here:https://github.com/vipm-io/vipm-desktop-issues/issues/16 Thanks for your patience and the great suggestions. 1 Quote Link to comment Share on other sites More sharing options...
Youssef Menjour Posted December 23, 2022 Author Report Share Posted December 23, 2022 (edited) 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 Edited December 23, 2022 by Youssef Menjour Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted December 23, 2022 Report Share Posted December 23, 2022 I sent you a message offline about how we can test a possible fix. Thanks. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.