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.
We regularly receive questions on how to obtain high frequency measures with the Yocto-3D and the Yocto-3D-V2. We already discussed the principle in a previous post, but to make your life easier, we prepared a concrete example.
Here in Switzerland, the population is currently not formally confined, but all the schools and all the non-essentials shops are closed, meetings of more than 5 people are forbidden. Borders are closed as well, unless you have a truly valid reason to cross them, and the population is strongly encouraged to stay at home. If you read this post, you are either bored senseless at home, or you wonder how Yoctopuce is handling this unprecedented crisis.
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.
InfluxDB is a database specifically designed to store time series of measures. You already could add measures from Yoctopuce sensors in an InfluxDB 1.0 database with YoctoHubs or with the VirtualHub. But the recently available new version of InfluxDB uses a new API which isn't compatible. We decided to add support for this new version in the firmware of YoctoHubs and of the VirtualHub. Here is how to insert the measures of Yoctopuce sensors into InfluxDB 2.0 directly from a YoctoHub.
1 ... 10 11 12 13 14 15 16 17 18 19 20 21 ... 30 ... 40 ... 50 ... 60 ... 70 ... 80 ... 90 ... 100 ... 106