PROTOCOL COMMUNICATION pag. 1/22 NEMO 96 HD/HD+ Profibus DP Interface. Application manual
|
|
- Abner Alexander
- 6 years ago
- Views:
Transcription
1 pag. 1/22 NEMO 96HD/HD+ Profibus DP Interface 02/06/08 NEMO 96 HD/HD+ Profibus DP Interface 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 Revisione B: Revisione C: Revisione D: Compilato Controllato Approvato
2 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 : 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
3 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 Header byte 1 Base address output periphery - offset = 1 Header byte 2 Base address output periphery - offset = 2 Header byte 3 Base address output periphery - offset = 3 Data byte Base address output periphery - offset = Telegram - or block number of the segment to be requested Reserved, not used at this time Bits for controlling the internal communication Reserved, not used at this time 28 user data byte, not used at this time 1..MAX decimal 8 Bit binary Input Telegrams NEMO 96HD - PLC Periphery Input Address Meaning / contents Value Header byte 0 Base address input periphery - offset = 0 Header byte 1 Base address input periphery - offset = 1 Header byte 2 Base address input periphery - offset = 2 Header byte 3 Base address input periphery - offset = 3 Data byte Base address input periphery - offset = Returned Telegram- / Block-number of the 1..MAX decimal requested block Reserved, not used at this time Reserved, not used at this time Status messages 8 Bit binary 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.
4 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: Bit 1: Bit 2: Bit 3: Bit 4: Bit 5: Bit 6-7: Not used Logical value 1 : block number specified in BYTE 0 of the control telegram wrong. Respect the limits (1..MAX). Logical value 0 : OK Internal error Internal error Logical value 1 : internal data processing still running Logical value 0 : internal data processing not running Logical value 1 : internal data processing completed Logical value 0 : internal data processing not yet completed Not used
5 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 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 = 01e240 MSB MB2 MB1 LSB e2 40
6 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 ) end end case End while 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
7 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
8 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
9 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
10 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
11 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
12 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
13 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
14 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). Measurement unit : mv Example : 100V => mv => 0x a0 Phase current 1 / 2 / 3 (block 1.4 / 1.5 / 1.6) Measurement unit : ma Example : 5.4A => 5400 ma => 0x Neutral current (block 1.7) The neutral current is the real time sum of the 3 single phase currents. Measurement unit : ma Example : 5.4A => 5400 ma => 0x
15 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. Measurement unit : mv Active power (block 2.4) This is the 3-phase active power. Measurement unit : hundredths of W => if KTA*KTV < 6000 W => if KTA*KTV 6000 Example : 900W => => if KTA*KTV < 6000 => 900 => if KTA*KTV > 6000 Reactive power (block 2.5) This is the 3-phase reactive power. Measurement unit : hundredths of var => if KTA*KTV < 6000 var => if KTA*KTV 6000 Example : 900 var => => if KTA*KTV < 6000 => 900 => if KTA*KTV > 6000 Apparent power (block 2.6) This is the 3-phase apparent power. Measurement unit : hundredths of VA => if KTA*KTV < 6000 VA => if KTA*KTV 6000 Example : 900 VA => => 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
16 pag. 16/22 BLOCK 3 Positive active energy (block 3.1) This is, conventionally, the energy actually consumed by the user. 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 < xxxxxx.yy MWh < KTA*KTV < xxxxxxx.y MWh Positive reactive energy (block 3.2) 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 < xxxxxx.yy Mvarh < KTA*KTV < 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
17 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. 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. 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
18 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. 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
19 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) Measurement unit : //
20 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 BASEADR_DP :=96 DEVICE_ADR := DEST_DB :=DB61... RELEASE :=M2.0 NEXT_INST:= // Call the manager with instance data block DB90 // Projected start address of peripheral input/output area in the hardware configuration // Not used for single Profibus NEMOs // Destination data block for values // Release bit for this call // Not used for single Profibus NEMOs * * * SET = M2.0 // Release bit is set to 1 CALL FB80, DB81 BASEADR_DP :=128 DEVICE_ADR := DEST_DB :=DB62... RELEASE :=M2.0 NEXT_INST:= // Call the manager with instance data block DB91 // Projected start address of peripheral input/output area in the hardware configuration // Not used for single Profibus NEMOs // Destination data block for values // Release bit for this call // 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.
21 pag. 21/22 Example for Profibus Link Module with 2 linked NEMOs: CALL FB80, DB80 BASEADR_DP :=96 DEVICE_ADR :=1 DEST_DB :=DB70... RELEASE :=M2.0 NEXT_INST:=M2.1 // Call the manager with instance data block DB95 // Projected start address of peripheral input/output area in the hardware configuration // Adjusted bus address for this NEMO // Destination data block for values // Release bit for this call // Release bit for the second NEMO * * * CALL FB80, DB81 BASEADR_DP :=96 DEVICE_ADR :=2 DEST_DB :=DB71... RELEASE :=M2.1 NEXT_INST:=M2.0 // Call the manager with instance data block DB96 // Projected start address of peripheral input/output area in the hardware configuration // Adjusted bus address for this NEMO // Destination data block for values // Release bit for this call // Release bit for the first NEMO When the sequence starts, the function block FB80 sends the telegram number 1 to the NEMO and in case of servicing an external Link Module additionally the NEMO address, from which the values should be requested. Then the internal data refresh or data request are enabled by a control bit in the header. After that the prepared data are ready for transfer and will be sent in blocks of 4 byte header + 28 data byte to the master. The telegram number is the block number of the data area. The FB80 stores the 28 data byte in the destination data block at the start address (telegram number 1) x 28. By incrementing the telegram number all data are transmitted. The Profibus NEMO needs 7 and the external Link Module needs 4 multiplex cycles. When the sequences of the FB80 are finished, it is signalled by the status bit DATA_COMPLETE in the instance data of the function call. This message is also generated, when an error occurred during running the sequences. In the case of error all functions in the FB80 are aborted and the content of the error byte in the instance is not zero. Additionally at the end of the sequences the release bit for this call is cleared and the instance bit NEXT_INSTR is set. This bit is the release bit for the function call for the next NEMO. The sequences of the function block FB80 are supervised by a internal watchdog counter, which is clocked by the instance bit CLOCK (1 sec pulse). When there is any reason that causes the sequences in FB80 to hang (for example new- or restart Profibus or no answer from NEMO / Link Module), the watchdog counter decrements to 0 in 5 sec, all internal sequence control bits and the release bit are cleared and the bit NEXT_INSTR is set. Address area and Data Blocks The base address (or start address) of the input/output peripheral area is free selectable and may be set to any address that the type of CPU allows. The projected base addresses of the decentralised input and output areas must be the same. The minimum length of destination data blocks for values are: - for Profibus NEMO 28 x 7 = 196 byte - for external Link Module: 28 x 4 = 112 byte
22 pag. 22/22 Instance of the Function Block Name Declaration Type Description BASEADR_DP IN INT Projected base address input / output decentralised periphery DEVICE_ADR IN INT Device address NEMO on external interface bus, not used at single Profibus NEMO DEST_DB IN BLOCK_DB Destination data block number for NEMO values NO_BLOCKS IN INT Amount of 28-byte-blocks to be requested (7:intern. 4:external interface) CLOCK IN BOOL 1 sec clock pulse for decrementing the watchdog counter RELEASE IN_OUT BOOL Enables the functions in the FB for this call. This bit is cleared internally with the message DATA_COMPLETE (with or without error). NEXT_INSTR IN_OUT BOOL This bit is the release bit for the next call of the FB80 for the next NEMO. This bit is set internally with the message DATA_COMPLETE (with or without error). Not used at single Profibus NEMO DATA_COMPLETE IN_OUT BOOL Message from function block: data transfer to PLC is complete Error status is available in the error byte ERR_BYTE OUT BYTE Error status of communication Interface - NEMO S7 Sample Project NEMO-MANAGER Table of Contents FB 10 NEMO Management ext. / calls the Manager for every NEMO on interface bus FB 11 NEMO Management int. / calls the Manager for every Profibus NEMO FB80 NEMO-Manager, controls the requests, multiplex sequences and downloading DB61 Formatted data block with the structure of measure values from Profibus NEMO 1 DB62 Formatted data block with the structure of measure values from Profibus NEMO 2 DB70 Formatted data block with the structure of measure values from NEMO via Link Module DB71 Formatted data block with the structure of measure values from NEMO via Link Module DB80 Instance data block DB81 Instance data block OB1 Cycle Execution OBxx Error organisation blocks VAT61 Variable table data block 61 (Values NEMO 1 (internal version) ) VAT62 Variable table data block 62 (Values NEMO 2 (internal version) ) VAT70 Variable table data block 70 (Values NEMO 1 (external version) ) VAT71 Variable table data block 71 (Values NEMO 2 (external version) ) VAT80 Variable table instance data block 80 VAT96 Variable table input / output status decentralised peripheral byte The project NEMO MANAGER is made for a PLC type SIMATIC S DP. This project runs in combination with 1 Profibus NEMO (int.) without any changes. Other constellations must be arranged in the FB10 / 11. In the organisation block OB1 the management function FB11 is called (for NEMO internal version). The function block FB10 (NEMO management ext.) contains 2 calls for a net constellation 1 external interface with 2 NEMOS. It shows the working of the release bits. When it is necessary to change the CPU due to another type, it is to check whether the mark byte MB1 is available as the clock byte in CPU hardware parameterisation, because the mark bit M1.5 is used for the 1 sec clock pulse.
COMMUNICATION MODBUS PROTOCOL
COMMUNICATION MODBUS PROTOCOL MFD4E06 - NEMO-D4e PR146 08/03/2018 Pag. 1/16 CONTENTS 1.0 ABSTRACT... 2 2.0 DATA MESSAGE DESCRIPTION... 3 2.1 Parameter description... 3 2.2 Data format... 4 2.3 Description
More informationCOMMUNICATION MODBUS PROTOCOL MF96001 / 021 NEMO 96HD
COMMUNICATION MODBUS PROTOCOL MF96001 / 021 NEMO 96HD PR106 20/10/2016 Pag. 1/31 Contents 1.0 ABSTRACT... 2 2.0 DATA MESSAGE DESCRIPTION... 3 2.1 Parameters description... 3 2.2 Data format... 4 2.3 Description
More informationCE4DMID01 COMMUNICATION PROTOCOL CONTENTS 1.0 INTRODUCTION
11/11/2011 Pagina 1 di 11 ELECTRICITY ENERGY METER FIRMWARE 1.3 CE4DMID01 COMMUNICATION PROTOCOL CONTENTS 1.0 INTRODUCTION 2.0 DATA MESSAGE DESCRIPTION 2.1 Data field description 2.2 Data format 2.3 Description
More informationSommario. COMMUNICATION PROTOCOL PR 150 Rev. A 31/01/2018 Pag 1 Multifunction Firmware NEMO 96 EA ModBus
31/01/2018 Pag 1 Sommario 1. ABSTRACT... 2 1.1. 1.2. Physical level... 2 Data link level... 2 1.3. Application level... 2 2. DATA MESSAGE DESCRIPTION... 3 2.1. Parameters description... 3 2.2. Data format...
More informationCOMMUNICATION MODBUS PROTOCOL
COMMUNICATION MODBUS PROTOCOL BOZZA_V04 Conto D6-Pd 05/12/2017 Pag. 1/15 CONTENTS 1.0 ABSTRACT... 2 2.0 DATA MESSAGE DESCRIPTION... 3 2.1 Parameters description... 3 2.2 Data format... 4 2.3 Description
More informationCOMMUNICATION MODBUS PROTOCOL
COMMUNICATION MODBUS PROTOCOL CE4DMID31 / CE4DMID21 CONTO D4 Pd MID PR123 20/10/2016 Pag. 1/9 Contents 1.0 ABSTRACT... 2 2.0 DATA MESSAGE DESCRIPTION... 3 2.1 Parameters description... 3 2.2 Data format...
More informationCOMMUNICATION MODBUS PROTOCOL
COMMUNICATION MODBUS PROTOCOL CE4DT36 CONTO D4 Pd (3-single phase) PR134 20/10/2016 Pag. 1/11 Contents 1.0 ABSTRACT... 2 2.0 DATA MESSAGE DESCRIPTION... 3 2.1 Parameters description... 3 2.2 Data format...
More informationCOMMUNICATION M-BUS PROTOCOL PR 118
COMMUNICATION M-BUS PROTOCOL PR 118 CE4DT CONTO D4 Pd 03/01/2017 Pag. 1/27 CONTENTS 1. Standard M-Bus telegrams (Mb2) 2 1.1 Request for Data (REQ_UD2 ) 2 1.2 Details of telegrams 1,2,3 6 1.2.1 Telegram
More informationUser manual PROFIBUS C/Q 15/96 MCU
Page 1 of 12 SUMMARY 1. DESCRIPTION.... 2 2. AVAILABLE VARIABLES... 3 3. MODULES DESCRIPTION... 5 4. PROFIBUS WIRING... 10 5. ADDRESS SETTING.... 10 6. STATUS LED INDICATIONS... 11 7. TROUBLE SHOOTING...
More informationMIC-2 MKII, Multi-instrument DATA SHEET
MIC-2 MKII, Multi-instrument DATA SHEET Measurements All 3-phase AC measurements True RMS 4-Quadrant energy Power Quality Analysis Replaces analogue meters RS-485 Modbus RTU protocol TCP/IP Modbus (optional)
More informationEM210 COMMUNICATION PROTOCOL. Version 3 Revision 3
EM210 COMMUNICATION PROTOCOL Version 3 Revision 3 November 13 th, 2015 Index 1.1 Introduction... 3 1.2 MODBUS functions... 3 Function 03h (Read Holding Registers)... 3 Function 04h (Read Input Registers)...
More informationMIC-2 MKII & MIC-2 MKII DIN, Multi-instrument DATA SHEET
& DIN, Multi-instrument DATA SHEET Measurements All 3-phase AC measurements True RMS 4-Quadrant energy Power Quality Analysis Replaces analogue meters RS-485 Modbus RTU protocol TCP/IP Modbus (optional)
More informationA2000 Multifunctional Power Meter Profibus Interface
Interface Description A2000 Multifunctional Power Meter Profibus Interface 3-349-092-03 12/1.10 Contents 1 General Information... 3 1.1 Interface Hardware...3 1.2 Communications Protocol...4 2 Telegram
More informationConnecting UniOP to Simatic S7 Profibus
Connecting UniOP to Simatic S7 Profibus This Technical Note contains all the information required to connect the UniOP panels to a Profibus DP system with a Simatic S7 master and to take advantage from
More informationMIC-2 Multi-instrument DATA SHEET
Measurements All 3-phase AC measurements True RMS 4-Quadrant energy Power Quality Analysis Replaces analogue meters RS-485 Modbus RTU protocol TCP/IP Modbus (optional) Profibus DP (optional) I/O modules
More informationEM300 Series. ET300 Series
EM300 Series and ET300 Series COMMUNICATION PROTOCOL Version 2 Revision 11 Index 1.1 Introduction... 3 1.2 MODBUS functions... 3 1.2.1 Function 03h (Read Holding Registers)... 3 1.2.2 Function 04h (Read
More informationGNM3D Series COMMUNICATION PROTOCOL. Version 1 Revision 0
GNM3D Series COMMUNICATION PROTOCOL Version 1 Revision 0 Index 1.1 1.2 Introduction... 3 MODBUS functions... 3 1.2.1 Function 03h (Read Holding Registers)... 3 1.2.2 Function 04h (Read Input Registers)...
More informationC192PF8-RPR. Power Factor Manager & Reactive Power Regulator Reference Guide. Modbus. Communications Protocol. BG0348 Rev. A1
C192PF8-RPR Power Factor Manager & Reactive Power Regulator Reference Guide Modbus Communications Protocol BG0348 Rev. A1 C192PF8-RPR POWER FACTOR MANAGER AND REACTIVE POWER REGULATOR COMMUNICATIONS Modbus
More informationCDN Series Displays with Profibus-DP ELEN UNI-TXT (ND) protocol PARAMETRIZATION OF PROFIBUS-DP COMMUNICATION INTERFACE
CDN Series Displays with Profibus-DP ELEN UNI-TXT (ND) protocol PARAMETRIZATION OF PROFIBUS-DP COMMUNICATION INTERFACE ELEN, s.r.o. NDI Display Profibus DP UNI TXT(ND) CONTENT Page 2 of 12 1. Introduction...
More informationEM24-DIN PFA, PFB & X models
EM24-DIN PFA, PFB & X models COMMUNICATION PROTOCOL Version 4 Revision 0 December 03 th, 2012 Index 1.1 Introduction...3 1.2 MODBUS functions...3 1.2.1 Function 03h (Read Holding Registers)...3 1.2.2 Function
More informationPM290 POWERMETER. Communication Protocols ASCII & Modbus Reference Guide
PM290 POWERMETER Communication Protocols ASCII & Modbus Reference Guide PM290 Communication Protocols Communication protocol is a method of transferring information between different devices (i.e., the
More informationImplementation of the Identification System IRI-KHD2-4HB6 to a SIMATIC S PLC
Implementation of the Identification System IRI-KHD2-4HB6 to a SIMATIC S-7 400 PLC Side 1 of 13 Contents 1 Hardware Specification... 3 1.1 Equipment and Devices... 3 1.2 Configuration and Installation...
More informationEM210 COMMUNICATION PROTOCOL. Version 3 Revision 1
EM210 COMMUNICATION PROTOCOL Version 3 Revision 1 June 4 th, 2014 Index 1.1 Introduction...3 1.2 MODBUS functions...3 Function 03h (Read Holding Registers)...3 Function 04h (Read Input Registers)...4 Function
More informationConto D2 COMMUNICATION PROTOCOL CONTENTS 1.0 INTRODUCTION
PR 121 rev. 0 11/11/2011 Pagina 1 di 9 ELECTRICITY ENERGY METER FIRMWARE 1.6 Conto D2 COMMUNICATION PROTOCOL CONTENTS 1.0 INTRODUCTION 2.0 DATA MESSAGE DESCRIPTION 2.1 Data field description 2.2 Data format
More informationGNM3D M-BUS COMMUNICATION PROTOCOL. Revision 1
GNM3D M-BUS COMMUNICATION PROTOCOL Revision 1 Index 1.1 1.2 Introduction... 3 M-BUS functions... 3 1.2.1 Single control character procedure SND_NKE... 3 1.2.2 Request/Respond Procedure (REQ/RSP)... 4 1.2.3
More informationEM21 COMMUNICATION PROTOCOL. Version 1 Revision 0
EM21 COMMUNICATION PROTOCOL Version 1 Revision 0 April 7 th, 2008 Index 1.1 Introduction...3 1.2 MODBUS functions...3 1.2.1 Function 03h (Read Holding Registers)...3 1.2.2 Function 04h (Read Input Registers)...4
More informationEM24-DIN COMMUNICATION PROTOCOL. Version 3 Revision 1
EM24-DIN COMMUNICATION PROTOCOL Version 3 Revision 1 July 15 th, 2008 Index 1.1 Introduction... 3 1.2 MODBUS functions... 3 1.2.1 Function 03h (Read Holding Registers)...3 1.2.2 Function 04h (Read Input
More informationPM130 Powermeters Reference Guide ASCII Communications Protocol
PM130 Powermeters Reference Guide ASCII Communications Protocol BG0309 Rev. A1 SERIES PM130 POWERMETERS COMMUNICATIONS ASCII Communications Protocol REFERENCE GUIDE Every effort has been made to ensure
More informationPM130 Powermeters Reference Guide Modbus Communications Protocol
PM130 Powermeters Reference Guide Modbus Communications Protocol BG0310 Rev. A1 SERIES PM130 POWERMETERS COMMUNICATIONS Modbus Communications Protocol REFERENCE GUIDE Every effort has been made to ensure
More informationSERIES PM130EH POWERMETERS COMMUNICATIONS REFERENCE GUIDE
SERIES PM130EH POWERMETERS COMMUNICATIONS ASCII Communications Protocol REFERENCE GUIDE Every effort has been made to ensure that the material herein is complete and accurate. However, the manufacturer
More informationEM271 COMMUNICATION PROTOCOL. Version 0 Revision 0
EM271 COMMUNICATION PROTOCOL Version 0 Revision 0 May 12 th, 2014 Index 1.1 Introduction... 3 1.2 MODBUS functions... 3 1.2.1 Function 03h (Read Holding Registers)... 3 1.2.2 Function 04h (Read Input Registers)...
More informationCOMMUNICATION M-BUS PROTOCOL CE4DMID0M (MBus meter)
COMMUNICATION M-BUS PROTOCOL CE4DMID0M (MBus meter) PR144 Rev A Fw. Version 2.00 16/02/2018 Pag. 1/17 1. Standard M-Bus telegrams... 3 1.1 Request for Data (REQ_UD2 )... 3 1.2 Details of telegrams 1,2,3...
More informationEM26-96 COMMUNICATION PROTOCOL. Version 1 Revision 0
EM26-96 COMMUNICATION PROTOCOL Version 1 Revision 0 February 5 th, 2007 Index 1.1 Introduction...3 1.2 MODBUS functions...3 1.2.1 Function 03h (Read Holding Registers)... 3 1.2.2 Function 04h (Read Input
More informationNEMO HD MULTI-FUNC METER BASE (MF96001)
NEMO HD MULTI-FUNC METER BASE (MF96001) Quick and easy to install Compact modern design High accuracy monitoring and measurement to IEC 62053-21 Easy to read and configure Options for remote communication
More informationEM270 COMMUNICATION PROTOCOL. Version 1 Revision 0
EM270 COMMUNICATION PROTOCOL Version 1 Revision 0 October 4 th, 2013 Index 1.1 Introduction... 3 1.2 MODBUS functions... 3 1.2.1 Function 03h (Read Holding Registers)... 3 1.2.2 Function 04h (Read Input
More informationGNM1D M-BUS COMMUNICATION PROTOCOL. Revision 0
GNM1D M-BUS COMMUNICATION PROTOCOL Revision 0 Index 1.1 1.2 Introduction... 3 M-BUS functions... 3 1.2.1 Single control character procedure SND_NKE... 3 1.2.2 Request/Respond Procedure (REQ/RSP)... 4 1.2.3
More informationDNP3 Communications Protocol
Powermeter and Power Quality Analyzer PM174 DNP3 Communications Protocol Reference Guide BG0413 Rev. A3 Every effort has been made to ensure that the material herein is complete and accurate. However,
More informationAutomating with STEP 7 in STL
Automating with STEP 7 in STL SIMATICS 7-300/400 Programmable Controllers by Hans Berger Publicis MCD Verlag Contents Introduction 16 1 SIMATIC S 7-300/400 Programmable Controller 17 1.1 Structure of the
More informationOption H3 Serial communication Profibus DP
MULTI-LINE 2 DESCRIPTION OF OPTIONS Option H3 Serial communication Profibus DP Description of option Functional description Parameters Data tables Document no.: 4189340443H Multi-line 2 Option H3, Serial
More information8 data bits, least significant bit sent first 1 bit for even/odd parity (or no parity) 1 stop bit if parity is used; 1 or 2 bits if no parity
1 Eastron SDM630 Smart Meter Modbus Protocol Implementation V1.2 1.1 Modbus Protocol Overview This section provides basic information for interfacing the Eastron Smart meter to a Modbus Protocol network.
More informationEM24-DIN COMMUNICATION PROTOCOL. Version 3 Revision 0
EM24-DIN COMMUNICATION PROTOCOL Version 3 Revision 0 March 25 th, 2008 Index 1.1 Introduction...3 1.2 MODBUS functions...3 1.2.1 Function 03h (Read Holding Registers)...3 1.2.2 Function 04h (Read Input
More informationEM111-EM112 M-BUS COMMUNICATION PROTOCOL. Revision 4.0
EM111-EM112 M-BUS COMMUNICATION PROTOCOL Revision 4.0 Index 1.1 Introduction...3 1.2 M-BUS functions...3 1.2.1 Single control character procedure SND_NKE...3 1.2.2 Request/Respond Procedure (REQ/RSP)...4
More informationTECHNICAL NOTES By6150-S-485 MODBUS J BUS Communication
By6150-S-485 MODBUS J BUS Communication By6150-S-485_MODBUS COMMUNICATIONS_Rev 1.doc 09.04.2014 1/9 General descriptions 1RAEM4CS485 speaks using the MODBUS protocol managed in RTU (and JBUS) mode. 3 Function
More informationPowerLogic ION6200 Serial Communications Protocol and ION / Modbus Register Map
70022-05-XX PROTOCOL DOCUMENT 04/2007 PowerLogic ION6200 Serial Communications Protocol and ION / Modbus Register Map This document explains the Modbus protocol on the ION6200 meter. The ION6200 meter
More informationPowerLogic ION7300 Profibus DP. Serial Communications Protocol October 2006
PowerLogic ION7300 Profibus DP Serial Communications Protocol October 2006 The information contained in this document is believed to be accurate at the time of its publication; however, assumes no responsibility
More information1.Eastron SDM530-Modbus Smart Meter Modbus Protocol Implementation V1.1
1.Eastron SDM530-Modbus Smart Meter Modbus Protocol Implementation V1.1 1.1 Modbus Protocol Overview This section provides basic information for interfacing the Eastron Smart meter to a Modbus Protocol
More information1.Eastron SDM230Modbus Smart Meter Modbus Protocol Implementation V1.2
1.Eastron SDM230Modbus Smart Meter Modbus Protocol Implementation V1.2 1.1 Modbus Protocol Overview This section provides basic information for interfacing the Eastron Smart meter to a Modbus Protocol
More informationU niversal Measuring Device UMG 96 S. Little Fieldbus Giant. Modbus / Profibus. Harmonics. Memory. Analogue outputs. Digital I/O
U niversal Measuring Device Little Fieldbus Giant Modbus / Profibus Harmonics Memory Analogue outputs Digital I/O Modem Recorder Profibus Modbus PC I/O Universal Measuring Device Application Application
More informationEM100 Series and ET100 Series
EM100 Series and ET100 Series COMMUNICATION PROTOCOL Version 2 Revision 6 Index 1.1 1.2 Introduction... 3 MODBUS functions... 3 1.2.1 Function 03h (Read Holding Registers)...3 1.2.2 Function 04h (Read
More informationIF96017 MODBUS COMMUNICATION PROTOCOL
CONTENTS 1.0 ABSTRACT 04/07/14 Pagina 1 di 9 MULTIFUNCTION FIRMWARE 1.00 COMMUNICATION PROTOCOL IF96017 MODBUS COMMUNICATION PROTOCOL 2.0 DATA MESSAGE DESCRIPTION 2.1 Parameters description 2.2 Data format
More informationMultiCube. Modbus Data Tables. August Northern Design (Electronics) Ltd Bradford UK
MultiCube Modbus Data Tables August 2005 Modbus Data Tables Northern Design (Electronics) Ltd Bradford UK 1. Introduction This document is intended as a supplement to the MultiCube Modbus Options Installation
More informationINSTRUCTION MANUAL RVT communication How to use RS485 USB Ethernet RVT connections
INSTRUCTION MANUAL RVT communication How to use RS85 USB Ethernet RVT connections Table of contents 1 Introduction to the controller... 1.1 Intended audience... 1.2 Before you start... 1.3 How to use this
More informationSPM33. MODBUS Protocol and register List V1.5
SPM33 MODBUS Protocol and register List V1.5 ZHUHAI PILOT TECHNOLOGY CO.,LTD 目 录 1. Introduction... 1 1.1 Purpose of the Communication Protocol... 1 1.2 Version of Communication Protocol... 1 2. Detailed
More informationDRS-100-3P MID Energy Meter Direct Connect, 100A, Three phase Communications Guide
DRS-100-3P MID Energy Meter Direct Connect, 100A, Three phase Communications Guide Contents 1 DRS-100-3P - Modbus Protocol Implementation 3 1.1 Modbus Protocol Overview 3 1.2 Modbus Protocol Input Registers
More informationSKD-005-M Protocol. 2 RS485 General Information 2.1 Half Duplex 2.2 Connecting the Instruments 2.3 A and B terminals 2.
Controlin BV Glasblazerstraat 1 2984 BL Ridderkerk Customer Service: +31 (0)180 330 522 www.controlin.nl SKD-005-M Protocol 1. SKD-005-M Protocol Implementation 1.1 Modbus Protocol Overview 1.2 Input register
More informationInterface Definition RISH EM 2340/1320/30/ _Rev. D - 8/2016
Interface Definition RISH EM 2340/1320/30/40 1 2-60-006-00-00494_Rev. D - 8/2016 2 Section DIGITAL MULTIFUNCTION INSTRUMENT Contents 1. Introduction Programmable Multi-function Energy Meter Installation
More informationSERIES PM296/RPM096 POWERMETERS COMMUNICATIONS REFERENCE GUIDE
SERIES PM296/RPM096 POWERMETERS COMMUNICATIONS ASCII Communications Protocol REFERENCE GUIDE Every effort has been made to ensure that the material herein is complete and accurate. However, the manufacturer
More informationU niversal Measuring Device NEW! UMG 96 S. Little Fieldbus Giant. Modbus / Profibus. Harmonics. Memory. Analogue outputs.
U niversal Measuring Device NEW! Little Fieldbus Giant Modbus / Profibus Harmonics Memory Analogue outputs Digital I/O Modem Recorder Profibus Modbus PC I/O Universal Measuring Device Application Application
More informationA2000 Multifunctional Power Meter
3-348-980-03 3/12.99 Capable of communications via Profibus-DP, LONWORKS interface or RS 485 interface (depending upon model) Measurement of current, voltage, active, reactive and apparent power, power
More informationDevice manual Profibus encoder. RM30xx RN30xx /00 06/2013
Device manual Profibus encoder RM30xx RN30xx 706355/00 06/2013 Contents 1 Preliminary note................................................. 4 1.1 Symbols used...............................................
More informationRM30xx Profibus Brief instructions efector400
RM30xx Profibus Brief instructions efector400 706414/00 Page 1 of 14 ifm efector gmbh Contents The description may contain deviations from the user system, because different manufacturers or software versions
More informationEMS_ _Measure_MonoPh_R_2P_ModbusTable_LG_EN_v1.01.xlsx
EMS_ 19 19_Measure_MonoPh_R_2P_ModbusTable_LG_EN_v1.01.xlsx GENERAL MODBUS TABLE ORGANIZATION Starting of the Group Starting of the Group System Version System Version Group Name (Text) Group Code Group
More informationStart-up of IRI-KHD2-4HB6, IRI-KHA6-4HB6 at S7-300 V1.2. Table of Contents TABLE OF CONTENTS... 1
Table of Contents TABLE OF CONTENTS... 1 1. DESCRIPTION OF HARDWARE... 2 1.1 Modules and devices... 2 1.2 Set-up and installation... 2 2. HARDWARE CONFIGURATION... 2 2.1 Installation of the GSE file...
More informationCPU. Switch 1 Switch 2
10BaseT Overview Data Sheets F 8626 F 8626: Communication Module for Profibus-DP- Communication Application in H51q PLCs (usable with BS41q/51q V7.0-7 (9835) and higher) with ELOP II-NT. General Description
More informationDevice manual Supplement. S7 library for evaluation unit DTE / / 2012
Device manual Supplement S7 library for evaluation unit DTE100 706146 / 00 04 / 2012 Contents 1 Preliminary note................................................. 3 1.1 Symbols used...............................................
More informationTraining Document for Comprehensive Automation Solutions Totally Integrated Automation (T I A) MODULE E09. PROFINET with 2x CPU 315F-2 PN/DP
Training Document for Comprehensive Automation Solutions Totally Integrated Automation (T I A) MODULE PROFINET with 2 x CPU 315F-2 PN/DP T I A Training Document Page 1 of 45 Module This document has been
More informationMODBUS APPLICATION MANUAL DKM-411
MODBUS APPLICATION MANUAL DKM-411-1 - COPYRIGHT NOTICE Any unauthorized use or copying of the contents or any part of this document is prohibited. This applies in particular to trademarks, model denominations,
More informationDKM-407 DIN RAIL TYPE NETWORK ANALYZER
DKM-407 User Manual DKM-407 DIN RAIL TYPE NETWORK ANALYZER DESCRIPTION The DKM-407 is a DIN rail mounted precision and low cost unit allowing measurement and remote monitoring of AC parameters of a distribution
More informationConto D1 MODBUS COMMUNICATION PROTOCOL
ENERGY METER Conto D1 MODBUS COMMUNICATION PROTOCOL 4/03/15 Pagina 1 di 7 FIRMWARE CONTENTS 1.0 ABSTRACT 2.0 DATA MESSAGE DESCRIPTION 2.1 Parameters description 2.2 Data format 2.3 Description of CRC calculation
More informationSoftstarters. Type PSTX Fieldbus communication, Anybus Modbus TCP. 1SFC132087M0201 March SFC132087M0201 1
Softstarters Type PSTX Fieldbus communication, Anybus Modbus TCP 1SFC132087M0201 March 2015 1SFC132087M0201 1 1 Modbus TCP The Modbus protocol is a fieldbus protocol that provides full control and status
More informationData sheet CC 03, Commander Compact (603-1CC21)
Data sheet CC 03, Commander Compact (603-1CC21) Technical data Order. Type 603-1CC21 CC 03, Commander Compact General information Note - Features Display: 2 x 20 characters Interface: MP²I User memory:
More informationFNL Modbus TCP Interface
FNL Modbus TCP Interface Users Manual V0.1 17.06.2009 Project No.: 5304 Doc-ID.: FNL Modbus TCP Interface-UM-V0.1 Status: Released COMSOFT d:\windoc\icp\doku\hw\fnl\modbus tcp\version_0.1\fnl_modbus_tcp_e.doc
More informationPQM - Power Quality Monitoring
UMG 96S PQM - Power Quality Monitoring The little field bus giant Universal flush-mounting measuring instruments of the UMG 96S product family are mainly designed for use in low and medium voltage distribution
More informationSoftstarters. Type PSTX Fieldbus communication, Fieldbus Plug Modbus RTU. 1SFC132092M0201 June SFC132092M0201 1
Softstarters Type PSTX Fieldbus communication, Fieldbus Plug Modbus RTU 1SFC132092M0201 June 2017 1SFC132092M0201 1 1 Modbus RTU The Modbus protocol is a fieldbus protocol that provides full control and
More informationSmart Energy & Power Quality Solutions. UMG 96S Universal flush-mounting measuring instrument
Smart Energy & Power Quality Solutions UMG 96S Universal flush-mounting measuring instrument UMG 96S UMG 96S Universal flushmounting measuring instrument Universal flush-mounting measuring instruments
More informationEM24_E1. (Ethernet) COMMUNICATION PROTOCOL. Version 0 Revision 1.2
EM24_E1 (Ethernet) COMMUNICATION PROTOCOL Version 0 Revision 1.2 Index 1 INTRODUCTION... 3 1.1 1.2 Introduction... 3 Modbus functions... 3 1.2.1 Function 03h (Read Holding Registers) and 04h (Read Input
More informationE 1. SPECOM - Network analyser. Content. E.2 Description. E.3 Specom C - Technical data. E.4 Specom M - Technical data. E.5 Data communication
SPCOM - Network analyser Content.2 Description.3 Specom C - Technical data.4 Specom M - Technical data.5 Data communication.5 Converter RS 485/232.5 Specom L - xploitation software The SPCOM network analyser
More informationBLR-CM Modbus. Technical Documentation. Technical Documentation. Rev BLR-CM Modbus. Beluk GmbH Taubenstrasse Schongau Germany
Beluk GmbH Taubenstrasse 1 86956 Schongau Germany Tel.: +49/(0)8861/2332-0 Fax: +49/(0)8861/2332-22 E-Mail: blr@beluk.de Web: http://www.beluk.de Document history Date Name Revision Comment 08.11.06 ATh
More informationIntegra Ri3 Digital Meters. Communications Guide
Integra Ri3 Digital Meters Communications Guide Contents Crompton Instruments 1 Integra Ri3 Digital Meter Modbus Protocol implementation 3 1.1 Modbus Protocol Overview 3 1.2 Input Registers 3 Ri3 Input
More informationData Sheet. Digital Multifunctional Power Meter with LCD Display and Optional Modules WPM D
WPM 770 Data Sheet 679.D.141.02 Digital Multifunctional Power Meter with LCD Display and Application The digital Weigel Power Meters WPM 770 have been designed to display the electrical parameters in low
More informationIntegra, INT-0220 and INT-0230 (MID) Power Measurement Digital Metering System Communications Guide
Integra, INT-0220 and INT-0230 (MID) Power Measurement Digital Metering System Communications Guide Contents 1 INTEGRA INT-0230 - Modbus Protocol Implementation 3 1.1 Modbus Protocol Overview 3 1.2 Modbus
More informationOptidrive Applications Support Library
Optidrive Applications Support Library Application Note Title AN-ODE-3-038 Related Products Optidrive E3 Overview Level 3 Modbus RTU Control and Register Mapping 1 Fundamental - No previous experience
More informationCONTO IMP PROTOCOL COMMUNICATION CONTENTS 1.0 INTRODUCTION
7/02/12 Pagina 1 di 14 PULSE MANAGER FIRMWARE 1.01 CONTO IMP PROTOCOL COMMUNICATION CONTENTS 1.0 INTRODUCTION 2.0 DATA MESSAGE DESCRIPTION 2.1 Data field description 2.2 Data format 2.3 Description of
More informationTechnical Documentation
BLR-CM - MODBUS Technical Documentation BLR-CM MODBUS Beluk GmbH Tel.: +49/(0)8861/2332-0 Fax: +49/(0)8861/2332-22 e-mail: blr@beluk.de http://www.beluk.de BLR-CM - MODBUS Page 2 of 20 Document history
More informationUsing power measurement module with TIA A500671
Application Note Building Automation TIA Using power measurement module 750-495 with TIA A500671 2 Application Note A500671 2016 by WAGO Kontakttechnik GmbH & Co. KG All rights reserved. WAGO Kontakttechnik
More informationPM210v Multi-Function Panel Meter. Modbus Reference. DAE Instrument Corp.
DAE Instrument Corp. v312 11 Multi- Panel Meter Modbus Reference Revision 2.6.1e Updated 2015/1/22 Prepared By: David Ling Firmware: v312 Table of Contents General Information! 3 Register Tables! 4 Real
More informationMPR-4 SERIES NETWORK ANALYSER USER MANUAL
MPR-4 SERIES NETWORK ANALYSER USER MANUAL INDEX SAFETY AND WARNINGS... 3 Warning... 3 Safety... 3 Warranty... 3 OPERATING CONDITIONS... 4 INTRODUCTION... 5 General Features... 5 Applications... 6 MPR-4
More informationSoftstarters. Type PSTX Fieldbus communication, Fieldbus Plug Modbus RTU
Softstarters Type PSTX Fieldbus communication, Fieldbus Plug Modbus RTU 1SFC132092M0201 July 2014 1 Modbus RTU The Modbus protocol is a fieldbus protocol that provides full control and status information
More informationDRT-205C M-Bus Protocol V1.1
DRT-205C M-Bus Protocol V1.1 Initialization slave Format: Start C A Check Sum Stop XX=1 to FF 10 40 XX CS 16 Parse of the primary address: The address field serves to address the recipient in the calling
More informationUser Manual. KE-Relay or KD-Relay Profibus DPV0 Communication Module. Page 1 / 18. KE-PROFI-DP0 Version (NE_NC-KE-PROFI-DP0_MAN_01_10_FN04)
Page 1 / 18 KE-Relay or KD-Relay Profibus DPV0 Communication Module User Manual Version 01.04 (NE_NC-_MAN_01_10_FN04) 28 June 2010 NewElec Pretoria (Pty) Ltd Head Office: c/o 298 Soutter street & Maltzan
More informationData sheet VIPA CPU 115DP (115-6BL22)
Data sheet VIPA CPU 115DP (115-6BL22) Technical data Order no. Type 115-6BL22 VIPA CPU 115DP General information Note - Features Work memory [KB]: 16 Load memory [KB]: 24 Onboard 16x DI / 12x DO / 4x DIO
More informationPROFIBUS DP/CAN Gateway PCA-100. User Manual
PCA-100 REV 4.0 SiboTech Automation Co., Ltd. Technical Support: 021-5102 8348 E-mail: support@sibotech.net Catalog 1 Introduction... 2 1.1 About This Instruction... 2 1.2 Copyright... 2 1.3 Related Products...
More informationAP25-3DO PROTOCOL. Modbus Guide - Issue 1.0 SUBJECT TO CHANGE WITHOUT NOTICE
MODBUS PROTOCOL IMPLEMENTATION AP25-3DO www.sifamtinsley.co.uk NEW PRODUCT Multifunction Meters Transducers & Isolators Temperature Controllers Converters & Recorders Digital Panel Meters Current Transformers
More informationMains Monitoring Instruments 4
The power quality of the electrical supply networks plays an increasingly important role for the operational safety of electrical installations and equipment. Therefore it becomes more and more important
More informationVERIS H8035 and H8036
VERIS H8035 and H8036 MODBUS IMPLEMENTATION SPECIFICATION OVERVIEW This document describes the implementation of Modbus protocol used in the Veris H8035 and H8036 power meters. It is intended to assist
More informationSoftstarters. Type PSTX Fieldbus communication, Fieldbus Plug Profibus DPV0/DPV1. 1SFC132091M0201 June SFC132091M0201 1
Softstarters Type PSTX Fieldbus communication, Fieldbus Plug Profibus DPV0/DPV1 1SFC132091M0201 June 2017 1SFC132091M0201 1 1 Profibus The Profibus protocol is a fieldbus protocol that provides full control
More informationINTEGRA DIGITAL METERING SYSTEMS
CROMPTON INSTRUMENTS INTEGRA DIGITAL METERING SYSTEMS INTEGRA DIGITAL METERING SYSTEMS The Integra digital metering product portfolio offers an extensive range of systems designed to suit any power monitoring
More informationSMARTRAIL X100 Protocol
Smart Process & Control Ltd 11 Totman Close Brook Road Industrial Estate Rayleigh, Essex SS6 7UZ Customer Service: 01268 773422 www.smartprocess.co.uk SMARTRAIL X100 Protocol 1. SMARTRAIL X100 Protocol
More informationPACSystems* RX3i IC695PBM300
June 2010 PACSystems* RX3i IC695PBM300 PROFIBUS Master Module The PACSystems * RX3i PROFIBUS Master Module, IC695PBM300, allows the RX3i CPU to send and receive data on a PROFIBUS-DP network. The IC695PBM300
More informationPQM - Power Quality Monitoring
UMG 511 PQM - Power Quality Monitoring Class A power quality analyser according to IEC61000-4-30 The UMG 511 power quality analyser is particularly suitable for monitoring power quality according to standards
More information