Date post: | 16-May-2018 |
Category: |
Documents |
Upload: | trinhduong |
View: | 216 times |
Download: | 1 times |
Operating Manual
SITRANS F 1015N-5M
ModBus/N2 Protocol Converter Module
CQO:1015N-5FM-1 Revision 02Printing January 2012
s
THIS PAGE INTENTIONALLY LEFT BLANK
Errata 1010FMA-56 January 2012
E1
Errata
ModBus Register Map Additions and Fault Bit Decoding List Update The following applies to the 1015N-5M ModBus manual (Revision 1) and Modscan32 Quick Start Guide.
1. Update the front cover of the 1015N-5M ModBus manual: a. From: CQO:1015N-5FM-1 Revision 01 Printing July 2008 b. To: CQO:1015N-5FM-1 Revision 02 Printing January 2012
2. Add the following tables to the Table of Contents (page 2) and Appendix A (page 30): a. Table 10 - 2 Channel Energy System - Reflexor – N2 b. Table 11 - FUS1010 Gross Vol. 1 Channel – MB 16 Bit Word Normal c. Table 12 - FUS1010 Gross Vol. Dual Channel Doppler – MB 16 Bit Word Normal
3. Add the following ModBus Register maps to the 1015N-5M ModBus manual and insert after page 34. See attached sheets.
a. 1010EDN3 2 Channel Reflexor b. 1010N1 1 Channel c. 1010DN1 Dual Channel Doppler
4. Replace the Fault Bit Decoding list in the 15N-5M ModBus manual (pages 29 and 49) and in the Modscan32 Quick Start Guide (page 3) with the following:
Bytes Status b1 b2 b3 b4 7FF 37 46 46 20 - Good 3xx 33 xx xx 20 - Channel disable (x = don’t care) 6xx 36 xx xx 20 - Interface 5xx 35 xx xx 20 - Pig Detect xEx xx 45 xx 20 - Fault indicated xCx xx 43 xx 20 - Fault, aeration indicated xAx xx 41 xx 20 - Memory xxE xx xx 45 20 - Spacing indicator xxC xx xx 43 20 - ZeroMatic channel fault xxB xx xx 42 20 - Empty Pipe xx7 xx xx 37 20 – hi/lo flowrate
METER TYPE: MB 9600/8/N/1
Op System: 5EN04-5.04.04 16 ASCIIConfiguration File 5DCER3-C.S19 NParsing File 5DCER3-P.S19 2
Data Description Sample Data DataType
Register Type Report CH 1 REFLEXOR
Report CH 2 REFLEXOR
Site Name 9D0001789 , Site ID Input Register 30001-30004 30011-30014Date 3783, Date Input Register 30005-30006 30015-30016Time 268, Time Input Register 30007-30008 30017-30018Avg Energy -0.01 , Float Holding Register 41001-41002 41029-41030Energy Rate -0.01 , Float Holding Register 41003-41004 41031-41032Eng Rate Units KBTU/HR , Units Not UsedEnergy Total -0.00 , Float Holding Register 41005-41006 41033-41034Eng Tot Units KBTU , Units Not UsedFlow 0.08748, Float Holding Register 41007-41008 41035-41036Average Flow 0.08745, Float Holding Register 41009-41010 41037-41038Flow Units GAL/MIN, Units Not UsedLiq Total 0.95, Float Holding Register 41011-41012 41039-41040Liq Total Units GAL, Units Not UsedSupply Temp 31.77, Float Holding Register 41013-41014 41041-41042Ts Units TSF, Units Not UsedReturn Temp 31.96, Float Holding Register 41015-41016 41043-41044Tr Units TRF, Units Not UsedTemp Difference -0.19, Float Holding Register 41017-41018 41045-41046Td Units TDF, Units Not UsedAlarms 7FF, Bitfield Input Register 30009-30010 30019-30020Alarm Units S, Units Not UsedAnalog Inputs 0 Float Holding Register 41019-41020 41047-41048A. I. Units Aux Units Not UsedDev 31.90, Float Holding Register 41021-41022 41049-41050Dev Units DevB1 Units Not UsedChiller Effeciency 1 1000.000 Float Holding Register 41023-41024 41051-41052Chiller Effeciency 2 0.012 Float Holding Register 41025-41026 41053-41054Chiller Effeciency 3 0.004 Float Holding Register 41027-41028 41055-41056Chiller Effeciency Units CEBB Units Not Used
EOFEOF
SIEMENS REGISTER MAP FOR 1015N-5M N2/MODBUS COMMUNICATION BOARD.
1010EDN3 2 CHANNEL REFLEXOR
s
ModBus REGISTERSMB1010N1 1 CHANNELMETER TYPE:16 BIT FORMAT165N01-5.04.04Op System:WORD NORMALN10N1-C.S19Configuration File1 CHANNEL110N1-P.S19Parsing File
9600/8/N/1Report CH1Register TypeTypeData
Sample DataData Description30001--30004INPUT REGSite ID820001A ,SiteName30005--30006INPUT REGDate3171,Date30007--30008INPUT REGTime388, Time41001--41002HOLDING REGFloat50.086, AvLiqFlwRate41003--41004HOLDING REGFloat50.092, Instant LiqFlwRate
NOT USEDUnitsGAL/MIN, LiqFlowRateUnits41005--41006HOLDING REGFloat2.047970e2,Raw Flow
NOT USEDUnitsI3/S, Raw Flow Units41007--41008HOLDING REGFloat0.98, 0.98, 0.98, Liq Total
NOT USEDUnitsKGAL, Liq Total Units41009--41010HOLDING REGFloat1490.02,Liq Sonic Vel
NOT USEDUnitsVS, Sonic Vel Units30009INPUT REGInteger55,Singal Strength
NOT USEDUnitsS, Units30010INPUT REGInteger2,Aeration
NOT USEDUnitsA,Aeration Units30011--30012INPUT REGCharacter7FF,Status/Alarms
NOT USEDUnitsS, Status Indicator41011--41012HOLDING REGFloat0.07460,Delta Time
NOT USEDUnitsdt(uS)16Time UnitsEOFEOF
APPENDIX ASIEMENS REGISTER MAP FOR 1015N-5M N2/MODBUS COMMUNICATION BOARD.
METER TYPE: MB ModBus REGISTERSOp System: 5N03-5.04.05 16 16 BIT FORMATConfiguration File 5DCR1-C.S19 N WORD NORMALParsing File 5DCR1-P.S19 1 2 Channel 9600/8/N/1
Data Description Sample DataDataType Register Type Report CH 1 Report CH 2
SiteName 540001363 , SITE ID INPUT REG 30001--30004 30011-30014Date 3CF5, DATE INPUT REG 30005--30006 30015-30016Time 29A, TIME INPUT REG 30007--30008 30017-30018Flow 0.09995, FLOAT HOLDING REG 41001--41002 41009-41010Average Flow 0.06969, FLOAT HOLDING REG 41003--41004 41011--41012Average Flow Units GAL/MIN, UNITS NOT USEDTotal 0.16, FLOAT HOLDING REG 41005--41006 41013-41014Total Units GAL, UNITS NOT USEDAlarms 7FF, CHARACTE INPUT REG 30009--30010 30019-30020Alarm Units S, UNITS NOT USEDDeviation 12.08, FLOAT HOLDING REG 41007--41008 41015-41016Deviation Units DevC8 UNITS NOT USED
EOFEOF
1010DN1 DUAL CHANNEL DOPPLER
s
THIS PAGE INTENTIONALLY LEFT BLANK
ModBus 1015N-5M
2 1015N-5FM-1
CONTENTS1. Introduction ............................................................................................................ 32. Data Information Available ...................................................................................... 43. Quick Start Instructions .......................................................................................... 54. ModBus/N2 Device ID Setting ................................................................................. 65. Flowmeter Setup .................................................................................................... 75.1 Configure Datalogger .............................................................................................. 75.2 Configure RS-232 Port of the FUS 1010 Flowmeter ............................................... 86. Uploading Configuration File to the 1015N-5M ...................................................... 96.1 Using Omnitalk.exe ................................................................................................ 96.2 Download Instructions ............................................................................................ 97. J2 Electrical RS-232 or RS-485 Jumper Settings ...................................................... 108. Status Indicators ..................................................................................................... 119. Data Access ............................................................................................................ 1210. Connections and Wiring .......................................................................................... 1311. ModBus Configuration and Protocol Discussion ..................................................... 1911.1 ModBus Configuration Form Instructions .............................................................. 1911.2 ModBus Protocol .................................................................................................... 2012. Protocol Card Operation .......................................................................................... 2312.1 LED Indicators ......................................................................................................... 2312.2 Switch Functions .................................................................................................... 2312.3 Jumper Functions ................................................................................................... 2313. Troubleshooting Tips ............................................................................................... 2414. Modscan32 Quick Start Guide ................................................................................ 25
TABLES
Table 1 LED Status Indicators ........................................................................................ 11Table 2 J2 Pin Definitions .............................................................................................. 17Table 3 Jumper Settings Revision A3 Boards ................................................................ 18Table 4 Jumper Settings Revision A4 Boards ................................................................. 18Table 5 ModBus Configuration Form ............................................................................. 22Table 6 Dual Beam Gas System--MB 32 Bit Word Normal .............................................. 31Table 7 FUH 1010DVDN Dual Beam—MB 16 Bit Word Normal .................................... 32Table 8 Dual Channel Energy System—MB 16 Bit Word Normal ................................... 33Table 9 Single Channel Energy System—N2 ................................................................. 34
FIGURES
Figure 1 Device ID Switch Settings ................................................................................ 6Figure 2A 1015N-5M Assembly for Revision A3 Boards .................................................. 14Figure 2B 1015N-5M Assembly for Revision A4 Boards .................................................. 15Figure 3 J2 Pin Definitions ............................................................................................ 16Figure 4 RS-232 and RS-422/485 Connections .............................................................. 16Figure 5 N2 Connections .............................................................................................. 17
APPENDIX A - ModBus/N2 Protocol Converter Module & N2 Point Maps .......................... 30APPENDIX B - Installation Drawings ................................................................................... 35APPENDIX C - FM Intrinsically Safe Wiring Diagrams .......................................................... 39APPENDIX D - Date Time/Field Decoding & Fault Bit Decoding ......................................... 49
Metasys Compatibility Status ............................................................................................ 50
ModBus 1015N-5M
3 1015N-5FM-1
1. Introduction The 1015N-5M is a protocol converter module designed for use with the Siemens 1010family of flow computers. It allows communication to take place between the Siemensflow computer’s RS-232 port and RS-232, RS-485 or RS-422 ModBus or N2 Masters. Thismanual describes the configuration procedures and operating procedures based on theModBus and N2 protocol.
The converter allows the ability to configure the onboard connector for Protocol Type, baudrate, stop bits, data bits and parity. This connector is used to communicate to the ModBusor N2 network. The converter can be configured for use as an N2 slave, or ModBus slave; inModBus mode, either in ASCII or RTU mode, Gould or Daniels protocol. For ModBus both 16and 32 bit floating point data can be configured.
The card is preconfigured at the factory per the parameters chosen on the ModBus con-figuration form, which is part of the sales process. The card received is customized to theend users application, and therefore plug and play installation is standard.
1. Introduction
ModBus 1015N-5M
4 1015N-5FM-1
2. Data Information Data available from the ModBus/N2 card includes all data that is accessible from the flowcomputer’s datalogger function. In other words, all flow data that is present on the flowcomputer’s RS-232 port is available through the protocol converter card. (See Siemensflowmeter field manual for list.) The user then has the ability to poll the ModBus/N2 card forany data points of interest.
2. Data Information Available
Available
ModBus 1015N-5M
5 1015N-5FM-1
3. Quick Start 3.1 Using the supplied Field Upgrade kit, install the 1015N-5M card into the flowmeter perinstallation instructions in Appendix-B.
3.2 Wire J2 connector per your network. Refer to figures 4 & 5.
3.3 Set the Device ID, using SW1 through SW3. Press SW4 reset for changes to take effect.Reference Paragraph 4 for details.
3.4 Install Top cover.
3.5 Setup RS-232 and Datalogger functions of the FUS 1010 per Paragraph 5.
3.6 Configure your data acquisition system for the flowmeter type point map.
Note: The point map applicable to your flowmeter is included with the ModBus/N2 card.Appendix-A shows standard point maps examples.
3. Quick Start Instructions
Instructions
ModBus 1015N-5M
6 1015N-5FM-1
4. ModBus/N2 Device ID The ModBus/N2 Device ID is an identifier of the particular flow computer on a multi-dropnetwork. Each card on a Network must have a unique device ID in order for contention freecommunication to occur. Available Addresses (ID’s) for each protocol are listed below:
ModBus: 001 to 247 decimal.N2: 001 to 256 decimal.
To set a device ID, refer to Figure 1, as follows:
There are 3 switches that define the address, located on the top of the 1015N-5M. TheExample ID shown below is 005. The MSB is on the left, the LSB is on the right. After settingthe switches to the proper value, make sure that Jumper JP-2 is between Pins 2 & 3 (factorydefault, away from board edge) and press SW4 once. This will reset the 1015N-5M cardwith the new device address.
0
5
1
2
3
46
7
8
9
SW3
0
5
1
2
3
46
7
8
9
SW2 LSB
0
5
1
2
3
46
7
8
9
SW1 MSB
FIGURE 1
4. ModBus/N2 Device ID Setting
Setting
ModBus 1015N-5M
7 1015N-5FM-1
5. Flowmeter Setup [Setup must be done to every channel of the meter]
In order for the 1015N-5M to work properly, all of the possible Datalogger and RS-232parameters and configuration choices in the site setup must be correct.
5.1 Configure DataLogger NOTE: This must be done for both channels if configured as a dual channel unit; or allchannels, if a multi-channel unit. Refer to the manual for the FUS 1010 flowmeter formenu details, if required.
5.1.1 On the FUS 1010 flowmeter keypad, press the <MENU> key.
5.1.2 Use the UP/DN arrows and scroll to Meter Type. If this does not appear as a choice,the previous menu access was to a nested menu level deeper than the top menu.Use the Left arrow key to return.
5.1.3 With Meter Type shown use the right arrow to access the sub menu of how yourflowmeter is configured.
5.1.4 Select Channel 1 and the appropriate transducer type; we are setting up within thecontext of the site setup that was created for this installation.
5.1.5 Use the UP/DN arrows and scroll to Datalogger Setup. Use the Right arrow key toaccess the submenu.
5.1.6 Five menu choices will be shown. Since we have to check each one, the order inwhich you change these is not important. Use the UP/DN arrows to select the mainchoices. Use the Right arrow key to access the choices. Using the UP/DN arrows,select the item desired as defined below. Pressing the <ENT> key will select thatchoice.
Datalogger MODE: Set to RS-232 Output.Log Interval Set: Set to DEMAND.Event Selected: Set to NONE.Data Selected: Select All Items.
Press Right arrow to access. Highlight each Datalogger item using the UP/DN arrows, andthen press the ENTER key, to set EVERY choice on. Each item will have [+] sign to left of itemwhen selected.
Use the Left arrow key to back out of the nested menu to the top menu. Use of the Leftarrow key intermediately saves the configuration information permanently. You also mustthen Re-Save the site.
5. Flowmeter Setup
ModBus 1015N-5M
8 1015N-5FM-1
5.2 Configure RS-232 This sets up the communication parameters between the FUS 1010 and the 1015N-5Mcard. Note: These are not the ModBus or N2 parameters
5.2.1 Use the UP/DN arrows and scroll to Meter Facilities.
5.2.2 With Meter Facilities shown use the Right arrow to access the sub menu.
5.2.3 Use the UP/DN arrows and scroll to RS-232 Setup.
5.2.4 Use the Right arrow to access the RS-232 setup parameters. Use the right arrow tochoose the parameters shown below. Use UP/DN arrow to scroll to desired choice.Press the <ENT> key to select.
Baud Rate = 9600Parity = OddDatabits = 7Linefeed = NoNetwork ID = 1 (Note: This is not the MODBUS ID.)RTS Key Time = 0.2
At this point you are ready to start communicating over ModBus or N2. Using the registeror point maps supplied with the card, access to the data registers of the 1015N-5M cardshould occur.
5: Flowmeter Setup
Port of the FUS 1010Flowmeter
ModBus 1015N-5M
9 1015N-5FM-1
6. Uploading Configura- [NOTE: Section 6 is usually NOT Required]
There are those cases where the requirements of the end user has changed, such asdiffering parity or baud rate for the ModBus connection. In cases such as these, newconfiguration files must be uploaded to the 1015N-5M card. The configuration files can beobtained by contacting Siemens TSG department. Call (800) 275-8480 for these purposes.Please have all pertinent information required on the configuration form available toexpedite this process.
Upon receipt of the new configuration and parsing files, the following must be performedto upload these new files into the 1015N-5M card. The Omnitalk.exe program is a DOSbased program that enables communication between a PC and the configuration port ofthe 1015N-5M. These configuration files may be uploaded to the ModBus card withoutdisconnecting the ModBus network cabling, or ceasing ModBus network communica-tions.
6.1 Using Omnitalk.exe This supplied program is required to install the necessary files into the Protocol Converter.To install the data files into the Protocol Converter, it will be necessary to connect to theConverter card with a laptop or computer. The supplied 1015-59 cable will connect the J-1port of the Converter card to the COM port of the computer.
NOTE: Omnitalk is a DOS program and will not run under the Windows operating system. Itmay be necessary to reboot the computer into MS-DOS mode before attempting touse Omnitalk.
6.2 Download Instructions The following will provide step-by-step instructions to upload the necessary files into theProtocol Converter card.
6.2.1 Note (write down) the names of the two required files <configuration.S19> and<parsing.S19>. The configuration file always ends in “-C.S19 and the par-sing filealways ends in “-P.S19”. These 2 files, along with Omnitalk.exe should be located inthe same directory.
6.2.2 Make the current directory of the PC equal to where these three files are located.
6.2.3 Invoke the Omnitalk.exe program
6.2.4 Upon invoking the program, key <ENTER>; you should see the Omnitalk> prompt atthe bottom of your screen. If this does not occur, exit the program by pressing the<F10> key, and restart the program. On some machines, in DOS mode, the COM1port is not seen initially. After this exit restart sequence, failure to see this promptwill require a rechecking of the cable connections. Make sure no other programsare running such as HyperTerminal, that steal the COM1 port.
6.2.5 On the 1015N-5M board, insure that Jumper JP2-1 is between Pins 1 & 2. Refer toFigure 2A or 2B for location of Jumpers and switches. Press SW4 once. This will bringthe 1015N-5M card into configuration mode.
6.2.6 Key <F3>; a message will appear which states “send ~worksht.dba”; key “N” andtype in the proper configuration file filename. Key <ENTER> ; a proper data transferwill place you back at the Omnitalk> prompt with no stated errors.
6.2.7 Key <F3> to send the parsing file, a message will appear which states “send~worksht.dba”; key “N” and type in the proper parsing filename. Key <ENTER>; a properdata transfer will place you back at the Omnitalk> prompt with no stated errors.
6.2.8 Key W 6000 – 0000 – 2000 to move the parsing file from RAM to EEPROM. Note:Spaces and dashes will be inserted automatically. The Omnitalk> prompt will thenreappear.
6.2.9 Key <F4> to reset with new settings. Press <F10> to exit Omnitalk.
6.2.10 Return Jumper JP2 to Pins 2 & 3.
6. Uploading Configuration Files to the 1015N-5M
tion Files to the1015N-5M
ModBus 1015N-5M
10 1015N-5FM-1
7. J2 Electrical RS-232 or Applicable to: Revision A3 of the 1015N-5M:
The jumper [JP1] located on the converter card is used to set connector [J2] to either RS-232 or RS-485/422. Refer to Figure 2A for location of Jumpers and switches.
Note: Jumpers JP3 and JP4 are factory set and must not be changed.
Applicable to Revision A4 of the 1015N-5M:
Jumpers JP1, JP3 & JP4 have been eliminated. The J2 connector is configured to receivedata from either the RS232 or RS422/485 connections automatically, eliminating the needfor the jumper. Refer to Figure 2B for location of Jumpers and switches.
7. J2 Electrical RS-232 or RS-485 Jumper Settings
RS-485 Jumper Settings
ModBus 1015N-5M
11 1015N-5FM-1
8. Status Indicators The protocol converter card has eight LED’s onboard. These LED’s are status and indicatorlights that inform of the following:
8. Status Indicators
Note 1: All ModBus/N2 Communication is via Port J2.
Note 2: TX/RX LED’s will flash during Port communication activity.
LED REF PORT FUNCTIONACTIVE D6 All Flashing @ 0.5 Second interval indicates Operation.ERROR D2 All Error Indicator. If Flashing, Communication Not Possible.TXD1 D1 J2 Indicates ModBus/N2 Response to Data Request.RXD1 D3 J2 Indicates ModBus/N2 Network Traffic.TXD2 D4 J3 Indicates Protocol Card to 1010 Request for data.RXD2 D5 J3 Indicates 1010 Response for request for data.TXD3 D7 J1 Indicates Configuration Port Transmission of DataRXD3 D8 J1 Indicates Configuration Port Reception of Data
Table 1. LED Status Indicators
ModBus 1015N-5M
12 1015N-5FM-1
9. Data Access Flow computer data is stored in registers within the Modbus/N2 protocol converter. Thisdata is updated approximately every 20 seconds and can be accessed within milliseconds,if necessary. However, since the data is updated every 20 seconds, requesting data fasterthan this time will result in repeat data until the registers are again updated.
Each data item is stored either as a floating point number or an integer and must beaccessed as such. For ModBus, 32 bit floating point data are stored in the 45,000 addressrange. 16 bit floating point data are stored in sequential pairs in the 41,000 address range.All integers are stored in the 30,000 range. See Appendix-A for differences between 16 and32 bit ModBus.
For Example: To retrieve “flow rate” (flow rate is a float) the address may be 45007. TheModbus Master must request address 45007 in order to retrieve the proper information. ForIntegers such as 30018, the Modbus Master must request address 30018 to receive thecorresponding data for address 30018. Exact data type definitions are specific to eachflowmeter variant.
For N2, data is stored as either Analog Inputs AI’s or ADI’s.
9. Data Access
ModBus 1015N-5M
13 1015N-5FM-1
10. Connections and Figures 2A (Rev A3 boards) & 2B (Rev A4 Boards) details the card’s connectors, jumpers,switches and LED’s.
Figure 3 shows the connections for implementing various electrical specifications.
Figure 4 shows Connections for an RS232 and RS422/485 connection.
Figure 5 details the N2 connection setup.
Table 2 Details the pin connection usage for each specification.
Table 3 shows Jumper Settings Revision A3 Boards.
Table 4 shows Jumper Settings Revision A4 Boards.
10. Connections and Wiring
Wiring
ModBus 1015N-5M
14 1015N-5FM-1
10. Connections and Wiring
DCD
RX+
ERROR
RXD
1
RTS
12
JP2
RX-
JP3
RXD
3
CFG1010
11
J3
RX
JP4
1
1
TX+
MODBUS/N2 USERCONNECTIONS
7
UPGRADE TO VER 5.0, ALLPCB REVISION LEVELS. CALLTSG FOR UPGRADE EPROM
J2
12
SW33
GN
D
ADDRESS
1
SEE MANUAL FORJP2 USAGE
2
R/M A3
3
10
FIGURE 2A 1015N-5M ASSEMBLY
4
ACTIVE
FOR REVISION A3 BOARDS
TXD
3
1
J1
CONFIGURATIONPORT
6
TX TX-
RXD
2SW4
JP1
DTR
1015N-5M-5
2
MB/N2
SELECTFOR RS232OR RS485
VE
R 5.0 03-03-08
JUMP J2-5 TO J2-6
1ED
Bh
RS232
CTS
2
2
SW2
1015-146-1
RS485
8
TXD
2
TXD
1
5 9
3
3
3
N/C
SW1
ModBus 1015N-5M
15 1015N-5FM-1
10. Connections and Wiring
129
SW2
FOR REVISION A4 BOARDS
SEE MANUAL FORJP2 USAGE
R/M A4
RXD
3
1
11
CFGJP
2
6
DTR
CONFIGURATIONPORT
2 8
DCD
1ED
Bh
SW1
1
RXD
1
JUMP J2-5 TO J2-6
FIGURE 2B 1015N-5M ASSEMBLY
CTS
GN
D
TXD
1
ACTIVE
SW3
MB/N2
MSB
NOTE: PIN 7 [RTS] & PIN 8 [CTS] ARECONNECTED VIA JUMPER ON BOTTOMOF BOARD.
1015N-5M-5ERROR
1015-146-1
RTS
3
RX-
TX+
VE
R 5.0 03-03-08
RX+
SW4
LOADCONFIG
RX
4
TXD
2
UPGRADE TO VER 5.0, ALLPCB REVISION LEVELS. CALLTSG FOR UPGRADE EPROM
10
J1
J2
TXD
3
2
TX-
ADDRESS
TX
RESET
N/C
MODBUS/N2 USERCONNECTIONS
3
J3
RXD
2
7
1010
5
ModBus 1015N-5M
16 1015N-5FM-1
10. Connections and Wiring
FIGURE 3 J2 PIN DEFINITIONS
RS422/485SIGNALS
GROUNDJ2-5
J2-7
RS232-DTR
RS232--DCD
J2-10
J2-6
RS422/485--TX+
J2-11
JUMP TO J2-5
J2-2
RS422/485--TX-
J2-1
J2-12
J2-8
J2-3
RS422/485--RX+
RTS
RS232SIGNALSRS232--RX
J2-9
J2
RS232--TX
CTS
RS422/485--RX-
J2-4
COMMONSIGNALS
GROUND
N/CJUMP CTS TO RTSNOT REQ'D ON R/MA4 BOARDSJ2-7
J2-3
N/C
J2-5
J2-1
JUMP TO J2-5J2-6RTS
J2-12
RTS
N/C
J2
N/C
J2-6
FIGURE 4 RS232 AND RS422/485 CONNECTIONS
GROUND
TERMINATIONSRESISTOR ISNETWORKDEPENDENT
J2-9
J2-11
J2-2
J2-4
RS232--RX J2-2
RS422/485--RX-
N/C
J2-10
JUMP CTS TO RTSNOT REQ'D ON R/MA4 BOARDS
CTS
J2-4RS232-DTR
J2-1
RS422/485SIGNALS
N/CJ2-11
J2-8 CTS
RS422/485--RX+J2-10
J2-3
RS422/485--TX+
J2-5
N/C
J2-8
J2-12
J2-9
RS232--TX
RS232--DCD
J2-7JUMP TO J2-5
N/C RS232SIGNALS
RS422/485--TX-
J2
ModBus 1015N-5M
17 1015N-5FM-1
10. Connections and Wiring
N2+J2-12
J2-10
GROUNDJUMP TO J2-5
J2-4
J2-8
N/CJ2-2
N2-
J2-5
CTS
N/C
J2-9 TERMINATIONSRESISTOR ISNETWORKDEPENDENT
J2
J2-3
J2-6J2-7
N/C
N2+
RTS
N2-
FIGURE 5 N2 CONNECTIONS
J2-11
N/CJ2-1
JUMP CTS TO RTSNOT REQ'D ON R/MA4 BOARDS
J2 Pin Number RS232 RS422/485 N2J2-1 DCD NOT USED NOT USEDJ2-2 RX NOT USED NOT USEDJ2-3 TX NOT USED NOT USEDJ2-4 DTR NOT USED NOT USEDJ2-5 GROUND GROUND GROUNDJ2-6 JUMP TO J2-5 JUMP TO J2-5 JUMP TO J2-5J2-7 RTS RTS JUMP TO J2-8J2-8 CTS CTS JUMP TO J2-7J2-9 NOT USED TX+ N2+J2-10 NOT USED TX- N2-J2-11 NOT USED RX+ JUMP TO J2-9J2-12 NOT USED RX- JUMP TO J2-10
TABLE 2. J2 Pin Definitions
ModBus 1015N-5M
18 1015N-5FM-1
10. Connections and Wiring
JP2 SETTINGS CONFIGURATION MODE CONNECT 1-2RESET ADDRESS [DEFAULT] CONNECT 2-3
TABLE 4. Jumper Settings Revision A4 Boards
JP1 SETTINGS RS232 CONNECT 1-2RS422/485 or N2 [DEFAULT] CONNECT 2-3
JP2 SETTINGS CONFIGURATION MODE CONNECT 1-2RESET ADDRESS [DEFAULT] CONNECT 2-3
JP3 SETTINGS FACTORY DEFAULT CONNECT 1-2JP4 SETTINGS FACTORY DEFAULT CONNECT 1-2
TABLE 3. Jumper Settings Revision A3 Boards
ModBus 1015N-5M
19 1015N-5FM-1
11. ModBus Configuration and Protocol Discussion
11. ModBus Configuration This information is designed for the end user of the Siemens ModBus card, the 1015N-5Mprotocol converter, to properly select the operating parameters of the ModBus card for theirspecific application. Due to the numerous versions of the ModBus protocol deployed in endapplications, the need for a flexible interface is apparent. Controlotron’s 1015N-5M sup-plies this flexibility, requiring only knowledge of the end users data acquisition system.
11.1 ModBus Refer to Table 5. ModBus Configuration Form in this section.
11.1.1 Customer & Date Please fill in with end customer name or a unique name identifying the project.
11.1.2 Unit PN This is the part number of the Siemens Flowmeter that will receive the ModBus card. Thisneeds to be specified especially for retrofitting existing installed FUS 1010 family flowmeters.
11.1.3 Op System PN & This is required for field retrofits. The Op System must be specified as the latest installedoperating system into the referenced flowmeter. The form details how to determine theoperating systems.
11.1.4 Configuration In this section, one type of unit configuration must be chosen.
11.1.5 ModBus Refer to the following discussion for an explanation of all the differing communication para-meters and the restrictions therein. Generally the end user or integrator has responsibilityfor proper selection of these parameters.
Note that on receipt of the ModBus card and Flowmeters, the ModBus card is identified forinstallation into the flowmeter for which it is intended. On multiple flowmeter orders, orvarying flowmeter types within the same order, or field retrofits, unique identification infor-mation will be provided for each ModBus card identifying the end flowmeter. You will alsoreceive a “point map” that defines the registers and associated data information. All Mod-Bus cards shipped from Siemens are preconfigured for the end flowmeter. No uploading ofconfiguration or parsing files is required.
Almost 90% of all field problems associated with ModBus cards are caused by incorrectspecifications of the communication parameters. It is therefore essential that due dili-gence be performed prior to filling out the configuration form to insure proper informationis provided.
& Protocol Discussion
Configuration Form Instructions
Unit Serial Number
Communication Parameters
ModBus 1015N-5M
20 1015N-5FM-1
11. ModBus Configuration and Protocol Discussion
11.2 ModBus Protocol The Siemens communications card for ModBus protocol concerns itself with two datatypes: Integer and Floating Point. Integers are whole numbers in the range of -32768 to32767 inclusive and may be represented with a single 16-bit register.
11.2.1 Integer Registers Known as “Input Registers” all have an address beginning at 30001 and are sequentiallynumbered 30001, 30002, 30003, etc. Some registers may contain two “packed” 8-bit ASCIIbytes of data. For example, a typical register map may store the flowmeter’s site name inInput Registers 30001 through 30004 as 8 bytes of ASCII data.
ModBus Input Register – 16-bit Integer
ModBus Input Register – 16-bit Integer
30001
30002
30003ModBus Input Register – 16-bit Integer
The number 15 is represented as 0000000000001111b or 000Fh. The number –15 is repre-sented as 111111111110001b or FFF1h. The ASCII value of “ST” is stored as a “packed” in-teger of 5354h.
11.2.2 Floating Point Known as “Holding Registers” all have an address beginning at 40001 and are referencedin pairs. Like Integer registers, each register in the 4x address range contains 16 bits ofdata. These register pairs are combined to form a single 32-bit IEEE format floating pointnumber with a range of ±10±38 and a precision of approximately 7 decimal digits.
The number 123.456 is represented as 42F6E979h (32 bits). Half of these bits are stored inthe odd numbered address in the 4x range and half in the even numbered address. Twosequential Holding Register addresses will contain the values of 42F6h and E979h.
Registers
41001
41002These two registers are read by a ModBus controller and combined to form a single 32-bitvalue of 42F6E979h, which represents 123.456 decimal. If the high-order byte is containedin the smaller (odd-numbered) address, the format is known as “Word Reversed.” If the low-order byte is contained in the smaller, odd-numbered address, the format is known as“Word Normal.” We can configure these registers for either format. The format required isdependent on the customer’s ModBus controller and how it is configured.
This covers the most basic ModBus protocol format, also known as “Gould” or “Modicon.”Nearly every ModBus controller may be configured to read registers in 16-bit “Gould” format,also known as “Modicon Compatible.”
ModBus Holding Register containing 42F6h
ModBus Holding Register containing E979h
ModBus 1015N-5M
21 1015N-5FM-1
11. ModBus Configuration and Protocol Discussion
11.2.3 Daniel Protocol This is a type of ModBus controller which adds many extensions and options to this basiccommunication protocol. Some Daniel controllers may be configured to read Modiconcompatible format. We can support the Daniel controller and provide one protocol exten-sion, which is the addition of 32-bit registers. We typically place our 32-bit floating pointregisters in the 45x address range. This eliminates the need for combining register pairsand eliminates the decision of “Word Normal” or “Word Reversed.”
4500145001This 32-bit Holding Register can contain a single value of 42F6E979h, which represents123.456 decimal. “Daniel” extensions need to be enabled. Register addresses typicallybegin at 45000 and are sequential: 45000, 45001, 45002, etc. Daniel format meters cannotbe read with a Gould controller.
11.2.4 Line Rate At the bit level, the backbone communications is typically provided by an RS-485 multi-drop, differential driver network. Similar to RS-232, baud rate, data bits, stop bits, and paritymust be specified for each installation. This data format is not specified by the Modbusprotocol, with the following caveat. If RTU mode is specified, the number of data bits mustbe at least 8.
11.2.5 RTU Mode This mode is often favored since data may be transmitted nearly twice as quickly as ASCIImode. In RTU mode, each single byte of data is sent over the wire in 8 bits, 1 for 1. Thedisadvantage of RTU mode is that an internal timer must be used to determine the startand end of each message on the bus. This timing is critical and may be affected in highnoise environments.
11.2.6 ASCII Mode In contrast to RTU mode, it encodes each byte of data into an ASCII-encoded format. Forexample, the 8-bit value of B9h is encoded as the ASCII value for “B” followed by the ASCIIvalue of “9”, or 42h followed by 39h. ModBus ASCII only uses 7 bits of data per byte, whichfacilitates a line format of as few as 7 data bits. The advantage of ASCII format is that everyModBus message terminates with a Carriage Return <CR>. Timing is less critical and isgenerally more reliable. The disadvantage of ASCII mode is that twice the number of bytesis required to send the same information, compared to RTU. ASCII and RTU modes areavailable to be used in either Gould or Daniel format.
and Format
ModBus 1015N-5M
22 1015N-5FM-1
11. ModBus Configuration and Protocol Discussion
Table 5. ModBus Configuration Form
MODBUS CONFIGURATION SHEET CUSTOMER:[Click here & type name] DATE: 4/9/2008 Siemens WO#: [Click here & type WO#] Sales Person: [Click here & type name]
UNIT P/N: [ALWAYS REQUIRED] [Click here & type Unit P/N] Siemens Rep: [Click here & type name]
OP SYSTEM P/N: [FIELD UPGRADES ONLY] FULL OP SYSTEM TYPE AND REVISION LEVEL SEE NOTE 1
[Click here & type opSystem P/N]
Integrator:
[Click here & type name]
UNIT S/N: [FIELD UPGRADES ONLY] LOCATED ON LABEL
[Click here & Unit S/N]
Contact Name:
[Click here & type name]
CONFIGURATION: [CHECK AS REQ’D] [ALWAYS REQUIRED] SEE NOTE 2
SINGLE CHANNEL DUAL CHANNEL DUAL BEAM MULTI CHANNEL FOUR BEAM
Contact:
Phone
Fax
[Click here & type Contact Phone]
[Click here & type Contact FAX]
[Click here & type Contact Email]
BAUD RATE Check one 300
600 1200 2400
4800 9600 19200
DEFAULT = 9600
STOP BITS Check one 1
2
DEFAULT = 1
DATA BITS Check one 7
8
DEFAULT = 8
PARITY CHECK Check one NONE
ODD EVEN
DEFAULT = NONE
MODBUS DATA Check one 16 BIT
32 BIT
DEFAULT = 16 BIT
DATA FORMAT Check one WORD NORMAL
WORD REVERSED
DEFAULT = WORD NORMAL
MODBUS MODE Check one ASCII
RTU
DEFAULT = RTU
MODBUS
COMMUNICATION
PARAMETERS
ALL PARAMETERS MUST BE SPECIFIED
SEE NOTE 3
MODBUS FORMAT Check one GOULD
DANIEL
DEFAULT = GOULD
NOTES: 1) Full operating system part number is located under “Meter Facilities” –> System Info –> OpSystem PN.
2) The configuration is how the meter is setup on a pipe. Please refer to the front display, under any of the flow display screens. The top
line will tell you how the meter is configured.
3) If not sure of the parameters, consult your system integrator.
ModBus 1015N-5M
23 1015N-5FM-1
12. Protocol Card Operation
12.1 LED Indicators Active LED [D6]Blinking = Run ModeConstant On = Configuration Mode
Error Light [D2]Off = No ErrorsOn = ModBus Communcation Not Possible.
In 95% of all cases, the error light indicates it is not receiving properly formatted data fromthe FUS 1010 Flowmeter. The flowmeter Datalogger must be set up properly, along with theRS-232 parameters that define the FUS 1010 RS-232 port setting. The Datalogger can onlybe enabled after at least 1 flow path has been set up.
MODBUS LED’s [D1 & D3]TXD1 = Tranmitting Data onto ModBus NetworkRXD1 = Receiving Data from ModBus Network. (Note the card receives all ModBus trafficand responds only to proper address)
FUS 1010 LED’s [D4 & D5]TXD2 = Requesting data from the Flowmeter.RXD2 = Receiving Data from the Flowmeter.
CONFIG LED’s [D7 & D8]TXD3 = Transmitting data to the connected PC.RXD3 = Receiving Data from the connected PC.
12.2 Switch Functions SW1 SW2 & SW3 Sets ModBus/N2 Network Address.SW4 Reset Switch. Function depends on Jumper JP2-1.
12.3 Jumper Functions With Jumper JP2-1 between Pins 2 & 3, SW4 will reset the ModBus card and read the new ad-dress set on switches SW1 to SW3.
With Jumper JP2-1 between Pins 1 & 2, SW4 will place card into configuration mode. Con-figuration mode is exited by pressing <F4> in Omnitalk, recycling power or placing jumperJP2 between pins 2 & 3 & again pressing SW4.
12. Protocol Card Operation
ModBus 1015N-5M
24 1015N-5FM-1
13. Troubleshooting Tips The following are ommon problems encountered when integrating the 1015N-5M equippedflowmeter into the end user’s data acquisition system.
Symptom: Error Light Flashing:
Possible Causes:
Datalogger System on FUS 1010 Flowmeter not set up properly. All Datalogger functions foreach channel must be set up correctly in a dual or multi-channel unit, or at least one pathset up on a dual beam or multi-beam unit.
All FUS 1010 RS-232 parameters must be set correctly. Note that these setting are not theMod-Bus settings, but rather the connection between the FUS 1010 Flowmeter and the1015N-5M card.
Hint: For an “X” channel unit where “X” is either 1,2 or 4 the TXD2 LED should illuminate onceevery 20 seconds. This is a request from the 1015N-5M card to the FUS 1010 Flowmeter forthe latest Datalogger information. Subsequently, the RXD2 should illuminate “X” times,depending on the number of channels the operating system supports. So for a dual chan-nel unit, the RXD2 should illuminate twice in sequence. If this does not occur, then the FUS1010 Flowmeter has not been set up properly. All channels must be setup correctly. For anygiven dual beam or 4-beam system, there will be only 1 response from the FUS 1010N. Indual beam or 4-beam mode, all channels are measuring the same pipe, hence there is only1 Datalogger message available.
Symptom: ModBus Card RXD1 LED indicates Card is receiving data, but no response fromModBus Card.
Possible Causes:
Wrong Device ID set on SW1 – SW3.Baud Rate, Parity, etc. Incorrect from Data Acquisition system.CTS to RTS Jumper not installed. Note this jumper is installed on Rev A4 cards.
Symptom: ModBus Card RXD1 LED indicates Card is receiving data, RXD2 illuminates to therequest, but the data acquisition system does not acknowlede the message.
Possible Causes: This is most likely a problem in the data acquisition setup. Verify propercard operation using ModScan.
Symptom: Omnitalk.exe shows continuous message “No response.”
Possible Causes: 1015N-5M not in configuration mode. Move JP2 to pins 1 & 2 and pressSW4.
13. Troubleshooting Tips
ModBus 1015N-5M
25 1015N-5FM-1
14. Modscan32 Quick-Start This is a brief “quick start” guide to using Modscan32 to communicate with the SiemensFUS 1010 flowmeter using the ModBus protocol. Modscan32 is distributed by Win-Tech,http://www.win-tech.com/ as a trial version and it functions for a limited time. If you findthis software useful, it may be purchased directly from them.
Note the device address of the ModBus card and the communication parameters of theModBus network. This differs from the serial communications of the flowmeter as selectedfrom the front panel.
When Modscan32 starts, the following screen is displayed:
Step 1 – Establish a connection. Select ‘Connection’ from the pull-down menu and choosethe COM port which has been wired to the ModBus network or directly to theflowmeter.
Modscan32 Quick-Start Guide
Guide
ModBus 1015N-5M
26 1015N-5FM-1
Modscan32 Quick-Start Guide
For this example, we have chosen COM1 at 9600 baud, 8 data bits, no parity and 1 stop bit.
Step 2 – Select the Device ID, Address (of the first ModBus register), and Length (numberof registers to query). Note: The default length of 100 will almost always producea communications error. The length parameter must be set to no more than thenumber of registers available.
Once Modscan32 is put on-line, the status message “Device NOT CONNECTED!” will nolonger be displayed. These messages appear just above the displayed registers.
If the status message is “Exception Response” or “Invalid Response,” this indicates thatthe flowmeter does not understand the read command. Double-check the address range,length, and type of registers being examined.
There are four types of ModBus registers available from the pull-down menu, “01: CoilStatus,” “02: Input Status,” “03: Holding Register,” and “04: Input Register.” We are con-cerned with the last two types: Holding Registers for values such as flow rate and tempera-ture, and Input Registers for Date, Time, Signal Strength, Aeration, and Alarms. Other datamay be examined by referring to the ModBus Register Map for each individual flowmeter.Each one may reflect a unique configuration.
ModBus 1015N-5M
27 1015N-5FM-1
Modscan32 Quick-Start Guide
To examine Holding Registers, select either “Floating Pt. or “Swapped FP” depending if yourflowmeter is configured for “Word Normal” or “Word Reversed.” ModScan32 will then com-bine two adjacent 16-bit registers to form a single 32-bit IEEE format floating point num-ber.
Corresponding values for Flow Rate, Raw Flow, etc will appear as odd-numbered registerpairs:
The other set of registers we concern ourselves with is Input Registers for Date, Time, Sig-nal Strength, Aeration, and Alarms. Select “04: Input Register” from the pull-down menu.Click on “Hex” from the data format selection:
Next, reduce the number of registers to no more than the number of available Input Regis-ters for your flowmeter. If the length specified exceeds the number of actual registers, nodata will be displayed.
ModBus 1015N-5M
28 1015N-5FM-1
Modscan32 Quick-Start Guide
ASCII values are packed in adjacent bytes. In this example, “SiteName” is shown in regis-ters 30001 thru 30004, which is 48 42 31 20 20 20 20 20 or “HB1 “.
The alarms are returned as ASCII hex digits. In this example, the alarms are at 30011 thru30012, which is 37 46 46 20, or “7FF “. This hex value indicates status alarms (inverted), bitencoded as follows:
0x001 - spacing0x002 - Zeromatic channel fault0x004 - empty0x008 - hi/lo flowrate0x010 - fault0x020 - aeration or turbulence (GAS)0x040 - memory0x080 - makeup0x100 - interface0x200 - pig detect0x400 - channel/path enable
ModBus 1015N-5M
29 1015N-5FM-1
Modscan32 Quick-Start Guide
A condition of 7FF indicates no alarms. These four bytes of “3746 4620” may also beexamined for decoding of alarms as follows:
1 2 3 47FF - 37 46 46 20 - Good6xx 36 xx xx 20 - Channel disabled (x = don’t care)xEx xx 45 xx 20 - Fault indicatedxCx xx 43 xx 20 - Fault, aeration indicatedxxE xx xx 45 20 - Spacing indicatorxxC xx xx 43 20 - Zeromatc channel faultxxB xx xx 42 20 - Empty Pipexx7 xx xx 37 20 - hi/lo flowrate
The date in this example is contained in registers 30005 thru 30006, which is 33 30 43 34;30C4 hex is encoded as follows:
date_of_month + (month * 32) + ((year - 1980) * 512). In this example, 30C4 or 12484represents June 4th, 2004.
The time field is the number of minutes past midnight, contained in registers 30007 thru30008 (first three bytes only). In this example, 33 43 33, 3C3 hex is 963 minutes past thehour, or 16:03 (4:03pm).
ModBus 1015N-5M
30 1015N-5FM-1
APPENDIX A 1015N-5M ModBus/N2 Protocol Converter Module
Sample ModBus Register Maps and N2 Point Maps
Appendix A shows available data items and its corresponding register addresses forspecific types flow computers. The supplied card will include the Register or point mapspecific to the configuration specified on the configuration form.
The following tables are included as samples:
Table 6: Dual Beam Gas System—MB 32 Bit Word Normal
Table 7: FUH 1010DVDN Dual Beam—MB 16 Bit Word Normal
Table 8: Dual Channel Energy System—MB 16 Bit Word Normal
Table 9: Single Channel Energy System—N2.
APPENDIX A
ModBus 1015N-5M
31 1015N-5FM-1
s
ModBus REGISTERSMB1010GCCDN DUAL BEAMMETER TYPE:32 BIT FORMAT321010GN12Op System:WORD NORMALN10GN12-C.S19Configuration File1 CHANNEL110GN12-P.S19Parsing File
Report CH4Report CH3Report CH2Report CH1Register TypeTypeData
Sample DataData Description30001--30004INPUT REGSITE ID39000233 ,SiteName30005--30006INPUT REGDATE2F73,Date30007--30008INPUT REGTIME443,Time
45001HOLDING REGFloat20.00238,Flow Rate Path 145002HOLDING REGFloat20.00257,Flow Rate Path 245003HOLDING REGFloat20.00247,Inst Liq Flow Rate45004HOLDING REGFloat20.00241,Avg Liq Flow Rate
NOT USEDUnitsKCU FT/H,Flow Rate Units45005HOLDING REGFloat1.009714e4,Raw Flow Path 145006HOLDING REGFloat1.009724e4,Raw Flow Path 2
NOT USEDUnitsI3/S,Raw Flow Units45007HOLDING REGFloat5030.70,Gas Velocity
NOT USEDUnitsF/S,Velocity Units45008HOLDING REGFloat2.95,Totalizer, Flow
NOT USEDUnitsKCU FT,Totalizer Units45009HOLDING REGFloat550.00,Sonic Vel Path 145010HOLDING REGFloat550.00,Sonic Vel Path 245011HOLDING REGFloat550.00,Sonic Vel Average
NOT USEDUnitsVS,Sonic Vel Units30009INPUT REGInteger56,Singal Strength P130010INPUT REGInteger54,Singal Strength P230011INPUT REGInteger55,Singal Strength AVG
NOT USEDUnitsS,Units30012INPUT REGInteger22,Aeration
NOT USEDUnitsA,Aeration Units45012HOLDING REGFloat0.356,Specific Gravity
NOT USEDUnitsSG,Specific Gravity /UN45013HOLDING REGFloat0.473,Base Specific Gravit
NOT USEDUnitsBSG,Units30013--30014INPUT REGCHARACT7FE,Status/Alarms P130015--30016INPUT REGCHARACT7FE,Status/Alarms P230017--30018INPUT REGCHARACT7FE,Status/Alarms Site
NOT USEDUnitsS,Alarm Unit45014HOLDING REGFloat230.72,Temperature RTD 145015HOLDING REGFloat418.94,Temperature RTD 2
NOT USEDUnitsF,Temp Units45016HOLDING REGFloat18.45167,Delta Time Path 145017HOLDING REGFloat18.45186,Delta Time Path 2
NOT USEDUnitsdt(uS),Time Units45018HOLDING REGFloat0.000,Analog Input 1
NOT USEDUnitsOff,Units45019HOLDING REGFloat0.000,Analog Input 2
NOT USEDUnitsOff,Units45020HOLDING REGFloat0.000,Analog Input 3
NOT USEDUnitsOff,Units45021HOLDING REGFloat0.000,Analog Input 4
NOT USEDUnitsOff13UnitsEOFEOF
APPENDIX A
Table 6. Dual Beam Gas System--MB 32 Bit Word Normal
ModBus 1015N-5M
32 1015N-5FM-1
APPENDIX A
Table 7. 1010DVDN Dual Beam--MB 16 Bit Word Normal
s
ModBus REGISTERSMB1010DVDN DUAL BEAMMETER TYPE:16 BIT FORMAT161010DVN02Op System:WORD NORMALN10DVDN-C.S19Configuration File1 CHANNEL110DVDN-P.S19Parsing File
Report CH4Report CH3Report CH2Report CH1Register TypeTypeData
Sample DataData Description30001--30004INPUT REGSITE IDB000014615 ,SiteName30005--30006INPUT REGDATE307A,Date30007--30008INPUT REGTIME368,Time41001--41002HOLDING REGFloat15.02605,Flow Rate Path 141003--41004HOLDING REGFloat15.01587,Flow Rate Path 241005--41006HOLDING REGFloat15.02043,Inst Liq Flow Rate41007--41008HOLDING REGFloat14.85797,Avg Liq Flow Rate
NOT USEDUnitsGAL/MIN,Flow Rate Units41009--41010HOLDING REGFloat6.111632e1,Raw Flow Path 141011--41012HOLDING REGFloat6.104782e1,Raw Flow Path 2
NOT USEDUnitsI3/S,Raw Flow Units41013--41014HOLDING REGFloat2259.40,Totalizer, Flow
NOT USEDUnitsGAL,Totalizer Units41015--41016HOLDING REGFloat982.02,Sonic Vel Path 141017--41018HOLDING REGFloat982.02,Sonic Vel Path 241019--41020HOLDING REGFloat980.51,Sonic Vel Average
NOT USEDUnitsVS,Sonic Vel Units30009INPUT REGInteger53,Singal Strength P130010INPUT REGInteger55,Singal Strength P230011INPUT REGInteger54,Singal Strength AVG
NOT USEDUnitsS,Units30012INPUT REGInteger3,Aeration
NOT USEDUnitsA,Aeration Units30012--30016INPUT REGCharacter--------,Liquident ID Type41021--41022HOLDING REGFloat1359.677,Liquident
NOT USEDUnitsLI,Liquident ID41023--41024HOLDING REGFloat1.000,Specific Gravity
NOT USEDUnitsSG,Specific Gravity /UN41025--41026HOLDING REGFloat10.000,API
NOT USEDUnitsAPI,API Units41027--41028HOLDING REGFloat999.012,Density
NOT USEDUnitsKGM3,Kg/Meter[3]41029--41030HOLDING REGFloat1.000,Base Specific Gravit
NOT USEDUnitsBSG,Base Specific Gravit41031--41032HOLDING REGFloat10.000,Base API
NOT USEDUnitsBAPI,Base API Units41033--41034HOLDING REGFloat999.012,Base Density
NOT USEDUnitsBKGM3,Kg/Meter[3]30017--30018INPUT REGBitfield7FE,Status/Alarms P130019--30020INPUT REGBitfield7FE,Status/Alarms P230021--30022INPUT REGBitfield7FE,Status/Alarms Site
NOT USEDUnitsS,Alarm Unit41035--41036HOLDING REGFloat224.20,Temperature RTD 141037--41038HOLDING REGFloat420.39,Temperature RTD 2
NOT USEDUnitsF,Temp Units41039--41040HOLDING REGFloat0.06444,Delta Time Path 141041--41042HOLDING REGFloat0.06439,Delta Time Path 2
NOT USEDUnitsdt(uS),Time Units41043--41044HOLDING REGFloat0.000,Analog Input 1
NOT USEDUnitsOff,Units41045--41046HOLDING REGFloat0.000,Analog Input 2
NOT USEDUnitsOff,Units41047--41048HOLDING REGFloat0.000,Analog Input 3
NOT USEDUnitsOff,Units32141049--41050Float0.000,Analog Input 4
NOT USEDUnitsOff,UnitsEOFEOF
ModBus 1015N-5M
33 1015N-5FM-1
Table 8. Dual Channel Energy System--MB 16 Bit Word Normal
APPENDIX A
s
ModBus REGISTERSMB1010EDN1 2 CHANNELMETER TYPE:16 BIT FORMAT161010EN04Op System:WORD NORMALN10DCE1-C.S19Configuration File2 CHANNEL210DCE1-P.S19Parsing File
Report CH4Report CH3Report CH2Report CH1Register TypeTypeData
Sample DataData Description30013-3001630001--30004INPUT REGSite IDCE000105H CHSiteName30017--3001830005--30006INPUT REGDate3294,Date30019--3002030007--30008INPUT REGTime208,Time41025--4102641001--41002HOLDING REGFloat905.6,AvNRGFlo41027--4102841003--41004HOLDING REGFloat906.7,NRG Flo
NOT USEDUnitsKBTU/HR ,NRG Units41029--4103041005--41006HOLDING REGFloat914.57 ,Energy Totalizer
NOT USEDUnitsKBTU ,TotUnits41031--4103241007--41008HOLDING REGFloat19.179,AvLiqFlwRate41033--4103441009--41010HOLDING REGFloat19.131,Instant LiqFlwRate
NOT USEDUnitsGAL/MIN,LiqFlowRateUnits41035--4103641011--41012HOLDING REGFloat7.856044e1,Raw Flow
NOT USEDUnitsI3/S,Raw Flow Units41037--4103841013--41014HOLDING REGFloat1.18,Liq Total
NOT USEDUnitsKGAL,Liq Total Units41039--4104041015--41016HOLDING REGFloat1498.39,Liq Sonic Vel
NOT USEDUnitsVS,Sonic Vel Units41041--4104241017--41018HOLDING REGFloat126.81,Supply Temp
NOT USEDUnitsTSF,Temp Units41043--4104441019--41020HOLDING REGFloat32.40,Return Temp
NOT USEDUnitsTRF,Temp Units41045--4104641021--41022HOLDING REGFloat94.40,Temp Difference
NOT USEDUnitsTDF,Temp Units3002130009INPUT REGInteger55,Singal Strength
NOT USEDUnitsS,Units3002230010INPUT REGInteger2,Aeration
NOT USEDUnitsA,Aeration Units30023--3002430011--30012INPUT REGCharacter7F7,Status/Alarms
NOT USEDUnitsS,Status Indicator41047--4104841023--41024HOLDING REGFloat0.02864,Delta Time
NOT USEDUnitsdt(uS)79Time UnitsEOFEOF
ModBus 1015N-5M
34 1015N-5FM-1
s
N2 POINT MAPN21010EN1 1 CHANNELMETER TYPE:161010EN01-3.01.06BOp System:RN2SE1-C.S19Configuration File
1 CHANNEL1N2SE1-P.S19Parsing FileReport CH4Report CH3Report CH2Report CH1Register TypeTypeSample DataData Description
ADI-1--4ADISite IDD80001EN01 27SiteNameADI-5--6ADIDate2AF8,DateADI-7--8ADITime55C,Time
ADI-9ADIInteger56,Singal StrengthADI-10ADIInteger3,Aeration
ADI-11--12ADIBitfield7F7,Status/AlarmsAI-1AIFloat4757.9,AvNRGFloAI-2AIFloat5602.9,NRG FloAI-3AIFloat126.29 ,Energy TotalizerAI-4AIFloat120.023,AvLiqFlwRateAI-5AIFloat101.956,Instant LiqFlwRateAI-6AIFloat4.159972e2,Raw FlowAI-7AIFloat166.30,Liq TotalAI-8AIFloat1609.75,Liq Sonic VelAI-9AIFloat125.27,Supply TempAI-10AIFloat32.09,Return TempAI-11AIFloat93.18,Temp DifferenceAI-12AIFloat0.16776,Delta Time
NOTES:UNITS ARE METER SETUP SPECIFIC. PLEASE REFER TO THE INSTALLED METER FOR ACTUAL UNITS DEFINED.REFER TO APPENDIX FOR DATE/TIME /ALARM WORD DECODING AND BIT DEFINITIONS
APPENDIX A
Table 9. Single Channel Energy System--N2
ModBus 1015N-5M
35 1015N-5FM-1
APPENDIX B 1015N-5FM-1 ModBus/N2 Protocol Converter Module
Installation Drawings
APPENDIX B
THIS PAGE INTENTIONALLY LEFT BLANK
MODULE LOADING OPTION I : 1010N-5* WITH 1010N-2* IN 1010N/DN TYPE SYSTEM
POWER
START VIEW
1015N-5M-MK-721614C
COMPUTER, NEMA 4FLOW AND ENERGY
ASSEMBLY, 1010 SERIES
FINISH VIEW
DISASSEMBLY/ASSEMBLY PROCEDURE
ModBus 1015N-5M
38 1015N-5FM-1
Page Intentional Left Blank
ModBus 1015N-5M
39 1015N-5FM-1
APPENDIX C 1015N-5FM-1 ModBus/N2 Protocol Converter Module
FM Intrinsically Safe Wiring Diagrams
APPENDIX C
ModBus 1015N-5M
48 1015N-5FM-1
Page Intentional Left Blank
ModBus 1015N-5M
49 1015N-5FM-1
APPENDIX D 1015N-5M ModBus/N2 Protocol Converter Module
DATE/TIME FIELD DECODING The Date and Time functions are hex coded for compression of total data flow. To decodethese variables, the following algorithm is used.
Date / Time code
Bits Description Hex Range Valid RangeTime: 0-5 Seconds (0-63) (0-59)
6-11 Minutes (0-63) (0-5912-17 Hours (0-31) (0-23)
Date: 0-4 Day (0-31) (1-31)5-8 Month (0-15) (1-12)9-15 Year +1980 (0-127) (0-127)
Note: Calendar year = 1980 + ‘years since 1980’
Example for Date:2507 =
0 1 0 0 1 0 1 0 0 0 0 0 1 1 1
APPENDIX D
Day = 7Month = 8Year = 18 + 1980 = 1998
Year Month Day
FAULT BIT DECODING alarm bit definitionsA_SPC 1 spacing
2 (undefined)A_EMPTY 4 emptyA_ALARM 8 rate alarmA_FAULT 0x10 faultA_AER 0x20 aerationA_MEMRY 0x40 memoryA_SETUP 0x80 makeupA_INT 0x100 interfaceA_PIG 0x200 pig detectA_ENAB 0x400 enabled
Fault bits are presented as a 3-digit hex value, which is ASCII packed into a ModBus registerpair. The lower ModBus register address contains the first two ASCII characters. The upperModBus register contains the last ASCII value followed by an ASCII space, 20h. Faults can bedetermined by examining these four bytes as follows:
BytesStatus b1 b2 b3 b47FF 37 46 46 20 - Good3xx 33 xx xx 20 - Channel disable (x = don’t care)6xx 36 xx xx 20 - Interface5xx 35 xx xx 20 - Pig DetectxEx xx 45 xx 20 - Fault indicatedxCx xx 43 xx 20 - Fault, aeration indicatedxxE xx xx 45 20 - Spacing indicatorxxC xx xx 43 20 - Zeromatc channel faultxxB xx xx 42 20 - Empty Pipexx7 xx xx 37 20 - hi/lo flowrate
Location of the bytes The “Status/Alarms” register pair for the meter path, for example 30011-30012 (see suppliedRegister Map for your flowmeter), would contain bytes 1 thru 4 as {b1b2} in 30011, {b3b4}in 30012.
ModBus 1015N-5M
50 1015N-5FM-1
Metasys Compatibility Status 1015N-5M ModBus/N2 Protocol Converter Module
The following Siemens System 1010 Non-Intrusive Flow and Thermal Energy Flowmetersare listed by Johnson Controls as Metasys Compatible:
FUS 1010N Single Channel Flow Meter w/N2 Comm 1015-5M V3.0FUS 1010DN Dual Channel Flow Meter w/N2 Comm 1015-5M V3.0FUS 1010MN Four Channel Flow Meter w/N2 Comm 1015-5M V3.0FUE 1010EN Single Channel Thermal Energy Flow Meter w/N2 Comm 1015-5M V3.0FUE 1010EDN Dual Channel Thermal Energy Flow Meter w/N2 Comm 1015-5M V3.0
Metasys Compatibility Status
JCI assigns Metasys Compatibility status to products of a specific software/hardwaredesign. Any future software/hardware revisions made to a module or main circuit board,which supports network communications, should be reported to the JCI MetasysCompatibility Program team. For insignificant changes, JCI may simply update the MetasysCompatible Products database and extend Metasys Compatible status to the newly revisedproduct(s). For changes that JCI considers significant (potentially affecting compatibility),either limited re-testing and/or site verification may need to occur before JCI can extendMetasys Compatible status to the newly revised product(s). Other expectations aredescribed in the Metasys Compatible Logo License Agreement