fsa1027 - project notes

Project Notes

Reference = FSa1027

ModbusRTU, BAcnet MSTP and Rockwell ‐ FS30

Rev 2 – 2011Jan27

Support : Call 1866 383 1657 ext 200 and quote the reference number or email [email protected] Good Practice: When you have commissioned this project please execute procedure 9 “backup your configuration, firmware and other files” in the attached support procedure. It uploads the configuration and capture diagnostic info. Send us the upload.zip file so we have a record of the site in case you ask for support in the future.

1. Objective.

All Field Data is read into the PLC’s internal arrays, then it is unpacked, bytes extracted, bit are extracted, values are scaled. All this data is packed into a buffer allocated to each field device. These buffers are written to the PLC. The FieldServer reads a set of buffers from the PLC. This data is then served to the BMS. The purpose of this strategy is to give the PLC a chance to manipulate some of the field data, calculate and add new data (such as alarms) and have this data served to the BMS.

Map 3 MobdusRTU Boilers onto MSTP and Rockwell

Map 4 Emmerson Drives onto MSTP and Rockwell

Ethernet Network

Diagnostics

Ethernet Connection can carryBACnet-IP and/or BACnet-Ethernetand/or Ethernet-IP. Flavour ofBACnet depends on installedfirmware.

Connection via std networkinginterfaces such as hubs, switches,routers.

Modbus Device Modbus Device

FS30 Series

MSTPDevice

MSTPDevice

PossibleBACnet MSTP

Front End /Controller

Rockwell PLC(s)

Ethernet/IP protocol

2x Spare RS232 portscan be used forModbus or MSTP(add $100 232/485converter to use theseports)

2. Port Allocation

RS485 Port R1 = ModbusRTU for Boilers and VFD’s

RS485 Port R2 = BACnet MSTP

3. FieldServer IP Address Execute step 3 of the support procedures to change

As Shipped

Port N1

192.168.1.84

255.255.255.0

192.168.1.1

Port N2

192.168.1.83

255.255.255.0

192.168.1.1

4. Device Addresses

Field devices need to be configured with the following addresses or the config file must be changed.

Nodes

Node_Name ,Node_ID ,Protocol ,Port,

Boiler01 ,1 ,Modbus_RTU ,R1 ,



VFD_a ,4 ,Modbus_RTU ,R1 ,

VFD_b ,5 ,Modbus_RTU ,R1 ,

VFD_c ,6 ,Modbus_RTU ,R1 ,

VFD_d ,7 ,Modbus_RTU ,R1 ,

Note / change addresses here. No duplicates.

5. Boiler Data Flow

Client reads data into DA_4xxxx01

Moves split the byte apart (Vendor shares each word with 2 variables)

Moves

Function ,Source_Data_Array ,Source_Offset ,Target_Data_Array ,Target_Offset ,Length

1.i16‐2.i8 ,DA_4xxxx01 ,0 ,DA_BYTE01 ,0 ,461

Each byte value is scaled in preparation for serving

Moves

Source_Data_Array ,Source_offset ,Target_Data_Array ,Target_Offset ,Length ,Function ,Source_Low_Scale ,Source_High_Scale ,Target_Low_Scale ,Target_High_Scale

DA_BYTE01 ,00 ,DA_BOILER01 ,00 ,1 ,Scale ,0 ,100 ,0 ,100 // State

The entire array is served with an active write to the PLC as an EthernetIP tag, (An array of floats)

The FieldServer reads back a similar (maybe equal) array from the PLC and uses this data to serve to the BMS. This gives the PLC a chance to manipulate this data.

6. VFD Data Flow

Client reads data into DA_4xxxxa

Each value is scaled in preparation for serving

Moves

Source_Data_Array ,Source_offset ,Target_Data_Array ,Target_Offset ,Length ,Function ,Source_Low_Scale ,Source_High_Scale ,Target_Low_Scale ,Target_High_Scale

DA_4xxxxa ,01 ,DA_VFD___a ,0 ,1 ,Scale ,0 ,100 ,0 ,100 // Freq_Speed ref

The entire array is served with an active write to the PLC as an EthernetIP tag, (An array of floats)

The FieldServer reads back a similar (maybe equal) array from the PLC and uses this data to serve to the BMS. This gives the PLC a chance to manipulate this data.

