What is a Vendor Extension RFC?
In the market today there is a wide variety of creative thinking being labeled as Modbus. Some of these create no market/user confusion, but most DO create problems. Much to the dismay of buyers/users, often 2 or more vendors create similar but incompatible creativity. So ‘Vendor Extension’ RFC are designed to be easier to pass. They will NOT be included in conformance tests – however be warned that most Vendor Extension RFC will include the clause that the vendor extension is an option and must NOT be enabled by default. In other words, Modbus products with vendor extensions MUST BY DEFAULT BE 100% compatible with Modbus products that do not implement the vendor extensions. This will likely require many vendors to modify their products in order to claim full Modbus compliance. return to top Packing of IEC data types in Holding Registers (Core RFC) By now everyone should know that the recommended way to move 32-bit long integers and floating points is to pack them into two consecutive
Related Questions
- Once my document has been sent to the IESG for review, or approved by the IESG for publication, how do I know the RFC Editor has it in their queue?
- What is the relationship between the Internet RFC 3066 (and its predecessor RFC 1766) and the ISO 639 standards?
- What style guide does the RFC Editor use?
