Libmodbus – A modbus library for Linux, Mac OS, FreeBSD and windows
Not sure what the intended use is, but traditional modbus is generally regarded as insecure. It&#x27;s difficult to implement and meet requirements for cyber security required by functional safety, as one case example.<p>Here are just a couple of many possible references:<p><a href="https:&#x2F;&#x2F;www.incibe-cert.es&#x2F;en&#x2F;blog&#x2F;deconstructing-modbus" rel="nofollow">https:&#x2F;&#x2F;www.incibe-cert.es&#x2F;en&#x2F;blog&#x2F;deconstructing-modbus</a><p><a href="https:&#x2F;&#x2F;www.researchgate.net&#x2F;publication&#x2F;290732323_MODBUS_protocol_fuzzing_for_cyber-security_evaluation_of_industrial_control_systems" rel="nofollow">https:&#x2F;&#x2F;www.researchgate.net&#x2F;publication&#x2F;290732323_MODBUS_pr...</a><p>Additionally, managing address based protocols like modbus, esp where they span a battery limit or responsibility boundary can be far, far more expensive in engineering alignment efforts than most people realise. Once you go tag based, your never willingly go back to address based.<p>These days the use OPC is often preferred, having the ability to be both secure and encrypted, as well as all the advantages of being a tag based protocol.<p>NB: In my younger days I implemented many, many modbus links, over RS-232&#x2F;485 and TCP and it really filled many practical needs, not least of which being a default industry standard that vastly increased you chances of communication between devices made by differing vendors.<p>But these days, the focus on cyber security has really started to curb enthusiasm for modbus, but there is a drive to a newer version with security addressed. I would think the complexity added means, just go with OPC where possible.