Download
Share
Print this page
IME NEMO 96 HD Applications Manual
  1. Manuals
  2. Brands
  3. IME Manuals
  4. Recording Equipment
  5. NEMO 96 HD
  6. Applications manual

IME NEMO 96 HD Applications Manual

Profibus dp interface. protocol communication
Hide thumbs Also See for NEMO 96 HD:

Advertisement

Quick Links

NEMO 96 HD/HD+
NEMO 96 HD/HD+
NEMO 96 HD/HD+
NEMO 96 HD/HD+

Table of contents

Revisione B: 02 - 06 - 2008
Revisione C:
Revisione D:
PROTOCOL COMMUNICATION
NEMO 96HD/HD+
Profibus DP Interface
Profibus DP Interface
Profibus DP Interface
Profibus DP Interface
Profibus DP Interface
Application manual
Application manual
Application manual
Application manual
Compilato
Controllato
pag. 1/22
02/06/08
Approvato

Advertisement

loading
Need help?

Need help?

Do you have a question about the NEMO 96 HD and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for IME NEMO 96 HD

Summary of Contents for IME NEMO 96 HD

  • Page 1: Table Of Contents

    Application 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.

  • Page 2: General Description

    PT10789220 PROTOCOL COMMUNICATION 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.

  • Page 3: User Communication Plc - Nemo 96Hd

    PT10789220 PROTOCOL COMMUNICATION 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.

  • Page 4: Control And Status Byte Description

    PT10789220 PROTOCOL COMMUNICATION 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.

  • Page 5: Telegram Control

    PT10789220 PROTOCOL COMMUNICATION 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.
  • Page 6 PT10789220 PROTOCOL COMMUNICATION 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...

  • Page 7: Assignment Of Measurements

    PT10789220 PROTOCOL COMMUNICATION pag. 7/22 6. Assignment of measurements Telegram Number 1 = Block Number 1 Input byte Value NEMO 96HD Byte Format Note Base address + Header byte 0 (Returned Block Number) Decimal Header byte 1 (not used) Header byte 2 (not used) Header byte 3 (Status) 8 Bit binary Phase 1 : phase voltage...
  • Page 8 PT10789220 PROTOCOL COMMUNICATION pag. 8/22 Telegram Number 2 = Block Number 2 Input byte Value NEMO 96HD Byte Format Note Base address + Header byte 0 (Returned Block Number) Decimal Header byte 1 (not used) Header byte 2 (not used) Header byte 3 (Status) 8 Bit binary Chained voltage 1-2...
  • Page 9 PT10789220 PROTOCOL COMMUNICATION pag. 9/22 Telegram Number 3 = Block Number 3 Input byte Value NEMO 96HD Byte Format Note Base address + Header byte 0 (Returned Block Number) Decimal Header byte 1 (not used) Header byte 2 (not used) Header byte 3 (Status) 8 Bit binary 3 phase : positive active energy...
  • Page 10 PT10789220 PROTOCOL COMMUNICATION pag. 10/22 Telegram Number 4 = Block Number 4 Input byte Value NEMO 96HD Byte Format Solution Base address + Header byte 0 (Returned Block Number) Decimal Header byte 1 (not used) Header byte 2 (not used) Header byte 3 (Status) 8 Bit binary 3 phase : peak maximum demand...
  • Page 11 PT10789220 PROTOCOL COMMUNICATION pag. 11/22 Telegram Number 5 = Block Number 5 Input byte Value NEMO 96HD Byte Format Note Base address + Header byte 0 (Returned Block Number) Decimal Header byte 1 (not used) Header byte 2 (not used) Header byte 3 (Status) 8 Bit binary Phase 2 : phase reactive power...
  • Page 12 PT10789220 PROTOCOL COMMUNICATION pag. 12/22 Telegram Number 6 = Block Number 6 Input byte Value NEMO 96HD Byte Format Note Base address + Header byte 0 (Returned Block Number) Decimal Header byte 1 (not used) Header byte 2 (not used) Header byte 3 (Status) 8 Bit binary Phase 2 : Power Factor...
  • Page 13 PT10789220 PROTOCOL COMMUNICATION pag. 13/22 Telegram Number 7 = Block Number 7 Input byte Value NEMO 96HD Byte Format Note Base address + Header byte 0 (Returned Block Number) Decimal Header byte 1 (not used) Header byte 2 (not used) Header byte 3 (Status) 8 Bit binary Phase 3 : thermal current...

  • Page 14: Variables Description

    PT10789220 PROTOCOL COMMUNICATION 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 =>...
  • Page 15 PT10789220 PROTOCOL COMMUNICATION 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 =>...
  • Page 16 PT10789220 PROTOCOL COMMUNICATION 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 xxxxxx.yy kWh 1 < KTA*KTV < 10 xxxxxxx.y kWh 10 <...
  • Page 17 PT10789220 PROTOCOL COMMUNICATION 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 =>...
  • Page 18 PT10789220 PROTOCOL COMMUNICATION 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...
  • Page 19 PT10789220 PROTOCOL COMMUNICATION 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.

  • Page 20: Nemo Manager Description

    PT10789220 PROTOCOL COMMUNICATION 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.
  • Page 21 PT10789220 PROTOCOL COMMUNICATION pag. 21/22 Example for Profibus Link Module with 2 linked NEMOs: CALL FB80, DB80 // Call the manager with instance data block DB95 BASEADR_DP :=96 // Projected start address of peripheral input/output area in the hardware configuration DEVICE_ADR :=1 // Adjusted bus address for this NEMO DEST_DB :=DB70...
  • Page 22 PT10789220 PROTOCOL COMMUNICATION pag. 22/22 Instance of the Function Block Name Declaration Type Description Projected base address input / output decentralised BASEADR_DP periphery Device address NEMO on external interface bus, DEVICE_ADR not used at single Profibus NEMO DEST_DB BLOCK_DB Destination data block number for NEMO values Amount of 28-byte-blocks to be requested (7:intern.

This manual is also suitable for:

Nemo 96 hd+
Save PDF