User’s Manual

PROFINET IO
Industrial Communication Protocol
In IR Gauges

NDC INFRARED ENGINEERING LTD 105/14787-01 Issue 7

Bates Road
The Causeway
Maldon
Essex
CM9 5FA
England

www.ndcinfrared.com
Blank Page
Contents

1. Ethernet Connectivity Introduction

2. Ethernet Connectivity Network Architecture
3. Ethernet Connectivity Configuration
4. PROFINET IO Introduction
5. PROFINET IO Definitions
6. PROFINET IO Implementation in IR Gauges
7. PROFINET IO Data Layout
8. PROFINET IO GSDML file
9. Protocol Parameter Selector Introduction
10. Parameter List Introduction
11. Parameter List Definitions
12. Parameter List
13. Simatic Step 7
14. S7 Diagnostic
15. Troubleshooting

Page 2
1. Ethernet Connectivity Introduction
NDC’s IR Gauges have the option of communicating via the Ethernet network.
This document contains the details of the network settings.
The Gauge User’s Guide contains information regarding the physical
installation and operation of the Gauge and its peripherals such as the OWS.
The GaugeToolsXL User’s Guide details the installation and operation of the
GaugeToolsXL software package.
This User’s Guide and any other files relating to the Protocol may be found on
the GaugeToolsXL CD supplied with the Gauge (in the appropriate folder).

2. Ethernet Connectivity Network Architecture

IR Gauges can be connected to the existing Ethernet network as shown
below.

NDC
IR Gauge NDC
NDC GaugeToolsXL
OWS optional

PROFINET Ethernet Switch

Other Devices…

Figure (1) - Network Diagram – Gauge through OWS

Page 3
Multiple TCP/IP communications protocols may be used concurrently over the
Ethernet network; and it is possible to configure the settings and parameters
of the IR Gauge using the NDC GaugeToolsXL software.
Similarly, the NDC OWS may still be used to display output values from the
Gauge, while using various protocols to communicate with the host system.
The NDC OWS (or HMI or User Port) appears transparent to the protocols
used over the network.

3. Ethernet Connectivity Configuration

3.1 GaugeToolsXL
The IR Gauge may be configured using the GaugeToolsXL software. To
change the settings of the IR Gauge, the GaugeToolsXL host computer
should be on the same subnet as the IR Gauge. This may be achieved by
temporarily changing the computer’s IP address to match the subnet of the IR
Gauge.
Make a note of the computer settings before changing them !
The IR Gauge default IP Address settings are detailed on the System
Configuration sheet supplied with each order.

3.2 OWS
The OWS is pre-configured by NDC to either a fixed IP address, or to
automatic IP address assignment (APIPA: DHCP or link-local 169.254.0.0/16).
The OWS IP settings are detailed on the System Configuration sheet supplied
with each order.
To change this setting, please contact NDC.

Page 4
3.3 IR Gauge
Start GaugeToolsXL and drag the Gauge node to the “Gauge Utility” icon.

Select the Configuration tab and enter the required values.

Click ‘Apply’ to use the new settings.

The host computers original settings may now be re-applied.
Note: Each IP addresses on the network should be unique, if an IP clash is
found. It will be impossible to connect to the Gauge via GaugeToolsXL.

Page 5
3.4 Device Name
PROFINET identifies the devices by name. It is important that the device
name set in the host system matches that as set in the gauge itself otherwise
communication will not be established.

IMPORTANT: PROFINET uses lowercase names! Always use a name that

comprises lowercase alpha/numeric characters.
For example:
Mm123 will not work because the M is upper case.

IMPORTANT: Gauge firmware version prior to 1v3v8 must ensure that the
station name length is EVEN.
For example:
Bmm1234 will not work because the length is an ODD number of characters.

There are two ways of setting the device name for the gauge depending on
the firmware version. The firmware version can be found under the gauge
diagnostics from GTXL.

Page 6
3.4.1 Gauge firmware earlier than version 1v3v1.

The device name is set as the general name of the gauge using GTXL as
follows:

Note that this name must also be used as the Device name in the PLC.

Page 7
3.4.2 Gauge firmware version 1v3v1 and later.
The device name is set for ProfiNet communications (separate from the
general gauge name) using GTXL as follows:

Note that the version of GTXL must be version 2.3.2 or later to support this
function.
Note that this name must also be used as the Device name in the PLC.

