Jump to content

wyzromek

Members
  • Content Count

    7
  • Joined

  • Last visited

  • Days Won

    3

wyzromek last won the day on December 3

wyzromek had the most liked content!

Community Reputation

6 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yep, the new version works well. Many thanks!
  2. 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)
  3. 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.]
  4. wyzromek

    JKI SM conversion to LVNXG

    Sorry for my late answer, I am very bussy at work. Yes, I've tried. There a many placeholders. For examples: So, a lot of work to do. But OK. New technology (LV NXG), new philosophy, new tools... It is better to start the new project directly in NXG. But another problem in NXG 2.1. I have instaled JKI SM 2.0 and there is an option to start the new project with JKI SM. But... if I need to add JKI SM to new, empty VI I'm not able to do it. In new JKI SM project, there is also a lack of Close Reference in "Data: Cleanup" state. I am sorry for so many questions and comments, but I often use JKI SM and recommend it to my students as the next step with programming in LabVIEW (something more then a simple state machine). Regards
  5. Hi, I'm trying to convert a project with JKI SM from LabVIEW 2017 to LabVIEW NXG. I'm using JKI SM version 4.0.0.22 (in LV2017). During the conversion I get the message: In LV NXG I have JKI SM for NXG, version 2.0. Even a single VI with JKI SM inside can not be converted. It looks like there is a missing JKI SM version for NXG 1.0, but it can not be installed in NXG 2.0. I realize that LV NXG is still "fresh" and lacks many useful add-ons available in the "conventional" LV. But I wonder... maybe threre is a solution?
  6. I found one problem that occurs to me. "Find Data Accessors" is available in any VI (not only JKI State Machine) for the Unbudle by Name function, but its call does not cause the appropriate list to be displayed in the dialog box, although the application is started and consumes processor resources. Calling it several times on a notebook with an i5-4210M processor results in 100% CPU load. I've attached a screenshot for the FMSM example from LabVIEW example projects. As you can see, also Add Dynamic Events and JKI State Machine Editor... are visible - only when pop-up on Bundle/Unbundle by Name.
×

Important Information

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