7. EthernetIP Data

The FieldServer sends field data to the PLC for inspection and manipulation.

The FieldServer reads data from the PLC to serve to the BMS. Most of this data will be the same/similar to the field data sent to the PLC, some will be changed and some additional data may be added.

There are 7 tags. Each is an array of floats. One for each device. Note the tag names and lengths below

These map descriptors write raw data to the PLC.

Map_Descriptors,

Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,EIP_CON_TYP ,Node_Name ,Function ,EIP_PATH ,EIP_SERVICE ,EIP_TAG_NAME ,Length, Scan_Interval,

BOILER01_toPLC ,DA_BOILER01 ,0,EXPLICIT ,EIP_01 ,wrbc ,1 0,DATA_TABLE_WRITE ,boiler01_data,47, 1.0s,



VFD_A_toPLC ,DA_VFD____A ,0,EXPLICIT ,EIP_01 ,wrbc ,1 0,DATA_TABLE_WRITE ,vfd_a_data,63, 1.0s,

VFD_B_toPLC ,DA_VFD____B ,0,EXPLICIT ,EIP_01 ,wrbc ,1 0,DATA_TABLE_WRITE ,vfd_b_data,63, 1.0s,

VFD_C_toPLC ,DA_VFD____C ,0,EXPLICIT ,EIP_01 ,wrbc ,1 0,DATA_TABLE_WRITE ,vfd_c_data,63, 1.0s,

VFD_D_toPLC ,DA_VFD____D ,0,EXPLICIT ,EIP_01 ,wrbc ,1 0,DATA_TABLE_WRITE ,vfd_d_data,63, 1.0s,

These map descriptors read data from the PLC. The data is then served to the BMS

BOILER01_fromPLC ,Db_BOILER01 ,0,EXPLICIT ,EIP_01 ,rdbc ,1 0,DATA_TABLE_READ ,plc_boiler01_data,47, 1.0s,



VFD_A_fromPLC ,Db_VFD____A ,0,EXPLICIT ,EIP_01 ,rdbc ,1 0,DATA_TABLE_READ ,plc_vfd_a_data,63, 1.0s,

VFD_B_fromPLC ,Db_VFD____B ,0,EXPLICIT ,EIP_01 ,rdbc ,1 0,DATA_TABLE_READ ,plc_vfd_b_data,63, 1.0s,

VFD_C_fromPLC ,Db_VFD____C ,0,EXPLICIT ,EIP_01 ,rdbc ,1 0,DATA_TABLE_READ ,plc_vfd_c_data,63, 1.0s,

VFD_D_fromPLC ,Db_VFD____D ,0,EXPLICIT ,EIP_01 ,rdbc ,1 0,DATA_TABLE_READ ,plc_vfd_d_data,63, 1.0s,

Other_fromPLC ,Db_OTHER ,0,EXPLICIT ,EIP_01 ,rdbc ,1 0,DATA_TABLE_READ ,plc_other_fs_data,200, 1.0s,

8. Appendix – Emerson Affinity 1 Drive Modbus Info

Relationship between parameter and Modbus register Number

Param xx.yy = Holding Register (4xxyy – 1 )

Eg

param 1.01 = 40100

param 10.20 = 41019

List of points requested

1.01 Frequency reference/Speed reference

1.02 Frequency reference/Speed reference

1.03 Pre-ramp reference 2.01 Post-ramp reference 3.01 Final speed reference 3.02 Speed feedback 3.03 Speed error 3.04 Speed controller output 4.01 Current magnitude 4.02 Active current 4.17 Magnetising current 5.01 Output frequency 5.02 Output voltage 5.03 Power 5.05 DC bus voltage 7.01 Analog input 1 7.02 Analog input 2 7.03 Analog input 3

10.01 Drive OK 10.02 Drive Active 10.03 Zero Speed 10.06 At Speed

10.09 Drive Output Is At Current Limit 10.15 Mains Loss 10.16 Undervoltage Active 10.17 Overload Alarm 10.18 Drive Overtemp Alarm 10.20 Trip 0 10.21 Trip 1 10.22 Trip 2 10.23 Trip 3 10.24 Trip 4 10.25 Trip 5 10.26 Trip 6 10.27 Trip 7 10.28 Trip 8 10.29 Trip 9

