LabVIEW Wiki - User contributions [en]

GLA Summit 2024/LabVIEW is a game: HiFi Graphics and Web UIs in LabVIEW Apps

2024-03-30T04:01:11Z

NegentropicDev:

'''LabVIEW is a game: HiFi Graphics and Web UIs in LabVIEW Apps''' by Derrick Bommarito

''Continuing my trend of "Why do that in LabVIEW?" I'll be showing off some demos of how I'm aiming to make Summer of LabVIEW challenges more engaging and fun that can also be used to elevate GUIs for LabVIEW applications and the adventurous. See how to integrate web builds from the Godot game engine (and other web exports) with a LabVIEW application. This also opens to door for more tightly integrating web UIs into LabVIEW applications.''

<div style="text-align:center;"><youtube width="800" height="600">NpEaa2P7qZI</youtube></div>

==Presentation Links==
* [https://youtu.be/NpEaa2P7qZI Presentation on YouTube]
{{ambox|text=Replace the placeholder video code with actual YouTube video code after it is available.}}
{{ambox|text=Add links to presentation slides and source code.}}
{{ambox|text=If you need to Upload a file for the LabVIEW Wiki to host it, upload it [[Special:Upload|Here]].}}
{{ambox|text=After uploading to the LabVIEW Wiki, add the line"<code>[[media:<Your Filename>|<Description>]]</code>". The Description is what will show as the link text.}}

==See Also==
{{ambox|text=Add links to other internal LabVIEW Wiki pages about this topic}}

==External Links==
[https://www.vipm.io/package/illuminatedg_lib_ig_godotserver/ IG GodotServer VIPM Package]

[https://github.com/illuminated-g/lv-godot-wrapper GodotServer github repository]

[https://godotengine.org/ Godot Game Engine]

[https://youtube.com/watch?v=5m7nBj98rx4 LegionGames Godot Car Tutorial]

[https://www.youtube.com/@Gdquest GDQuest YouTube channel - Godot Tutorials]

[[Category:GLA Summit 2024]]

GLA Summit 2024/LabVIEW is a game: HiFi Graphics and Web UIs in LabVIEW Apps

2024-03-30T03:42:24Z

NegentropicDev:

GLA Summit 2024/LabVIEW is a game: HiFi Graphics and Web UIs in LabVIEW Apps

2024-03-30T03:42:12Z

NegentropicDev: added links to package/source repo

'''LabVIEW is a game: HiFi Graphics and Web UIs in LabVIEW Apps''' by Derrick Bommarito

''Continuing my trend of "Why do that in LabVIEW?" I'll be showing off some demos of how I'm aiming to make Summer of LabVIEW challenges more engaging and fun that can also be used to elevate GUIs for LabVIEW applications and the adventurous. See how to integrate web builds from the Godot game engine (and other web exports) with a LabVIEW application. This also opens to door for more tightly integrating web UIs into LabVIEW applications.''

<div style="text-align:center;"><youtube width="800" height="600">NpEaa2P7qZI</youtube></div>

==Presentation Links==
* [https://youtu.be/NpEaa2P7qZI Presentation on YouTube]
{{ambox|text=Replace the placeholder video code with actual YouTube video code after it is available.}}
{{ambox|text=Add links to presentation slides and source code.}}
{{ambox|text=If you need to Upload a file for the LabVIEW Wiki to host it, upload it [[Special:Upload|Here]].}}
{{ambox|text=After uploading to the LabVIEW Wiki, add the line"<code>[[media:<Your Filename>|<Description>]]</code>". The Description is what will show as the link text.}}

==See Also==
{{ambox|text=Add links to other internal LabVIEW Wiki pages about this topic}}

==External Links==
[https://www.vipm.io/package/illuminatedg_lib_ig_godotserver/ IG GodotServer VIPM Package]
[https://github.com/illuminated-g/lv-godot-wrapper GodotServer github repository]

[[Category:GLA Summit 2024]]

Building .so on target

2021-05-25T14:13:12Z

NegentropicDev: Added additional dependencies for linx target library building

== Build .so On Target ==
The LabVIEW run-time engine on the target (BBB/RPI) runs inside a chroot, which is a Linux construct that is similar to a virtual machine. This allows the LV run-time to be installed and run safely on many different Linux operating systems. Shared objects must be built to run inside the chroot to be accessible from LabVIEW. The easiest way to ensure the shared object is built correctly is to build it inside the chroot on the target.

1. SSH into the target as a user with root privileges.

2. Run the following command to enter the chroot:
* sudo schroot --run-session -c lv

''Note that all of the following commands until exiting the chroot must be run inside the chroot or they will fail.''
3. Install the build tools:
* opkg update
* opkg install packagegroup-core-buildessential

4. Optionally install git and gdb:
* opkg install git
* opkg install gdb

5. If building updated versions of the Linx target libraries, install the additional development dependencies:
* opkg install --force-depends libc6-dev
* opkg install --force-depends libgcc-s-dev
* opkg install libstdc++-staticdev

6. Build the .so

The actual process of building the .so will vary based on the project/source. There are many good tutorials for building shared objects on Linux available online.

6. Copy the .so to /usr/lib.<br>
Note that this is the /usr/lib directory inside the chroot. Outside of the chroot this directory is /srv/chroot/labview/usr/lib.

7. Call the .so from LabVIEW using the Call Library Function Node<br>
Since /usr/lib is in the LabVIEW search path simply specify the .so name under Library name or path. For example 'myfirstobject.so'.<br>
Under Thread choose Run in any thread to allow the .so to run in any thread rather than just the main thread.<br>

8. Exit the chroot
* exit

=== Debugging ===
The .so will be loaded into memory the first time it is called using the CLFN in LabVIEW. To debug the .so attach to it using GDB before running the a VI.

LabVIEW LINX

2020-12-22T17:45:26Z

NegentropicDev:

[[File:LabVIEW MakerHub.png|frame|LabVIEW MakerHub Logo]]'''LabVIEW LINX''', ''a.k.a. LabVIEW LINX Toolkit'', is an add-on to [[LabVIEW]] that adds the tools for development with [https://www.raspberrypi.org/ Raspberry Pi], [https://www.beagleboard.org/ BeagleBoard] and [https://www.arduino.cc Arduino]. It comes bundled in the installer with [[LabVIEW Community Edition]] but is also available for download for [[LabVIEW 2020]] Basic and Professional versions. The LINX tools allows for deployment of [[G]] directly to a Raspberry Pi or BeagleBoard and has tools facilitate communications with an Arduino ([[G]] does not deploy to an Arduino with the LINX Toolkit).
{{TOCright}}

== Linx Tricks ==
[[chroot SSH trick]]<br>
[[Building .so on target]]

== History ==
{| class="wikitable"
! Version
! Change(s)
|-
|[[File:LV2020.png|frameless|border|64x64px|LabVIEW 2020|link=LabVIEW 2020]]
|'''LABVIEW LINX''' re-introduced and included with [[LabVIEW Community Edition|LabVIEW 2020 Community Edition]]. It is now also available as an additional download for commercial use with [[LabVIEW 2020]].
|-
|[[File:LV2014.png|frameless|border|64x64px|LabVIEW 2014|link=LabVIEW 2014]]
|'''LABVIEW LINX''' was first introduced with [[LabVIEW 2014]] Home Edition.
|}

The old LabVIEW MakerHub website is no longer available.

== See Also ==
* [[LabVIEW Community Edition]]

== External Links ===
* [https://www.raspberrypi.org/ Raspberry Pi]
* [https://www.beagleboard.org/ BeagleBoard]
* [https://www.arduino.cc Arduino]

[[Category:LabVIEW LINX]]
[[Category:Raspberry Pi]]
[[Category:BeagleBoard]]
[[Category:Arduino]]

LabVIEW LINX

2020-12-22T17:45:02Z

NegentropicDev: updated information about now closed down makerhub site.

[[File:LabVIEW MakerHub.png|frame|LabVIEW MakerHub Logo]]'''LabVIEW LINX''', ''a.k.a. LabVIEW LINX Toolkit'', is an add-on to [[LabVIEW]] that adds the tools for development with [https://www.raspberrypi.org/ Raspberry Pi], [https://www.beagleboard.org/ BeagleBoard] and [https://www.arduino.cc Arduino]. It comes bundled in the installer with [[LabVIEW Community Edition]] but is also available for download for [[LabVIEW 2020]] Basic and Professional versions. The LINX tools allows for deployment of [[G]] directly to a Raspberry Pi or BeagleBoard and has tools facilitate communications with an Arduino ([[G]] does not deploy to an Arduino with the LINX Toolkit).
{{TOCright}}

== Linx Tricks ==
[[chroot SSH trick]]<br>
[[Building .so on target]]

== History ==
{| class="wikitable"
! Version
! Change(s)
|-
|[[File:LV2020.png|frameless|border|64x64px|LabVIEW 2020|link=LabVIEW 2020]]
|'''LABVIEW LINX''' re-introduced and included with [[LabVIEW Community Edition|LabVIEW 2020 Community Edition]]. It is now also available as an additional download for commercial use with [[LabVIEW 2020]].
|-
|[[File:LV2014.png|frameless|border|64x64px|LabVIEW 2014|link=LabVIEW 2014]]
|'''LABVIEW LINX''' was first introduced with [[LabVIEW 2014]] Home Edition.
|-
|The old LabVIEW MakerHub website is no longer available.
|}

== See Also ==
* [[LabVIEW Community Edition]]

== External Links ===
* [https://www.raspberrypi.org/ Raspberry Pi]
* [https://www.beagleboard.org/ BeagleBoard]
* [https://www.arduino.cc Arduino]

[[Category:LabVIEW LINX]]
[[Category:Raspberry Pi]]
[[Category:BeagleBoard]]
[[Category:Arduino]]

Building .so on target

2020-07-08T00:16:43Z

NegentropicDev:

== Build .so On Target ==
The LabVIEW run-time engine on the target (BBB/RPI) runs inside a chroot, which is a Linux construct that is similar to a virtual machine. This allows the LV run-time to be installed and run safely on many different Linux operating systems. Shared objects must be built to run inside the chroot to be accessible from LabVIEW. The easiest way to ensure the shared object is built correctly is to build it inside the chroot on the target.

1. SSH into the target as a user with root privileges.

2. Run the following command to enter the chroot:
* sudo schroot --run-session -c lv

''Note that all of the following commands until exiting the chroot must be run inside the chroot or they will fail.''
3. Install the build tools:
* sudo opkg update
* sudo opkg install packagegroup-core-buildessential

4. Optionally install git and gdb:
* sudo opkg install git
* sudo opkg install gdb

5. Build the .so

The actual process of building the .so will vary based on the project/source. There are many good tutorials for building shared objects on Linux available online.

6. Copy the .so to /usr/lib.<br>
Note that this is the /usr/lib directory inside the chroot. Outside of the chroot this directory is /srv/chroot/labview/usr/lib.

7. Call the .so from LabVIEW using the Call Library Function Node<br>
Since /usr/lib is in the LabVIEW search path simply specify the .so name under Library name or path. For example 'myfirstobject.so'.<br>
Under Thread choose Run in any thread to allow the .so to run in any thread rather than just the main thread.<br>

8. Exit the chroot
* exit

=== Debugging ===
The .so will be loaded into memory the first time it is called using the CLFN in LabVIEW. To debug the .so attach to it using GDB before running the a VI.

Building .so on target

2020-07-08T00:16:13Z

NegentropicDev:

== Build .so On Target ==
The LabVIEW run-time engine on the target (BBB/RPI) runs inside a chroot, which is a Linux construct that is similar to a virtual machine. This allows the LV run-time to be installed and run safely on many different Linux operating systems. Shared objects must be built to run inside the chroot to be accessible from LabVIEW. The easiest way to ensure the shared object is built correctly is to build it inside the chroot on the target.

1. SSH into the target as a user with root privileges.

2. Run the following command to enter the chroot:
* sudo schroot --run-session -c lv

''Note that all of the following commands until exiting the chroot must be run inside the chroot or they will fail.''
3. Install the build tools:
* sudo opkg update
* sudo opkg install packagegroup-core-buildessential

4. Optionally install git and gdb:
* sudo opkg install git
* sudo opkg install gdb

5. Build the .so

The actual process of building the .so will vary based on the project/source. There are many good tutorials for building shared objects on Linux available online.
Copy the .so to /usr/lib.
Note that this is the /usr/lib directory inside the chroot. Outside of the chroot this directory is /srv/chroot/labview/usr/lib.

6. Call the .so from LabVIEW using the Call Library Function Node<br>
Since /usr/lib is in the LabVIEW search path simply specify the .so name under Library name or path. For example 'myfirstobject.so'.<br>
Under Thread choose Run in any thread to allow the .so to run in any thread rather than just the main thread.<br>

7. Exit the chroot
* exit

=== Debugging ===
The .so will be loaded into memory the first time it is called using the CLFN in LabVIEW. To debug the .so attach to it using GDB before running the a VI.

Building .so on target

2020-07-08T00:15:30Z

NegentropicDev: Created page with "== Build .so On Target == The LabVIEW run-time engine on the target (BBB/RPI) runs inside a chroot, which is a Linux construct that is similar to a virtual machine. This allow..."

== Build .so On Target ==
The LabVIEW run-time engine on the target (BBB/RPI) runs inside a chroot, which is a Linux construct that is similar to a virtual machine. This allows the LV run-time to be installed and run safely on many different Linux operating systems. Shared objects must be built to run inside the chroot to be accessible from LabVIEW. The easiest way to ensure the shared object is built correctly is to build it inside the chroot on the target.

1. SSH into the target as a user with root privileges.

2. Run the following command to enter the chroot:
* sudo schroot --run-session -c lv

''Note that all of the following commands until exiting the chroot must be run inside the chroot or they will fail.''
3. Install the build tools:
* sudo opkg update
* sudo opkg install packagegroup-core-buildessential

4. Optionally install git and gdb:
* sudo opkg install git
* sudo opkg install gdb

5. Build the .so

The actual process of building the .so will vary based on the project/source. There are many good tutorials for building shared objects on Linux available online.
Copy the .so to /usr/lib.
Note that this is the /usr/lib directory inside the chroot. Outside of the chroot this directory is /srv/chroot/labview/usr/lib.

6. Call the .so from LabVIEW using the Call Library Function Node
Since /usr/lib is in the LabVIEW search path simply specify the .so name under Library name or path. For example 'myfirstobject.so'.
Under Thread choose Run in any thread to allow the .so to run in any thread rather than just the main thread.
Exit the chroot
exit
Debugging
The .so will be loaded into memory the first time it is called using the CLFN in LabVIEW. To debug the .so attach to it using GDB before running the a VI.

Chroot SSH trick

2020-07-08T00:13:34Z

NegentropicDev:

== chroot SSH Trick ==
This technique allows LabVIEW to run commands outside of its chroot on a LINX 3.0 (BBB or RPi2) target. This can be useful for interacting with commands that are unavailable inside the chroot like raspistill.

1. Install an ssh client to your chroot:<br>
* sudo schroot -r -c lv
* opkg update
* opkg install openssh-ssh
* exit

2. Configure pub key authentication so you don't have to type in a password interactively (Hint: This let's you use the ssh client from LabVIEW System Exec VI).
* ssh-keygen -t rsa<br> stick with the defaults when it prompts you, especially when it asks for the passphrase; we want an empty passphrase
* cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys
* sudo mkdir /srv/chroot/labview/root/.ssh
* sudo cp ~/.ssh/id_rsa* /srv/chroot/labview/root/.ssh/.

3. Now log back into the chroot and run the ssh command once so that you can add localhost to the list of known hosts
* sudo schroot -r -c lv
* ssh root@localhost ls
* When prompted to add localhost to the list of known hosts, say yes
* exit

4. At this point you can run commands from within the LV chroot in the system outside the chroot by running a command of the form ssh <root_user>@localhost <command>. For instance, if I wanted to check the version of the Debian operation system on a Raspberry Pi I would run ssh pi@localhost cat /etc/debian_version. These commands can be run in a LabVIEW VI by using the System Exec VI, so now you have a way to execute commands outside of the LV chroot.

Chroot SSH trick

2020-07-08T00:12:26Z

NegentropicDev:

== chroot SSH Trick ==
This technique allows LabVIEW to run commands outside of its chroot on a LINX 3.0 (BBB or RPi2) target. This can be useful for interacting with commands that are unavailable inside the chroot like raspistill.

1. Install an ssh client to your chroot:
sudo schroot -r -c lv
opkg update
opkg install openssh-ssh
exit

2. Configure pub key authentication so you don't have to type in a password interactively (Hint: This let's you use the ssh client from LabVIEW System Exec VI).
ssh-keygen -t rsa
stick with the defaults when it prompts you, especially when it asks for the passphrase; we want an empty passphrase
cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys
sudo mkdir /srv/chroot/labview/root/.ssh
sudo cp ~/.ssh/id_rsa* /srv/chroot/labview/root/.ssh/.

3. Now log back into the chroot and run the ssh command once so that you can add localhost to the list of known hosts
sudo schroot -r -c lv
ssh root@localhost ls
When prompted to add localhost to the list of known hosts, say yes
exit

4. At this point you can run commands from within the LV chroot in the system outside the chroot by running a command of the form ssh <root_user>@localhost <command>. For instance, if I wanted to check the version of the Debian operation system on a Raspberry Pi I would run ssh pi@localhost cat /etc/debian_version. These commands can be run in a LabVIEW VI by using the System Exec VI, so now you have a way to execute commands outside of the LV chroot.

Chroot SSH trick

2020-07-08T00:11:55Z

NegentropicDev: Created page with "== chroot SSH Trick == This technique allows LabVIEW to run commands outside of its chroot on a LINX 3.0 (BBB or RPi2) target. This can be useful for interacting with commands..."

== chroot SSH Trick ==
This technique allows LabVIEW to run commands outside of its chroot on a LINX 3.0 (BBB or RPi2) target. This can be useful for interacting with commands that are unavailable inside the chroot like raspistill.

# Install an ssh client to your chroot:
sudo schroot -r -c lv
opkg update
opkg install openssh-ssh
exit

# Configure pub key authentication so you don't have to type in a password interactively (Hint: This let's you use the ssh client from LabVIEW System Exec VI).
ssh-keygen -t rsa
stick with the defaults when it prompts you, especially when it asks for the passphrase; we want an empty passphrase
cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys
sudo mkdir /srv/chroot/labview/root/.ssh
sudo cp ~/.ssh/id_rsa* /srv/chroot/labview/root/.ssh/.

# Now log back into the chroot and run the ssh command once so that you can add localhost to the list of known hosts
sudo schroot -r -c lv
ssh root@localhost ls
When prompted to add localhost to the list of known hosts, say yes
exit

#At this point you can run commands from within the LV chroot in the system outside the chroot by running a command of the form ssh <root_user>@localhost <command>. For instance, if I wanted to check the version of the Debian operation system on a Raspberry Pi I would run ssh pi@localhost cat /etc/debian_version. These commands can be run in a LabVIEW VI by using the System Exec VI, so now you have a way to execute commands outside of the LV chroot.

LabVIEW LINX

2020-07-08T00:10:39Z

NegentropicDev: /* Linx Tricks */

[[File:LabVIEW MakerHub.png|frame|LabVIEW MakerHub Logo]]'''LabVIEW LINX''', ''a.k.a. LabVIEW LINX Toolkit'', is an add-on to [[LabVIEW]] that adds the tools for development with [https://www.raspberrypi.org/ Raspberry Pi], [https://www.beagleboard.org/ BeagleBoard] and [https://www.arduino.cc Arduino]. It comes bundled in the installer with [[LabVIEW Community Edition]] but is also available for download for [[LabVIEW 2020]] Basic and Professional versions. The LINX tools allows for deployment of [[G]] directly to a Raspberry Pi or BeagleBoard and has tools facilitate communications with an Arduino ([[G]] does not deploy to an Arduino with the LINX Toolkit).
{{TOCright}}

== Linx Tricks ==
[[chroot SSH trick]]<br>
[[Building .so on target]]

== History ==
{| class="wikitable"
! Version
! Change(s)
|-
|[[File:LV2020.png|frameless|border|64x64px|LabVIEW 2020|link=LabVIEW 2020]]
|'''LABVIEW LINX''' and [https://www.labviewmakerhub.com/doku.php?id=libraries:linx:start LabVIEW MakerHub] re-introduced with [[LabVIEW Community Edition|LabVIEW 2020 Community Edition]]. It is now also available and additional download for commercial use with [[LabVIEW 2020]].
|-
|[[File:LV2014.png|frameless|border|64x64px|LabVIEW 2014|link=LabVIEW 2014]]
|'''LABVIEW LINX''' and [https://www.labviewmakerhub.com/doku.php?id=libraries:linx:start LabVIEW MakerHub] was first introduced with [[LabVIEW 2014]] Home Edition.
|}

== See Also ==
* [[LabVIEW Community Edition]]

== External Links ==
* [https://www.labviewmakerhub.com/doku.php?id=libraries:linx:start LabVIEW MakerHub - LabVIEW LINX Start]
* [https://www.raspberrypi.org/ Raspberry Pi]
* [https://www.beagleboard.org/ BeagleBoard]
* [https://www.arduino.cc Arduino]

[[Category:LabVIEW LINX]]
[[Category:Raspberry Pi]]
[[Category:BeagleBoard]]
[[Category:Arduino]]

LabVIEW LINX

2020-07-08T00:10:26Z

NegentropicDev: Adding links to start pulling info from Makerhub page

[[File:LabVIEW MakerHub.png|frame|LabVIEW MakerHub Logo]]'''LabVIEW LINX''', ''a.k.a. LabVIEW LINX Toolkit'', is an add-on to [[LabVIEW]] that adds the tools for development with [https://www.raspberrypi.org/ Raspberry Pi], [https://www.beagleboard.org/ BeagleBoard] and [https://www.arduino.cc Arduino]. It comes bundled in the installer with [[LabVIEW Community Edition]] but is also available for download for [[LabVIEW 2020]] Basic and Professional versions. The LINX tools allows for deployment of [[G]] directly to a Raspberry Pi or BeagleBoard and has tools facilitate communications with an Arduino ([[G]] does not deploy to an Arduino with the LINX Toolkit).
{{TOCright}}

== Linx Tricks ==
[[chroot SSH trick]]
[[Building .so on target]]
== History ==
{| class="wikitable"
! Version
! Change(s)
|-
|[[File:LV2020.png|frameless|border|64x64px|LabVIEW 2020|link=LabVIEW 2020]]
|'''LABVIEW LINX''' and [https://www.labviewmakerhub.com/doku.php?id=libraries:linx:start LabVIEW MakerHub] re-introduced with [[LabVIEW Community Edition|LabVIEW 2020 Community Edition]]. It is now also available and additional download for commercial use with [[LabVIEW 2020]].
|-
|[[File:LV2014.png|frameless|border|64x64px|LabVIEW 2014|link=LabVIEW 2014]]
|'''LABVIEW LINX''' and [https://www.labviewmakerhub.com/doku.php?id=libraries:linx:start LabVIEW MakerHub] was first introduced with [[LabVIEW 2014]] Home Edition.
|}

== See Also ==
* [[LabVIEW Community Edition]]

== External Links ==
* [https://www.labviewmakerhub.com/doku.php?id=libraries:linx:start LabVIEW MakerHub - LabVIEW LINX Start]
* [https://www.raspberrypi.org/ Raspberry Pi]
* [https://www.beagleboard.org/ BeagleBoard]
* [https://www.arduino.cc Arduino]

[[Category:LabVIEW LINX]]
[[Category:Raspberry Pi]]
[[Category:BeagleBoard]]
[[Category:Arduino]]

Linx Toolkit Hardware Compatibility List

2020-07-02T13:43:01Z

NegentropicDev: adding link to Rock Pi S work

This is a list of tested hardware that works with the [[LINX]] Toolkit that ships with the [[LabVIEW Community Edition]].

== Raspberry Pi ==
* Raspberry Pi4 Model B
** '''SoC''': Broadcom BCM2711B0 quad-core A72 (ARMv8-A) 64-bit @ 1.5GHz
* Raspberry Pi3 Model B+
** '''Soc''': Broadcom BCM2837B0, Cortex-A53 (ARMv8) 64-bit SoC @ 1.4GHz
* Raspberry Pi3 Model B v1.2
** Quad Core 1.2GHz Broadcom BCM2837 64bit CPU

== Beaglebone Black ==
* Processor: AM335x 1GHz ARM® Cortex-A8

== Successful manual installation of runtime (no direct Linx support yet) ==
[https://forums.ni.com/t5/LINX/Successfully-running-LabVIEW-on-a-RockPi-S-512MB/m-p/4064100 NI Forum post with instructions for arm64 Debian OS]
* Rock Pi S: Rockchip RK3308 Quad-core ARM Cortex-A35 (ARMv8-A) @ 1.3GHz

== External links ==
* [https://www.raspberrypi.org/ Raspberry Pi]
* [https://www.beagleboard.org/ BeagleBoard]
* [https://www.arduino.cc/ Arduino]

LabVIEW Community Edition

2020-06-25T23:12:13Z

NegentropicDev: Clarify availability of Linx toolkit

[[File:LVComEd Logo Horiz Color RGB.png|700px|center|link=https://www.ni.com/en-us/shop/labview/select-edition/labview-community-edition.html]]

{{TOCright}}
'''LabVIEW Community Edition''' is a free (unpaid) edition of [[LabVIEW]] and [[LabVIEW NXG]] that may only be used for personal, non-commercial, non-industrial and non-academic purposes.<ref name="lvce-usage"/> It provides all of the capabilities of the professional editions of LabVIEW and LabVIEW NXG. LabVIEW comes bundled with the [https://www.labviewmakerhub.com/doku.php?id=libraries:linx:start LINX toolkit] for use with [https://www.raspberrypi.org/ Raspberry Pi], [https://www.beagleboard.org/ BeagleBoard] and [https://www.arduino.cc Arduino] among other popular microcontroller development boards.<ref name="lvce-home"/> LabVIEW Community Edition is for the hobbyist wishing to use graphical programming for their projects.

==Download==
LabVIEW Community Edition is available for download on the
'''[https://www.ni.com/en-us/shop/labview/select-edition/labview-community-edition.html LabVIEW Community Edition]''' page.

==Learn==
===Announcement video with Darren Nattinger===
<youtube>FTW525ZG3po</youtube>
===Post from LabVIEW Champion Joerg Hampel===
Visit Joerg Hampel's '''[https://forums.ni.com/t5/NI-Blog/LabVIEW-Community-Edition/ba-p/3970512?profile.language=en blog post]''' to learn about LabVIEW Community edition. Joerg answers questions like:

*What exactly is this new edition?
*Is it free?
*Who is it for?
*What about hobbyist hardware?
===LabVIEW Community Edition Sneak Peek (VI Shots)===
''Note'': Audio is delayed in this video.<br>
<youtube>4HLVqYXpxIo</youtube>

==Getting Started==
{| class="wikitable sortable"
|-
! About The Example !! Download Link !! Author
|-
| This example demonstrates how to use LabVIEW Community Edition in conjunction with BeagleBone, SystemLink Cloud, and a web front to monitor the open/close state of doors and windows in a house. || '''[https://ekerry.wordpress.com/2019/11/26/getting-started-with-labview-community-edition-and-beaglebone-or-raspberry-pi/ Getting Started with LabVIEW Community Edition And Beaglebone Or Raspberry Pi]''' || Elijah Kerry
|-
| This example introduces you to the basic syntax of the LabVIEW Graphical language by implementing an alarm clock state machine. The example is broken down into lessons that build on each other and introduce digestible concepts one phase at a time. || '''[https://bit.ly/ChrisCilino_LabVIEWCommunityAndRP LabVIEW Community and a Slice Of Raspberry Pi]''' || [[Chris Cilino (LabVIEW Champion)|Chris Cilino]]
|-
| A manual for a programming language called "LabVIEW". This is written for people over junior high school who are interested in programming and electronic work. || '''[http://www.quatsys.com/labview/1109/lvproraku.en.html Enjoy Programming with LabVIEW Community Edition]''' || Japan LabVIEW Users Group
|-
| For NI Days 2019 I was asked to give a demo of something fun/interesting using a Raspberry Pi and the LINX Toolkit. I was originally thinking of demoing some simple sensors but then I remembered an idea I had a few years ago for a 3D printed two-wheeled robot (I nicknamed it the PuckBot) for STEM/educational use. || '''[https://www.mediamongrels.com/democracybot-rpi-linx-websockets-nxg-webvis/ DemocracyBot – Raspberry Pi, LINX Toolkit, WebSockets & NXG WebVIs]''' || [https://www.mediamongrels.com/ Media Mongrels]
|-
| Also check out the resources at the [[Getting Started]] LabVIEW Wiki page. || '''[[Getting Started]]''' ||

|}

==Find Code==
Use '''[https://www.GCentral.org GCentral.org]''' to find LabVIEW packages.

==Ask Questions==
Ask your friendly, neighborhood LabVIEW Experts at:
* [https://lavag.org/forum/58-labview-community-edition/ LabVIEW Community Edition board on LAVA]
* NI's Forums. There is a board for [https://forums.ni.com/t5/forums/filteredbylabelpage/board-id/170/label-name/labview LabVIEW] and [https://forums.ni.com/t5/forums/filteredbylabelpage/board-id/170/label-name/labview%20nxg LabVIEW NXG].

==See Also==
* [[LabVIEW LINX]]
* [[Linx Toolkit Hardware Compatibility List]] - List of open-source hardware supported by LabVIEW Community Edition and the LINX toolkit.

==References==
<references>
<ref name="lvce-usage">[https://www.ni.com/en-us/support/documentation/supplemental/20/labview-community-edition-usage-details.html LabVIEW Community Edition Usage Details]</ref>
<ref name="lvce-home">[https://www.ni.com/en-us/shop/labview/select-edition/labview-community-edition.html LabVIEW Community Edition]</ref>
</references>

[[Category:LabVIEW Community Edition]]
[[Category:Videos]]