Page 8
4. PROFINET IO Introduction
NDC’s IR Gauges have the option of communicating via the PROFINET IO
protocol. PROFINET IO utilizes the regular Ethernet network.
This document uses the terminology as defined in the PROFINET standard,
see PROFINET International – www.profinet.com for a complete reference.
The I/O data offered by the Gauge can be configured using the
GaugeToolsXL Protocol Parameter Selector tool (GTXL – PPS).

5. PROFINET IO Definitions
AR Application Relation
CR Connection Relation
DCP Discovery and basic Configuration Protocol
DHCP Dynamic Host Configuration Protocol
PI PROFINET International
RPC Remote Procedure Call

Page 9
6. PROFINET IO Implementation in IR Gauges
The Gauge implements a PROFINET IO Device with the following capabilities:
Cyclic (RT Class 1)
1 AR
1 Input CR
1 Output CR
1 Alarm CR
Cycle Time (interval between two parameter value updates):
New measurement data from hardware: 200 ms
Recommended for Pre 1v3v8 Firmware: 512ms
Recommended for 1v3v8 Firmware or higher: 256ms
Acyclic
Connected Mode: Read & Write record
Non-connected mode: Read record
General:
Processing DCP requests
Processing RPC requests
DHCP supported
PROFINET specification V2.1

Further implementation details may be found in the PROFINET IO GSDML

file.
The Device name, Initial IP address, and other settings may be altered using
the GaugeToolsXL software.
The IR Gauge as a PROFINET IO Device is not certified by PROFINET
International; however, it is targeted at Conformance Class A.
The IR Gauge is tested with de-fact industrial standard Siemens PLCs (CPU
315-2, CPU 317-2, CPU 414-2, CPU 416-2, Software PLC) using the
configuration software STEP7 5.4.

Page 10
7. PROFINET IO Data Layout
The Data byte ordering is little endian by default – in accordance with the
protocol specification.
The GTXL – PPS tool provides a summary of the layout under
[ViewPROFINET Configuration]:

The following dialog appears showing the summary.

NOTE: The PROFINET cyclic I/O data size is variable depending on firmware
and GSDML configuration. If 252 bytes configuration is used and fewer
parameters are required, the data located in the unused area will be ignored.
The GSDML file section contains a complete reference of the I/O data format.

Page 11
8. PROFINET IO GSDML file
The GSDML is applicable to all types of IR Gauges, as it is not reliant on the
physical Gauge configuration.
Example GSDML file name: GSDML-V2.1-NDC-710e-20101220.xml, where
the last tag indicates the date of the creation.
Although the GSDML file doesn’t change too often, whenever the firmware is
updated in the gauge, check if there’s a newer GSDML file too.

9. Protocol Parameter Selector Introduction

This document contains the details of the Protocol Parameter Selector (PPS)
tool implemented in GaugeToolsXL (GTXL) for NDC’s IR Gauges.
The GaugeToolsXL User’s Manual details the installation and operation of the
GaugeToolsXL software package.

9.1 Starting PPS

The PPS tool is activated by dragging one of the available configuration items
to the Configuration Tool icon in GTXL.

Only those Protocols enabled by NDC prior to delivery will be present.

Page 12
Initially, a dialog with an empty list will appear:

9.2 File Menu

The PPS is an offline tool. There are three ways to select a configuration:
A new configuration may be created from the emply list.
A configuration may be loaded from a previously saved file.
A configuration may be uploaded from the Gauge.

The resulting Configuration may be Downloaded to the Gauge or saved to a

File under the File drop down menu.
The downloaded selection takes effect only after restarting the gauge.
Note: a Configuration may also be saved or loaded directly from a file to the
Gauge using the Gauge Utility ‘SettingsProtocol Parameters’ menu. See the
GTXL documentation for further details.

Page 13
9.3 Parameter Selection
The parameters of interest may be selected using the checkboxes in the
‘Select’ tab as shown below.
The selected parameters represent the input and output data of the gauge
through different protocols.

Page 14
9.3.1 Parameter List
The list in the tree shows all of the parameters available to the selected
Protocol.
Note that four channels are always displayed, regardless of how many
measurement channels are used in the connected Gauge. If the Gauge has
fewer than four channels, then the parameters for the missing channels will be
ignored by the Gauge and excluded from the I/O data communication.
If the Gauge has never had a configuration uploaded, it will use the following
parameters by default: (not an actual screen)

