readme update, PNS auto-IO length

Author: hilschernetpi

Dockerfile

@@ -6,11 +6,11 @@ RUN [ "cross-build-start" ]
 
 #labeling
 LABEL maintainer="[email protected]" \
-      version="V0.9.2" \
+      version="V0.9.3" \
       description="Debian(jessie) with netX real-time ethernet programming examples"
 
 #version
-ENV HILSCHERNETPI_NETX_PROGRAMMING_EXAMPLES_VERSION 0.9.2
+ENV HILSCHERNETPI_NETX_PROGRAMMING_EXAMPLES_VERSION 0.9.3
 
 #install ssh, gcc, create user "pi" and make him sudo
 RUN apt-get update  \

README.md

@@ -8,7 +8,7 @@ Base of this image builds a tagged version of [debian:jessie](https://hub.docker
 
 Additionally the image provides netX programming examples in source code (and as precompiled executables) for 
 
-* PROFINET IO device 
+* PROFINET IO-device 
 * EtherNet/IP adapter
 * EtherCAT slave
 
@@ -89,9 +89,9 @@ To install a firmware package move to the folder `firmwares` and call
 
 Any firmware package extracts its firmware into the folder `/opt/cifx/deviceconfig/FW/channel0`. 
 
-The firmware will be loaded by the driver into netX the first time the driver is accessed with `cifXDriverInit()` command.
+The firmware will be loaded by the driver into netX network controller the first time the driver is accessed using the `cifXDriverInit()` command.
 
-There can be only one installed firmware package at a time. An existing package will be automatically uninstalled during installation.
+There can be only one installed netX firmware package at a time. An existing package will be automatically uninstalled during the installation procedure.
 
 ##### Compiling the programming examples
 
@@ -109,6 +109,14 @@ You may be faced with the following warning during compilation process
 
 There is a discrepancy between netPI's system clock and the time the executeables/object files have been generated. Call `make clean` and remove the executeable. Then start the compilation process again. Make also sure you have set netPI's system clock correctly.
 
+##### Changing the default IO size of 10 bytes input and 4 bytes output
+
+All three examples configure a process data input length of 10 bytes and an output length 4 bytes. The provided electronic data sheets for the master/controller engineering software match exactly to this example size.
+
+If a different IO length is required you have to adjust the length in the file `/includes/App.h` in the structures APP_INPUT_DATA_T and APP_OUTPUT_DATA_T accordingly. Please take into account that there is a limit of maximum allowed IO length. This limit can be found in each of the three programming manuals provided in the folder ./manuals.
+
+Afterwards recompile and start the new examples to become effective. Make sure you also modify the device description files and reload them into the master/contoller engineering software to sychronize the project with the new physical setup.
+
 ##### Starting the executables
 
 To start the compiled examples call the following executeables in the pi home directory
@@ -117,25 +125,35 @@ To start the compiled examples call the following executeables in the pi home di
 * `sudo ./EIS_simpleConfig` for the EtherNet/IP adapter example
 * `sudo ./ECS_simpleConfig` for the EtherCAT slave example
 
-The examples check if the corresponding firmware package has been installed properly, if not they install it automatically.
+Each example checks if its corresponding firmware package has been installed properly and loaded into netX, else it will install and load it automatically.
+
+##### Electronic Data Sheets
+
+Any master/controller engineering software needs device descriptions, socalled electronic data sheets, of all IO devices it shall communicate to. They inform about device parameters such as vendor-ID, product-ID, name, IO length etc. For all three examples the devices description files can be found in the github project under `/electronic-data-sheets`.
+
+By default the provided files are preconfigured to an IO length of 10 bytes input and 4 bytes output. In case you modified an example to configure a different IO length you have to modify the electronic data sheet accordingly and reconfigure your master/controller with it.
+
+##### Protocol specifics
+
+In case of PROFINET please keep in mind that a virgin netX needs a PROFINET device name setup over the network as described [here](https://profinetuniversity.com/profinet-basics/dcp/profinet-dcp/). Use your master engineering software to assign a corresponding name ("netx51repns" which is default in the electronic data sheet).
 
 ##### Linking the cifX library to applications
 
 To link the cifX driver library to own applications just add the option `-lcifx` to your GCC compilation command.
 
-##### The cifX API reference (netX driver API)
+##### The cifX API funtions reference (netX driver API)
 
-The cifX driver function API is described in the manual 
+The cifX driver's function application interfaace (API) is described in the manual 
 
 `cifX_API_PR_04_EN.pdf` 
 
-located in the `manuals` folder.
+located in the `manuals` folder. These call functions provide you a simple interface between your application and netX network controller.
 
 ##### The protocol specific APIs (PROFINET, EtherNet/IP ... APIs)
 
 A netX firmware has a common part that is behaving the same for all firmwares and a protocol dependent specific part. Particularly the configuration varies from protocol to protocol and shows different characteristics.
 
-The protocol specific dependencies are described in these manuals
+The protocol specific dependencies are described in the manuals
 
 * `PROFINET_IO-Device_V3.12_Protocol_API_17_EN.pdf` for PROFINET IO device 
 * `EtherNetIP_Adapter_Protocol_API_19_EN.pdf` for EtherNet/IP adapter

examples/sources/PacketHandlerPNS.c

@@ -82,8 +82,8 @@ long SetConfigParams( void* pvPck, uint16_t usDeviceClass )
     ptSetConfig->ulWdgTime            = 1000;                                           /* Watchdog time (in milliseconds)        */
     ptSetConfig->ulVendorId           = 0x011E;                                         /* Vendor ID                              */
     ptSetConfig->ulMaxAr              = 0;                                              /* Currently not used                     */
-    ptSetConfig->ulCompleteInputSize  = 10;                                              /* Maximum amount of allowed input data   */
-    ptSetConfig->ulCompleteOutputSize = 10;                                              /* Maximum amount of allowed output data  */
+    ptSetConfig->ulCompleteInputSize  = sizeof(APP_INPUT_DATA_T);                       /* Maximum amount of allowed input data   */
+    ptSetConfig->ulCompleteOutputSize = sizeof(APP_OUTPUT_DATA_T);                      /* Maximum amount of allowed output data  */
 
 
     if (usDeviceClass == RCX_HW_DEV_CLASS_CHIP_NETX_51)