We usually consider IP connection as a means to access Internet, but in fact it's quite possible to build networks which do not have outside connectivity. It's called non routable networks. They are useful, but they also introduce some difficulties. This week, we explain how to use Yoctopuce modules in a non routable network.
For already some time, we offer a software solution to connect remotely to your Yoctopuce hubs, even when they are behind a NAT filter: the GatewayHub. However that solution requires to setup an Internet-facing Web hosting with Node.js. Today we will show another different solution, which is not applicable to GSM hubs but can save the effort of setting up a public hosting. Its name is ngrok.
Yoctopuce serial communication modules are more than simple interfaces: they are able to query and analyze autonomously the data coming from any device to then present the results in the way of a Yoctopuce sensor and/or record them in the embedded data logger. But in order to do so, you must tell the Yoctopuce module how to manage the dialog with the device. So here are a few examples as a complement to the documentation, to make this task easier.
A few weeks ago, we announced the Linux version of Yocto-Visualization V2, and in that post we explained how to install and run the application. But we realized that our installation process was tedious. Therefore, we revised our process and we now offer you an easier solution.
This week, we are implementing a program suggested by one of our customers: Using the Windows API to adapt the brightness of a monitor depending on the ambient light. Most laptops already do that, but desktops don't because they don't have a light sensor. We are going to use a Yocto-Light-V3 to determine the ambient light.
1 2 3 4 5