...
Description | File | ||||
|---|---|---|---|---|---|
Instructions on how to change the device’s IP address over Telnet |
|
...
Dispatcher Implementation
This dispatcher is part of kpfmet (currently.)
There are an arbitrary number of sensors for the unit. The names, denoted as $(NAME), are stored in the configuration file, as are the ID or address values. Readout is done in serial for the device, and done in the order of appearance in the configuration file. The “#” denotes the dispatcher number. Currently that is 4 for the kpfmet service but if dispatcher is moved or the service rearranged, this could change.
Keyword | Value | Type |
|---|---|---|
$(NAME) | Temperature in deg C | Double - read only |
$(NAME)_ID | ID value | String - read only |
LINKSTA | 0 - Done 1 - Reading When Reading, the temperature values are being retrieved and the values will appear in the keywords | Enumerated - read only |
CONN# | 0 - Off 1 - On The connection keyword which turns on or off the connection to the device | Enumerated |
MODEL# | Model of the hub, value of the command ' '. | String - read only |
LINK_IP | IP Address from configuration file | String - read only |
LINK_PORT | Port for device from configuration file | String - read only |
DISP#CLK | Number of whole seconds dispatcher has been alive | Integer - read only |
DISP#ERR | Error value | Integer - read only |
DISP#MSG | Message from the dispatcher | String - read only |
DISP#REQ | Last keyword requested to be modified, written before modify is sent. | String - read only |
DISP#MEM | Memory used by dispatcher in kB | Integer - read only |
DISP#STA | Status of the dispatcher 0 - Ready - working 1 - Initializing - only true during start up 2 - Shutting down - A control-C or the stop command has been issued 3 - Connecting - Attempting to connect to the device 4 - Not Connected - No connection to the device | Enumerated - read only |
DISP#STOP | Stop command which ends the dispatcher. 0 - Continue 1 - Stop | Enumerated |
DISP#VER | A version number | String |
...
Configuration File
The required sections are:
device which has the first four configuration keyword value pairs
dispatcher which has the dispnum value
[0], [1], [2], … [number-1] - A section for each sensor, starting from 0, and the total number must match the value of the number configuration. Extra sections are ok, but if any are missing the dispatcher will throw an error message and exit.
Configuration | Value | Explanation |
|---|---|---|
ip_address | 192.168.23.184 | IP address of device |
port | 10001 | Port for telnet connection to device |
number | 31 | The number of active sensors |
poll_time | 60 | The time between requests for temperature measurements |
dispnum | 4 | Number of the dispatcher in the service |
name | temp0 | The human readable name requested for a temperature value, will set the keyword name |
id | 2890F1DD06000089 | The ID value for the temperature measuring device on the hub. This is what will be referenced. Note- This is the reverse of the order that the ID number is returned when querying the device. There is a swap of byte order and this is the ID that must be used for a lookup |