Jump to content

All Activity

This stream auto-updates     

  1. Last week
  2. Sorry to open this thread again. However, I have VIPM 2018.0.0f1 and I am trying to build a package with VIMs in and I am getting exactly the same issue that James Powell posted earlier in this thread. Please can you tell me what the workaround was? As simply upgrading VIPM didn't work.
  3. Jim Kring

    [FIXED] JKI SM - problem with JKI SM Editor...

    Great! Thanks @wyzromek for reporting the issue (especially the steps to reproduce). It was very helpful in finding and fixing the issue. I'm sure lots of people are happy about this fix, too
  4. Yep, the new version works well. Many thanks!
  5. Jim Kring

    [FIXED] JKI SM - problem with JKI SM Editor...

    We figured it out -- it was getting an error during Macro Exit (shutdown), that was causing it to go into the error handler, which was going into Macro Exit (an infinite loop). You can work around this issue by tweaking the code inside the JKI SM Explorer window to look like the following. (You can open the JKI SM Explorer then press Ctrl+Space to stop the VI, then Ctrl+M to go into Edit mode). Update: This has been fixed in version 2018.0.1.36 of the JKI State Machine package, which has been published and is available for download and installation using VIPM.
  6. Earlier
  7. Jim Kring

    [FIXED] JKI SM - problem with JKI SM Editor...

    We figured it out -- it was getting an error during Macro Exit (shutdown), that was causing it to go into the error handler, which was going into Macro Exit (an infinite loop). You can work around this issue by tweaking the code inside the JKI SM Explorer window to look like the following. (You can open the JKI SM Explorer then press Ctrl+Space to stop the VI, then Ctrl+M to go into Edit mode).
  8. Jim Kring

    [FIXED] JKI SM - problem with JKI SM Editor...

    OK, we're looking into it. I see what you're seeing -- I'm also using LabVIEW 2018. I'll check on older versions of LabVIEW, too, to see if this is a new problem.
  9. No, CPU usage is high all of the time. Yes, Mass Compile is enabled (always). I reinstalled JKI State Machine, but still nothing. So, I have to remember to close the Block Diagram first or JKI SM Editor (Explorer in fact...). Maybe it is important or not... my LabVIEW version is 2018 (18.0f2)
  10. Jim Kring

    [FIXED] JKI SM - problem with JKI SM Editor...

    Hello @wyzromek. Do you notice that the CPU usage goes down after a minute? Do you have Mass Compile (in VIPM options dialog) enabled or disabled? I did a little testing and see that if I do not have JKI State Machine Editor mass compiled during installation, then I have this increased CPU issue (but that it goes away after a minute). However, if I I let VIPM Mass Compile the JKI State Machine Editor on installation, then I do not see the CPU increase after closing the VI that was using it. I'm curious if you see a similar behavior to what I'm observing.
  11. I've got a problem with JKI SM Editor (JKI SM ver. 2018). In one case, it increases the CPU resources consumption. The procedure is as follow: 1. Open New VI or existing VI with JKI SM. 2. Open block diagram. 3. Open JKI SM Editor. 4. Close front panel of the VI. CPU usage increases - in my case (i5-4210M) up to 38 - 40%. Have to reset the LabVIEW. Has anyone observed silmilar behaviour? [Update: This has been fixed in version 2018.0.1.36 of the JKI State Machine package, which has been published and is available for download and installation using VIPM.]
  12. Jim Kring

    Error 1055 in JKI State Machine Editor

    Hello @Bhaghyaraj. Thanks for letting us know and I'm glad you were able to figure it out. It's probably a good idea not to rename the frame that contains the Event Structure, since the JKI SM and it's under the hood APIs depend on some of those conventions.
  13. Bhaghyaraj

    Error 1055 in JKI State Machine Editor

    The issue is because I renamed the event case to "Idle" from "" (empty string). Renaming the case name will resolve this issue.
  14. Hi @kevin.j.r.ross, @Sam Taggart, We can reproduce the issue and it's a bit tricky, due to limitations in the scripting APIs associated with project libraries and the fact that these project items are not LabVIEW file types. There's no scripting API function to move a project item on disk that is a non-labview file type (and the build process used by VIPM loads the lvlibs and VIs into memory and moves them on disk, causing the links to those lvlib/project items to change). The work-around to this would be to do a lot of fancy, custom relinking on disk, which involves parsing and modifying the raw XML files for the lvlibs. This could work for unlocked lvlibs, but won't work for a password-protected lvlib. Now, it's possible to do these changes in memory, but I think it would involve removing items from the lvlib and then re-adding them to the lvlib after they are moved on disk. I looked to see if anyone has solved this problem and there's a discussion on LAVA about it -- I checked out these resources (GOOP Developer and Darren's Hidden Gems) and these don't deal with non-labview file types, from what I can tell. Now, you could work-around this LabVIEW limitation with a post-build custom action (requires VIPM Pro) that temporarily unpacks (unzips) the package, modifies the lvlib's (and lvproj's) xml files to link to the correct paths, and then re-packs (zips) the package. I've created a sample project that shows this technique and it works for the Simple Example that Sam posted earlier. Here is that work-around in action: >>> Simple Example - Post Build Fix.zip <<< Some notes about this example work-around: Requires VIPM Pro Uses OpenG Zip Tools to unpack/repack (I've included a VIPC file you can apply to quickly install this) Has a very brittle XML parser/fixer (you can see the code, below) -- you'll want to put some of your own love into this (e.g. depending on the actual relative paths to the items inside the lvlib) 🙂 Hope that offers some possibilities for you...
  15. Jim, Thank you so much for your reply. I look forward to hearing from you in the near future, hopefully with a solution. Many thanks Kevin
  16. Hi Sam, Thanks for posting this example. I'll pass it along to our team to reproduce and review. As always, we can't commit to a fix timeline, but we'll certainly look into it.
  17. Thanks for posting this information. Since this is an issue with installing LabVIEW, maybe you could try contacting NI support? One idea that I have is for you to try (first) installing the latest version of VIPM by itself (vipm.jki.net/get) and then (second) installing LabVIEW 2018.
  18. And so on, If I press "Ignore", Labview will continue install, but after finish, nothing happen when you start Labview. I meant it even not start.
  19. Hi everyone! When I try to reinstall Labview 2018 after uninstall last week(maybe uninstall in the wrong way), I have a problem. an error was encountered as image below. Please help me! Thank you so much!
  20. I have been using the JKI State Machine Editor (V.2013.3.2.170) and facing the following issues. Can anyone help me resolve them?
  21. Hi Thanks for uploading this, this replicates my problem in a simple way. Jim hopefully this should help debug the problem further. Let me know if you need anything else from me. Kev
  22. Jim, Here is a simple example. Note it appears that also text files (and perhaps any non-LV files) are affected. The .vipb file is from 2017. Sam Simple Example.zip
  23. Hi Jim, Thanks for your email. Let me see what I can do, the current code is private so I don't think I can share but let me see if I can create a simple project. The .PNG files are not the only files in the lvlib, there is also .vi and .ctls in the .lvlib also Do you have an email address or skype that I would be able to share any code with you. Thanks Kevin
  24. Jim Kring

    Problem with VIPM for linux

    It looks like you need to install the LabVIEW 2015 run-time engine for Linux. http://www.ni.com/download/labview-run-time-engine-2015-sp1/5838/en/
  25. Jim Kring

    Updating VIPM 2017 to 2018

    Hi Tim. This is one of those odd Windows/IT issues -- sorry it's such a pain. Perhaps installing 2017 on a new system and then seeing if you can find the uninstaller files and copy them over to the old computer might work? I don't necessarily recommend that, but if you're trying to figure out a solution, perhaps that could work.
  26. Hi Kev. Can you zip up a simple project that demonstrates the problem. This will make it easier for our team to reproduce and possibly fix this issue. Note that this might not be an easy fix. And, it's also worth noting that VIPM should be able to build packages that include PNG files. Is there a reason why they have to be part of the LVLIB (considering that these are not LabVIEW file types)?
  27. Hi, Please help... I am trying to create a .vip that will install my LabVIEW project as a LabVIEW project template (note: I have done this process a few time before with no issues) I have my project that I want to make into a template, everything works perfectly. I configure the .vipb, I build and install the .vip. I check the destination to see if my files have installed to the correct location, they have. Here's where the problem kicks in...... I open my LabVIEW project that has installed in the destination, and notice that the .png files in my project some are missing and some are saying missing. In my project I have .png files in various .lvlibs. The first .lvlib in the project has the .png's showing, however showing as missing and the expected location is saying C:\ which is incorrect, it should be in the location where my .lvlib is in the destination. The other .lvlib's don't even show the .pngs in the LabVIEW project explorer. Now checking on disk all the png's are there and in the correct location. In summary it looks as if as part of the vip install it is removing the link the .lvproj has to my .png files VI Package Manager Version : 2018.0.0f1 Jul 21 2018 LabVIEW Version : 2016 (32 bit) OS : Windows 10 Pro Version 1803 Any help is greatly appreciated Thanks in advance. Kev
  1. Load more activity
×

Important Information

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