Open the data source input screen and assign a name for the data source. If the name contains the word “s7“, “S7_Compatible” is already preselected as the data source type. (This works with all data source types)
If the S7 data source is selected as the “Type” , the data source-specific settings of the S7 data source are automatically adjusted.
Specific for S7 data sources
- Model Select which S7 model you want to connect to.
- Connection type Here you can choose between the connection type “TCP” and “MPI“. Whether both or only one of the connection types is available for selection depends on the “Model” selected.
- Connection details
| – Here you enter the connection information that is relevant for the desired S7. |
| – Enter the “IP address“, “Rack” and “Slot“. |
| – The default value for “Rack” is “0“. |
| – The default value for “Slot” is “0“ |
- Read timeout The default value is 200 milliseconds. After this time, the read attempt would be aborted if the variable could not be read within these 200 milliseconds. Too slow a response from the controller, connection errors to the controller or the non-existence of the variable can be reasons for a read abort. The “read timeout” therefore specifies how long the variable is searched for before the read attempt is aborted.
200 milliseconds until the “read timeout” is a recommended value. We only recommend changing the value if you know that more is required.
- Read optimization Here you can choose between different optimization methods:
| NONE No read optimization. All requests are processed one after the other. This is stable, but slow. Recommended for test purposes only. |
| CROSS_AREAS Requests are summarized across areas. Advantage: Split areas (e.g. data across several data modules) can be read simultaneously. |
| COMBINE_AREAS Requests from the same areas are combined. Advantage: Quick access to data from the same areas (e.g. data from a data module). |
| AUTO Automatically selects the optimization method so that the lowest possible number of requests are sent to the controller. |
After entering the relevant information for the connection, click on “Add” or on “Save” after editing an already created data source.
The S7 data source is created and subsequently displayed in the data source overview.
Created data sources can be edited or deleted again. You can do this using the corresponding buttons.
You also have the option of displaying all internal data sources. This works via the “Show internal data sources” button.
You can create variables for the S7 data source below.
You can find out how to add variables for the S7 data source in the chapter “Adding S7 variables“.
Special features Logo! Control system
The following section is intended to provide you with assistance on the functionalities provided for connection to a Logo! control unit 0BA7 or 0BA8.
This is not a complete documentation, but the text is provided to give you an initial introduction.
All information in this document is published without guarantee. Changes and all rights reserved. The content of this document is protected by copyright and may not be copied (even in part), reproduced, transmitted, processed and stored in media or translated without our consent.
Note: All product names or other names or brands referred to in this document are trademarks or registered trademarks and are the property of their respective owners. There is no connection whatsoever between the named brand or brand owner and Indi.An GmbH. Any mention of brands serves solely as a reference for use.
Preparing the Logo! controller for access via TCP/IP
It is possible to access inputs, outputs, flags and shared DBs with QuickHMI. Access to a Logo! controller is deactivated by default.
You must carry out the following steps to enable access to the control unit:
1. select Extras > Ethernet connections and right-click to create a new connection:
2. set the connection as follows:
3. save the settings and upload them to the PLC, done!
Please note when accessing a logo! 0BA7:
Only one connection can be established at a time.
Connection timeout at the Logo! 0BA8
When using a control unit Logo! 0BA8 it should be noted that the control unit closes the connection after 10 seconds if no more data is requested during this period. The period starts again with each new request.
For this reason, we recommend that you do not open the connection manually, but let the driver establish the connection using Auto-Connect.
Memory organization of the Logo! controls
The memory organization of the Logo! controllers differs considerably from the memory organization of the classic Siemens controllers.
The main feature is that all variable areas are combined in the VM memory. You can call up or write to the VM memory with QuickHMI via DB1.
Memory areas of the Logo! 0BA7 controller
The following table gives you an overview of the memory areas of a Logo! 0BA7 control unit.
You can retrieve or write VM memory with QuickHMI via DB1. Furthermore, you can also address the respective memory areas from the QuickHMI library directly via the respective data type (markers, flags, input, output, etc.).
| Logo! Range | Block Type | From VM address | Up to VM address | Data type |
| DI | Digital input | Byte 923.0 | Byte 927.7 | Bit |
| AI | Analog input | Byte 926 | Byte 940 | Word |
| Q | Digital output | Byte 942.0 | Byte 943.7 | Bit |
| AQ | Analog output | Byte 944 | Byte 946 | Word |
| M | Digital marker | Byte 948.0 | Byte 951.2 | Bit |
| AM | Analog marker | Byte 952 | Byte 982 | Word |
Memory areas of the Logo! 0BA8 controller
The following table gives you an overview of the memory areas of a Logo! 0BA8– Control unit. The available memory areas have been expanded compared to the Logo! 0BA7.
You can retrieve or write VM memory with QuickHMI via DB1. Furthermore, you can also address the respective memory areas from the QuickHMI library directly via the respective data type (markers, flags, input, output, etc.).
| Logo! Range | Block Type | From VM address | Up to VM address | Data type |
| DI | Digital input | Byte 1024.0 | Byte 1031.7 | Bit |
| AI | Analog input | Byte 1032 | Byte 1063 | Word |
| Q | Digital output | Byte 1064.0 | Byte 1071.7 | Bit |
| AQ | Analog output | Byte 1072 | Byte 1103 | Word |
| M | Digital marker | Byte 1104.0 | Byte 1117.7 | Bit |
| AM | Analog marker | Byte 1118 | Byte 1245 | Word |
| NI | Digital network input | Byte 1246.0 | Byte 1261.7 | Bit |
| NAI | Analog network input | Byte 1262 | Byte 1389 | Word |
| NQ | Digital network output | Byte 1390.0 | Byte 1405.7 | Bit |
| NAQ | Analog network output | Byte 1406 | Byte 1469 | Word |
Preparing the 1200/1500 controller for access via TCP/IP
It is possible to access inputs, outputs, flags and enabled DBs with PLCcom. Access to an S7-1200 or 1500 controller is deactivated by default.
You must carry out the following steps to enable access to the control unit:
1. allow general access. To do this, the option: “Connection mechanisms” – “Allow access via PUT/GET communication by remote partner” must be activated in the“Protection” section of the controller’s property settings. This setting is located further down, simply scroll down!
2. release the blocks (DBs) to be queried. To do this, go to the properties of the DB. Optimized access must be deactivated here.
3. load the changes onto the PLC, done!
Symbolic access to 1200/1500 control unit
The firmware of the S7 CPU must have at least the following version number:
- S7-1500: Firmware 2.9 or newer
- S7-1200: Firmware 4.5 or newer
The TIA project must be created with at least TIA version 17. If the project or individual components have been created with a TIA version lower than 17, the project must be completely translated once with TIA >=17 (hardware + software)
