IME NEMO 96 HD Instructions for use

PROTOCOL COMMUNICATION
pag. 1/22
02/06/08
NEMO 96HD/HD+
Profibus DP Interface
Revisione B: 02 – 06 - 2008
Revisione C:
Revisione D: Compilato Controllato Approvato
NEMO 96 HD/HD+
NEMO 96 HD/HD+NEMO 96 HD/HD+
NEMO 96 HD/HD+
Profibus DP Interface
Profibus DP InterfaceProfibus DP Interface
Profibus DP Interface
Application manual
Application manualApplication manual
Application manual
Table of contents
1. General description
2. Installation of NEMO 96 HD Profibus
3. User Communication PLC – NEMO 96 HD
4. Control and status byte description
5. Telegram control
6. Assignment of measurements
7. Variables description
8. Nemo Manager Description

PROTOCOL COMMUNICATION
PT10789220
pag. 2/22
1. General description
The measuring instrument NEMO 96HD works in a Profibus network according to EN50170 with baud rates up to 3
Mbaud.
The functions through the Profibus interface are limited to the reading of the measured values.
The setting of parameters must be done in the local setup.
NEMO 96HD - measuring data can be processed in the PLC software and can be displayed e.g. with corresponding
visualisation systems or operator panels.
2. Installation of NEMO 96HD Profibus
In the PLC project, NEMO 96HD Profibus is to be installed with the corresponding GSD file.
The address space as a Profibus DP slave is between 01 to 126 decimal.
The parameter that must be set locally is :
The address : 01 .. 126
The selected address will be accepted after the device power up.
A module reserves, in the decentralised peripheral field, the following :
- 32 bytes input periphery
- 32 bytes output periphery

PROTOCOL COMMUNICATION
PT10789220
pag. 3/22
3. User Communication PLC - NEMO 96HD
On the application layer (PLC), the telegrams from and to the Profibus module of NEMO 96HD are shaped from 32 bytes
of the output- and input periphery. These telegrams consist fundamentally of a header, which uses 4 bytes and 28 bytes
user data for measured values.
Output Telegrams PLC - NEMO 96HD
Periphery – Output Address Meaning / contents Value
Header byte 0,
Base address output periphery - offset =
0
Telegram - or block number of the segment to
be requested
1..MAX decimal
Header byte 1
Base address output periphery - offset =
1
Reserved, not used at this time
Header byte 2
Base address output periphery - offset =
2
Bits for controlling the internal communication 8 Bit binary
Header byte 3
Base address output periphery - offset =
3
Reserved, not used at this time
Data byte 0..27
Base address output periphery - offset =
4..31
28 user data byte, not used at this time
Input Telegrams NEMO 96HD - PLC
Periphery – Input Address Meaning / contents Value
Header byte 0
Base address input periphery - offset = 0
Returned Telegram- / Block-number of the
requested block
1..MAX decimal
Header byte 1
Base address input periphery - offset = 1
Reserved, not used at this time
Header byte 2
Base address input periphery - offset = 2
Reserved, not used at this time
Header byte 3
Base address input periphery - offset = 3
Status messages 8 Bit binary
Data byte 0..27
Base address input periphery - offset =
4..31
28 bytes user data for measured values WORD, DWORD
For the transfer of all measured values form NEMO 96HD to the PLC, seven (7) telegrams are necessary.

PROTOCOL COMMUNICATION
PT10789220
pag. 4/22
4. Control and status byte description
Control byte (Output header byte 2 => NEMO 96HD)
Bit 0: Internal Request start/stop
Logical value 1 : this bit has to be set by PLC in order to start the internal retrieving process of data from
internal memory and preparing them for Profibus communication.
After this, the internal operation continues cyclically.
Note : for this reason it would be better to stop the internal processing to avoid the task overload of the
device.
Logical value 0 : this bit has to be reset by PLC in order to stop the internal processing.
Bits 1-7: Not used
Status byte (E-header byte 3 => NEMO 96HD)
Byte 3 of the data returned by NEMO 96HD includes error and status bits with the following meaning.
Bit 0: Not used
Bit 1: Logical value 1 : block number specified in BYTE 0 of the control telegram wrong.
Respect the limits (1..MAX).
Logical value 0 : OK
Bit 2: Internal error
Bit 3: Internal error
Bit 4: Logical value 1 : internal data processing still running
Logical value 0 : internal data processing not running
Bit 5: Logical value 1 : internal data processing completed
Logical value 0 : internal data processing not yet completed
Bit 6-7: Not used

