Update documentation links

Author: dhoomakethu

README.md

@@ -35,21 +35,44 @@ For .e.g
 #### Run Server
 ```
 (pymodbus3.8)
-pymodbus/repl/server on  repl-server-startup [!?] via 🐍 v3.8.13 (pymodbus3.8)
 ❯ python3 main.py --host 0.0.0.0 --verbose run --modbus-config default_config.json --modbus-server tcp --modbus-framer socket --modbus-port 5020 --unit-id 1 --unit-id 2 -u 4 -r 1 --timeout 2
-2024-02-17 13:27:17,218 INFO  logging:97 Modbus server started
-2024-02-17 13:27:17,219 DEBUG logging:103 Awaiting connections server_listener
-2024-02-17 13:27:17,219 INFO  logging:97 Server listening.
+2024-02-28 14:38:24,952 INFO  logging:97 Modbus server started
+2024-02-28 14:38:24,952 DEBUG logging:103 Awaiting connections server_listener
+2024-02-28 14:38:24,952 INFO  logging:97 Server listening.
 
 __________                          .______.                    _________
 \______   \___.__. _____   ____   __| _/\_ |__  __ __  ______  /   _____/ ______________  __ ___________
  |     ___<   |  |/     \ /  _ \ / __ |  | __ \|  |  \/  ___/  \_____  \_/ __ \_  __ \  \/ // __ \_  __ \\
  |    |    \___  |  Y Y  (  <_> ) /_/ |  | \_\ \  |  /\___ \   /        \  ___/|  | \/\   /\  ___/|  | \/
  |____|    / ____|__|_|  /\____/\____ |  |___  /____//____  > /_______  /\___  >__|    \_/  \___  >__|
            \/          \/            \/      \/           \/          \/     \/                 \/
+                                                                                                v2.0.2-Pymodbus3.7.0dev
+
+
+SERVER > 2024-02-28 14:39:15,352 DEBUG logging:103 Connected to server
+2024-02-28 14:39:15,352 DEBUG logging:103 recv: 0x0 0x1 0x0 0x0 0x0 0x6 0x1 0x4 0x0 0x1 0x0 0x1 old_data:  addr=None
+2024-02-28 14:39:15,352 DEBUG logging:103 Handling data: 0x0 0x1 0x0 0x0 0x0 0x6 0x1 0x4 0x0 0x1 0x0 0x1
+2024-02-28 14:39:15,352 DEBUG logging:103 Processing: 0x0 0x1 0x0 0x0 0x0 0x6 0x1 0x4 0x0 0x1 0x0 0x1
+2024-02-28 14:39:15,352 DEBUG logging:103 Factory Request[ReadInputRegistersRequest': 4]
+2024-02-28 14:39:15,352 DEBUG logging:103 validate: fc-[4] address-1: count-1
+2024-02-28 14:39:15,352 DEBUG logging:103 getValues: fc-[4] address-1: count-1
+2024-02-28 14:39:15,352 DEBUG logging:103 send: 0x0 0x1 0x0 0x0 0x0 0x5 0x1 0x4 0x2 0xc5 0x7c
+2024-02-28 14:39:37,029 DEBUG logging:103 recv: 0x0 0x2 0x0 0x0 0x0 0x6 0x4 0x4 0x0 0x1 0x0 0x1 old_data:  addr=None
+2024-02-28 14:39:37,029 DEBUG logging:103 Handling data: 0x0 0x2 0x0 0x0 0x0 0x6 0x4 0x4 0x0 0x1 0x0 0x1
+2024-02-28 14:39:37,029 DEBUG logging:103 Processing: 0x0 0x2 0x0 0x0 0x0 0x6 0x4 0x4 0x0 0x1 0x0 0x1
+2024-02-28 14:39:37,029 DEBUG logging:103 Factory Request[ReadInputRegistersRequest': 4]
+2024-02-28 14:39:37,029 DEBUG logging:103 validate: fc-[4] address-1: count-1
+2024-02-28 14:39:37,029 DEBUG logging:103 getValues: fc-[4] address-1: count-1
+2024-02-28 14:39:37,029 DEBUG logging:103 send: 0x0 0x2 0x0 0x0 0x0 0x5 0x4 0x4 0x2 0xc7 0xbe
+2024-02-28 14:39:41,010 DEBUG logging:103 recv: 0x0 0x3 0x0 0x0 0x0 0x6 0x5 0x4 0x0 0x1 0x0 0x1 old_data:  addr=None
+2024-02-28 14:39:41,010 DEBUG logging:103 Handling data: 0x0 0x3 0x0 0x0 0x0 0x6 0x5 0x4 0x0 0x1 0x0 0x1
+2024-02-28 14:39:41,010 DEBUG logging:103 Processing: 0x0 0x3 0x0 0x0 0x0 0x6 0x5 0x4 0x0 0x1 0x0 0x1
+2024-02-28 14:39:41,010 DEBUG logging:103 Not a valid slave id - 5, ignoring!!
+2024-02-28 14:39:41,010 DEBUG logging:103 Resetting frame - Current Frame in buffer - 0x0 0x3 0x0 0x0 0x0 0x6 0x5 0x4 0x0 0x1 0x0 0x1
+2024-02-28 14:39:44,015 DEBUG logging:103 -> transport: received eof
+2024-02-28 14:39:44,015 DEBUG logging:103 Connection lost server due to None
+2024-02-28 14:39:44,015 DEBUG logging:103 Handler for stream [server] has been canceled
 
-
-SERVER >
 ```
 
 #### Run client
