The Yoctopuce API has several distinct mechanisms to optimize access to the sensors, through USB as well as through the network. In a previous post, we talked about the polling and callback methods and compared their respective advantages. Today, we offer a new intermediary method, enabling you to optimize access to some sensor attributes, when you can't do it with a callback.
Node-RED is a visual programming language that can be used to connect various Web services, API or peripherals together. Node-RED can use data coming from a Web server, a MQTT broker, a mail server or even Twitter, but not from Yoctopuce sensors. That is, until yesterday...
From time to time, a customer contacts Yoctopuce support to complain about significant instabilities on measures performed with a Yocto-Thermocouple. Each time, the conclusion is the same: the instabilities are the result of an unwanted ground loop. The Yocto-Thermocouple is not an electrically isolated module: there is no electric separation between the measuring part and the USB part. This has consequences that you must clearly understand. This is what we are going to explain this week.
If you have been following this blog for a while, you might remember our 2014 Advent window, for which we created an animated landscape in shadow play. This year, we created a new animated Advent window, but based on a different principle: a drawing with UV on a phosphorescent surface, with the help of an embryonic robotic plotter.
Last year, Microsoft announced the Azure IoT Suite. Behind this somewhat pompous name hides two examples of use of their Azure cloud with connected objects. We are going to see how to use Yoctopuce modules in one of these two examples.
1 ... 10 ... 20 ... 30 ... 39 40 41 42 43 44 45 46 47 48 49 50 ... 60 ... 70 ... 80 ... 90 ... 100