Page 15
9.3.2 Parameter Types
The symbol before the name indicates the parameter type.
If the symbol is shown in a red box, then the parameter is read-only. i.e. it is
an output from the Gauge, but not an nput. Both intput and output data sizes
will be identical, but any ‘read-only’ parameters in the input data will have no
effect on the Gauge.
The letter in the symbol indicates the native data type:
F – Floating Point Number
I – Integer
B – Boolean
S – String
Each numeric parameter (Float, Integer and Boolean) occupies 4 bytes in the
I/O data stream.
A String is 64 bytes long.

9.3.2.1 Floating Point Numbers

Default representation: IEEE-754 32-bit single-precision format.
Example (bytes on the network, little endian):
0xA4 0x70 0x45 0x41 = 12.34

9.3.2.2 Integers
Integers are converted to 32-bit unsigned value (even if the parameter is a
two byte signed value).
Example (bytes on the network, little endian):
0x15 0xCD 0x5B 0x07 = 123456789

9.3.2.3 Booleans
Boolean values use 32-bits where zero (all bits) represents ‘FALSE’ and non-
zero (any bit) represents ‘TRUE’.
Example (bytes on the network, little endian):
0x00 0x00 0x00 0x00 = FALSE
0x01 0x00 0x00 0x00 = TRUE

Page 16
9.3.2.4 Strings

Strings consist of a series of wide (2-byte) characters, with the first two bytes
indicating the length of the string (in characters) if Length Indication In First
Two Bytes has been selected in the Settings tab of the Protocol Parameter
selector.
The maximum length of a string is 31 characters when Max.Size (Bytes) has
been set to 64. Any data after the indicated length is ignored.

Example (bytes on the network, little endian, In First Two Bytes):

0x04 0x00 0x37 0x00 0x31 0x00 0x30 0x00
0x65 0x00 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC
0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC
0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC
0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC
0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC
0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC
0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC
= “710e”

Example (bytes on the network, little endian, Zero-terminated):

0x37 0x00 0x31 0x00 0x30 0x00 0x65 0x00
0x00 0x00 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC
0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC
0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC
0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC
0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC
0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC
0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC
= “710e”

Page 17
When configuring any device that includes strings, please make sure that the
string length and the total size of the data block does not exceed the Module
Size selected in the semantic S7 Hardware setup.
To reduce the parameter size of a string, change the Max. Size (Bytes):
number box to a smaller value.

9.4 Parameter Ordering

The sequence of parameters in the I/O data buffer is determined by the order
in which they are selected, and not as they appear in the Select tab tree. This
order can be reviewed and altered in the ‘Order’ tab using the [Up] and [Down]
arrows on the selected item:

Page 18
9.5 Other Settings

9.5.1 Float Representation

By default, floats are represented as 32-bit IEEE-754 floating point numbers.
It is also possible to convert floats to integers in the I/O data stream. The
value is multiplied by the provided scaling factor, and the resulting integer is
used as the output data. Similarly, the input Integer from the network is
divided by the scaling factor and converted to a float before being passed to
the Gauge.
For Example (Scaled Integer. Scale: 100)
If the Gauge Output is 20.53 the Output at PLC would be 20.53 x 100 = 2053
If 7087 was sent to the TRIM register of the Gauge by the PLC, the Gauge
would set the TRIM register to 7087 / 100 = 10.87
The Scaling factor must be a positive integer.

9.5.2 Endian Swap

It is possible to override the protocol’s default endian specification and to
choose little or big endian explicitly in the I/O data representation.
Endian swapping on floats, integers and booleans reverses the order of all
four bytes.
Endian swapping on Strings reverses the order of the bytes for each individual
character (two bytes), not the whole string.
NOTE: endian swapping only affects the parameter values in the I/O data
buffer. The other values in the protocol (tags in packet headers, attributes of
services, etc.) still obey the protocol’s default endian requirement.

Page 19
9.6 View menu
The View menu shows a summary of the Configuration for the selected
protocol.

NOTE: This refers to the current offline settings, not necessarily what is in the
Gauge.

Page 20
10. Parameter List Introduction
This section briefly describes the main parameters available in the IR Gauge.
The parameters are displayed by GaugeToolsXL (GTXL) or the GTBrowser
software, and may be selected for communication over the chosen Ethernet
Protocol in the GTXL Protocol Parameter Selector (PPS) tool.

11. Parameter List Definitions