@@ -64,36 +87,31 @@ __________          _____             .___  __________              .__
  |    |    \___  /    Y    (  <_> ) /_/ |    |    |   \  ___/|  |_> >  |__
  |____|    / ____\____|__  /\____/\____ | /\ |____|_  /\___  >   __/|____/
            \/            \/            \/ \/        \/     \/|__|
-                                        v1.3.1 - 3.6.4
+                                                v2.0.2 - Pymodbus-3.7.0dev
 ----------------------------------------------------------------------------
 
-> client.read_input_registers address 1 count 1 slave 4
-{
-    "registers": [
-        34518
-    ]
-}
-
 > client.read_input_registers address 1 count 1 slave 1
 {
     "registers": [
-        32198
+        50556
     ]
 }
 
-> client.read_input_registers address 1 count 1 slave 2
+> client.read_input_registers address 1 count 1 slave 4
 {
     "registers": [
-        51557
+        51134
     ]
 }
 
-> client.read_input_registers address 1 count 1 slave 3
+> client.read_input_registers address 1 count 1 slave 5
 {
     "original_function_code": "4 (0x4)",
     "error": "[Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)"
 }
 
+>
+
 ```
 
 
@@ -112,10 +130,10 @@ This will create distribution packages in the dist/ directory.
 ## Usage
 
 ### Pymodbus Client
-Refer [REPL Client](./pymodbus/repl/client/README.rst)
+Refer [REPL Client](./pymodbus_repl/client/README.md)
 
 ### Pymodbus Server
-Refer [REPL Server](./pymodbus/repl/server/README.rst)
+Refer [REPL Server](./pymodbus_repl/server/README.md)
 
 ## Contributing
 * Fork the repository.

pymodbus_repl/client/README.rst pymodbus_repl/client/README.md

@@ -72,9 +72,7 @@ Invoke REPL server with `pymodbus.server run` command.
 The REPL server comes with auto-completion and can be installed for the supported shell with `pymodbus.server --install-completion <shell>`.
 Don't forget to restart the terminal for the auto-completion to kick-in. Use `TAB` key to show auto-completion.
 
-.. image:: ../../server_repl.png
-  :width: 400
-  :alt: Server in Action
+![Server in Action](../../server_repl.png)
 
 Example usage.