Fieldservers can act as web servers serving html pages, files, images and real time data. The web pages can be animated based on the real time data acquired by any protocol.
Using these features, the FieldServer can be configured to serve real time data using REST and SOAP. Notes towards the bottom of this page describe the capabilities of this driver.
We have module solutions which allow integration directly into HTTP as well as the stand alone solutions shown bottom right.
Range of Conversion Solutions
Depending on project requirements select from units with varying resources, and multi port devices. OEM and embedded solutions too.
|FS20 Series||1x RS232/485||1x Ethernet||1x Lonworks|
|FS25 Series||2x RS232/485||1x Ethernet|
|FS30 Series||2x RS232 and 2x RS485||2x Ethernet||1x Lonworks||FieldBus Support:eg Profibus, DeviceNet etc
Hot Standby Support
|FS40 Series||10x RS232 and 2x RS485||2x Ethernet||1x Lonworks||FieldBus Support: eg DH+, MB+, Profibus, DeviceNet etc
Hot Standby Support
|SlotServer||1x RS232/485||1x Ethernet||1x Lonworks||For Rockwell ControlLogix 5600|
Lonworks and Fieldbus are options not proviced on base models.
FS30 series shown for purposes of illustration. Capability depends on hardware, firmware and configuration.
FieldServer’s Web Server
In a nutshell:
- The FieldServer reads data from field devices.
- This data can be used to animate web pages that can be served by the FieldServer.
- Using a browser, a customer or user can monitor data from field devices and also control them.
A little more detail:
The FieldServer Web Server allows you to display and change data in a FieldServer. The FieldServer’s data is obtained by communication with remote devices such as gas Detectors, Lighting Controllers and many more.
The web server is a front end HMI (human machine interface) that can serve screens and data to any web browser such as Internet Explorer. Amongst other things, it allows your users to view and change values on your devices without having to install any special software or be anywhere near the site.
Since the system is built in to a webpage, most of your users should already have the required skills to operate the system (click the link, push a button, flip a switch), a lower learning curve and less training. So simple that just about anyone can operate the system.
Your users can connect and change values on your devices from anywhere that has an internet connection and a web browser. Imagine sitting down in the comfort of your own home, and browsing to your site, viewing the status and making any changes that are needed, then rolling over and going back to sleep, with having to set one foot on the site.
The values on your device can be displayed in a number of ways from simple text and progress bars to animated images and sliders, it’s up to you how you want to display your data and the system is flexible to do just about anything you can think of, while remaining simple enough for anyone to use.
The system uses a simple template tag system to display and change the data on your devices; these tags can be inserted into any html document and placed on the FieldServer. The server will then will run through and strip out these tags and replace them with the data from your device. It’s much simpler then it sounds, put this tag where you want to show your data. The template tags are built with web designers in mind, there simple to use and simple to debug.
How it all works
This system works by creating a mini web server on our FieldServer that the users can browse to. When a user browses a webpage, the FieldServer searched the html document for special template tags, if the FieldServer finds these special template tags in the html document, it replaces them with data from your device. When you push a button on one of these web pages, the value is sent from your webpage to the FieldServer, to your device.
Step 1: FieldServer is configured to read data from field devices using RS232/ RS485/ Ethernet, Controlnet, DeviceNet, DH+, Modbus+ and any combination of drivers from the extensive protocol library. Over 100 protocols are available.
Step 2: A browser surfs the FieldServer. Pages served are just like any other html pages except that they can include animations based on the real time data obtained from the field devices. The pages can also contain elements to change the data in the FieldServer. These changes then get sent back down to the field devices, if this is what you require.
Step 3: Data read from the field devices can also be served to other field devices using another protocol. It depends on your requirements.
These are some of the examples you can produce with this system, the system is only limited by your imagination.
In this simple example we are only using the very basics of the template system, (display text and action buttons) but you can instantly see the power of this system, it’s easy to read, it’s easy to operate, it provides all the information that the user needs about the building.
Sleek and Pretty Example
In this example we put an information tag on an image of the factory; the loading doc has two tags associated with it, Lights and AC. You can see that the lights are on and the AC is off, the boarder is flashing red indicating a panic, the user then could click on this tag and get a screen similar to the one above where they can get more information and acknowledge the alarm.
In this example we copied the front display of the real device, anyone that has used the device before can quickly and easily navigate this interface.
Data Sheets and Manuals
HTTP Web Site: www.w3.org/Protocols/
Need more info ? Call or email us.
Metasys® as used in this document is a trademark of Johnson Controls, Inc.