Boiler Data

Various FieldServer Support Procedures for Customers

Warning: Some procedures call for you to restart the FieldServer. Only do this when you are authorized and it is safe to do so.

1. Objective. 1

2. Appendix – Emerson Affinity 1 Drive Modbus Info 7

1. Install Utilities 18

2. Connect Cables and Prepare to Use Ruinet (Remote User Interface) 18

3. This is how you re‐assign the FieldServer IP 20

4. Capturing Diagnostic Info 20

5. Capturing Ethernet Traffic 20

6. This is how you download the configuration file. 21

7. This is how you download new firmware 21

8. This is how you upload the configuration file. 22

9. This is how backup your configuration, firmware and other files. 23

10. This is how you ‘take a log’ 23

11. This is how you download a point count license file. 24

12. Poking Data into a FieldServer for Test purposes. 24

1. Install Utilities

You can download from here: (Preferred)

Download Installl.zip from this page: http://www.fieldserver.com/techsupport/utility/utility.php

Or install from the memory stick shipped with the FieldServer.

2. Connect Cables and Prepare to Use Ruinet (Remote User Interface)

Use standard Ethernet patch cables.

Connect your computer to a hub/switch

Connect the FieldServer to the hub/switch.

If the computer’s IP Address and the FieldServer’s IP Address are not on the same subnet then the utility will use broadcasts. You can avoid this by changing your computer IP to be on the same subnet as the FieldServer. Then you can connect, reassign the FieldServer IP Address (reboot after changing) and then change your computer IP Address back. There are some limitations to using broadcasts but you can download configurations, firmware and do some monitoring.

You may need to turn off your windows/other firewall(s).

Start the Ruinet application.

3. This is how you reassign the FieldServer IP

1. Download and install the FieldServer Utilities. a. http://www.fieldserver.com/techsupport/utility/utility.php b. Download install.zip c. Install.

2. Connect a cable to you computer and start RUInet (Remote User Interface) 3. From the main menu 4. Type I for IP – you are presented with a page of IP Info 5. Make the changes as required. 6. When the download is complete, push any key, return to the main menu using ESC and the restart the

FieldServer to give effect to the new configuration 7. Quit ruinet and then restart it.

4. Capturing Diagnostic Info

1. This procedure captures diagnostic info, uploads a copy of the config in use, uploads the firmware and other files that are in use and captures some serial communications. If you are having problems with an Ethernet protocol you will need to simultaneously execute the procedure to capture Ethernet Traffic.

2. More detail to this procedure is provided in ENOTE0083. http://www.fieldserver.com/docs/pdf/ENOTE0083‐FST_Diag.pdf


4. Connect a cable to you computer and start RUInet (Remote User Interface). 5. Quit Ruinet – we simply wanted to establish that you can connect. 6. Use the FST_Diag tool: Start ‐> All Programs ‐> FieldServer Utilities ‐> Tools ‐ > FST Diagnostic 7. At one point in the capture you will be asked to reproduce the events that caused the error. 8. When the capture is complete email the upload.zip file produced by the tool to [email protected].

5. Capturing Ethernet Traffic

1. Details to this procedure are provided in ENOTE0063. You will download and install the freeware Wireshark. This tool captures all Ethernet traffic on your computer.

2. http://www.fieldserver.com/docs/pdf/ENOTE0063‐How_to_take_Ethernet_Captures.pdf

6. This is how you download the configuration file.


2. The config file config.csv must be placed in this folder. c:\FieldServer Technologies\FieldServer Utilities\Config

3. Connect a cable to you computer and start RUInet (Remote User Interface) 4. From the main menu 5. Type D for download – you are presented with a download page 6. Type D to start the download. You will see a byte counter as the download proceeds 7. When the download is complete, push any key, return to the main menu using ESC 8. Restart the FieldServer to give effect to the new config.

7. This is how you download new firmware


2. Copy the firmware file to this folder c:\FieldServer Technologies\FieldServer Utilities\Config File Name=fserver.img for FS20 and FS40 , File Name=nlx30 for FS30 File Name=nlx25.bin for FS25 File Name=nlpn.bin for CAS25

