Hear, hear! After all these years, the LabVIEW library is here at long last! Until now, LabVIEW users who wanted to use Yoctopuce modules had to settle for a handcrafted workaround that we designed a few years ago. But this time we're not joking anymore, we offer a true library for LabVIEW which enables you to exploit the whole potential of Yoctopuce modules.
This week, we are going to clarify the use of two methods of our API: YAPI.RegisterHub() and YAPI.PreregisterHub(). These two functions enable you to adapt the library behavior to your needs, more particularly managing network disconnection when you use a YoctoHub or a VirtualHub.
The Yocto-SPI documentation contains an example to interface the AlphaSense OPC-N2 particle counter. Since then, Alphasense has released a new model, the OPC-N3, and the commands to query it are slightly different. This week, by popular request, we explain who to make the OPC-N3 work with a Yocto-SPI and we take this opportunity to introduce a small innovation.
A few weeks ago, we listed the Yoctopuce libraries supporting Linux ARM64, but C# was not part of the list because .NET Core 2.0 doesn't support this architecture. We nevertheless added ARM64 support to our C# library because it is possible to use a preview version on the next version of .NET Core which will support this platform.
We recently noticed that, when drawing on a raster display is involved, not everybody thinks about "double buffering" as the go to technique. That's why, this week, we are proposing a short article explaining how this technique works and why it is so easy to use it with Yoctopuce displays.
1 2 3 4 5 6 ... 10 ... 20 ... 23