11.1 Abbreviations
HMI Operator Interface (Human – Machine Interface)
ADC Analogue to Digital Converter
<meas> Measurement Units (application defined)
A Amps
V Volts
s Seconds
ºC Degrees Celsius
rpm Revs per minute
Hz Hertz
kB/s Kilobytes per second

11.2 Parameter Data Types

Read-only Boolean (TRUE/FALSE) parameter
Read-write Boolean (TRUE/FALSE) parameter
Read-only floating point parameter
Read- write floating point parameter
Read-only integer parameter
Read-write integer parameter
Read-only UNICODE string parameter
Read-write UNICODE string parameter

Page 21
12. Parameter List

12.1 Channel Specific Parameters

12.1.1 Output [<meas>]

Measurement value of the specified channel
The Units of the measured value depend on the target material and the
application (e.g. moisture [%]).

12.1.2 Enabled
TRUE when the measurement is running.
It may be set to FALSE to disable the measurement.

12.1.3 Application Code

This value may be set to either the full 32-bit integer application code, or the
index into the application set (the application index).

12.1.4 Application Code Full

This always reflects the full application code, regardless of how the application
is selected in Application Code above.

12.1.5 Span
Multiplier factor for the Output: Output = (Span * X) + Trim
(Where X is the raw measurement value)

12.1.6 Trim
Offset for the output: Output = (Span * X) + Trim
(Where X is the raw measurement value)

12.2 General Gauge Parameters

12.2.1 Gauge Status

Bit-coded information:
0: Error………(set when any Error is present)
1: Warning…..(set when any Warning is present)
2: Motor Error
3: Lamp Current Error
4: Lamp Voltage Error
5: Window Contamination Error

Page 22
6: Window Contamination Warning
7: Cooler Fault
8: RX Head Fault
9: Internal Temperature High Error
10: Internal Temperature High Warning
11: Internal Temperature Low Warning
12: Signal High
13: Signal Low
14: Self-Test Error

12.2.2 HW Gate 0
Indicates the state of the hardware ‘Gate Input 0’ to the microprocessor
(Normally used for photocells) TRUE = No product detected.

12.2.3 HW Gate 1
A second Input similar to HW Gate 0.

12.2.4 Off Web

TRUE if the Gauge considers itself to be off-web.
This will be based on various conditions for different Gauge types.

12.2.5 Motor Speed [rpm]

The current speed of the Filter Wheel (motor) in the gauge

12.2.6 Motor Speed Target [rpm]

The desired speed of the Filter Wheel

12.2.7 Motor Speed at Target

Indicates if the Filter Wheel has reached the target speed

12.2.8 Lamp State

TRUE if the lamp control switch is set to ON

12.2.9 Temperature Internal [oC]

The internal temperature of the gauge
This is typically ºabove the external temperature, and will slowly track any
changes in the ambient.

Page 23
12.2.10 Temperature External [oC]
The product (target material) temperature
This is only available on Gauges fitted with an external temperature sensor.

12.2.11 Mains Frequency [Hz]

The local mains frequency as detected by the optics in the sensor.
If there is very little artificial light falling onto the beam patch, it is valid for this
to read zero.

12.2.12 Mains frequency present

TRUE if the sensor can detect the local mains frequency from the ambient
light falling onto the beam patch.

12.2.13 Lamp Current [A]

Current through the lamp

12.2.14 Lamp Voltage [V]

Voltage across the lamp

12.2.15 Window Contamination

The Window Contamination level in raw ADC units as seen by the sensor
(A clean window will usually generate a base reading of a few thousand).

12.2.16 CPU Loading [%]

Indicates how hard the processor is working.

12.2.17 CPU Up Time [s]

Elapsed time from when the Gauge was last switched on.

12.2.18 Comms Loading TX [kB/s]

Ethernet TCP/IP transmission rate

12.2.19 Heated Wheel Temperature [oC]

The current temperature of the heated filter wheel (where applicable)
NOTE: This is for future Gauge development.

12.2.20 Height Product Detected

TRUE if the Product (target material) is detected by the Internal Gating option
(when fitted).

Page 24
12.2.21 Height Product Signals Valid
TRUE if the Product height detectors are working within their valid range
(where the Internal Gating option is fitted).

12.2.22 Active Recipe

The Recipe that is currently in use, this can either be used in one of two ways.

12.2.22.1 Used to load Products stored within the Gauge

