Transcript ProtoCom-Lon - Sierra Monitor
Electro Industries’ ProtoCom Training Presented by: Sean Gaines Accounts Development Manager
Presentation Highlights
Session Summary
• Introduction • BMS Networking 101 • Installation Overview • ProtoCom Demo • Troubleshooting ⁻ FieldServer Toolbox - Taking Logs
Who is ProtoCessor
• • • • • OEM Division of FieldServer Technologies Leader in the OEM Protocol Gateway market. (190+ OEMs) We provide preprogrammed/tested protocol gateways for the OEMs.
2 SKU’s preprogrammed to support all OEM meters to multiple protocols.
Complete Turnkey solution – Dynamically supports 1 or multiple EIG Meters to one ProtoCom – No configuration files to manual build or load – Dock to Stock to Field. – Easiest to install/support – We are there when YOU need us.
Benefits of The EIG ProtoCom
• • • • • • • • Branded Electro Industries Easiest to Install The Best Support on Market 2 Part numbers support all of EIG’s BMS needs – – BACnet MS/TP, BACnet/IP, Metasys N2, EtherNet/IP, AB DF1, Modbus TCP/IP LonWorks No config files to build/load – Provides BMS protocols for 9 of EIG’s products Supports BACnet Virtual nodes.
– Each EIG meter appears as a separate device on BACnet network.
No Proprietary software needed to install gateway.
BACnet BTL and LonMark Certified
Supported Devices:
Shark ® 100 Meter Shark ® 200 Meter Nexus ® 1252 1262 1272 Meters DMMS 425 Meter Nexus ® 1500 Meter MP200-Y Metering System MP200-S Metering System
EIG 2 Methods of Configuration
•
2 Methods of Configuration:
Auto-Discover supported RS-485 meters Modbus RTU Serial Protocol • • •
BACnet MS/TP Metasys N2 AB DF1
Ethernet Protocols • • •
BACnet/IP AB EtherNet/IP Modbus TCP/IP Supports any mix of RS-485 meters:
EIG 2 Methods of Configuration
•
2 Methods of Configuration:
Auto-Discover supported RS-485 meters Modbus RTU Serial Protocol • • •
BACnet MS/TP Metasys N2 AB DF1
Ethernet Protocols • • •
BACnet/IP AB EtherNet/IP Modbus TCP/IP
•
Supports any mix of RS-485 meters: Including multiples of any meters
EIG 2 Methods of Configuration
• •
2 Methods of Configuration:
Auto-Discover supported RS-485 meters Web-Configurator for Modbus TCP/IP and RS-485 meters Modbus TCP/IP Modbus RTU
ProtoCom
Serial Protocol • • •
BACnet MS/TP Metasys N2 AB DF1
Ethernet Protocols • • •
BACnet/IP AB EtherNet/IP Modbus TCP/IP
EIG 2 Methods of Configuration
• •
2 Methods of Configuration:
Auto-Discover supported RS-485 meters Web-Configurator for Modbus TCP/IP and RS-485 meters
ProtoCom-Lon
•
LonWorks
Modbus TCP/IP Modbus RTU
Electro Industries ProtoCom Auto-Discovery
Dynamic Building of Configurations
• • • • • • •
Auto-Discovery Method:
Discoverable Profiles are preloaded for EIG Meters.
Each Profile has a unique expected register/value.
ProtoCom polls each Modbus Node-ID address 1 to 255.
Tests each device with stored Profiles until match is confirmed.
When a Profile is identified, the Profile gets loaded into memory.
Once the polling is completed (255 node address), Profiles build and load Configuration file.
The devices are installed .
Electro Industries ProtoCom Web-Configuration
• • • •
Web-Configurator:
Offers Modbus RTU / Modbus TCP Profiles for all 9 EIG meters.
Must be used for Ethernet
meters (Modbus TCP meters cannot be Auto-Discovered).
Can also be used for any RS-485 meters (with or without Modbus RTU Auto-Discovery).
Dynamically builds the required Configuration file.
BMS Networking 101: Primary BMS Network Protocols
North American Market Share
BACnet Metasys N2 LonWorks
8% 4% 32%
LonWorks
56%
BACnet
BACnet MS/TP vs. BACnet/IP
BACnet IP 10% BACnet MS/TP 90%
BMS Networking 101: BACnet/IP
Typical BACnet/IP network
• BACnet/IP on Ethernet backbone – BMS front-ends are on BACnet backbone monitoring/controlling the devices BMS System BACnet/IP Switch/Router BACnet/IP
BACnet/IP Backbone
BMS Networking 101: What A BACnet Network Looks Like
BACnet MS/TP Trunk #1 BACnet MS/TP Trunk #2 Modbus RTU • • • • • • • • • • • • • • Fire Alarms Chillers Boiler Controls Power Systems Variable Frequency Drives Elevators Generators Lighting Controls HVAC Security Indoor Air Quality Energy Management Smoke Control And More
BMS Networking 101: BACnet MS/TP & BACnet/IP
•
BACnet MS/TP >> BACnet MS/TP MAC Address + BACnet Device Instance
• • • • • 32 devices per trunk, with multiple trunks Connected with twisted pair wire; the 2 wires have polarity Maximum length = 1,000 m BACnet MS/TP trunks use BACnet routers connect trunks to BACnet/IP backbones Serial data bandwidth •
BACnet/IP >> Network IP Address + BACnet Device Instance
• • • • • Point-to-point wiring; one device per trunk/cable Connected with CAT5 Ethernet cables Maximum length = 100 m Each junction/connection requires switch or router Ethernet data bandwidth
BMS Networking 101 LonWorks
LonWorks >> Only a LonWorks Admin can install LonWorks Devices on LonWorks networks.
• • • • Adding a Device is call Commissioning.
Requires a program like LonMaker.
Proprietary hardware and software architecture; Uses Echelon Neuron Chip.
BMS Frontend uses a PC running LonWorks Software.
>> EIG’s responsibility for Installing LonWorks ProtoCom-Lon:
• • • • Wiring the EIG meters to Connecting ProtoCom-Lon to the LonWorks network; connects with 2 wires (not twisted); No polarity.
Power the device up.
the ProtoCom-Lon.
Configure the meters’ Profiles via Auto-Discovery or Web-Configurator.
• Contact Network Admin for Commissioning.
Questions You Must Ask
BACnet MS/TP Networks:
• How many Meters do they have on site (to be installed)?
• What is the assigned BACnet MS/TP MAC address?
• What is the desired BACnet Device Instance value?
• What is the BACnet MS/TP baud rate for the BMS RS-485 network?
BACnet/IP Networks:
• How many Meters do they have on site (to be installed)?
• What is the assigned Network IP address for the ProtoNode on the BMS BACnet/IP network?
• What is the desired BACnet Device Instance value?
EIG Devices and Available Point Count Section 1.2
Do not exceed the supported point count:
• • ProtoCom cannot exceed 1500 Modbus registers ProtoCom-Lon cannot exceed 1000 Modbus registers
Devices Point Count Shark_100 Shark_200 Nexus_1252_1262_1272 DMMS_425 Nexus_1500 MP200Y MP200S Modbus Registers per meter
56 68 48 46 56 241 571
Examples:
Shark 200: 1500 / 68 = 22.05 >> 22 meters max (MP200S) + (16 x Shark 100) = ?
(571) + (16 x 56) = (571) + (896) = 1467 (MP200Y) + (3 x Shark 200) + (4 x Nexus 1500) = (241) + (3 x 68) + (4 x 56) = (241) + (204) + (224) = 669
ProtoCom Installation
1) Set COM Settings on ALL meters 2) ProtoCom DIP Switch Settings
– – – – Select Required Field Protocol (S Bank) Set BACnet MS/TP MAC Address (A Bank) Set BACnet MS/TP Baud Rate (B Bank) Turn on Auto-Discovery - if Discovering RS-485 devices.
3) Wiring
– – – – Wire EIG Modbus RTU meters to ProtoCom’s RS485 FIELD port And/Or: Wire EIG Modbus/TCP meters to ProtoCom’s Ethernet port Connect ProtoCom’s HOST port to BMS network (RS-485/Ethernet/LonWorks) Connect and provide Power to ProtoCom
4) Auto-Discovery and/or Web Configurator
– Discover or select Profiles
5) Change Network IP Address of ProtoCom (BACnet/IP only)
– Set IP Address for BACnet/IP with Web-Configurator
ProtoCom Installation 2.1 – Setting COMS on EIG meters
For Modbus RTU meters: SET the meter’s Modbus Node-ID
• • Modbus Node-ID values range between 1 and 255 Each meter must have a unique Node-ID value
Confirm the Serial Device Communications of the EIG meters
• •
ALL meters MUST use the SAME SETTINGS, as specified:
These settings were pre-determined and are “hard coded”
For Modbus/TCP meters: SET the meter’s IP Address
• • Must be on the same subnet as ProtoCom Example: 192.168.1.200
• Each meter must have a unique IP address • If the IP Address of the ProtoCom is going to be changed, set meter to use same subnet
SET the meter’s TCP_ID value
• Value must be in the range of 1 – 255 (typical default is 1) >> Record these values: You will need to know them later for Web-Configuration
ProtoCom Installation 2.2 – Setting BMS Field Protocol • •
ProtoCom
SET the desired BMS Field Protocol on ProtoCom with: S0, S1, S2 Use a very small screwdriver; be gentile
ProtoNode FPC-N34 Profile
BACnet IP BACnet MSTP Metasys N2 EtherNet IP DF1 Modbus TCP/IP Off
S0
On Off On Off On
S Bank DIP Switches
Off
S1
Off On On Off Off Off
S2
Off Off Off On On • •
ProtoCom-Lon
ProtoCom-Lon does not offer protocol options; it offers LonWorks (only)
On ProtoCom-Lon units switches S0, S1, S2 are disabled Switch Positions:
>> I
N
= O
N >> O
UT =
O
FF
ProtoCom Installation 2.3 – Enable Auto-Discovery
ProtoCom/ProtoCom-Lon:
• For new installations – – – Set DIP switch S3 to the ON position to “Enable Auto-Discovery“ of all of the EIG Modbus RTU Meters connect to the ProtoCom/ProtoCom-Lon.
LATER in installation: Provide power to ProtoCom; wait 3 minutes for Auto-Discovery to complete.
After Auto-Discovery completes, return DIP switch S3 to the OFF position.
ProtoCom Installation 2.4.1 – Set BACnet MS/TP MAC Address
ProtoCom
• •
BACnet MS/TP Installation:
• Set BACnet MS/TP MAC Address with DIP switch Bank A – See Appendix C.1 in Startup Guide for DIP switch settings.
– Value can ONLY be set within range of 1 through 127 (Master MAC Addresses).
Addresses between 128 to 255 are Slave Addresses (not discoverable by BMS).
Only 1 MAC Address per ProtoCom
ProtoCom Installation 2.4.2 – Set BACnet Device Instance
ProtoCom BACnet MS/TP and BACnet /IP both have a Device Instance:
• • • Device Instance = (Modbus Node-ID) + (ProtoCom’s Node_Offset) Node_Offset default value is 50,000.
Node_Offset value can be changed via Web Configurator.
Example • 1 st EIG meter Modbus Node-ID = 1 • • 2 nd EIG meter Modbus Node-ID = 22 Default Node_Offset value = 50,000 • • 1st EIG meter’s Device Instance = 50,001 2nd EIG meter Device Instance = 50,022
ProtoCom
ProtoCom Installation 2.5 – Set BACnet MS/TP Baud Rate
BACnet MSTP Installation:
• Set BACnet MS/TP Baud Rate for the BMS Field Network with DIP switch Bank B – BACnet MS/TP typically uses 38,400 or 76,800 (factory default = 38,400) – Metasys N2: Baud switches disabled on FPC-N34; factory set for N2 (9600)
ProtoCom Installation 2.6 – Connect Meters to HOST Port
ProtoCom/ProtoCom-Lon 6-Pin HOST Port connections:
• Connect Meters to RS485 HOST Port using Pins 1 & 2
ProtoCom Installation 2.7 – Wire FIELD Port to the RS485 Network
ProtoCom 3-Pin FIELD Port connections:
• Connect to the BACnet MS/TP (or AB DF1) BMS Network wiring using Pins 1 & 2
ProtoCom Installation 2.7 – Wire FIELD Port to the RS485 Network
ProtoCom-Lon 2-Pin FIELD Port connections:
• Connect to the LonWorks BMS Network with the LonWorks Port using Pins 1 & 2 – – Connection is polarity independent Medium is FT-10. All other LonWorks Mediums require a router.
• Network Admin: Commission Network using Service Pin Service Pin LonWorks TP/FT-10 interface
ProtoCom Installation 2.8/2.9 – Power & Auto-Discovery
ProtoCom /ProtoCom-Lon Powering the Unit:
• • • Power Unit on Pins shown:
Frame GND must be connected
12-24 Vac or 9-30 Vdc
Auto-Discover RS-485 meters:
• • • • Make sure S3 is turned on before power application.
Auto-Discover will take 3 minutes to find all discoverable devices.
One complete TX and RX will flash Rapidly. Turn S3 to off position to save configuration.
ProtoCom Installation 2.10.1 – Set BACnet Device Instance Enter Node_Offset
ProtoCom Installation Connecting to Web-Configurator
Web-Configuration Connecting Laptop to ProtoCom (Section 1.9):
• • • Set PC’s IP address to same Subnet as ProtoCom (192.168.1.xxx) Connect Laptop to Ethernet Port with CAT5 cable Open browser, enter the ProtoCom’s IP address (192.168.1.24)
ProtoCom Installation 2.10.1 – Set BACnet Device Instance
ProtoCom BACnet MS/TP and BACnet /IP both have a Device Instance:
• • Device Instance = (Modbus Node-ID) + (ProtoCom’s Node_Offset) Node_Offset default value is 50,000.
• Node_Offset value can be changed via Web Configurator.
Example:
•
Node_Offset (required) = Device Instance (desired) - Node_ID
• • •
Desired Device Instance for 1st device = 1,001
Device 1 has a Modbus Node-ID of 1
Node_Offset (required) = 1,001 - (Node_ID) = 1,001 - 1 = 1,000
•
The Node_Offset value will be applied to all devices.
– Device 1 Instance will then be 1,000 + Node_ID = 1,000 + 1 = 1,001 – – Device 2 Instance will then be 1,000 + Node_ID = 1,000 + 22 = 1,022 Device 3 Instance will then be 1,000 + Node_ID = 1,000 + 33 = 1,033
ProtoCom Installation 2.10.1 – Set BACnet IP Address Click this button
ProtoCom Installation 2.10.1 – Set BACnet IP Address Enter IP Address Expand Tree > Select Network Settings
Web Configuration Adding Additional Meters (RS-485 or Ethernet)
Click “Add” button
Web Configuration Adding Additional Meters (RS-485 or Ethernet) Select a Profile
Web Configuration Adding Additional Meters (RS-485 or Ethernet) Enter Meter’s IP Address Enter Meter’s TCP_ID Plus fictitious Node-ID value: Range = 1-255 ProtoCom uses it for setting BACnet Device Instance
Web Configuration Adding Additional Meters (RS-485 or Ethernet) BACnet Device Instance for each EIG meter: 50,001 50,022 50,033 50,044
Electro Industries Demo ProtoCom Demo
Debugging Tools Troubleshooting Using FieldServer’ Toolbox Taking a Serial Data Capture
Debugging Tools
Requirements for successful data capture
• Laptop must be on same subnet as FieldServer • Diagnostic event must occur while capturing • If Ethernet traffic is important, Wireshark must be running at the same time
Debugging Tools – Tool Box
FST Toolbox available on www.ProtoCessor.com
website Main Menu > Tech Support > Utilities & Design Documents
Debugging Tools – Tool Box
Debugging Tools – Tool Box
• • • • Log File found in folder:
C:\FieldServer\FieldServer Toolbox\Config\Diagnostic_YYYY-MM-DD_HH-MM
Log zipped for user convenience: Diagnostic_2014-09-23_13-45.zip Diagnostic event must occur while capturing If Ethernet traffic is important, Wireshark must be running at the same time
ProtoCessor Contact Information
Support Contacts: Clarke Ramilo, Senior Application Engineer 8:00 am – 5:00 pm Pacific Time
FieldServer Technologies 1991 Tarob Court, Milpitas CA 95035 408-964-4444 [email protected]
Sean Gaines, Accounts Development Manager 8:30 am – 5:30 pm East Coast Time (Call me anytime; leave message)
408-964-4408 978-302-7239 Cell [email protected]
www.ProtoCessor.com
THANK YOU!
…..for taking the time to attend this presentation.
Questions?