JKI
-
Posts
803 -
Joined
-
Last visited
-
Days Won
1
Posts posted by JKI
-
-
http://www.jkisoft.com/packages/packages/jgcode_rpk_ni_system_style_daqmx_controls/jgcode_rpk_ni_system_style_daqmx_controls-1.0-1.bmp
Product: jgcode_rpk_ni_system_style_daqmx_controls v1.0
Company: National Instruments
Release Date: Mon, 04 Jan 2021 12:25:10 -0800
Packager: Jonathon Green <jg@jgcode.net>
Description: SimonH:
Between the system controls defined by the operating system and the additional system-styled controls I posted here we have options for most LabVIEW controls. The most notable missing elements were the special I/O controls that are more than simple ring controls (as they are able to self-populate based on what I/O is configured in the system).
I recently found out that we have created system-style DAQmx controls for internal use, they just aren't in the normal palettes. I'll work on getting these on the default palettes in the future but for now you can just download the attached MNU file and you'll have the following new controls.
Release Notes:
-
http://www.jkisoft.com/packages/packages/labview_open_source_project_lib_mqtt_broker/labview_open_source_project_lib_mqtt_broker-3.1.4.12.bmp
Product: MQTT Broker v3.1.4.12
Company: LabVIEW Open Source Project
Release Date: Fri, 01 Jan 2021 12:55:14 -0800
Packager: Francois Normandin
Description: LV-MQTT-Broker
Native LabVIEW MQTT Broker Server
This project is an exercise in Test-Driven Development, which essentially means that the code is implemented gradually and verified through comprehensive unit tests. At any point in time, the features included in a particular release are fully functional. This also means that all releases have partial functionality.
For a fully compliant MQTT broker, 141 requirements (as listed in the OASIS specification) need to be satisfied. Those requirements have been added as issues and the progress can be tracked on the Github's website. The list of currently supported features is found by filtering the issues to show only the "closed" issues.
https://github.com/LabVIEW-Open-Source/LV-MQTT-Broker
For example, release 1.0 features a functional client and broker but does not support QoS>0, retain messages, duplicate flag, wills or support for session persistency. Some topic sub-level matching is also not yet supported.
Compliance
This project is an implementation of the MQTT 3.1.1 Oasis Standard as defined here:
MQTT Version 3.1.1. Edited by Andrew Banks and Rahul Gupta. 29 October 2014. OASIS Standard. http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html. Latest version: http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt->v3.1.1.html.
For those interested, MQTT 5.0 was released in March 2019 and will be tackled by this project when the broker is mature enough for production deployments.
Contribution to the project
It is an all-LabVIEW MQTT broker. The project includes a subset for a MQTT Client, as this is useful for testing the server implementation. All normative requirements are being listed in this project as issues to solve in order to have a fully compliant MQTT broker.
To contribute to this project, you must:
Sign the contributor agreement and agree that your contribution will be licensed under "0-BSD" and attribution will be in the name of "LabVIEW Open Source Project". As a co-author, your contribution will be recognized through the commit logs made on this repository and in your personal Github activity report.
Use LabVIEW 2013 SP1 for source code
Dependencies have to be compatible with "0-BSD" licensing requirements. If in doubt, please ask.
Use the [MQTT-x.x.x-y] format in any commit that addresses a particular requirement whether it relates to bug, question or conformance to the said requirement.
This project is developed using a Test-Driven approach (TDD). This means that ALL requirements MUST have a unit test that confirms that a requirement is met before that requirement can be labeld as "closed".
Excerpt From the OASIS MQTT Specification
==============================
MQTT is a Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed so as to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium.
The protocol runs over TCP/IP, or over other network protocols that provide ordered, lossless, bi-directional connections. Its features include:
Use of the publish/subscribe message pattern which provides one-to-many message distribution and decoupling of applications.
A messaging transport that is agnostic to the content of the payload.
Three qualities of service for message delivery:
"At most once", where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after.
"At least once", where messages are assured to arrive but duplicates can occur.
"Exactly once", where message are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied.
A small transport overhead and protocol exchanges minimized to reduce network traffic.
A mechanism to notify interested parties when an abnormal disconnection occurs.
Release Notes: [Fix: 162] Disabled the DUP resend feature for packets which affected QoS = 2. Feature is not yet unit tested and will be re-enabled only when tests demonstrate it works according to specification
-
http://www.jkisoft.com/packages/packages/labview_open_source_project_lib_openuri/labview_open_source_project_lib_openuri-1.0.0.9.bmp
Product: OpenURI v1.0.0.9
Company: LabVIEW Open Source Project
Release Date: Thu, 31 Dec 2020 15:29:43 -0800
Packager: Francois Normandin
Description:
Release Notes: Initial release of openURI for handling resource locators and resource names as per RFC 3986
-
http://www.jkisoft.com/packages/packages/wovalab_lib_asciidoc_for_labview/wovalab_lib_asciidoc_for_labview-1.3.0.33.bmp
Product: Asciidoc for LabVIEW v1.3.0.33
Company: Wovalab
Release Date: Mon, 21 Dec 2020 11:21:21 -0800
Packager: Olivier Jourdan
Description: This toolkit provides a set of vis that helps you builds plain-text file using asciidoc syntax
= What is AsciiDoc ?
AsciiDoc is two things:
. A mature, plain-text writing format for authoring notes, articles, documentation, books, ebooks, web pages, slide decks, blog posts, man pages, and more.
. A text processor and toolchain for translating AsciiDoc documents into various formats (called backends), including HTML, DocBook, PDF, and ePub.
More information here https://asciidoctor.org/docs/what-is-asciidoc/#what-is-asciidoc
NOTE: This product description is written with asciidoc syntax ;)
Release Notes: == New:
. Handle column formating in tables --> https://gitlab.com/wovalab/open-source/asciidoc-toolkit/-/issues/34
. Handle table attributes --> https://gitlab.com/wovalab/open-source/asciidoc-toolkit/-/issues/33
. Handle TOC position for HTML5 output --> https://gitlab.com/wovalab/open-source/asciidoc-toolkit/-/issues/29
. Handle document revision number, date and remark --> https://gitlab.com/wovalab/open-source/asciidoc-toolkit/-/issues/32
. Add accessor to get sections contain in a subsection --> https://gitlab.com/wovalab/open-source/asciidoc-toolkit/-/issues/30
-
http://www.jkisoft.com/packages/packages/wiresmith_technology_lib_futures/wiresmith_technology_lib_futures-0.1.0.8.bmp
Product: Futures v0.1.0.8
Company: Wiresmith Technology
Release Date: Fri, 18 Dec 2020 10:22:54 -0800
Packager: James McNally
Description: Implements a basic API for promises and futures in LabVIEW to enable easier management of asynchronous messaging.
Release Notes: First release with basic APIs.
-
http://www.jkisoft.com/packages/packages/hooovahh_copy_and_zip_with_progress/hooovahh_copy_and_zip_with_progress-1.0.0.4.bmp
Product: Hooovahh File IO >> Copy and Zip with Progress v1.0.0.4
Company: Hooovahh
Release Date: Wed, 16 Dec 2020 11:22:40 -0800
Packager: Brian Hoover (Hooovahh)
Description: This package contains a set of API that can copy or zip files and query the progress, and invoke a cancel.
Release Notes: 1.0.0.4
- Initial release with 3 zipping, and 4 copying methods
-
http://www.jkisoft.com/packages/packages/hooovahh_file_io/hooovahh_file_io-1.0.1.2.bmp
Product: Hooovahh File IO v1.0.1.2
Company: Hooovahh
Release Date: Wed, 16 Dec 2020 08:20:19 -0800
Packager: Brian Hoover (Hooovahh)
Description: This package contains VIs which perform operations involving the file system or the path data type. Some of these functions will use .Net and will be for Windows only.
Release Notes: 1.0.1.2
- Fixed a dependency linkage, previous version would work eventually but would get a searching dialog from LabVIEW
1.0.0.1
- Initial release with Get/Set File Attributes and date information
- Is Path Valid and Exists
- List Directory Recursive with performance improvements
- Minor fix allowing for Get and Set File Creation date to work on OSs that don't support the .Net method
- Append File to file, create Dir changes, Delete Empty Folder, dupliate files and folder
- Mapping and testing network drives
- Palette for path and name manipulation
- Added Create Directory if Non-Existant 777 which is an improvement over the OpenG implementation and should be used on RT
- Integrity Check subpalette with CRC32 of an array, and moved MD5 of folder into it
- Program Data Path to Get INI Config Path
- Create Unique File Name with Incrementing Suffix
- Initial release with many File I/O function for TDMS, Windows, and path contstants.
-
http://www.jkisoft.com/packages/packages/jki_lib_network_streams_connection/jki_lib_network_streams_connection-1.1.1.15.bmp
Product: JKI Network Streams Connection v1.1.1.15
Company: JKI
Release Date: Tue, 15 Dec 2020 15:22:25 -0800
Packager: Javier Ruiz
Description: This library allows for bi-directional communication over LabVIEW Network Streams in order to communicate with remote systems. You can specify the two endpoint names and one of the IP addresses. You can also communicate on the same computer by using "localhost" as the address. Check out the examples for ideas on how to use the library.
Release Notes: - Fixed an issue that would cause classes not to be included in the build for some LabVIEW versions.
-
http://www.jkisoft.com/packages/packages/labview_open_source_project_lib_mqtt_client/labview_open_source_project_lib_mqtt_client-3.1.5.12.bmp
Product: MQTT Client v3.1.5.12
Company: LabVIEW Open Source Project
Release Date: Sat, 12 Dec 2020 16:25:13 -0800
Packager: Francois Normandin
Description: LV-MQTT-Client
https://github.com/LabVIEW-Open-Source/MQTT-Client
Release Notes: [Fix: 161] Client acknowledges the PUBLISH message when QoS > 0, which prevents broker from retrying to send packet multiple times. (reported in MQTT Broker issue tracker)
[Fix: 4] Fixed a memory leak where packet ID were stored and never removed from memory when QoS = 0
-
http://www.jkisoft.com/packages/packages/labview_open_source_project_lib_mqtt_broker/labview_open_source_project_lib_mqtt_broker-3.1.3.11.bmp
Product: MQTT Broker v3.1.3.11
Company: LabVIEW Open Source Project
Release Date: Sat, 12 Dec 2020 16:24:04 -0800
Packager: Francois Normandin
Description: LV-MQTT-Broker
Native LabVIEW MQTT Broker Server
This project is an exercise in Test-Driven Development, which essentially means that the code is implemented gradually and verified through comprehensive unit tests. At any point in time, the features included in a particular release are fully functional. This also means that all releases have partial functionality.
For a fully compliant MQTT broker, 141 requirements (as listed in the OASIS specification) need to be satisfied. Those requirements have been added as issues and the progress can be tracked on the Github's website. The list of currently supported features is found by filtering the issues to show only the "closed" issues.
https://github.com/LabVIEW-Open-Source/LV-MQTT-Broker
For example, release 1.0 features a functional client and broker but does not support QoS>0, retain messages, duplicate flag, wills or support for session persistency. Some topic sub-level matching is also not yet supported.
Compliance
This project is an implementation of the MQTT 3.1.1 Oasis Standard as defined here:
MQTT Version 3.1.1. Edited by Andrew Banks and Rahul Gupta. 29 October 2014. OASIS Standard. http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html. Latest version: http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt->v3.1.1.html.
For those interested, MQTT 5.0 was released in March 2019 and will be tackled by this project when the broker is mature enough for production deployments.
Contribution to the project
It is an all-LabVIEW MQTT broker. The project includes a subset for a MQTT Client, as this is useful for testing the server implementation. All normative requirements are being listed in this project as issues to solve in order to have a fully compliant MQTT broker.
To contribute to this project, you must:
Sign the contributor agreement and agree that your contribution will be licensed under "0-BSD" and attribution will be in the name of "LabVIEW Open Source Project". As a co-author, your contribution will be recognized through the commit logs made on this repository and in your personal Github activity report.
Use LabVIEW 2013 SP1 for source code
Dependencies have to be compatible with "0-BSD" licensing requirements. If in doubt, please ask.
Use the [MQTT-x.x.x-y] format in any commit that addresses a particular requirement whether it relates to bug, question or conformance to the said requirement.
This project is developed using a Test-Driven approach (TDD). This means that ALL requirements MUST have a unit test that confirms that a requirement is met before that requirement can be labeld as "closed".
Excerpt From the OASIS MQTT Specification
==============================
MQTT is a Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed so as to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium.
The protocol runs over TCP/IP, or over other network protocols that provide ordered, lossless, bi-directional connections. Its features include:
Use of the publish/subscribe message pattern which provides one-to-many message distribution and decoupling of applications.
A messaging transport that is agnostic to the content of the payload.
Three qualities of service for message delivery:
"At most once", where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after.
"At least once", where messages are assured to arrive but duplicates can occur.
"Exactly once", where message are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied.
A small transport overhead and protocol exchanges minimized to reduce network traffic.
A mechanism to notify interested parties when an abnormal disconnection occurs.
Release Notes: [Fix: 161] Repetition of publish packet in QoS > 0 (MQTT Client package upgrade)
- Fixed a unit test which failed after fixing CONNECT packet handling of length-prefixed password
- Includes upgrade for MQTT Client and Control Packet Dependencies which fix a few bugs
Please refer to https://github.com/LabVIEW-Open-Source/MQTT-Client and https://github.com/LabVIEW-Open-Source/LV-MQTT-Control-Packets for more info
-
http://www.jkisoft.com/packages/packages/jki_lib_network_streams_connection/jki_lib_network_streams_connection-1.1.0.14.bmp
Product: JKI Network Streams Connection v1.1.0.14
Company: JKI
Release Date: Fri, 11 Dec 2020 11:35:58 -0800
Packager: Javier Ruiz
Description: This library allows for bi-directional communication over LabVIEW Network Streams in order to communicate with remote systems. You can specify the two endpoint names and one of the IP addresses. You can also communicate on the same computer by using "localhost" as the address. Check out the examples for ideas on how to use the library.
Release Notes: - Updated to BSD License
- Added RT Palette
- Updated copyright on VIs
-
http://www.jkisoft.com/packages/packages/jki_lib_network_streams_connection/jki_lib_network_streams_connection-1.1.0.13.bmp
Product: Network Streams Connection v1.1.0.13
Company: JKI
Release Date: Thu, 10 Dec 2020 22:46:34 -0800
Packager: Javier
Description: This library allows for bi-directional communication over LabVIEW Network Streams in order to communicate with remote systems. You can specify the two endpoint names and one of the IP addresses. You can also communicate on the same computer by using "localhost" as the address. Check out the examples for ideas on how to use the library.
Release Notes: - Upgraded to LabVIEW 2015
- First public release
- Fixed dependency issues
-
http://www.jkisoft.com/packages/packages/hse_lib_hse_layout_manager/hse_lib_hse_layout_manager-1.2.1.4.bmp
Product: HSE Layout Manager v1.2.1.4
Company: Hampel Software Engineering
Release Date: Thu, 10 Dec 2020 11:49:48 -0800
Packager: Hampel Software Engineering
Description: A layout system for LabVIEW frontpanel objects (controls) inspired by Qt5 (https://doc.qt.io/qt-5/layout.html).
==============================
Beware: Even though the version number suggests differently,
this tool is still in beta state. At this time, it really only caters to
a vertical grid layout.
==============================
More information is available at
https://dokuwiki.hampel-soft.com/code/open-source/hse-layout-manager
The latest release version can be found at
https://gitlab.com/hampel-soft/open-source/hse-layout-manager
Release Notes: [BETA] Beware: This tool is still in beta stage.
[FIX] When resizing, update parent pane size so controls are sized to the new pane dimensions
-
http://www.jkisoft.com/packages/packages/jki_simple_localization/jki_simple_localization-1.0.2.30.bmp
Product: JKI Simple Localization v1.0.2.30
Company: JKI
Release Date: Thu, 10 Dec 2020 10:22:01 -0800
Packager: JKI
Description: This toolkit makes use of the "Language for non-Unicode programs" setting in Windows (located in the "Region and Language" settings). The toolkit uses a JSON dictionary file (can be in Unicode format) to store phrases in several different languages. The toolkit will translate from the default language (typically English) to the target language specified as the "Language for non-Unicode programs" in Windows.
It does all this by making calls into the Windows API to translate the Unicode 16-bit characters from the dictionary into 8-bit non-unicode characters that can be displayed by non-Unicode program (assuming the "Language for non-Unicode programs" has been properly set in Windows).
In this way, LabVIEW developers have a simple way to localize their applications, even though LabVIEW does not support Unicode, out-of-the-box.
Release Notes: Fix #30 - Boolean text with "multiple strings" (different strings for TRUE and FALSE) is reversed
-
http://www.jkisoft.com/packages/packages/zuehlke_engineering_lib_zalign/zuehlke_engineering_lib_zalign-1.0.0.4.bmp
Product: ZAlign v1.0.0.4
Company: Zuehlke Engineering
Release Date: Thu, 10 Dec 2020 06:21:31 -0800
Packager: Niko Naredi-Rainer
Description: Overview:
*****
This QuickDrop PlugIn allows the fast and clean arrangement of Fornt Panel elements.
On a front panel all controls are automatically arranged according to the connector pane and the window size is adjusted.
Controls that are not connected are listed under Locals.
The grid used can be customized in the ZAlign.ini file in the installation directory.
(C:\Program Files (x86)\National Instruments\LabVIEW 20XX\resource\dialog\QuickDrop\plugins\ZAlign)
There is also an extended mode for GUI front panels (see HowTo).
How to Use:
*******
On a front panel all controls are automatically arranged and the window size is adjusted.
Key commands to run ZAlign:
1) CTRL-Space (start QuickDrop)
2) Run CTRL-A ZAlign
There is also the extended mode for GUI front panels. In this case the elements must be selected which
should be aligned. The controls are then arranged in the upper left quadrant. Everything else remains
unchanged at its position.
Release Notes: Minor typo fixes
-
http://www.jkisoft.com/packages/packages/hooovahh_file_io/hooovahh_file_io-1.0.0.1.bmp
Product: Hooovahh File IO v1.0.0.1
Company: Hooovahh
Release Date: Tue, 08 Dec 2020 13:23:39 -0800
Packager: Brian Hoover (Hooovahh)
Description: This package contains VIs which perform operations involving the file system or the path data type. Some of these functions will use .Net and will be for Windows only.
Release Notes: 1.0.0.1
- Initial release with Get/Set File Attributes and date information
- Is Path Valid and Exists
- List Directory Recursive with performance improvements
- Minor fix allowing for Get and Set File Creation date to work on OSs that don't support the .Net method
- Append File to file, create Dir changes, Delete Empty Folder, dupliate files and folder
- Mapping and testing network drives
- Palette for path and name manipulation
- Added Create Directory if Non-Existant 777 which is an improvement over the OpenG implementation and should be used on RT
- Integrity Check subpalette with CRC32 of an array, and moved MD5 of folder into it
- Program Data Path to Get INI Config Path
- Create Unique File Name with Incrementing Suffix
- Initial release with many File I/O function for TDMS, Windows, and path contstants.
-
http://www.jkisoft.com/packages/packages/zuehlke_engineering_lib_zalign/zuehlke_engineering_lib_zalign-1.0.0.3.bmp
Product: ZAlign v1.0.0.3
Company: Zuehlke Engineering
Release Date: Mon, 07 Dec 2020 09:40:56 -0800
Packager: Niko Naredi-Rainer
Description: ZAlign:
*****
This QuickDrop PlugIn allows the fast and clean arrangement of Fornt Panel elements.
On a front panel all controls are automatically arranged according to the connector pane and the window size is adjusted.
Controls that are not connected are listed under Locals.
The grid used can be customized in the ZAlign.ini file in the installation directory.
(C:\Program Files (x86)\National Instruments\LabVIEW 20XX\resource\dialog\QuickDrop\plugins\ZAlign)
There is also an extended mode for GUI front panels (HowTo).
How to Use:
*******
On a front panel all controls are automatically arranged and the window size is adjusted.
Key commands to run ZAlign:
1) CTRL-Space (start QuickDrop)
2) Run CTRL-A ZAlign
There is also the extended mode for GUI front panels. In this case the elements must be selected which
should be aligned. The controls are then arranged in the upper left quadrant. Everything else remains
unchanged at its position.
Release Notes: Initial Build for the VIPM Community Edition
-
http://www.jkisoft.com/packages/packages/labview_open_source_project_lib_mqtt_control_packets/labview_open_source_project_lib_mqtt_control_packets-3.1.3.9.bmp
Product: MQTT Control Packets v3.1.3.9
Company: LabVIEW Open Source Project
Release Date: Thu, 03 Dec 2020 08:54:24 -0800
Packager: Francois Normandin
Description: LV-MQTT-Control-Packets
https://github.com/LabVIEW-Open-Source/LV-MQTT-Control-Packets
This package consists of a library for MQTT Control Packets handling
It currently supports version 3.1.1 of the MQTT protocol (Protocol Level 4).
These classes can be used as the basis for client and server by providing a clean and easy control packet handling scheme via OOP.
Release Notes: Fixed the password stream which was not length-prefixed
-
http://www.jkisoft.com/packages/packages/jki_lib_caraya/jki_lib_caraya-1.1.0.119.bmp
Product: Caraya Unit Test Framework v1.1.0.119
Company: JKI
Release Date: Wed, 02 Dec 2020 11:09:05 -0800
Packager: JKI
Description: Caraya Unit Test Framework is an open source unit testing framework for LabVIEW. It takes a whole new approach to unit testing; your VI is your test. Caraya allows you to convert your manual test VIs you use for debugging into unit test cases with nearly no effort. Even running the tests is easy, just run the test case VI. Caraya significantly lowers the barrier for developers to write unit tests leading into improved overall code quality in real-world projects where developers dont always have the luxury to write unit test cases first.
It runs on real-time targets and in the run-time engine too!
To learn more visit
http://jki.net/tools#caraya
Release Notes: Fixes:
[Fix: 98] Fixed the error on re-running tests from the Test Manager when called from "Run Tests in Active Project"
[Fix: 100] Test Event storage now uses Test and Assert IDs to update verbose explanations in reports
[Fix: 101] Broken VIs are now handled properly in the Batch Running all Tests in Active Project
[Fix: 102] Conditionally disable the "UI: Update Count" frame content on RT targets
[Fix: 103] OpenG dependencies are now included in the package (and namespaced)
[Fix: 104] Asserts in SubVIs not appearing as expected in JUnit reports
[Fix: 109] The Test Name/Assert Name are used instead of VI File Name (reverted to same behavior as 1.0.2)
[Fix: 110] Test Event storage now uses Test and Assert IDs to update verbose explanations in reports
New Features:
[Feature: 94] Added a Pre-Build PassFail verification step for package building
[Feature: 95] Test Suite now returns a "Test Result" object when it completes.
Thanks for all the contributions that led to this release, whether by reporting bugs, requesting features that made it to release or by lending a hand in fixing issues or releasing features:
Christopher Field (@volks73)
Joerg Hampel (@joerghampel)
Matthew Jacobson (@jacobson3)
Jim Kring (@jimkring)
James McNally (@JamesMc86)
Francois Normandin (@francois-normandin)
Felipe Pinheiro Silva (@felipefoz)
Chris Stryker (@ChrisStrykesAgain)
Sam Taggart (@stagg54)
Antonio Terrazas (@aterrazasl)
SRM256 (@SRM256)
-
http://www.jkisoft.com/packages/packages/labview_open_source_lib_serializer/labview_open_source_lib_serializer-1.1.1.14.bmp
Product: OpenSerializer v1.1.1.14
Company: LabVIEW Open Source Project
Release Date: Wed, 02 Dec 2020 10:45:13 -0800
Packager: Francois Normandin
Description: Serializer is a package serving as base class for serialization and deserialization of LabVIEW Data.
User are expected to extend the core to provide concrete implementation. The package contains one specific class to offer an example for text serialization.
*********
This library proposes an abstract Serializer class and supplements it with Serialzer.PlainText and Serializer.Plaintext.INI classes.
Examples of other serializers could be Serializer.JSON, Serializer.XML, etc.
Release Notes: Fixed a couple bugs in OpenSerializer.PlainText during unmarshalling of simple string and unnamed cluster element in the type terminal input.
-
http://www.jkisoft.com/packages/packages/jki_lib_vipm_api/jki_lib_vipm_api-2020.0.2.73.bmp
Product: VIPM API v2020.0.2.73
Company: JKI
Release Date: Fri, 27 Nov 2020 20:22:49 -0800
Packager: JKI
Description: The VIPM VI-based API is a collection of VIs that allow you to command and control VIPM (VI Package Manager). The VIs have been compiled in LabVIEW 2013 and can be used for automation code written in LabVIEW 2013 or newer.
The VIPM 2020 API VIs only work with <b>VIPM 2020 Pro or Community Edition</b> (or newer). It will not work with VIPM Free Edition. Also, In order for the API to work, you must have the main VIPM application running. It can be minimized, but it must be running.
For help with the VIPM API, please visit: <u>support.vipm.io</u>
List of Functions:
<b>Main (Root Palette)</b>
- Install VI Packages by Name.vi
- Uninstall VI Packages by Name.vi
<b>Library Subpalette</b>
- Add VI Packages to VIPM Package Library.vi
- Remove VI Package from VIPM Package Library.vi
- Download VI Packages.vi
- Network Update and Sync VIPM Package Library.vi
- List VIPM Package Library Contents.vi
<b>Package Building Subpalette</b>
- Build VI package.vi
- Write VI Package Build Spec.vi
- Read VI Package Build Spec.vi
<b>VI Package Configuration (VIPC) Subpalette</b>
- Apply VIPC File.vi
- Test VIPC Apply Needed.vi
- Scan Project.vi
- Create New VIPC File.vi
<b>Repository Subpalette</b>
- Publish VI Packages to Repository.vi
- Unpublish VI Packages from Repository.vi
- List Repository Contents.vi
- List VIPM Managed Repositories.vi
<b>Utility Subpalette</b>
- List VIPM LabVIEW Target Version.vi
- Switch Target.vi
- Open VIPM.vi
- Check is VIPM Running.vi
- Minimize VIPM.vi
- Exit VIPM.vi
Release Notes: - [FIX] Passing four-digit LabVIEW version (year) to Test VIPC Apply Needed was causing an error (was only supporting two digit LV version)
- [FIX] Test VIPC Apply Needed was returning an error for LabVIEW versions where packages havee never yet been installed (when the package installation database is empty).
- [ADD] VIPC File LabVIEW Version now passed out of Test VIPC Apply Needed (and can be passed to other API calls like Apply VIPC, etc.)
-
http://www.jkisoft.com/packages/packages/jki_lib_vipm_api/jki_lib_vipm_api-2020.0.1.69.bmp
Product: VIPM API v2020.0.1.69
Company: JKI
Release Date: Fri, 20 Nov 2020 10:10:31 -0800
Packager: JKI
Description: The VIPM VI-based API is a collection of VIs that allow you to command and control VIPM (VI Package Manager). The VIs have been compiled in LabVIEW 2013 and can be used for automation code written in LabVIEW 2013 or newer.
The VIPM 2020 API VIs only work with <b>VIPM 2020 Pro or Community Edition</b> (or newer). It will not work with VIPM Free Edition. Also, In order for the API to work, you must have the main VIPM application running. It can be minimized, but it must be running.
For help with the VIPM API, please visit: <u>support.vipm.io</u>
List of Functions:
<b>Main (Root Palette)</b>
- Install VI Packages by Name.vi
- Uninstall VI Packages by Name.vi
<b>Library Subpalette</b>
- Add VI Packages to VIPM Package Library.vi
- Remove VI Package from VIPM Package Library.vi
- Download VI Packages.vi
- Network Update and Sync VIPM Package Library.vi
- List VIPM Package Library Contents.vi
<b>Package Building Subpalette</b>
- Build VI package.vi
- Write VI Package Build Spec.vi
- Read VI Package Build Spec.vi
<b>VI Package Configuration (VIPC) Subpalette</b>
- Apply VIPC File.vi
- Test VIPC Apply Needed.vi
- Scan Project.vi
- Create New VIPC File.vi
<b>Repository Subpalette</b>
- Publish VI Packages to Repository.vi
- Unpublish VI Packages from Repository.vi
- List Repository Contents.vi
- List VIPM Managed Repositories.vi
<b>Utility Subpalette</b>
- List VIPM LabVIEW Target Version.vi
- Switch Target.vi
- Open VIPM.vi
- Check is VIPM Running.vi
- Minimize VIPM.vi
- Exit VIPM.vi
Release Notes: - [FIX] Was raising Error 42 (The LabVIEW version specified is not configured for use in VIPM. Please check the VIPM>Options>LabVIEW settings.) on Systems that used a comma "," as the system decimal symbol (e.g. German).
-
Product: VIPM API v2020.0.1.69
Company: JKI
Release Date: Fri, 20 Nov 2020 10:10:31 -0800
Packager: JKI
Description: The VIPM VI-based API is a collection of VIs that allow you to command and control VIPM (VI Package Manager). The VIs have been compiled in LabVIEW 2013 and can be used for automation code written in LabVIEW 2013 or newer.
The VIPM 2020 API VIs only work with <b>VIPM 2020 Pro or Community Edition</b> (or newer). It will not work with VIPM Free Edition. Also, In order for the API to work, you must have the main VIPM application running. It can be minimized, but it must be running.
For help with the VIPM API, please visit: <u>support.vipm.io</u>
List of Functions:
<b>Main (Root Palette)</b>
- Install VI Packages by Name.vi
- Uninstall VI Packages by Name.vi
<b>Library Subpalette</b>
- Add VI Packages to VIPM Package Library.vi
- Remove VI Package from VIPM Package Library.vi
- Download VI Packages.vi
- Network Update and Sync VIPM Package Library.vi
- List VIPM Package Library Contents.vi
<b>Package Building Subpalette</b>
- Build VI package.vi
- Write VI Package Build Spec.vi
- Read VI Package Build Spec.vi
<b>VI Package Configuration (VIPC) Subpalette</b>
- Apply VIPC File.vi
- Test VIPC Apply Needed.vi
- Scan Project.vi
- Create New VIPC File.vi
<b>Repository Subpalette</b>
- Publish VI Packages to Repository.vi
- Unpublish VI Packages from Repository.vi
- List Repository Contents.vi
- List VIPM Managed Repositories.vi
<b>Utility Subpalette</b>
- List VIPM LabVIEW Target Version.vi
- Switch Target.vi
- Open VIPM.vi
- Check is VIPM Running.vi
- Minimize VIPM.vi
- Exit VIPM.vi
Release Notes: - [FIX] Was raising Error 42 (The LabVIEW version specified is not configured for use in VIPM. Please check the VIPM>Options>LabVIEW settings.) on Systems that used a comma "," as the system decimal symbol (e.g. German).
-
http://www.jkisoft.com/packages/packages/foerster_tech_lib_labplot_ly/foerster_tech_lib_labplot_ly-0.2.0.6.bmp
Product: LabPlot.ly v0.2.0.6
Company: Foerster.tech
Release Date: Wed, 18 Nov 2020 08:36:54 -0800
Packager: Peter Foerster
Description: LabPlot.ly lets you plot your data to Plot.ly and display them in a browser.
The displayed data is interactive and you can zoom, pan and display values on mouse over.
For large datasets the library can downsample, using the lttb package in python.
Requires Python 3.x to be installed on the computer.
Release Notes: - added support for LabVIEW 2018 onwards
- improved python dependency checker
- added support for other python versions (auto detects highest version)
[VI Package Network] LVOOP Assistant v12.1.0.138
in VI Package Network - New Packages
Posted
Product: LVOOP Assistant v12.1.0.138
Company: LAVA
Release Date: Mon, 04 Jan 2021 12:26:49 -0800
Packager: Jonathon Green <jg@jgcode.net>
Description: This tool integrates into the LabVIEW Project Provider API and contains features to assist with LVOOP development
<b>Instructions:</b>
- Restart LabVIEW after installation
- In a LabVIEW Project, right click on a Class or Class Method VI and select 'LVOOP Assistant >> Plugin'
- If 'VIPM Options >> Mass Compile VIs after Package Installation' is set to FALSE, tool will mass compile on first load for LabVIEW versions after 2012
- See 'Help >> LAVA >> LVOOP Assistant' for more information
- Search 'LVOOP' in NI Example Finder for examples of LVOOP Assistant plugins
<b>Features:</b>
- Clone a Method VI to another Class
- Create a Child Class
- Display and edit all VI icons in a Class
- Open Accessor VIs from a block diagram property node for debugging
- Script Method VIs using templates from a sandbox
- Paste icon text from one Method VI to another
- Refresh a Method VI's icon without having to open the Class Properties Dialog and refresh all icons
- Rename LVOOP Labels
- Add favourite Virtual Folders to a Class with pre-configured scopes
Release Notes: - New (): Added 'Copy Icon' feature
- New (): Added 'Paste Icon Text' feature
- New (): Added 'Library Icon Viewer' feature
- New (): Added 'LVOOP Theme Creator' feature
- New (): Added 'LVOOP Custom User Scripting' feature
- New (): Added 'LVOOP Property Popper' feature
- Changed (): Removed 'Create Element Wrappers' feature
- Changed (): Removed support for Library type
Package Homepage