Products can be created by using an HMI or OWS, products are saved in the
Gauge and contain the Product Name, Application Code, Span, Trim, Decimal
Places, Exponential Average, Limit Alarm High and Limit Alarm Low.
By setting the Active Recipe to match a product name stored in the gauge, the
gauge will actively load and use these settings; the product will then be
displayed on the HMI/OWS
IMPORTANT: When using this to set up a gauge, please do not write values
to Application Code, Span, Trim, Decimal Places, Exponential Average, Limit
Alarm High and Limit Alarm Low because they will be over written when that
corresponding product is selected. Therefore, it is recommended not to use
both methods of changing calibrations concurrently.

12.2.22.2 Used to display a Product Name in the HMI/OWS

When no products have been saved to a gauge, this register can be used to
display the name of a product onto the HMI/OWS.

12.2.23 Loaded Recipe

This parameter indicates the most recent matching Product which was loaded
from those stored in the Gauge.

12.2.24 Active Recipe Index

Each Product stored in the Gauge is allocated an Index number. This number
may be written to select a Product, and will reflect the Index of the current
Product when changed via an HMI or the Active Recipe register above.
Indexes start at 1, and are allocated chronologically. Deleted Products will
leave a gap in the Index list. New Products will re-use deleted Indexes.
Writing deleted or out of range Product Index values will return a zero, and the
Active and Loaded Recipe strings will become empty.

12.2.24.1 Finding a Product Index using the HMI

After upgrading to the latest Gauge software, it may be difficult to determine
each Products allocated Index. There is a tool provided in GaugeToolsXL to
display the stored Products and their associated Indexes. Alternatively,
manually select a Product using the HMI touchscreen, while recording the
Index value returned via Ethernet/IP.

Page 25
IMPORTANT: The Indexes are Integers, and as such will be converted to 32
bits (unsigned) as are all other Integer parameters.

12.3 Targets and Limits

12.3.1 Target [<meas>]

Measurement target

12.3.2 Limit Alarm Low [<meas>]

Lower Alarm threshold of the measurement value
(This is normally used to trigger the alarm relays in an HMI or User Port)

12.3.3 Limit Alarm High [<meas>]

Upper Alarm threshold of the measurement value
(This is normally used to trigger the alarm relays in an HMI or User Port)

12.3.4 Limit OI Low [<meas>]

Lower Scaling limit of the measurement value
(This is normally used for analogue output scaling in an HMI or User Port)

12.3.5 Limit OI High [<meas>]

Upper Scaling limit of the measurement value
(This is normally used for analogue output scaling in an HMI or User Port)

12.4 Data Processing

12.4.1 Rolling Buffer

Output smoothing depth using box car averaging

12.4.2 Exponential Average

Output smoothing using an exponential factor [0…3600]

12.4.3 Decimal Places

The number of decimal places the measurement output is rounded to.

12.5 Batch Parameters

12.5.1 Batch Last Mean [<meas>]

The Mean value of the last complete batch to be sampled

Page 26
12.5.2 Batch Last SD
The Standard Deviation of the last complete batch to be sampled

12.5.3 Batch Active Mean [<meas>]

The Mean value of the sampled batch currently in progress

12.5.4 Batch Active SD

The Standard deviation of the sampled batch currently in progress

12.5.5 Batch Progress Percentage [%]

Indicates the progress of a timed sample as a percentage

12.5.6 Batch Mode

Bit-coded information:
Bit 0: Control Bit 0
1: Control Bit 1
2: not used
3: not used
4: not used
5: not used
6: not used
7: Suspend Bit
The Batch Mode comprises values represented as bit fields within a Mailbox.
All values are Read/Write. This Mailbox presents a method of monitoring and
controlling the batch averaging process. It enables a batch to be started,
stopped, paused and updated. The details are shown below.

Page 27
Control

The Control bit field has four values associated with batch control.

Value IN Data (Gauge to Host) OUT Data (Host to Gauge)

00h Batch is not collecting data Stop Batch data collection and
transfer data to Last Mean and
SD mailboxes
01h Batch is collecting data Start Batch data collection
02h Batch is collecting data Stop Batch and start next Batch
immediately (same as 00h then
01h)
03h Batch is collecting data Transfer Current Mean and SD
values to Last Mean and SD
mailboxes

Suspend
The Suspend bit stops measurement data from being added to the batch
Mean and SD while it is set to ‘1’. When it is reset to ‘0’, the batch is resumed.

