Almost all the features of the Yoctopuce API are present in the LabVIEW library, this represents more than 2000 possible distinct functions through more than 80 classes. However, there is only one VI per class, so how could we cram an average of 25 calls per VI? This week, we are going to explain to you in more details the concept of proxy objects for the LabVIEW Yoctopuce API.
This week, we continue our "For the beginners" post series. Do you know that you can configure YoctoHubs so that they connect themselves directly to Cloud services? This feature is available on all the YoctoHubs and on the VirtualHub. Here is an overview of the supported Cloud services.
The Yocto-Visualization application which enables you to easily visualize the data coming from Yoctopuce sensors wasn't implemented in a day. It's main development spread over more than two years. This is why the information about it is somewhat scattered around this blog. This week, we decided to gather all the pieces of information into a post. If you have never used Yocto-Visualization before, you can find here everything you need to know. If you have already used it, take the time to browse through this post, you may have missed some interesting details.
This week, we provide you with a short tutorial explaining the basis of the use of Yoctopuce modules into LabVIEW. We limit ourselves to a very simple application: turning on and off a light depending on the ambient light level.
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.
1 2 3 4 5 6 7 8