
|
Point Server 900
RF Receiver and Web Data Server
Main Features
|
· Integrated 100mw, 900 MHz SSFH Transceiver
· Optional 2.4 GHz Transceiver
· Supports Point Sensors and Mesh Repeaters
· Communicates: Ethernet (TCP/IP) or serial port
· Integrated Modem
· Optional 4 hour UPS – alarm call-out on AC power loss
· Data Logger – logs periodic snapshots of the current readings & logs events
· Web Server – Dynamic HTML web page server showing current readings, alarms, age of last transmission and sensor serial numbers
· Event based alarms – callout or email
· Push connection to other hosts using TCP/IP
· Simple ASCII command/response protocol
· 100 Sensors (total of 200 I/O points) maximum
· 8600 Historical Record capacity
· 1800 Event Logging capacity
· Two level password security
· Each I/O configurable to trigger events
· Periodic callouts with interval times of 1 minute to 7 days
|
|

|
Description:
The HTML file can be viewed with any standard browser. » Click Here « to see real time data. A PC can communicate with the Point Server using TCP/IP or serial protocol. You can send commands using TCP/IP over the Ethernet or using Direct Dial/PPP. Serial commands can be sent using RS232 or DirectDial.
The Point Server is a 900 Mhz or 2.4 GHz RF receiver with an integrated data Web server.It receives CRC-16 error-checked data packets from Point Six’s Point Repeaters, processes the data, and makes the data available to be queried by simple ASCII commands or through dynamic HTML. The dynamic HTML can be viewed with any standard browser. A PC can communicate with the Point Server using TCP/IP or serial protocol. Simple ASCII commands are sent over the Ethernet using TCP/IP, RS232 serial port or modem. The Point Server contains a time of day clock, battery backed RAM, and flash programmable memory. It is fully configurable, both locally and remotely. It can store configuration information for up to 100 sensors having a combined maximum of 100 I/O points.
The Point Server was built with the flexibility needed to satisfy varied user requirements. Conceptually there are several modes of operation that allow the user to balance simplicity, costs, precision, and timeliness.

Monitoring - The easiest way to get information from the Point Server is to view the current sensor values.This can be accomplished with a Web browser (no software coding required) or polling by a host.Both alarms and data are available.The following is an example of the dynamic HTML page.
The dynamic HTML page displays on each row the following sensor information: name, serial number, age since last reception, service mode indicator, readings and units.All readings are shown in engineering units. All readings are shown in engineering units. The image to the left is a monitored temperature trend using the new Pointware, measuring four temperatures over 24 hours.
Collecting – Snapshots of the current sensor values can be periodically stored in a Historical Log.The snapshots can be retrieved for later analysis. All configured sensors readings are used in the snapshot.The snaps can be taken from once a minute to once every 7 days.The Point Server can be thought of as a remote data logger.
Concentrating – Key changes in a sensor reading, sensor age or system parameters can trigger records to be logged into an Event Log.The following items can be configured to trigger events: Point Server startup, Historical Log % full, sensor age, sensor service button, analog I/O high/low thresholds, counter I/O base count and interval, and state change.The Point Server stores a time stamp with the event.Approximately 1800 events can be stored in the Event Log.Also when an event is triggered, the Point Server can optionally take a snapshot of the current sensor readings and store it in the Historical Log.
Sensor Scenario
| No. of Records Available
| | 1 Sensor - 1 I/O Point | 8634 | | 1 Sensor - 2 I/O Points | 4317 | | 10 Sensors - 2 I/O Points | 1501 | | 25 Sensors - 2 I/O Points | 651 | | 50 Sensors - 1 I/O Point | 651 | | 50 Sensors - 2 I/O Points | 335 | | 100 Sensors - 1 I/O Points | 335 | Maximum Record Storage for Historical Log | Notifying – Each event can be configured to trigger the Point Server to notify a host. The Point Server can notify a host either pushing a connection through the Ethernet (TCP/IP) or placing a phone call through the modem.The host computer then does not need to be always connected and polling the Point Server .The Point Server can inform the host of the exceptions by establishing the connection itself.The Point Server can be configured to notify up to 5 host destinations trying each destination until the event is confirmed delivered.The Point Server can also send alarms via SMTP email through the Ethernet.
The Point Server is a data logger that can be used to store data while the Point Server is not connected to a host computer.The data-logging feature can be used in dialup modem applications where the connection is temporary and short.The data-logging feature can be used as a backup in case communications is lost through the Ethernet connection.
Both the Historical Log and the Event Log are circular.If either becomes full, the next record will overwrite the oldest record.
CRC16 error checks are added to the simple ASCII commands and response when using the modem or local serial port.
The Point Server can be easily configurable using ASCII commands.Each sensor can be given a label name and setup information for each I/O point such as engineering scale and offset, units label, and alarm trigger information. The Point Server has a “media callout table” where the user can specify which host destinations the Point Server is going to call for notification by either modem or Ethernet.The Point Server can also be configured to callout periodically with interval times from once a minute to once every 7 days.
The Point Server has optional security through two levels of login passwords: one for access to data and setup information and the other for changing the setup information.

Axon
Return
|
|