From bb28a86b1a80ba5f4a2612e990daa680a7fe9438 Mon Sep 17 00:00:00 2001 From: Obe Van Lierde Date: Tue, 5 Dec 2023 21:06:37 +0100 Subject: [PATCH] Update modbus_tcp.md --- docs/modbus_tcp.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/docs/modbus_tcp.md b/docs/modbus_tcp.md index 04d440e..d7f27df 100644 --- a/docs/modbus_tcp.md +++ b/docs/modbus_tcp.md @@ -5,6 +5,7 @@ This is the documentation of the Modbus-TCP task - [Table of contents](#table-of-contents) - [Initialization](#initialization) - [Usage](#usage) +- [Guide](#Guide) ## Initialization The Modbus task is initialized in the main function. @@ -14,4 +15,17 @@ modbus_init(); ``` ## Usage -![QmodMaster.exe](./img/QmodMaster.jpg) \ No newline at end of file +![QmodMaster.exe](./img/QmodMaster.jpg) + +## Guide + +- Set qmodmaster to tcp mode +- Set IP of device +- Set the device in multiple register mode +- Connect with the board +- Fill in the data as in the example +- Send the data + +## Extra + +The start addres is ignored and the timeout warnings arne normal because there is no response from my code back to QModMaster. \ No newline at end of file