-
Notifications
You must be signed in to change notification settings - Fork 137
2.1 Modbus.Net Architecture
luosheng edited this page Jun 7, 2023
·
1 revision
Modbus.Net is based on OSI model, so it has a familiar architecture.
Physical Layer represent phycic electronical level. This layer is not implemented in Modbus.Net.
Link Layer in OSI corresponds to Controller in Modbus.Net
Network Layer in OSI corresponds to Connector in Modbus.Net.
Transport Layer in OSI corresponds to Protocol in Modbus.Net.
Session Layer in OSI corresponds to ProtocalLinker in Modbus.Net.
Tranport Layer in OSI corresponds to Utility(Low level API) in Modbus.Net.
Application Layer in OSI corresponds to Machine(High level API) and MachineJob(Scheduler tool) in Modbus.Net.
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