Allow for 'dynamic' Modbus sensor config
complete
k
keaton@vipindoorstorage.com
We have/will end up using a variety of Modbus sensors with our devices. I'd love to be able to write a single firmware to handle emission/processing of sensor data. The way I see this working is we can define multiple devices in Modbus configuration (with unique IDs and whatnot) and we have a block that is fired whenever any Modbus data is sent back which has the params of the data and the device ID
Jimmy Hu
marked this post as
complete
Jimmy Hu
marked this post as
open
k
keaton@vipindoorstorage.com
Jimmy Hu okay, I've been using the new blocks and I found a bug. Data is not set to anything useful (just zero). Additionally, its difficult to process the data since inside of
callback_modbus_slave_reply
the device ID is the static device ID for the pre-set device in Modbus Master instead of the 'dynamic' ID I have setJimmy Hu
marked this post as
closed
Jimmy Hu
We have a few new blocks that enable receiving modbus responses from blocks. They are currently listed in the "I/O" section of the blocks library. There is also an project that shows an example usage of these blocks here https://appblocks.io/examples/modbusscan.
k
keaton@vipindoorstorage.com
Jimmy Hu: thank you! How new is this? I swear it wasn’t there when I put in the ticket haha. Exactly what I was wanting, thank you!