Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 11/17/2018 in all areas

  1. 1 point
    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.]
  2. 1 point
    Yep, the new version works well. Many thanks!
  3. 1 point
    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.
  4. 1 point
    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)
  5. 1 point
    The issue is because I renamed the event case to "Idle" from "" (empty string). Renaming the case name will resolve this issue.
  6. 1 point
    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
  7. 1 point
    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
×

Important Information

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