LabVIEW NXG 4.0.0: Addons OpenG Library and JKI-SM; no install with NIPM; must be installed manually

[E.Schneider]

Hello,

it is not possible to install the OpenG Library or JKI-SM with the Paketmanager (current version 19.6.0) to LabVIEW NXG 4.0.0 installed.

If you don't have an older NXG installed you'll probably get the Screenshot attached (unfortunately in German).

To use the addons in NXG 4.0.0 you have to install them to NXG 2.0.0 and then manually copy to the addons folder to NXG 4.0.0.

(C:\Program Files\National Instruments\LabVIEW NXG 4.0\Addons)

Who can fix this behavior?

[E.Schneider]

OK I was wrong. Like in LabVIEW, we can't just copy these addons from one version to the other. 🙈

It seems essential that we have to do the NXG training before switching from LabVIEW.

Maybe I'll find a solution to install JKI SM and OpenG after some hours of learning... 😁

Update

My current solution: download the source code from https://github.com/JKISoftware/OpenG-NXG and https://github.com/JKISoftware/JKI-State-Machine-NXG and build the addon yourself...

[Manzolli]

I’m among the ones that had being with LabVIEW for a long time (since version 5.01) and still trying to find a good reason to switch to NXG, at least in one first project. Like you, I’m one of the few ones that “discovered” that NXG 4.0 was released prior to NIWeek.

You found the cumbersome (not your fault) solution to install the packages in 4.0. Why so hard? Looks like NXG is still in beta. I do think this latest version should be 3.2 not 4.0. There are not much novelties, and case reorder bug it is still present!

The new feedback system within the programming environment is handy, but we don’t get a proper feed back and there are no discussions on the web.

Thank you for your help, but I’m waiting for the official update to allow packages to be installed automatically on 4.0.

Bottom line: for every reason I have to use NXG, I have more than two to not use it.

[James_McN]

---

@E.Schneider wrote:

Update

My current solution: download the source code from https://github.com/JKISoftware/OpenG-NXG and https://github.com/JKISoftware/JKI-State-Machine-NXG and build the addon yourself...

---

Any particular steps for this?

I just cloned the OpenG repo but it wont "convert" the project to NXG 4.0.

[E.Schneider]

That's correct, if you open the "OpenG.lvproject" with NXG 4.0 you'll get an error.
You can create a new project in this repo and add all *.gcomp, save all, create new Package/Installer......

We stopped there and decided to wait for next NXG-releases and postponed the switch to NXG.

Sorry for the confusion! This is what I meant with "build the addon yourself..."

[Jim_Kring]

Hi All. Jim here -- I'm the maintainer of the JKI State Machine and OpenG packages. I was just informed of this thread. I'm following the discussion and will try to help get this going as best I can. NXG support is still ad hoc.

[billko]

---

@Jim_Kring wrote:

Hi All. Jim here -- I'm the maintainer of the JKI State Machine and OpenG packages. I was just informed of this thread. I'm following the discussion and will try to help get this going as best I can. NXG support is still ad hoc.

---

It's too bad that the big utility packages like OpenG are so hobbled by NXG exclusions, especially the ones that are design choices, and not just "not yet implemented".

A real back-breaker is not including properties on a wire.  Now you can't dig the name of a cluster out of a variant because it's not there any more.  There goes your special config file support.  I mean, you can include it as a string input, but that just makes maintainability for the user needlessly complicated.

And don't get me started about not being able to document controls inside a cluster.  Although I'm not entirely sure it just hasn't been implemented yet, there goes most of my self-documenting workflow, nonetheless.