Jim Kring

@twalter we have a rudimentary JSON Schema Generator here: https://github.com/JKISoftware/generate-json-schema-labview It's saved in LV2020 and you can also use LV2024 (Q3 works best) which supports preserving the Save Version of the Project/VIs. Feel free to create issues and submit pull requests.

Thanks for reporting this @SlippinJimmy We've reproduced the error and created an issue in the GitHub bug tracker here: https://github.com/JKISoftware/JKI-JSON-Serialization/issues/51 Please post any follow-up comments in GitHub -- you can also subscribe to notifications on the issue there, too.

Hi @Jan. A design pattern we often use is to put the OpenG Periodic Trigger into the Timeout frame of the Event Structure and enqueue a state when the period occurs. We're currently working on a new 2024 release of the JKI State Machine that has a support VI for Periodic Enqueuing of states. New VI Coming Soon How you can do this today (with Periodic Trigger in the OpenG Time Library)

@Steen Schmidt I agree with you about leaving dependencies in their place by default -- we actually do that. It's simply that "C:\Program Files" (and the '(x86)' variant) wasn't on the list of locations where external components were expected. As always, things get a little tricky trying to support decades old paradigms. Regarding a fix for this issue, can you try 2024.3.2761-rc2 here 👉 https://www.vipm.io/desktop/versions/ This should leave anything found under "C:\Program Files" or "C:\Program Files (x86)" along and not build it into the package.

@Steen Schmidt I agree that this is something that needs a fix. I’m trying to think of there is ever a situation where it is desirable to have the current behavior. I can’t think of any off hand.

VIPM 2024 Q3 Release Candidate 1 is now available for testing: https://www.vipm.io/desktop/installer/vipm-24.3.2759-rc1-windows-setup.exe/ Some Key Improvements Improved performance of package info downloads Improved package building when VI dependencies are moved on disk (and linkages have changed) Improvements for projects and packages that contain and call Malleable VIs (VIMs) Better integration with JKI Dragon

Hi @TimE, there's a download link for 2024.3.2759-rc1 on the https://www.vipm.io/desktop/versions/ page. Thanks for trying it out and letting us know how it works for you. -Jim

Hi @TimE I believe that this is related to this issue: https://github.com/vipm-io/vipm-desktop-issues/issues/44 We have a newer build of VIPM 2024 Q3 that I’d love for you to test to see if it work better for you. I’ll share a link shortly. Jim

This is a Pro feature: saving all your project’s packages into a VIPC file: https://support.vipm.io/hc/en-us/articles/214135883-How-to-use-VI-Package-Configurations-VIPC

> 1.0.0.4 (Apr 14, 2023) > 3. Add a mass compile post-install step to avoid bitness-related load warnings when opening the code for the first time after install. @Darren is this load warning a LabVIEW “bug”?

@Bob Schor you'll find the actual packages in the C:\ProgramData\JKI\VIPM\cache folder. You can copy those to another computer and install the packages.

Thanks for reporting this @jyoung8711. FYI @Rolf Kalbermatter

Adding @Rolf Kalbermatter to this thread.

Hi @hooovahh, I didn't realize that this library offers support for spanning TDMS. I'm going to take a look at this right away... 👍 Thanks for the great tool!

@Zaphiro Technologies CC: @RolfK There is a cross-platform shared library naming trick. (It could be that the package build process messed up the paths when writing linker info.) See: LabVIEW Help >> Configuring the Call Library Function Node