Update README.md

Author: serhmarch

README.md

@@ -7,6 +7,11 @@ to work with standard Modbus Protocol.
 Modbus Tools are a free, open-source  tools with a simple user interface written in C++/Qt. 
 It implements TCP, RTU and ASCII versions of Modbus Protocol.
 
+### *New in version 0.4*:
+
+*From now server application allows you to create program logic for the Modbus device simulator 
+using your favorite Python programming language.*
+
 Software implements such Modbus functions as:
 * `1 ` (`0x01`) - `READ_COILS`
 * `2 ` (`0x02`) - `READ_DISCRETE_INPUTS`
@@ -17,6 +22,7 @@ Software implements such Modbus functions as:
 * `7 ` (`0x07`) - `READ_EXCEPTION_STATUS`
 * `15` (`0x0F`) - `WRITE_MULTIPLE_COILS`
 * `16` (`0x10`) - `WRITE_MULTIPLE_REGISTERS`
+* `17` (`0x11`) - `REPORT_SERVER_ID` (since v0.4)
 * `22` (`0x16`) - `MASK_WRITE_REGISTER` (since v0.3)
 * `23` (`0x17`) - `READ_WRITE_MULTIPLE_REGISTERS` (since v0.3)
 
@@ -94,6 +100,47 @@ Device contains settings for a single device (such as Modbus Unit Address, memor
 The DataViewItem contains a single data unit to be read/write from the device and has many formats to 
 represent the current data. Action provides simulation capabilities (automatic change of device memory values).
 
+### Scripting using Python (since v0.4)
+
+Since v0.4 version 'server' application allows to extend logic of your Modbus device 
+simulator using one the most popular programming language - Python.
+All you need to use scripting is installed Python interpreter and `PyQt5` library.
+
+`server` application gives you access to the device's internal Modbus memory and
+provides `Output` window where standard output is redirected.
+The rest is the power of Python, its standard library, 3rd party libraries,
+and your own libraries and scripts.
+
+Objects for access corresponding device memory: `mem0x`, `mem1x`, `mem3x`, `mem4x`.
+
+Every object has set of get/set function to work with different data types:
+ * `mem0x`, `mem1x`: `get<datatype>(bitoffset:int)->int` and `set<datatype>(bitoffset:int,value:int)`
+ * `mem3x`, `mem4x`: `get<datatype>(regoffset:int)->int` and `set<datatype>(regoffset:int,value:int)`
+
+`<datatype>`: `int8`, `uint8`, `int16`, `uint16`, `int32`, `uint32`, `int64`, `uint64`, `float`, `double`.
+
+Examples:
+```python
+ v = mem0x.getint8(0)
+ mem1x.setint16(1, -1)
+ mem3x.setuint16(0, 65535)
+ mem4x.setdouble(10, 2.71828)
+```
+
+Also index operation is supported.
+In case of discrete memory (`mem0x`, `mem1x`) it work with `boolean` values
+and for registers memory (`mem3x`, `mem4x`) it work with `uint16` values:
+
+```python
+ b0 = mem0x[0]
+ mem1x[38] = True
+ mem3x[100] = 65535
+ if mem4x[0] > 32768:
+     mem4x[0] = 0 
+```
+
+To view all documentation and possible uses of objects and methods, use the built-in help system.
+
 ### Server Actions window
 
 The server has the ability to simulate/change data (actions, automaticaly change values) with predefined 

doc/images/client_view.png

@@ -3,8 +3,8 @@
 IDI_ICON1	ICON	DISCARDABLE	"gui\\icons\\client.ico"
 
 VS_VERSION_INFO VERSIONINFO
-	FILEVERSION 0,3,8,0
-	PRODUCTVERSION 0,3,8,0
+	FILEVERSION 0,4,0,0
+	PRODUCTVERSION 0,4,0,0
 	FILEFLAGSMASK 0x3fL
 #ifdef _DEBUG
 	FILEFLAGS VS_FF_DEBUG
@@ -21,11 +21,11 @@ VS_VERSION_INFO VERSIONINFO
 			BEGIN
 				VALUE "CompanyName", "\0"
 				VALUE "FileDescription", "\0"
-				VALUE "FileVersion", "0.3.8.0\0"
+				VALUE "FileVersion", "0.4.0.0\0"
 				VALUE "LegalCopyright", "\0"
 				VALUE "OriginalFilename", "client.exe\0"
 				VALUE "ProductName", "client\0"
-				VALUE "ProductVersion", "0.3.8.0\0"
+				VALUE "ProductVersion", "0.4.0.0\0"
 			END
 		END
 		BLOCK "VarFileInfo"

doc/images/server_view.png

@@ -1,19 +1,19 @@
-#ifndef MBCORE_CONFIG_H
-#define MBCORE_CONFIG_H
-
-/*
-   Major part of mbtools version
-*/
-#define MBTOOLS_VERSION_MAJOR 0
-
-/*
-   Minor part of mbtools version
-*/
-#define MBTOOLS_VERSION_MINOR 4
-
-/*
-   Patch part of mbtools version
-*/
-#define MBTOOLS_VERSION_PATCH 0
-
-#endif // MBCORE_CONFIG_H
+#ifndef MBCORE_CONFIG_H
+#define MBCORE_CONFIG_H
+
+/*
+   Major part of mbtools version
+*/
+#define MBTOOLS_VERSION_MAJOR 0
+
+/*
+   Minor part of mbtools version
+*/
+#define MBTOOLS_VERSION_MINOR 4
+
+/*
+   Patch part of mbtools version
+*/
+#define MBTOOLS_VERSION_PATCH 0
+
+#endif // MBCORE_CONFIG_H

src/client/win_resource.rc

@@ -196,9 +196,9 @@ void mbServerUi::initialize()
     connect(projectUi(), &mbServerProjectUi::deviceDoubleClick, this, &mbServerUi::editDeviceRef       );
     connect(projectUi(), &mbServerProjectUi::deviceContextMenu, this, &mbServerUi::contextMenuDeviceRef);
 
-    // Action
-    m_dockActions = new QDockWidget("Actions", this);
-    m_dockActions->setObjectName(QStringLiteral("dockActions"));
+    // Simulation Action
+    m_dockActions = new QDockWidget("Simulation", this);
+    m_dockActions->setObjectName(QStringLiteral("dockSimActions"));
     m_actionsUi = new mbServerSimActionsUi(m_dockActions);
     connect(m_actionsUi, &mbServerSimActionsUi::simActionContextMenu, this, &mbServerUi::contextMenuAction   );
     m_dockActions->setWidget(m_actionsUi);

src/core/sdk/mbcore_config.h

@@ -406,7 +406,7 @@
   </action>
   <action name="actionViewActions">
    <property name="text">
-    <string>Actions</string>
+    <string>Simulation</string>
    </property>
   </action>
   <action name="actionDeviceNew">

src/server/gui/server_ui.cpp

@@ -1,4 +1,4 @@
-# Object for access corresponding device memory: mem0x, mem1x, mem3x, mem4x.
+# Objects for access corresponding device memory: mem0x, mem1x, mem3x, mem4x.
 #
 # Every object has set of get/set function to work with different data types:
 #  * mem0x, mem1x: `get<datatype>(bitoffset:int)->int` and `set<datatype>(bitoffset:int,value:int)`

src/server/gui/server_ui.ui

@@ -3,8 +3,8 @@
 IDI_ICON1	ICON	DISCARDABLE	"gui\\icons\\server.ico"
 
 VS_VERSION_INFO VERSIONINFO
-	FILEVERSION 0,3,8,0
-	PRODUCTVERSION 0,3,8,0
+	FILEVERSION 0,4,0,0
+	PRODUCTVERSION 0,4,0,0
 	FILEFLAGSMASK 0x3fL
 #ifdef _DEBUG
 	FILEFLAGS VS_FF_DEBUG
@@ -21,11 +21,11 @@ VS_VERSION_INFO VERSIONINFO
 			BEGIN
 				VALUE "CompanyName", "\0"
 				VALUE "FileDescription", "\0"
-				VALUE "FileVersion", "0.3.8.0\0"
+				VALUE "FileVersion", "0.4.0.0\0"
 				VALUE "LegalCopyright", "\0"
 				VALUE "OriginalFilename", "server.exe\0"
 				VALUE "ProductName", "server\0"
-				VALUE "ProductVersion", "0.3.8.0\0"
+				VALUE "ProductVersion", "0.4.0.0\0"
 			END
 		END
 		BLOCK "VarFileInfo"