-
Notifications
You must be signed in to change notification settings - Fork 139
4 Using Modbus.Net
parallelbgls edited this page Jun 29, 2017
·
2 revisions
Modbus.Net unified all interfaces for different types of devices as for users(user developer).
That means users can use different device in a same architechture, especially in TaskManager.
This blueprint turns Modbus.Net from pure Modbus library to open architechture hardware communication library.
Modbus.Net has two different API levels: BaseUtility and BaseMachine, and task schedule tool TaskManager. Users can use these three methods for their targets.
Modbus.Net Hangzhou Delian Science Technology Co.,Ltd. © 2023
-
2 Specification of Modbus.Net main framework
- 2.1 Modbus.Net Architecture
- 2.2 Transmission Control Layer Controller
- 2.3 Transmission Link Layer Connector
- 2.4 Concrete Protocol Layer ProtocolLinker
- 2.5 Abstract Protocol Layer Protocol
- 2.6 Protocol Presentation Layer Utility
- 2.7 Device Application Layer Machine
- 2.8 Task Application Layer MachineJob
-
3 Using Modbus.Net to implement a protocol
- 3.1 Global Tools
- 3.2 Extends Protocol and ProtocolUnit according to protocol specification
- 3.3 Extends Connector to create a link method
- 3.4 Extends Machine and Utility, creating two apis
- 3.5 Extends API methods to Machine and Utility
- 3.6 Extends Formater, Translator and Combiner, Creating Encoding,Decoding,Combining methods for address
- 3.7 Extends Controller, to control message