1 / 12

Typical Shelter Hardware Components

Finding That Elusive Pot of Gold or Networking Your Shelter Rebecca Peltzer & Jennifer Bradley, Polk County – Air Quality Steve Drevik, Agilaire. Typical Shelter Hardware Components. Data Acquisition Front End Data Logger or PC Internet Access Device Wireless IP Modem DSL / Cable Modem

jacksonloretta
Download Presentation

Typical Shelter Hardware Components

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Finding That Elusive Pot of Goldor Networking Your ShelterRebecca Peltzer & Jennifer Bradley, Polk County – Air QualitySteve Drevik, Agilaire

  2. Typical Shelter Hardware Components • Data Acquisition Front End • Data Logger or PC • Internet Access Device • Wireless IP Modem • DSL / Cable Modem • Satellite • Router • May be built into Internet Device • Analyzers and Samplers • New analyzers are Ethernet-capable • Most are still serial, but terminal servers can be used to connect them to a network or a logger

  3. Software Components • Data Acquisition Software • Connections within the shelter • Logger to analyzer • External from the main DAS server • Central DAS to logger • Central DAS to analyzer • Diagnostic / Remote Control Software • Any client PC to analyzer • Specialty Software • Download sampler data • Note that in a networked environment, the location isn’t important to the software • But how do we make the most of all of these options and components?

  4. Our Architecture – A work in progress • Our Analyzers: • 2 Model 8832 data loggers • 2 collocated 49i Ozone • 1 43i-TLE SO2 • 1 48i-TLE CO • 142i NOx • 2 collocated PM2.5 BAM-1020 • Meterological Station: Wind Speed, Wind Direction, Relative Humidity, Ambient Temperature • Site is polled over private LAN connection inside the firewall. • All analyzer connections were retained as analog

  5. Our Shelter Network • Our analog data system- E-Das Ambient through Agilaire • Problems: • Limited digital capabilities • 1 ug/m3 error in BAM data • Data limitations • Teom-only 3 analog outputs • No metadata • Thermo i-Series analyzers with ethernet capabilities • Easy Transition to AirVision • Same hardware • Just a software upgrade

  6. Introduction to Ethernet/Modbus • Modbus over Ethernet was the ideal choice for the digital communications: • Transmission is error checked • Standardized protocol • Much faster than RS-232 • Easier to troubleshoot with diagnostic tools built into the 8832 data logger • Modbus only requires that the data logger knows the following: • Analyzer IP • we set • Analyzer port • defined by manufacturer • Register # in analyzer • from analyzer manual • What destination channel/parameter in the 8832 / AirVision • we choose

  7. Digital Programming • AirVision simplifies the configuration process: • MODBUS • select the analyzer brand and register you want, and the Modbus control file is automatically downloaded. • Direct Instrument Polling • AirVision can directly download data • BAM-1020 • Teoms • 3-steps Process: • Open up a connection to instrument • Send commands to retrieve data in native format • Run File Import Tool to import into database

  8. Metadata • Gives us remote trouble-shooting capability • Collect continuous diagnostic values • Or on demand only when there are problems • Thermo i-series - diagnostic data • Flows • Internal temperatures • Intensity • BAM-1020 • Relative humidity • Average hourly volume • Ambient temperature

  9. BAM-1020: Analog Data Issues • Difficult data collection to ensure data is reported in the same hour it’s collected: • Standard Average Channel • Average Math Channel • Digitally Timed Event • Contact Closure-clock sync program • 1ug/m3 error in analog data • Manual download of BAM internal data • Data editing – lengthy process • Adjusting data collected by data logger to match BAM internal data

  10. BAM-1020: Digital Solution • The BAM can be directly polled by AirVision via a terminal server. • No 1ug/m3 error in digital data • AirVision runs a File Import Tool to import data: • Stores data in correct hour of collection • Data is error checked for 3 consecutive hours • No need for manual data download • Digital data is downloaded directly from BAM on hourly basis • Data editing – quick and easy • No More comparing hourly data collected by logger to data downloaded from BAM

  11. Hyperterminal, iPort, etc AirVision WAN IP/Port = 22.33.44.55 : 9000 WAN IP/Port = 22.33.44.55 : 9001 Router / Switch LAN IP/Port = 192.168.1.4 : 9881 LAN IP/Port = 192.168.1.5 : 3000 Things you might need to know for your project • Our network architecture from Central to Site to site devices is simplified since everything is on the same network. • Most of you will have access through another gateway device (wireless IP, cable modem, etc). • You will need to use Network Address Translation or Port Forwarding settings in your router to direct traffic from WAN side ports to LAN side IP/ports • We’re scientists, not network experts, so we rely on support from our DAS vendor, Agilaire, to help us with each project, since every shelter network architecture can be unique.

  12. Planning Your Project / Avoiding Pitfalls • Must have correct firmware in BAM-1020 • 3.4.3 or newer • Contact Met-One • Must have Modbus Interface and correct firmware installed on 8832s • 2.14 or greater • Contact Agilaire • Must have a block of IP addresses available • Each individual analyzer requires its own address • All else fails, contact Agilaire

More Related