Abstract
This document describes using the Siemens S7-300/400 TCP/IP Master driver to communicate with a Siemens Logo! Basic module.
Products
Red Lion Controls CR1000 Human Machine Interface (HMI), CR3000 HMI, Data Acquisition (DA10, DA30), Data Station Plus, FlexEdge™ (DA50D, DA70D), G3 HMI, G3 Kadet HMI, Graphite® Controller, Graphite HMI, Modular Controller, and ProducTVity Station™
Use Case
Communicating with a Siemens Logo! module.
Introduction
Red Lion has not had the chance to test all of the Logo! modules, the mapping mentioned below are the ones that Red Lion or customers have verified with the modules that have been tested.
Crimson Communication Configuration
1. Navigate to the COmmunications section.
2. Click on Network (Crimson 3.x) or Ethernet (Crimson 2.0).
3. Configure the Ethernet port as required for the application.
4. Click on the first available Protocol under Network (or Ethernet).
5. Click the Pick button in the Driver Selection section.
6. Under Manufacturer, choose Siemens.
7. Under Driver, select S7-300/400 TCP/IP Master, as shown in Figure 1.
Figure 1.
8. Click OK.
9. Click on the device below the protocol, PLC1 as shown in Figure 2.
Figure 2.
10. Set the IP Address to the IP address of the Logo! module.
Crimson Tag Mapping
The following sections show how the addresses in the Logo! correspond to the addresses available in Crimson. In the case of bits, the Red Lion address is listed as Byte.Bit. Figure 3 shows a Flag tag mapped to MB1.3 (M12 in the Logo!).
Figure 3.
The following data is available for access from the Logo! modules that have been tested:
M Flags
| Logo! | Red Lion |
| M1 | MB0.0 |
| M2 | MB0.1 |
| M3 | MB0.2 |
| M4 | MB0.3 |
| M5 | MB0.4 |
| M6 | MB0.5 |
| M7 | MB0.6 |
| M8 | MB0.7 |
| M9 | MB1.0 |
| M10 | MB1.1 |
| M11 | MB1.2 |
| M12 | MB1.3 |
| M13 | MB1.4 |
| M14 | MB1.5 |
| M15 | MB1.6 |
| M16 | MB1.7 |
| M17 | MB2.0 |
| M18 | MB2.1 |
| M19 | MB2.2 |
| M20 | MB2.3 |
| M21 | MB2.4 |
| M22 | MB2.5 |
| M23 | MB2.6 |
| M24 | MB2.7 |
| M25 | MB3.0 |
| M26 | MB3.1 |
| M27 | MB3.2 |
| M28 | MB3.3 |
| M29 | MB3.4 |
| M30 | MB3.5 |
| M31 | MB3.6 |
| M32 | MB3.7 |
Input Bits
| Logo! | Red Lion |
| I1 | IB0.0 |
| I2 | IB0.1 |
| I3 | IB0.2 |
| I4 | IB0.3 |
| I5 | IB0.4 |
| I6 | IB0.5 |
| I7 | IB0.6 |
| I8 | IB0.7 |
Output Bits
| Logo! | Red Lion |
| Q1 | QB0.0 |
| Q2 | QB0.1 |
| Q3 | QB0.2 |
| Q4 | QB0.3 |
Analog Inputs and Outputs
Analog inputs and outputs will most likely be mapped to I or Q registers, respectively. They are 16-bit values, so Numeric tags would need to be mapped with the Byte as Word data type.
Disclaimer
It is the customer's responsibility to review the advice provided herein and its applicability to the system. Red Lion makes no representation about specific knowledge of the customer's system or the specific performance of the system. Red Lion is not responsible for any damage to equipment or connected systems. The use of this document is at your own risk. Red Lion standard product warranty applies.
HMS Technical Support
If you have any questions or trouble, contact HMS Technical Support by clicking here.