For several years, we have been offering different YoctoHubs to connect Yoctopuce sensors directly to the network, without using a computer. But as you may have noticed, on this product range, we don't throw ourselves headlong into cutting-edge technologies, especially when standards are split: LoRa, Sigfox, LTE-M, NB-IoT, 5G... With the multiplication of networks aimed at the IoT, we had to wait for the landscape to become clearer, because we couldn't do it all and we had to choose the solution which would best suit our customers. But there it is, we finally made our choice, and it's almost ready.
For one of our experiments, we needed a laboratory power supply, that we could easily move around and that we could drive remotely through a wired network connection. At Yoctopuce, hardware-wise, we tend to bet on the best known manufacturers, but this time we decided to give the RD6006 a chance...
Customers regularly ask us if YoctoHubs support the Modbus TCP protocol. The answer is negative, because the CPU of the YoctoHubs is too small to add the code of the Modbus TCP server in it. The solution that we recommend is to write a small Modbus TCP server in Python with the pymodbus library and to use our library to communicate with the Yoctopuce modules. This is exactly what we did this week.
While we were making improvements to the Yocto-PWM-Rx for our previous post, we noticed that this device has considerably changed since its conception in order to cover more use cases than the once planned initially. To help you navigate into all these possibilities, we summarize in this post the different working modes.
A customer recently contacted Yoctopuce support to ask why his DIY tachometer didn't work with a Yocto-PWM-Rx. We looked into it and, to our surprise, we discovered that generating a clean PWM signal with a magnet and a reed switch was not as easy as one could think.
1 ... 10 ... 20 ... 28 29 30 31 32 33 34 35 36 37 38 ... 40 ... 50 ... 60 ... 70 ... 80 ... 90 ... 100 ... 110 ... 120 ... 127