PROTOCOL COMMUNICATION
PT10789220
pag. 5/22
5. Telegram Control
The basic operations that must be performed in order to get data from NEMO 96HD are described in the following part of
the document.
Note
1. In the following of the document when referring to a bit, the notation "B.b" will be used where 'B' means BYTE and 'b'
means bit. So, for example, 3.4 means bit 4 of BYTE 3.
2. There is a variable, named "block number" which is initialized to 1 at the beginning.
The simplified sequence for retrieving data from NEMO is :
1. PLC sets bit 2.0 ( = 1 ).
The next telegram sends the information to NEMO 96HD => the internal retrieving process starts
2. If the internal sequence has started (bit 3.4), PLC resets bit 2.0 and waits for the completion of the internal operation
(bit 3.4 or bit 3.5)
3. The first telegram from NEMO that contains the end condition also contains the first data packet.
4. By other 6 telegrams the PLC requires the other 6 data packet from NEMO 96HD and then the whole process may
restart again.
Note : in multi-byte data, the adjustment of the BYTEs is as following :
MSB MB2 MB1 LSB
E.g.
Decimal 123456 = 01e240
MSB MB2 MB1 LSB
00 01 e2 40

PROTOCOL COMMUNICATION
PT10789220
pag. 6/22
The schematic conceptual flow of the program FB is the following :
block number = 1; /* init the number of block to be required to NEMO 96HD */
status = 1; /* init the internal status of the software */
while (TRUE) begin
case (status) :
if 1 begin
bit 2.0 (output header) = 1; /* start NEMO 96HD internal processing */
BYTE 0 (Output header) = block number;
status = 2;
end case
if 2 begin
if (bit 3.4 = 1) begin /* internal processing running */
bit 2.0 (output header) = 0; /* stop NEMO 96HD internal processing
after the completion of the
current operation */
status = 3;
end
end case
if 3 begin
if (bit 3.5 = 1) begin /* internal processing finished */
( data in the telegram are valid )
if (telegram is OK) begin /* block number between input and
output headers agree … */
transfer data from telegram in the PLC area;
block number = +1;
if (block number > 7) begin
block number = 1;
status = 1; /* restart */
else begin
status = 3; /* next request */
end
end
end
end case
End while

PROTOCOL COMMUNICATION
PT10789220
pag. 7/22
6. Assignment of measurements
Telegram Number 1 = Block Number 1
Input byte Value NEMO 96HD Byte Format Note
Base
address +
0 Header byte 0 (Returned Block Number) Decimal = 1
1 Header byte 1 (not used)
2 Header byte 2 (not used)
3 Header byte 3 (Status) 8 Bit binary
4 Phase 1 : phase voltage MSB DWORD
5 MB2
6 MB1
7 LSB
8 Phase 2 : phase voltage MSB DWORD
9 MB2
10 MB1
11 LSB
12 Phase 3 : phase voltage MSB DWORD
13 MB2
14 MB1
15 LSB
16 Phase 1 : phase current MSB DWORD
17 MB2
18 MB1
19 LSB
20 Phase 2 : phase current MSB DWORD
21 MB2
22 MB1
23 LSB
24 Phase 3 : phase current MSB DWORD
25 MB2
26 MB1
27 LSB
28 Neutral current MSB DWORD
29 MB2
30 MB1
31 LSB

