Add Read Device Identification support (function code 0x2B)#214
Merged
rquackenbush merged 1 commit intoApr 16, 2026
Merged
Conversation
Implement Modbus Read Device Identification (MEI type 0x0E) per Modbus Application Protocol V1.1b3, section 6.21. New API: - IModbusMaster.ReadDeviceIdentification(slaveAddress, category, objectId) - IModbusMaster.ReadBasicDeviceIdentification(slaveAddress) - Async variants of both methods Supports all four device ID categories (Basic, Regular, Extended, Individual) and parses variable-length object responses including vendor name, product code, and revision information. Includes EnhancedModbusRtuTransport for handling variable-length Device ID responses that cannot be determined from the response header. Use ModbusFactoryExtensions.CreateRtuMasterWithDeviceId() to create a master with Device ID support. New files: - Message/ReadDeviceIdRequest.cs - Message/ReadDeviceIdResponse.cs - Data/DeviceIdCategory.cs - Data/DeviceIdentificationHelper.cs - Device/MessageHandlers/ReadDeviceIdentificationService.cs - IO/EnhancedModbusRtuTransport.cs - ModbusFactoryExtensions.cs
rquackenbush
approved these changes
Apr 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implement Modbus Read Device Identification (MEI type 0x0E) per Modbus Application Protocol V1.1b3, section 6.21.
New API:
Supports all four device ID categories (Basic, Regular, Extended, Individual) and parses variable-length object responses including vendor name, product code, and revision information.
Includes EnhancedModbusRtuTransport for handling variable-length Device ID responses that cannot be determined from the response header. Use ModbusFactoryExtensions.CreateRtuMasterWithDeviceId() to create a master with Device ID support.
New files: