Two weeks ago, we presented an improvement of the Yoctopuce API enabling you to easily observe what happens on a serial line with a callback. Obviously, we hurried to integrate this in our ModbusTool application, which is now able to display the data that go through a Modbus line.
One of the specificities of Yoctopuce serial interfaces is their capacity to listen to messages circulating on an existing line in both directions to reconstruct the communications. Most of the time, it's used to understand how an undocumented protocol works, but you can also use this function in production to monitor and measure an existing system. That's why we have recently added a new API making it easy to integrate serial snooping into your projects.
When you design an automation solution intended to last, you must think about integrating tools which you will need one day to detect failure signs or aging signs. In some cases, this goes through managing error messages or exceptions. But on top of this, there can be diagnostic information transmitted by the modules: log messages. We are going to show you here how to integrate them into your projects.
A customer pointed out to us that the Yoctopuce API doesn't allow for the Yocto-I2C to scan an I2C bus to detect the devices connected to it. It turns out that this is not quite accurate...
Microsoft recently released version 6 of the .Net framework (formerly known as .Net Core). This version is supposed to be compatible with older versions of the framework, but in reality it isn't. We therefore had to fix some small problems in our library, in particular in the NuGet package.
1 2 3 4 5 6 ... 10 ... 20 ... 30 31