PROTOCOL COMMUNICATION
PT10789220
pag. 8/22
Telegram Number 2 = Block Number 2
Input byte Value NEMO 96HD Byte Format Note
Base
address +
0 Header byte 0 (Returned Block Number) Decimal = 2
1 Header byte 1 (not used)
2 Header byte 2 (not used)
3 Header byte 3 (Status) 8 Bit binary
4 Chained voltage 1-2 MSB DWORD
5 MB2
6 MB1
7 LSB
8 Chained voltage 2-3 MSB DWORD
9 MB2
10 MB1
11 LSB
12 Chained voltage 3-1 MSB DWORD
13 MB2
14 MB1
15 LSB
16 3-Phase: active Power MSB DWORD
17 MB2
18 MB1
19 LSB
20 3-Phase: reactive Power MSB DWORD
21 MB2
22 MB1
23 LSB
24 3-Phase: apparent Power MSB DWORD
25 MB2
26 MB1
27 LSB
28 Active Power sign HB WORD
29 LB
30 Reactive Power sign HB WORD
31 LB

PROTOCOL COMMUNICATION
PT10789220
pag. 9/22
Telegram Number 3 = Block Number 3
Input byte Value NEMO 96HD Byte Format Note
Base
address +
0 Header byte 0 (Returned Block Number) Decimal = 3
1 Header byte 1 (not used)
2 Header byte 2 (not used)
3 Header byte 3 (Status) 8 Bit binary
4 3 phase : positive active energy MSB DWORD
5 MB2
6 MB1
7 LSB
8 3 phase : positive reactive energy MSB DWORD
9 MB2
10 MB1
11 LSB
12 3 phase : negative active energy MSB DWORD
13 MB2
14 MB1
15 LSB
16 3 phase : negative reactive energy MSB DWORD
17 MB2
18 MB1
19 LSB
20 Power Factor 3-phase HB WORD
21 LB
22 Power Factor Sector HB WORD
23 LB
24 Frequency HB WORD
25 LB
26 3-Phase : average power MSB DWORD
27 MB2
28 MB1
29 LSB
30 3 phase : peak maximum demand MSB DWORD
31 MB2

PROTOCOL COMMUNICATION
PT10789220
pag. 10/22
Telegram Number 4 = Block Number 4
Input byte Value NEMO 96HD Byte Format Solution
Base
address +
0 Header byte 0 (Returned Block Number) Decimal = 4
1 Header byte 1 (not used)
2 Header byte 2 (not used)
3 Header byte 3 (Status) 8 Bit binary
4 3 phase : peak maximum demand MB1
5 LSB
6 Average power pointer HB WORD
7 LB
8 Phase 1 : phase active power MSB DWORD
9 MB2
10 MB1
11 LSB
12 Phase 2 : phase active power MSB DWORD
13 MB2
14 MB1
15 LSB
16 Phase 3 : phase active power MSB DWORD
17 MB2
18 MB1
19 LSB
20 Phase 1 : active power sign HB WORD
21 LB
22 Phase 2 : active power sign HB WORD
23 LB
24 Phase 3 : active power sign HB WORD
25 LB
26 Phase 1 : phase reactive power MSB DWORD
27 MB2
28 MB1
29 LSB
30 Phase 2 : phase reactive power MSB DWORD
31 MB2

PROTOCOL COMMUNICATION
PT10789220
pag. 11/22
Telegram Number 5 = Block Number 5
Input byte Value NEMO 96HD Byte Format Note
Base
address +
0 Header byte 0 (Returned Block Number) Decimal = 5
1 Header byte 1 (not used)
2 Header byte 2 (not used)
3 Header byte 3 (Status) 8 Bit binary
4 Phase 2 : phase reactive power MB1
5 LSB
6 Phase 3 : phase reactive power MSB DWORD
7 MB2
8 MB1
9 LSB
10 Phase 1 : reactive power sign HB WORD
11 LB
12 Phase 2 : reactive power sign HB WORD
13 LB
14 Phase 3 : reactive power sign HB WORD
15 LB
16 Phase 1 : phase apparent power MSB DWORD
17 MB2
18 MB1
19 LSB
20 Phase 2 : phase apparent power MSB DWORD
21 MB2
22 MB1
23 LSB
24 Phase 3 : phase apparent power MSB DWORD
25 MB2
26 MB1
27 LSB
28 Phase 1 : Power Factor HB WORD
29 LB
30 Phase 2 : Power Factor HB WORD
31 LB

