© KROHNE 09/2008 7.30855.35.
ALTOSONIC V TABLE OF CONTENTS 1 INTRODUCTION TO MODBUS.................................................................................................... 5 2 SERIAL TRANSMISSION FORMAT ............................................................................................ 6 2.1 ASCII-MODE ................................................................................................................................... 6 2.2 RTU-MODE .................................................................
ALTOSONIC V 8.8 FIELD 6 (READ ONLY ASCII FIELD 8 CHARACTERS) ........................................................................ 49 8.9 FIELD 6 (READ W RITE ASCII FIELD 16 CHARACTERS)..................................................................... 49 8.10 EXPLANATION OF DATA AVAILABLE TO MODBUS ......................................................................... 51 8.11 THE SYSTEM MESSAGES ........................................................................................................
ALTOSONIC V INTRODUCTION This manual describes how to use the Modbus protocol with the ALTOSONIC V flow meter system. Product Liability and warranty Responsibility for suitability and intented use of these ultrasonic flowmeters rests solely with the operator. Improper installation and operation of the flowmeters (systems) may lead to loss of warranty. In addition, the “General conditions of sale” forming the basis of the purchase contract are applicable.
ALTOSONIC V 1 INTRODUCTION TO MODBUS From this point in the manual the following abbreviations are used for the ALTOSONIC-V system: UFS-V: Ultrasonic Flow Sensor (primary flow meter body) UFC-V: Ultrasonic Flow Converter (5 converters) UFP-V: Ultrasonic Flow Processor Introduction to Modbus For communication with host systems the flow controller emulates a Modbus compatible controller.
ALTOSONIC V 2 SERIAL TRANSMISSION FORMAT The two transmission modes used are called: 1. ASCII, and 2. RTU. The user has to select the desired mode along with the serial communication parameters (baud rate, parity-type). Note that all these parameters must be the same for all controllers in the network. 2.1 • • • ASCII-mode Each byte of the message is sent as two ASCII characters. This means only the ASCII characters 0-9, A-F are transmitted.
ALTOSONIC V 3 MODBUS MESSAGE FRAMING ASCII-mode In ASCII-mode a message starts with a colon character (:) and ends with a carriage return–linefeed. Intervals up to one second can elapse between characters within the message. If the interval is longer, a timeout error occurs and the message is rejected. RTU mode In RTU-mode a message starts with a silent interval of at least 3.5 character times. The entire message frame must be transmitted as a continuous stream. If a silent interval of more than 3.
ALTOSONIC V In ASCII mode this byte is made of 2 ASCII characters. The data field of messages contains information which both master and slave use to perform an action. This includes the register address, quantity of registers, and the necessary data. 3.4 The Error Checking Field The error checking field contents depend on the transmission mode. Two kinds of error methods are used. Error check with ASCII-mode When the ASCII mode is used, the error-checking field contains two ASCII characters.
ALTOSONIC V 4 PHYSICAL COMMUNICATION LAYER The Modbus protocol is a half-duplex protocol. The physical layer can be half or full duplex. The Modbus driver supports both half (RS485) and full (RS232/RS422) duplex communication layers. In case of RS485, the parameter 3.8 MODBUS_UART_HALF_DUPLEX must be turned on. The transmitter is activated when the UFP-V transmits data. The RS485 receiver may not be disabled e.g. the transmitted data must also be received by the UFPV for correct functioning! 4.
ALTOSONIC V 5 SUPPORTED FUNCTIONS All data addresses in Modbus messages are referenced to zero. For example: • Coil 1 is addressed as Coil 0000. • Holding register 40001 is addressed as 0000. Note that the function code specifies the operation of a ‘holding register’, therefore the 4xxxx reference is implicit. When functions which do not support broadcast requests, are accessed with a broadcast address, the request will be rejected. 5.
ALTOSONIC V Note how the three remaining bits (toward the high order end) are zero-filled. If the request is not applicable an exception response will be sent. See chapter 5.10 for exception responses. 5.2 Function 02: READ INPUT STATUS In the UFP-V Modbus protocol, function 1 and 2 perform the same processing and are interchangeable. 5.3 Function 03: READ MULTIPLE HOLDING REGISTERS Description Function 3 reads the binary contents of holding registers (4X references) in the slave.
ALTOSONIC V 5.4 Function 04: READ INPUT REGISTERS In the UFP-V Modbus protocol, function 3 and 4 perform the same processing and are interchangeable. 5.5 Function 05: WRITE SINGLE COIL Description Function 5 forces a single coil to either ON or OFF (0x reference). When the address is a broadcast, all slaves will process the request. Query The query message specifies the coil reference to be forced. Coils are addressed starting at zero (coil 1 is addressed as zero).
ALTOSONIC V Example Here is an example of a request to preset register 40002 to 00 03 in slave 17. Header Slave Address Function Register Address -- 11(h) 06(h) Hi 00(h) Data Low 01(h) Hi 00(h) Low 03(h) Error Check Trailer -- -- Response is an echo of the query, returned after the register contents have been pre-set.
ALTOSONIC V The next byte transmitted (01) addresses coils 29 and 28, with the least significant bit addressing the lowest coil (28) in this set. Unused bits in the last data byte should be left zero.
ALTOSONIC V 5.10 Exception Responses Except for broadcast messages, a master device expects a normal response, when it sends a query to a slave device. One of the four possible events can occur from the master’s query: 1. If the slave device receives the query without a communication error and can handle the query normally, it returns a normal response. 2. If the slave does not receive the query due to a communication error, no response is returned.
ALTOSONIC V 6 HANDLING OF LARGE DATA TYPES The standard Modbus specification does not explain how data types larger than 16 bits should be handled. The standard Modbus functions to modify holding registers are used for handling larger data types. Function 03 (read multiple holding registers), function 06 (write single holding register), and function 16 (write multiple holding registers) are used to read or modify these data types. In the UFP-V each register-area contains a data type.
ALTOSONIC V 6.1 Floating Point Representation The exponent is biased by 127. The mantissa is 24 bits with the most significant bit 1 (not stored), 23 bit stored. Biased exponent SEEE EEEE 6.2 Mantissa 3 (high) E MMM MMMM Mantissa 2 MMMM MMMM Mantissa 1 (low) MMMM MMMM Double Representation The exponent is biased by 1023. The mantissa is 53 bits with the most significant bit 1 (not stored), 52 bits stored.
ALTOSONIC V The transmit order in both modes: IEEE Normal mode Reversed mode (1) 40h (1) 40h (3) 08h (2) 84h (2) 84h (4) 00h (3) 08h (3) 08h (1) 40h (4) 00h (4) 00h (2) 84h Doubles could be transmitted in two ways: Example The double number 4.125000001862645 will give the IEEE representation. S 0 EXPONENT 100 0000 0001 MANTISSA (1)0000 1000 0000 0000 0000 0000 0000 0010 0000 0000 0000 0000 0000 A biased exponent of 1025 (401 hexadecimal) is exp. 2 A positive sign Mantissa = 4 + 1/8 + 1/536870912.
ALTOSONIC V Another solution is to send the data to the hosts by means of a broadcast. Now all host systems receive the same data. ModBus Manual 0300 rev07 E 7.30855.35.
ALTOSONIC V 7 SET-UP OF THE UFP-V MODBUS DRIVER 7.1 Driver Contents The driver contains: • Standard Modbus protocol according to Modicon. • Simulation of Modbus Master and Slave mode. • ASCII-mode and RTU mode. • Half and full duplex communication layers supported. • Transmitter ON/OFF level select for half-duplex mode. • Seven or eight data bits, Even/Odd/No parity, 1 or 2 stop bits • Extended data type support. • Function 1, 2, 3, 4, 5, 6, 8,15,16 including exception generation. 7.
ALTOSONIC V 7.2.
ALTOSONIC V 7.2.
ALTOSONIC V 7.3 Software set-up Now set-up the software, all the settings for the Modbus driver is done in the file [coms0300.dat]. See also chapter 9.4 Appendix D: Coms0300.dat file 7.3.1 • • • • • • • • • 3.1 MODBUS_UART_BASEADRESS for channel 1 is COM4 this is baseaddress 0x2E8 3.2 MODBUS_UART_INTERRUPT is for COM4 set to interrupt 3. Depends on your application : 3.3 MODBUS_UART_BAUDRATE 1200,2400,4800,9600,19200 3.4 MODBUS_UART_RTS_MODE to 0. Depends on your application : 3.
ALTOSONIC V 7.3.4 The UFP-V as Master The master mode is activated when the parameter 5.1 MODBUS_DEVICE_TYPE=2. For master mode the UFP-V must know what it should send to the connected slave device, therefore the master works with poll blocks. Each poll block defines how a transaction should take place i.e. which slave is addressed, which registers are read or write and how to do it. The maximum number of poll blocks to define is 20. The number of poll blocks to use is set with the parameter 7.
ALTOSONIC V 7.4 What can go wrong? When using RS485, check: • Are the connections between terminal 1 and 4 made? • Are the connections between terminal 2 and 3 made? • Is the terminate resistor placed between 1+4 and 2+3 (only if UFP-V is the end of the line). • Is the jumper set to 485 and not 422? (else the transmitter will continuously be activated and destroy received messages) • Is the polarity correct? Are the lines by accident swapped? • Is the software set to Half Duplex (3.
ALTOSONIC V Example of reading a status flag from an UFP-V in slave mode The status flag is read by the master. 1. If the status flag is active, the master uses this state to perform its actions and sends an acknowledgement to the UFP-V by setting the accompanying ACK_flag to 1. Now the UFP-V updates the status flag with the actual status. Note that in this mode the status flag remains active until the acknowledge is given. 2.
ALTOSONIC V 7.6 How data is written to the float field Field 6 (addresses are default mapped to address 7500) is the read/write field for floats. Current applications for writing to the UFP-V system are: 1. API settings for the parameters used in the UFP-Program for calculating Standard/Mass flow and totals. The addresses used are 7501…7514 for floats and 2068…2069, 2201.. 2214 for Booleans 2.
ALTOSONIC V • • • • • To enable writing to a float field as described in application 1...5, an enable Boolean referring to the application must be written to the xxxxx enable writing data Boolean. For example for application 1 this is Boolean 2201. After writing this Boolean there will be 30 seconds of time to write float data to the application field.
ALTOSONIC V 8 MODBUS MAPPING ASSIGNMENTS The available data is grouped in 9 levels (groups): 1. Gross flow measurement 2. Standard flow measurement 3. Net flow measurement 4. Batching, includes normally the levels 1..3 5. Analysis, diagnostics, quality 6. Control data 7. Used settings (corrections on/of etc) 8. Master meter configuration (direct connection with duty meter) 9. Data measured but not directly used by Altosonic-V, but as an extra service. 8.
ALTOSONIC V 24 B+R Totaliser standard: totaliser reset occurred 2 5 25 B+R Totaliser process: forward totaliser rollover occurred 1 5 26 B+R Totaliser process: reverse totaliser rollover occurred 1 5 27 B+R Totaliser standard: forward totaliser rollover occurred 2 5 28 B+R Totaliser standard: reverse totaliser rollover occurred 2 5 29 B+R Totaliser mass: sum totalizer rollover occurred 2 5 30 B+R Totaliser mass: totalizer reset occurred 2 5 31 B+R Totaliser mass: forward
ALTOSONIC V 77 B+R OVERRIDE enable possible for pressure proving (ext flowm) 8 7 78 B+R OVERRIDE enable possible for pressure densitometer 2 7 79 B+R OVERRIDE enable possible for density densitometer 2 7 80 B+R OVERRIDE enable possible for density standard 2 7 81 B+R OVERRIDE enable possible for viscosity external 1 7 82 B+R OVERRIDE default (automatic) temperature body 1 5 if enabled in CLNT0300.
ALTOSONIC V 19 B+RW Acknowledge_flags_field_18 6 5 20 B+RW Acknowledge_flags_field_19 6 5 21 B+RW Acknowledge_flags_field_20 6 5 22 B+RW Acknowledge_flags_field_21 6 5 23 B+RW Acknowledge_flags_field_22 6 5 24 B+RW Acknowledge_flags_field_23 6 5 25 B+RW Acknowledge_flags_field_24 6 5 26 B+RW Acknowledge_flags_field_25 6 5 27 B+RW Acknowledge_flags_field_26 6 5 28 B+RW Acknowledge_flags_field_27 6 5 29 B+RW Acknowledge_flags_field_28 6 5 30 B+RW Acknow
ALTOSONIC V 71 B+RW EXT: save changed data in float write field (EXT 222..
ALTOSONIC V 245 B+RW OVERRIDE: save and enable written data 1 2 246 B+RW OVERRIDE: enable to set value temperature body 1 6 247 B+RW OVERRIDE: enable to set value temperature process 2 6 248 B+RW OVERRIDE: enable to set value temperature proving 8 6 249 B+RW OVERRIDE: enable to set value temperature densitometer 2 6 250 B+RW OVERRIDE: enable to set value pressure process 1 2 251 B+RW OVERRIDE: enable to set value pressure proving 8 6 2 6 2 6 2 6 252 B+RW 253 B+RW
ALTOSONIC V 8.3 Field 2 (Read only Integer Field) This data is read only and can be accessed with Modbus function 3 and 4 in Modbus slave mode and with functions 6 and 16 in Modbus master mode. 1 I16+R Flow process 1 Remark Level Level Level Description Type+Access start address ModiconComp NotModiconComp By default the start addresses are mapped to address 3000 (default value) scaled –32768…32767 ó -125%… +125% scaled –32768…32767 ó -3276.8…3276.7 m/s scaled –32768…32767 ó -327.68…327.
ALTOSONIC V 27 I16+R System messages 01..16 5 1 [] 28 I16+R System messages 17..32 5 1 [] 29 I16+R System messages 33..48 5 1 [] 30 I16+R System messages 49..
ALTOSONIC V 79 I16+R Batch stop: NonResetable Standard Totaliser Fract. (sum) 80 I16+R Batch stop: NonResetable Standard Totaliser Fract. (fwd) 4 2 0.xxxx m3 81 I16+R Batch stop: NonResetable Standard Totaliser Fract. (rev) 4 2 0.xxxx m3 82 I16+R Batch stop: NonResetable Mass Totaliser Fract. (sum) 4 2 0.xxxx ton 83 I16+R Batch stop: NonResetable Mass Totaliser Fract. (fwd) 4 2 0.xxxx ton 84 I16+R Batch stop: NonResetable Mass Totaliser Fract. (rev) 4 2 0.
ALTOSONIC V 8.4 Field 3 (Read only Long Integer Field) This data is read only and can be accessed with Modbus function 3 and 4 in Modbus slave mode and with functions 6 and 16 in Modbus master mode.
ALTOSONIC V 41 81 I32+R Resetable totaliser: mass forward (nett.oil) 3 kg 42 83 I32+R Resetable totaliser: mass reverse (nett.oil) 3 kg 43 85 I32+R Non resetable totaliser: process sum (nett.oil) 3 liter 44 87 I32+R Non resetable totaliser: process forward (nett.oil) 3 liter 45 89 I32+R Non resetable totaliser: process reverse (nett.oil) 3 liter 46 91 I32+R Non resetable totaliser: standard sum (nett.
ALTOSONIC V 94 187 I32+R CRC for UFS files 1 [ ] 95 189 I32+R CRC for UFP files 1 [ ] 96 191 I32+R CRC for DAT files 1 [ ] 97 193 I32+R CRC for (last) Ticket 1 [ ] 98 195 I32+R CRC for Executable (program) 1 [ ] 99 197 I32+R Serial number xxxxxxyyyy, project number x ( 6 or 7 digits ) 1 [ ] 100 199 I32+R Serial number xxxxxxyyyy, part number y (4 digits always) 1 [ ] 8.
ALTOSONIC V 34 67 F32+R Krohne use only 35 69 F32+R Krohne use only 36 71 F32+R Krohne use only 37 73 F32+R Krohne use only 38 75 F32+R Remaining hold time on real-profile sampling.
ALTOSONIC V 87 173 F32+R Batch 1 average Ctl (15°C to process) 4 2 [] 88 175 F32+R Batch 1 average Cpl (0 bar to process) 4 2 [] 89 177 F32+R Batch 1 average Ctl (15°C to standard) 4 2 [] 90 179 F32+R Batch 1 average Cpl (0 bar to standard.
ALTOSONIC V 140 279 F32+R Batch 2 average Ctl (15°C to standard) 4 2 [] 141 281 F32+R Batch 2 average Cpl (0 bar to standard.
ALTOSONIC V 193 385 F32+R Channel 5 indicative flow velocity in primary section 194 387 F32+R Krohne use: Calibration[0] [] 195 389 F32+R Krohne use: Calibration[1] [] 196 391 F32+R Krohne use: Calibration[2] [] 197 393 F32+R Krohne use: Calibration[3] [] 198 395 F32+R Krohne use: Calibration[4] [] 199 397 F32+R Krohne use: Calibration[5] [] 200 399 F32+R Krohne use: Calibration[6] [] 201 401 F32+R Krohne use: Calibration[7] [] 202 403 F32+R Krohne use: Calibra
ALTOSONIC V 246 491 F32+R Batch stop: Average Density external 4 8 kg/m3 247 493 F32+R Batch stop: Average Flow external 4 8 m3/h 248 495 F32+R Batch stop: Average Inst. K-Factor external 4 8 [] 249 497 F32+R Batch stop: Average New K-Factor external 4 8 [] 250 499 F32+R Batch stop: Average Diff. K-Factor Inst.. New 4 8 % 8.
ALTOSONIC V 8.7 Field 6 (Read/Write Float Field) In slave mode write to field by function 16, read from field by function 3. In Master mode write to field by function 3, read from field by function 16 NOTE that for explanation on how to handle writing to these parameters: see chapters 7.6 How data is written to the float field 8.
ALTOSONIC V F32+RW UFP batch control: Normal: Setup=9 (if UFP batch1 status batch=0 is no batch) Cancel=5 (if UFP batch1 status batch=1 is set-up) Start batch=119 (if UFP batch1 status batch=1 is set-up) End batch=229 (if UFP batch1 status batch=1 is running) reset print=1009 (if UFP batch1 status batch=5…10 printing) Confirm ticket=779 (if UFP batch1 status batch=10 is confirm) Continuous pipe line measurement, ticket on demand: End with no reset values=559 (if UFP batch1 status batch is not printing) En
ALTOSONIC V 72 143 F32+RW Input in UFP (if enabled): pressure proving.
ALTOSONIC V 125 249 F32+R Batch stop: Override External Temperature 4 8 5 s 126 251 F32+R Batch stop: Override Density Temperature 4 2 5 s 127 253 F32+R Batch stop: Override Process Pressure 4 2 5 s 128 255 F32+R Batch stop: Override External Pressure 4 8 5 s 129 257 F32+R Batch stop: Override Densito Pressure 4 2 5 s 130 259 F32+R Batch stop: Override Density 4 2 5 s 131 261 F32+R Batch stop: Override Standard Density 4 2 5 s 132 263 F32+R Batch st
ALTOSONIC V 4 25 S16+RW Ascii16 String 8 (batch ticket print code 2264) 5 33 S16+R Ascii16 String 9 Serial number 6 41 S16+R Ascii16 String 10 Tag number ModBus Manual 0300 rev07 E 4 6 To print in the batch ticket 1 1 7.30855.35.
ALTOSONIC V 8.10 Explanation of Data Available to Modbus Basic Flow measurement WARNING This warning occurs if 1…4 paths fail, but the system works within specifications. Possible sources of the warning are over range, path failure, deviation in sound velocity or communication failure. Basic Flow measurement ERROR This error occurs if all paths fail.
ALTOSONIC V Standard volume on output Status for the corrected/calculated standard conditions of 15 °C and 1 Bar. Correction parameters HOLD. Due to flow deviation In case of large flow deviation the correction parameters are ‘frozen’ until enough statistical information is available to perform a reliable correction. Overrange data sensor 1…5 This Boolean exists for each ultrasonic channel. If the flow converter measuring the flow is out of range (±125%) this Boolean is set.
ALTOSONIC V Flow of path 1…5 Available as scaled integer and float, these values represent internal UFP-V units. Sound velocity of path 1...5 Available as scaled integer and float. The floating-point numbers represent the sound velocity in m/s, the scaled integers are scaled to 32767 (scaled 0…32767 0...3276.7 m/s). System Set-up warning/error number This value contains the number of the last occurred system set-up warning or system set-up error.
ALTOSONIC V API: Density standard type When the correction type is 1 (Standard volume/mass by API2540): The type of density standard (at temperature and pressure standard) 0: Fill in manually 1: Calculated from process density ((measured by densito meter) 2: On AD/Modbus input API: Fluid type When the correction type is 1 (Standard volume/mass by API2540): The type of fluid: 0: Crude 1: Gasoline 2: Trans.area 3: Jet group 4: Fuel oil 5: Free fill API: Stand. Density crude/gasoline/trans.
ALTOSONIC V 8.11 The System Messages The system messages contains the system runtime warnings and alarms. They are stored as bits into the integer data. Each system message is packed as one message per bit of the integer. The message is active if the accompanying bit is one. The messages are numbered from the least significant bit to the most significant bit. The status of the system is divided into: • System Runtime Warnings. These are caused by system failures.
ALTOSONIC V See for the communication runtime errors also the ALTOSONIC V Modbus Manual. Err no.
ALTOSONIC V 9 Appendices 9.1 Appendix A: Time out values The character length lies between 9 and 12 bits The UFP-V determines the time between two bytes to recognise a communication failure or the end of a message. UFP-V discriminates between a timeout between 2 bytes and a timeout after the last byte, which occurs at the end of a message. The time between two bytes is measured with a resolution of ±100 us. To detect the timeout state (end of message) a timer is incremented every millisecond.
ALTOSONIC V 9.2 Appendix B: LRC Generation (As taken from the website: www.modicon.com/techpubs/crc7.html) The Longitudinal Redundancy Check (LRC) field is one byte, containing an eight-bit binary value. The LRC value is calculated by the transmitting device, which appends the LRC to the message. The receiving device recalculates an LRC during receipt of the message, and compares the calculated value to the actual value it received in the LRC field. If the two values are not equal, an error results.
ALTOSONIC V 9.3 Appendix C: CRC generation (As taken from the website: www.modicon.com/techpubs/crc7.html) The Cyclical Redundancy Check (CRC) field is two bytes, containing a 16-bit binary value. The CRC value is calculated by the transmitting device, which appends the CRC to the message. The receiving device recalculates a CRC during receipt of the message, and compares the calculated value to the actual value it received in the CRC field. If the two values are not equal, an error results.
ALTOSONIC V Indexing the CRC in this way provides faster execution than would be achieved by calculating a new CRC value with each new character from the message buffer. Note: This function performs the swapping of the high/low CRC bytes internally. The bytes are already swapped in the CRC value that is returned from the function. Therefore the CRC value returned from the function can be directly placed into the message for transmission.
ALTOSONIC V 0x3B, 0xFB, 0x39, 0xF9, 0xF8, 0x38, 0x28, 0xE8, 0xE9, 0x29, 0xEB, 0x2B, 0x2A, 0xEA, 0xEE, 0x2E, 0x2F, 0xEF, 0x2D, 0xED, 0xEC, 0x2C, 0xE4, 0x24, 0x25, 0xE5, 0x27, 0xE7, 0xE6, 0x26, 0x22, 0xE2, 0xE3, 0x23, 0xE1, 0x21, 0x20, 0xE0, 0xA0, 0x60, 0x61, 0xA1, 0x63, 0xA3, 0xA2, 0x62, 0x66, 0xA6, 0xA7, 0x67, 0xA5, 0x65, 0x64, 0xA4, 0x6C, 0xAC, 0xAD, 0x6D, 0xAF, 0x6F, 0x6E, 0xAE, 0xAA, 0x6A, 0x6B, 0xAB, 0x69, 0xA9, 0xA8, 0x68, 0x78, 0xB8, 0xB9, 0x79, 0xBB, 0x7B, 0x7A, 0xBA, 0xBE, 0x7E, 0x7F, 0xBF, 0x7D, 0x
ALTOSONIC V 9.4 Appendix D: Coms0300.dat File example as used by Altosonic-V system ----------------------------------------------------------------------------------------------------------------------------------------------------------FILE: COMS0300.DAT ----------------------------------------------------------------------------------------------------------------------------------------------------------01 [UFC500 COMMUNICATION SETUP] 01.
ALTOSONIC V ACCESS MODE 7 =#0 //0, 1: 0=NORMAL, 1=REVERSED DATATYPE 06.08 DATAFIELD 8 =#4000 //RW strings, length=8 ACCESS MODE 8 =#0 //0, 1: 0=NORMAL, 1=REVERSED DATATYPE 06.09 DATAFIELD 9 =#14000 //RW strings, length=16 ACCESS MODE 9 =#0 //0, 1: 0=NORMAL, 1=REVERSED DATATYPE ----------------------------------------------------------------------------------------------------------------------------------------------------------07 [MODBUS MASTER POLLBLOCK DEFINITION] 07.
Australia KROHNE Australia Pty Ltd. Unit 19 No. 9, Hudson Ave. Castle Hill 2154, NSW TEL.: +61(0)2-98948711 FAX: +61(0)2-98994855 e-mail: krohne@krohne.com.au Austria KROHNE Ges.m.b.H. Wagramerstr. 81 Donauzentrum A-1220 Wien TEL.: +43(0)1-2 03 45 32 FAX: +43(0)1-2 03 47 78 e-mail: kaut@via.at Belgium KROHNE Belgium N.V. Brusselstraat 320 B-1702 Groot Bijgaarden TEL.: +32(0)2-4 66 00 10 FAX: +32(0)2-4 66 08 00 e-mail: krohne@krohne.be Brazil KROHNE Conaut Controles Automaticos Ltda.