3. Connect a cable to you computer and start RUInet (Remote User Interface) 4. From the main menu 5. From the main menu 6. Type D for download – you are presented with a download page 7. Push the ‘F’ key to tell the fieldserver you wish to download firmware 8. Type D to start the download. You will see a byte counter as the download proceeds 9. When the download is complete, push any key, return to the main menu using ESC 10. Restart the FieldServer to give effect to the new firmware.

8. This is how you upload the configuration file.


2. Connect a cable to you computer and start RUInet (Remote User Interface) 3. From the main menu 4. Type U for upload – you are presented with a upload page 5. Type U to start the upload. You will see a byte counter as the upload proceeds 6. When the upload is complete, push any key, return to the main menu using ESC 7. The config file config.csv is place in this folder.

a. c:\FieldServer Technologies\FieldServer Utilities\Config 8. Reverse the process to download a config from the PC to the FieldServer using D for download. After the

file has been downloaded you should restart the FieldServer to give effect to the new config.

9. This is how backup your configuration, firmware and other files. Or

10. This is how you ‘take a log’


2. A single utility is used to backup all the files on the FieldServer and to capture diagnostic info. 3. Connect a cable to you computer and start RUInet (Remote User Interface). Once you have established

the connection, quit RUInet. 4. Start‐>FieldServer Utilities‐>Tools‐>Diagnostic Utility

Or Start‐>FieldServer Utilities‐>FST Diagnostic

5. Once you have started the tool you need to 1) find the FieldServer, 2)take the log and 3) send or store the file upload.zip.

a. Click button 1. 1. A FieldServer IP Address appears in the pull down list 2. Select the FieldServer

b. Click button 2. 1. A series of files are uploaded. No user action is required. 2. You are prompted to reproduce the error being reported. 3. You have a 5 minute window to take the actions required. 4. During this time, make notes and record the amount of time elapsed since the start.

Eg 30 secs – activated pull station 60 secs – pushed system reset

c. When the log has completed click button 3. Locate the log file. Its called upload.zip d. Open the file. In most cases it should contains some files name something similar to

com_a_p1.log. They will only be present if you are using a serial protocol. e. They will not be present if you are using a combination of Lonworks and Ethernet Protocols. f. If you expect them to be present or you are not sure then please call and ask for help. These files

can be very important and their absence might require another site trip. 6. Send us your notes and the upload.zip 7. Upload.zip is a very good backup. It contains the firmware, configuration and other important files and

settings. a. Inside the file upload.zip you will find upload0.csv. This is the backup of your config.csv. You will

also find cb8menu.e__ This is the typical name of the firmware. To use the backup config file you will need to rename upload0.csv to config.csv and rename cb8menu.e__ to fserver.img. After that you can use the procedure above to download them for use on the FieldServer.

11. This is how you download a point count license file.


2. The license file slots.ini must be placed in this folder. c:\FieldServer Technologies\FieldServer Utilities\Config

3. Connect a cable to you computer and start RUInet (Remote User Interface) 4. From the main menu 5. Type D for download – you are presented with a download page 6. Type O for Other Files 7. Type L for Local

You are prompted to type Entry: Type slots.ini and push the Enter Key The Remote file name is auto set to slots.ini too.

8. Type D to start the download. You will see a byte counter as the download proceeds 9. When the download is complete, push any key, return to the main menu using ESC 10. Restart the FieldServer to give effect to the new license file.

12. Poking Data into a FieldServer for Test purposes.

1. Connect a cable to you computer and start RUInet (Remote User Interface) 2. From the ruinet main menu 3. Select A for Arrays 4. You see a list of arrays 5. Each is numbered on the left hand side with an index number – 01,02 …. 6. To see details for an array type the index number eg. 01 7. You see details for the array – a header section and a grid of data. 8. The 1st element in the grid (top left corner) corresponds to offset zero, moving to the right on that

row you get offset 1,2,3,4.. 9. To Poke data into an offset 10. Eg Type: M0 1<Enter> (This means Modify offset zero to the value 1) 11. Eg. Type M1 123<Enter> (This means modify offset 1 to the value 123) 12. Note the space between the offset and the new value. 13. Note that for some data formats such as ‘byte’ the offset is specified in hex. 14. Note if you poke data into a location that is normally updated by data that is being read from the

Field Device, then the poke, will often (depends on protocol) result in the new value being written to the Field Device.

fsa1027 - project notes

Documents