It is possible to start a batch with the Suspend bit set to ‘1’. This resets the
Active Mean and SD to zero, but disallows updates until the Suspend bit is
reset to ‘0’

Applying a hardware Gate input to the Gauge has the same effect as
suspending the batch. When the Gate signal is removed, the batch resumes.
(The suspend bit does not reflect the state of the Gate input)

Page 28
12.6 Other Output Options

12.6.1 Output Slow [<meas>]

Same as Output but throttled to a maximum update interval of 0.3 seconds.
This is normally used for displays.

12.6.2 Output Fast [<meas>]

Same as Output but without smoothing applied.
This is usefull where users wish to apply their own data smoothing (e.g. in
scanning or data collection systems).

12.7 Other Parameters

The following parameters are currently also available, but may be removed in
later versions of the software. Their descriptions are beyond the scope of this
document.
Gate Mode
Gate Mask
Gate Fixed Value
Update rate
MRD
Current MRD
Current Ambient Light Depth
Motor Drive Enabled

Page 29
13. Simatic Step 7
This chapter describes how to add NDC IR gauge to a PROFINET project.
The starting point is an existing S7 project, which is set up for PROFINET
network and contains at least one configured PLC.
Open the project and go to HW Configuration, the following screen shot is has
been configured with a CPU 315-2 PN/DP and has had a PRONET IO system
inserted. Use a correct configuration for your hardware.

Page 30
13.1 PROFINET Device Name
IMPORTANT: PROFINET uses lowercase names! Always use a name that
comprises lowercase alpha/numeric characters and ensure that the length is
EVEN as per the screen shot below if using firmware previous to 1v3v8

13.2 Install GDSML File

Choose menu Options Install GSD File…
Select the GSD file provided for IR gauge and install.

Page 31
Page 32
13.3 Add Gauge
In the right panel browse for the device “NDCPRT” described in the previously
installed GSDML file.
Drag and drop to the black-white line representing the PROFINET network.
It creates an object for the gauge instance.

13.3.1 Gauge firmware earlier than version 1v3v8.

Please only drag the correct NDC IR Gauge that your device supports, either
the 060 byte CT Build or the 252 byte Build.

Page 33
13.3.2 Gauge firmware with version 1v3v8 or above.
Drag the Firmware Version 1v3v8 or Above to the PROFINET IO System.
Drag a module from NDC Modules section to slot one, making sure that
input/output module size is greater than the size of data selected in the
GaugeToolsXL protocol parameter selector.

Page 34
13.4 Gauge Properties
Select Object Properties… in the right-click menu of NDCPRT object.
Change the default name to the same device name as can be seen in GTXL.
IMPORTANT: PROFINET uses lowercase names! Always use a name that
matches that set in the gauge and comprises lowercase alpha/numeric
characters and ensure that the length is EVEN if using firmware previous to
1v3v8.
Specify also the same IP address as configured in GTXL.
Note that PROFINET will change the IP of the gauge to this IP even if
configured differently in GTXL. However it is recommended to use the same
IP in GTXL and in S7 configuration to avoid confusion.
Check if the version of GSDML is the same as the one installed previously.

Page 35
Switch to [IO Cycle] tab page
The Mode will default to automatic. Depending on the Firmware version of
your device, the update time (ms) will either default to 256 ms or 512 ms.

Now the project is configured for NDC IR gauge! Don’t forget to Save and
Compile… and Download to the PLC.

Page 36
14. S7 Diagnostic
Choose Station Open ONLINE in HW Configuration application.
Get Module Information by right-clicking on the IR Gauge device.

Check if Status is OK.

Note that after the configuration has been successfully established, the gauge
may produce zero readings. This is because at the beginning (and sometimes
at the end) of the connection, PLCs are usually sending zeroes to the device,
thus span, trim and other exposed gauge parameters will be overwritten by
zero. This behavior can be fixed by changing the PLC program.

Page 37
15. Troubleshooting

15.1 IO Cycle error dialog

When using Firmware 1v3v8 or above and “Please check consistency
appears”.
This indicates that No module has been dragged onto Slot 1 of the device in
the Hardware editor. Refer to section 13.3.2

Page 38
15.2 SF Led remains Red
If the following diagnostic errors can be seen and the SF Led remains Red, it
is most likely that the size of the IO data selected in the Protocol Parameter
Selector is larger than the Module size dragged onto slot 1.
To resolve refer to section 9 and section 13.3.2

Page 39