PROTOCOL COMMUNICATION
PT10789220
pag. 12/22
Telegram Number 6 = Block Number 6
Input byte Value NEMO 96HD Byte Format Note
Base
address +
0 Header byte 0 (Returned Block Number) Decimal = 6
1 Header byte 1 (not used)
2 Header byte 2 (not used)
3 Header byte 3 (Status) 8 Bit binary
4 Phase 2 : Power Factor HB WORD
5 LB
6 Phase 1 : power factor sector HB WORD
7 LB
8 Phase 2 : power factor sector HB WORD
9 LB
10 Phase 3 : power factor sector HB WORD
11 LB
12 Phase 1 : THD phase V1 or V1-2 HB WORD
13 LB
14 Phase 2 : THD phase V2 or V2-3 HB WORD
15 LB
16 Phase 3 : THD phase V3 or V3-1 HB WORD
17 LB
18 Phase 1 : THD phase current HB WORD
19 LB
20 Phase 2 : THD phase current HB WORD
21 LB
22 Phase 3 : THD phase current HB WORD
23 LB
24 Phase 1 : thermal current MSB DWORD
25 MB2
26 MB1
27 LSB
28 Phase 2 : thermal current MSB DWORD
29 MB2
30 MB1
31 LSB

PROTOCOL COMMUNICATION
PT10789220
pag. 13/22
Telegram Number 7 = Block Number 7
Input byte Value NEMO 96HD Byte Format Note
Base
address +
0 Header byte 0 (Returned Block Number) Decimal = 7
1 Header byte 1 (not used)
2 Header byte 2 (not used)
3 Header byte 3 (Status) 8 Bit binary
4 Phase 3 : thermal current MSB DWORD
5 MB2
6 MB1
7 LSB
8 Phase 1 : peak of thermal current MSB DWORD
9 MB2
10 MB1
11 LSB
12 Phase 2 : peak of thermal current MSB DWORD
13 MB2
14 MB1
15 LSB
16 Phase 3 : peak of thermal current MSB DWORD
17 MB2
18 MB1
19 LSB
20 3 phase : partial positive active energy MSB DWORD
21 MB2
22 MB1
23 LSB
24 Current ratio KTI HB WORD
25 LB
26 Voltage ratio KTV HB WORD
27 LB
28 Ratio KTI*KTV*10 HB WORD
29 LB
30
31

PROTOCOL COMMUNICATION
PT10789220
pag. 14/22
7. Variables description
BLOCK 1
Phase voltage 1 / 2 / 3 (block 1.1 / 1.2 / 1.3)
This is the phase to neutral voltage. This measure is available also in the 2 systems connection (Aron).
Format : DWORD
Measurement unit : mV
Example : 100V => 100000 mV => 0x00 01 86 a0
Phase current 1 / 2 / 3 (block 1.4 / 1.5 / 1.6)
Format : DWORD
Measurement unit : mA
Example : 5.4A => 5400 mA => 0x00 00 15 18
Neutral current (block 1.7)
The neutral current is the real time sum of the 3 single phase currents.
Format : DWORD
Measurement unit : mA
Example : 5.4A => 5400 mA => 0x00 00 15 18

PROTOCOL COMMUNICATION
PT10789220
pag. 15/22
BLOCK 2
Phase to phase voltage 12, 23, 13 (block 2.1 / 2.2 / 2.3)
This is the phase to phase voltage.
Format : DWORD
Measurement unit : mV
Active power (block 2.4)
This is the 3-phase active power.
Format : DWORD
Measurement unit : hundredths of W => if KTA*KTV < 6000
W => if KTA*KTV 6000
Example : 900W => 90000 => if KTA*KTV < 6000
=> 900 => if KTA*KTV > 6000
Reactive power (block 2.5)
This is the 3-phase reactive power.
Format : DWORD
Measurement unit : hundredths of var => if KTA*KTV < 6000
var => if KTA*KTV 6000
Example : 900 var => 90000 => if KTA*KTV < 6000
=> 900 => if KTA*KTV > 6000
Apparent power (block 2.6)
This is the 3-phase apparent power.
Format : DWORD
Measurement unit : hundredths of VA => if KTA*KTV < 6000
VA => if KTA*KTV 6000
Example : 900 VA => 90000 => if KTA*KTV < 6000
=> 900 => if KTA*KTV > 6000
Active power sign (block 2.7)
Format : WORD
Measurement unit : //
Values : 0x01 => negative single phase or 3-phase active power
0x00 => positive single phase or 3-phase active power
Reactive power sign (block 2.8)
Same as block 2.7

