Another bad discovery when using #LabVIEW on #rasperrypi: the webserver shipped with the image is not up-to-date(...), therefore you cannot use #SystemLink(Skyline) tags and messages.This is just not supported.

So we need to fallback to HTTP requests and websockets. Not that bad, but again not documented anywhere. So, you can program your stuff on rPI side without error with tags ; you can create your webpage with tags without problem ; but when you run the 2 together it never connects...

Trying to use the #LabVIEW Python nodes on Raspberry Pi 4. But with low success.
It just crashes the LV runtime...
Should Python be installed into the chroot jail ? Or can it be targetted by #LabVIEW on the main OS ?

Trying to get the best out of a #raspberrypi SPI port controlled with #LabVIEW.
The idea is to get the SCLK close to 1MHz. And be able to minimize the gaps between emissions (/CS time really close to the emission time).
I guess we'll need to rewrite the driver using #Rust if we want a high throughput...

Listening at some #GDevCon and #GLASummit sessions about open-source, one main comment is that #LabVIEW is not enough 'maker' (DIY) oriented.
Having a #homeassistant based installation at home, I know that many domotic devices can be controlled by third-party programs.
What if we start a group to bring domotic devices into the #LabVIEW ecosystem?

To start, it can be simple wrapping around existing Python code from domotic platforms maybe ? What do you think?