Jump to content
wyzromek

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

Recommended Posts

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.]

  • Like 1

Share this post


Link to post
Share on other sites

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. 

Share this post


Link to post
Share on other sites

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)

  • Like 1

Share this post


Link to post
Share on other sites

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.

 

Share this post


Link to post
Share on other sites

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).

image.png

Share this post


Link to post
Share on other sites

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).

image.png

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.

  • Like 1

Share this post


Link to post
Share on other sites
9 hours ago, wyzromek said:

Yep, the new version works well. Many thanks!

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 :)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

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