PROTOCOL COMMUNICATION
PT10789220
pag. 16/22
BLOCK 3
Positive active energy (block 3.1)
This is, conventionally, the energy actually consumed by the user.
Format : DWORD
Measurement unit :
Transformer ratio Measurement unit
1 < KTA*KTV < 10 xxxxxx.yy kWh
10 < KTA*KTV < 100 xxxxxxx.y kWh
100 < KTA*KTV < 1000 xxxxxxxx kWh
1000 < KTA*KTV < 10000 xxxxxx.yy MWh
10000 < KTA*KTV < 100000 xxxxxxx.y MWh
Positive reactive energy (block 3.2)
Format : DWORD
Measurement unit :
Transformer ratio Measurement unit
1 < KTA*KTV < 10 xxxxxx.yy kvarh
10 < KTA*KTV < 100 xxxxxxx.y kvarh
100 < KTA*KTV < 1000 xxxxxxxx kvarh
1000 < KTA*KTV < 10000 xxxxxx.yy Mvarh
10000 < KTA*KTV < 100000 xxxxxxx.y Mvarh
Negative active energy (block 3.3)
Same as block 3.1
Negative reactive energy (block 3.4)
Same as block 3.2

PROTOCOL COMMUNICATION
PT10789220
pag. 17/22
Power factor (3-phase) (block 3.5)
Format : WORD
Measurement unit : //
Values : multiplied by 100
Example : 0.98 => 98 => 0x00 62
Power factor sector (3-phase) (block 3.6)
Format : WORD
Measurement unit : //
Values : 0x00 => PF is 1
0x01 => PF is inductive
0x02 => PF is capacitive
Frequency (block 3.7)
Format : WORD
Measurement unit : tenth of Hz
Example : 50 Hz => 500 => 0x01 f4
Average power (block 3.8)
This is the power calculated with the shifting average algorithm. It is updated each minute.
Format : DWORD
Measurement unit : it depends on the type of the selected power and so it can be W, var o VA
with the same restrictions due to the product KTV*KTA
Peak maximum demand (block 3.9 / 4.1)
This is the power obtained as the maximum of the average powers and it is updated every minute.
Format : DWORD
Measurement unit : it depends on the type of the selected power and so it can be W, var o VA with the
same restrictions due to the product KTV*KTA
BLOCK 4
Average power pointer (block 4.2)
It gives an indication of the current minute in the time interval and its range is, obviously, between 0 and the (average
time – 1)
Format : WORD
Measurement unit : //
Example : average time = 15 minutes
counter = 10 means that the current minute is the 11th
Active power phase 1 / 2 / 3 (block 4.3 / 4.4 / 4.5)
Same as block 2.4
Active power phase 1 / 2 /3 sign (block 4.6 / 4.7 / 4.8)
Same as block 2.7
Reactive power phase 1 (block 4.9)
Same as block 2.5
Reactive power phase 2 (block 4.10 / 5.1)
Same as block 2.5

