Update doc structure. (#1017)

Author: janiversen

doc/source/library/pymodbus.client.calls.rst

@@ -0,0 +1,6 @@
+Device calls
+============
+
+Pymodbus makes a all standard modbus requests/responses available as simple calls.
+
+All calls are available as synchronous and asynchronous (asyncio based).

doc/source/library/pymodbus.client.rst

@@ -3,53 +3,17 @@ pymodbus\.client
 
 Pymodbus offers a :mod:`synchronous client <pymodbus.client>` and a :mod:`client based on asyncio <pymodbus.client.asynchronous>`.
 
-In general each transports (Serial, TCP, TLS and UDP) have its own class.
-However the actual implementation is highly shared.
+The documentation is divided in 2 parts , to keep it simple.
 
-AsyncModbusSerialClient class
------------------------------
+First part is centered around the connection (establishing/terminating)
 
-.. automodule:: pymodbus.client.async_serial
-    :members:
+Second part is centered around the calls to get/set information in the connected device.
 
-ModbusSerialClient class
-------------------------
 
-.. automodule:: pymodbus.client.sync_serial
-    :members:
+.. toctree::
 
-AsyncModbusTcpClient class
---------------------------
+    pymodbus.client.setup
 
-.. automodule:: pymodbus.client.async_tcp
-    :members:
+.. toctree::
 
-ModbusTcpClient class
----------------------
-
-.. automodule:: pymodbus.client.sync_tcp
-    :members:
-
-AsyncModbusTlsClient class
---------------------------
-
-.. automodule:: pymodbus.client.async_tls
-    :members:
-
-ModbusTlsClient class
----------------------
-
-.. automodule:: pymodbus.client.sync_tls
-    :members:
-
-AsyncModbusUdpClient class
---------------------------
-
-.. automodule:: pymodbus.client.async_udp
-    :members:
-
-ModbusUdpClient class
----------------------
-
-.. automodule:: pymodbus.client.sync_udp
-    :members:
+    pymodbus.client.calls

doc/source/library/pymodbus.client.setup.rst

@@ -0,0 +1,53 @@
+Client setup.
+=============
+
+Pymodbus offers different transport methods Serial/TCP/TLS/UDP, which are implemented
+as separate classes. Each class defines exactly on transport type.
+
+Applications can add custom transport types as long as the new class inherits
+from class BaseModbusClient.
+
+Applications can also custom decoders and customer framers.
+
+All transport types are supplied in 2 versions:
+a :mod:`synchronous client <pymodbus.client>` and
+a :mod:`client based on asyncio <pymodbus.client.asynchronous>`.
+
+Care have been made to ensure that large parts of the actual implementation or shared
+between the different classes, to ensure a higher stability.
+
+Serial RS-485 transport.
+------------------------
+
+.. automodule:: pymodbus.client.async_serial
+    :members:
+
+.. automodule:: pymodbus.client.sync_serial
+    :members:
+
+TCP transport.
+--------------
+
+.. automodule:: pymodbus.client.async_tcp
+    :members:
+
+.. automodule:: pymodbus.client.sync_tcp
+    :members:
+
+TLS transport (based on top of TCP).
+------------------------------------
+
+.. automodule:: pymodbus.client.async_tls
+    :members:
+
+.. automodule:: pymodbus.client.sync_tls
+    :members:
+
+UDP transport (NO multicast).
+-----------------------------
+
+.. automodule:: pymodbus.client.async_udp
+    :members:
+
+.. automodule:: pymodbus.client.sync_udp
+    :members: