Difference between revisions of "HwgMonitor"
| Line 37: | Line 37: | ||
== Datapoints == | == Datapoints == | ||
| − | + | The I/O Server generates asynchronous events based on the status of the devices input pins. The output data points can be written to control the output pins. | |
| − | |||
| − | |||
| − | |||
| − | The I/O Server generates asynchronous events based on the status of the | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 50: | Line 46: | ||
|- | |- | ||
| − | | | + | |model |
| − | | | + | |model id |
|R | |R | ||
| − | | | + | |the device model, as returned in the <model> tag of the XML response |
| + | |||
|- | |- | ||
| − | | | + | |<sensor name> |
| + | |value | ||
|R | |R | ||
| − | |input < | + | |the value returned for input <sensor name>, as returned in the <value> tag of the XML response |
| + | |||
|- | |- | ||
| + | |<sensor name>.cnt | ||
| + | |counter value | ||
| + | |R | ||
| + | |the counter value returned for input <sensor name>, as returned in the <cnt> tag of the XML response (for Damocles devices) | ||
| − | | | + | |- |
| − | | | + | |<sensor name>.units |
| + | |units | ||
|R | |R | ||
| − | | | + | |the units string returned for input <sensor name>, as returned in the <units> tag of the XML response |
|- | |- | ||
| + | |rowspan="2" |<output id> | ||
| + | |0 | ||
|W | |W | ||
|set output <n> to off | |set output <n> to off | ||
|- | |- | ||
| + | |1 | ||
| + | |W | ||
| + | |set output <n> to on | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|} | |} | ||
| + | |||
| + | |||
| + | {{note|Please note that while the assigned sensor name is used to identify sensors, the outputs are identified with their IDs, not the names.}} | ||
== Release Notes == | == Release Notes == | ||
Revision as of 17:23, 24 March 2014
The HWGMONITOR I/O Server supports the following monitoring devices from HW group:
- Damocles
- Poseidon
- STE
- WLD.
Contents
HSYCO Configuration
Add an HWGMONITOR I/O Server in the I/O Servers section of the Settings and set its parameters:
Communication
- IP Address: host name or IP address of the device
- IP Port: TCP/IP port to use, leave blank to use default port 80.
High Availability
- Shutdown when inactive: defaults to true (these devices accept multiple connection and could be accessed by two HSYCO servers simultaneously).
Options
There are no available configuration options for the HWGMONITOR I/O Server.
Monitoring Devices Configuration
This I/O Server uses the XML format and HTTP requests to constantly poll the devices for the current status.
All HWg monitoring devices allow you to assign custom names to each sensor connected to a device. The name is important, as it is used by HSYCO as the id to retrieve the sensor’s data. You should configure these names, using the configuration interface of the device.
Refer to the device manual for detailed configuration information.
Datapoints
The I/O Server generates asynchronous events based on the status of the devices input pins. The output data points can be written to control the output pins.
| ID | Value | R/W | Description |
|---|---|---|---|
| model | model id | R | the device model, as returned in the <model> tag of the XML response |
| <sensor name> | value | R | the value returned for input <sensor name>, as returned in the <value> tag of the XML response |
| <sensor name>.cnt | counter value | R | the counter value returned for input <sensor name>, as returned in the <cnt> tag of the XML response (for Damocles devices) |
| <sensor name>.units | units | R | the units string returned for input <sensor name>, as returned in the <units> tag of the XML response |
| <output id> | 0 | W | set output <n> to off |
| 1 | W | set output <n> to on |
Release Notes
3.0.1
- Fixed a bug that could block the update of the systemtopo.txt file at start-up.
2.8.4
- Support for the HWg Damocles line of products, with input lines counters.
2.8.0
- Initial support.
HWg is a registered trademark of HW group s.r.o.