PROTOCOL COMMUNICATION
PT10789220
pag. 18/22
BLOCK 5
Reactive power phase 3 (block 5.2)
Same as block 2.5
Reactive power phase 1 / 2 / 3 sign (block 5.3 / 5.4 / 5.5)
Same as block 2.7
Apparent power phase 1 / 2 / 3 (block 5.6 / 5.7 / 5.8)
Same as block 2.6
Power factor phase 1 / 2 (block 5.9 / 5.10)
Same as block 3.5
BLOCK 6
Power factor phase 3 (block 6.1)
Same as block 3.5
Power factor sector phase 1 / 2 / 3 (block 6.2 / 6.3 / 6.4)
Same as block 3.6
THD phase voltage phase 1 / 2 / 3 (or chained voltage V12 / V23 / V13) (block 6.5 / 6.6 / 6.7)
Format : WORD
Measurement unit : % with 1 decimal
THD current phase 1 / 2 / 3 (block 6.8 / 6.9 / 6.10)
Format : WORD
Measurement unit : % with 1 decimal
Thermal current phase 1 / 2 (block 6.11 / 6.12)
The thermal currents are the phase currents integrated in the desidered time period.
Format : DWORD
Measurement unit : mA
BLOCK 7
Thermal current phase 3 (block 7.1)
Same as block 6.11
Peak of thermal current phase 1 / 2 / 3 (block 7.2 / 7.3 / 7.4)
Same as block 6.11
Partial positive active energy (block 7.5)
Same as block 3.1

PROTOCOL COMMUNICATION
PT10789220
pag. 19/22
Current ratio (KTI) (block 7.6)
The current transformer ratio is the ratio between the rated primary value and the rated secondary value.
For example, if a CT primary/secondary ratio is 100/5, the value to be set in NEMO96HD is 20 and this is also the value
given on the remote line.
Format : WORD
Measurement unit : //
Voltage ratio (KTU) (block 7.7)
The voltage transformer ratio is the ratio between the rated primary value and the rated secondary value.
For example, if a VT primary/secondary is 380/100, the value to be set in NEMO96HD is 3.8
For the TVs, the first decimal of the ratio is kept and so the value given on the remote line is multiplied by 10, in this case
38.
Format : WORD
Measurement unit : //
Ratio KTV * KTU (block 7.8)
Format : DWORD
Measurement unit : //

PROTOCOL COMMUNICATION
PT10789220
pag. 20/22
8. Nemo Manager Description
The NEMO Manager is the SIMATIC S7 Project for Data Management of the Measuring Instrument NEMO Profibus and
NEMO Profibus-DP Link-Module.
Description of Software Function
The core of the NEMO-MANAGER is the function block FB80, that organises the transfer of measured data to the PLC of
every NEMO instrument, which is connected to Profibus DP. Both versions of interface technology can be served, the
NEMO with internal interface and the external Link Module .
In the S7 software a call of the function block has to be installed with an own instance data block and an own destination
data block for measured values for every connected NEMO
Because the amount of data from one NEMO is larger than 32 bytes, several transfer cycles are necessary. In every
multiplex cycle the Profibus master reads a data block from the Profibus consisting of a 4 byte header and 28 data byte.
The sequences in function block FB80 for reading values are started by a release bit. When the FB 80 serves a single
Profibus NEMO, the release bit must always be set TRUE before calling the FB. This bit can always be the same, because
the base addresses are different.
Example for single Profibus NEMOs:
SET
= M2.0 // Release bit is set to 1
CALL FB80, DB80 // Call the manager with instance data block DB90
BASEADR_DP :=96 // Projected start address of peripheral input/output area in the hardware
configuration
DEVICE_ADR := // Not used for single Profibus NEMOs
DEST_DB :=DB61 // Destination data block for values
...
RELEASE :=M2.0 // Release bit for this call
NEXT_INST:= // Not used for single Profibus NEMOs
* * *
SET
= M2.0 // Release bit is set to 1
CALL FB80, DB81 // Call the manager with instance data block DB91
BASEADR_DP :=128 // Projected start address of peripheral input/output area in the hardware
configuration
DEVICE_ADR := // Not used for single Profibus NEMOs
DEST_DB :=DB62 // Destination data block for values
...
RELEASE :=M2.0 // Release bit for this call
NEXT_INST:= // Not used for single Profibus NEMOs
When an external Link Module is connected with several instruments, only 1 release bit with status TRUE is allowed. This
is valid for calls with the same base address DP. In this case all release bits must be different.
At power on a service routine has to guarantee that only one of the release bits is controlled to 1 and the other to 0 status.