Parameter | Description |
|
Parity | Refers to the bit that is used for error checking. | |
|
| |
Stop | Refers to the number of bits used as stop bits. | |
|
|
|
GPIO | General Purpose | Input / Output. Can be set to output to |
| control external logic controllable devices. Can be set to an | |
| input to monitor an external logic level. Voltage on this pin | |
| should must remain within 0.0 to 4.0 volts!! The GPIO | |
| must be set to RS 485 transmit enable when the WSM6300 is | |
| configured for use with a RS 485 interface. | |
|
| |
| Used when the device is manually configured to support RS- | |
| 485. |
|
|
| |
Transmission Event Type | Parameter used to define how often or when derail data is | |
| packetized and sent to a destination via the wireless network. | |
| Three choices exist as follows: | |
| Update Interval – Data is packetized for transmission at | |
| this periodic | interval. |
| Sync Character - Data is packetized for transmission when | |
| this ASCII | character is received from the serial |
| interface. |
|
| Bytes Collected - Data is packetized for transmission when | |
| this number | of bytes is collected in the serial interface |
| receive buffer. | |
|
| |
Transmit IP Address | IP Address that a sensor to will send its data to. This address | |
| can be on the same host that executes MeshManager or a | |
| standalone host. Each sensor node can be configured to send | |
| data to a different host, i.e., – all temperature sensors would | |
report data to one host address and all fluid level sensors would report data to another host address. This address must be on the same segment of the network as the MeshManager. This is achieved by attaching a host to one of the available LAN ports on the CyberGuard SG300. The destination host will typically use the Sensor API to transfer data to a sensor management application. This field must be populated to enable the serial port.
8
