In addition to standard 2D and 3D positioning modes, Eliko RTLS supports such special positioning modes as 1D mode, corridor mode and proximity mode. While 2D and 3D positioning mode settings are configurable with SET_TAG_PARAMS command, these special positioning modes and related API commands are described in the present chapter in more details.
The 1D mode
Introduction
In situations where the tag can move only back and forth on a fixed line, like a vehicle in the corridor or some machine on the rails, the coordinate calculation can benefit from this bit of extra information. The benefits could be reduced anchor count or increased accuracy, depending on the use case.
It should be noted that even in 1D mode, the output of the Eliko RTLS Ranging software is still in the format of 3D (X, Y, Z) coordinates, but in certain situation, this may be achieved even by using only a single anchor. The other helping information for the math algorithm are the dimensions and orientation of the 1D space, where the tag can physically be.
The main special configuration for the 1D mode is the definition of the 1D “line” or “axis”. Please note that while for simplicity, the word “line” may be used in the following document, in Eliko RTLS 1D mode, the line is never infinite, but rather a line segment with defined endpoints.
For more information about the 1D mode in the Eliko RTLS, please refer to the feature description in the Eliko Knowledge Hub.
SET_1D_MODE
This is a global switch which enables or disables the 1D mode subsystem. When disabled, no 1D calculations are done, but setting the 1D mode configuration or verifying it is still possible.
To switch the 1D mode subsystem ON, the client sends:
$PEKIO,SET_1D_MODE,ON
To switch the 1D mode subsystem OFF, the client sends:
$PEKIO,SET_1D_MODE,OFF
If the request was successful, the system responds:
$PEKIO,OK
If the supplied parameter was not ON or OFF, the system responds:
$PEKIO,NOT_GOOD,CANNOT_UNDERSTAND_PARAMETER
GET_1D_MODE
This request allows to read back the global switch set by SET_1D_MODE.
Client sends:
$PEKIO,GET_1D_MODE
When enabled the system responds:
$PEKIO,1D_MODE,ENABLED
When disabled the system responds:
$PEKIO,1D_MODE,DISABLED
SET_TAG_1D_MODE
This request allows to switch the 1D mode for a specific RTLS tag or for all the tags present in the system. With the system’s default settings, the tags are not operating in 1D mode, so if needed, this should be specifically enabled.
Client sends:
$PEKIO,SET_TAG_1D_MODE,<parameter list>
<parameter list> is a comma-separated list with the following fields:
|
Field name |
Explanation |
Example |
|
Tag’s Serial Number OR Tag group ID OR The keyword “ALL” |
May be one of the following:
|
0x123464 TG;1 ALL |
|
Tag’s 1D Mode |
May be one of the following three values:
|
ON |
A full example of client request would be:
$PEKIO,SET_TAG_1D_MODE,0x000454,FREE
If the request was successful, the system responds:
$PEKIO,OK
If there was an error while processing the request, the following response will be sent:
$PEKIO,NOT_GOOD,<error ID>
<error ID> can be one of the following:
|
Error ID |
Explanation |
|
NO_ID |
The tag’s serial number was missing or could not be parsed from the request. |
|
UNKNOWN_ID |
The specified tag’s serial number does not exist in the system’s database. |
|
NO_PARAM |
The 1D mode specifier (“ON”, “OFF” or “FREE”) was missing from the request. |
|
UNKNOWN_MODE |
The 1D mode specifier could not be parsed as “ON”, “OFF” or “FREE”. |
A full example of the system’s error response would be:
$PEKIO,NOT_GOOD,UNKNOWN_ID
GET_TAG_1D_MODE
This request allows the read back the tag’s 1D mode set with the SET_TAG_1D_MODE request.
Client sends:
$PEKIO,GET_TAG_1D_MODE,<parameter>
<parameter> has the following meaning:
|
Field name |
Explanation |
Example |
|
Tag’s Serial Number OR Tag group ID OR The keyword “ALL” |
May be one of the following:
|
0x123464 TG;1 ALL |
A full example of client request would be:
$PEKIO,GET_TAG_1D_MODE,0x000454
If the request was successful, the system responds:
$PEKIO,<parameter list>
<parameter list> is a comma-separated list with the following fields:
|
Field name |
Explanation |
Example |
|
Tag’s Serial Number |
A 24-bit identifier that is unique among all the produced RTLS tags, in 6-digit hexadecimal format. The Serial Number does not change during the whole life cycle of the tag and can thus be used to uniquely identify it. |
0x003464 |
|
Tag’s 1D Mode |
May be one of the following three values:
|
ON |
A full example of the system’s response, when requested for a specific tag, may be:
$PEKIO,0x0004A0,OFF
If the client used the request with the “ALL” keyword, a list of tags and their corresponding 1D Mode parameters will be sent, terminated by the EOF marker:
$PEKIO,<parameter list>
$PEKIO,<parameter list>
...
$PEKIO,EOF
If there was an error while processing the request, the following response will be sent:
$PEKIO,NOT_GOOD,<error ID>
<error ID> can be one of the following:
|
Error ID |
Explanation |
|
NO_ID |
The tag’s serial number was missing or could not be parsed from the request. |
|
UNKNOWN_ID |
The specified tag’s serial number does not exist in the system’s database. |
ADD_1D_AREA
This request allows to define a 1D area, which basically is a line segment with two endpoints in X, Y, Z coordinate space and an optional snap space around it. Multiple areas may be defined by using this request multiple times, a user defined name is used to distinguish between them.
Client sends:
$PEKIO,ADD_1D_AREA,<parameter list>
<parameter list> is a comma-separated list with the following fields:
|
Field name |
Explanation |
Example |
|
Area name |
A user-defined name for this area. Can later be used to request information about this area or remove it, if needed. When using an area name that already exists, the parameters for this area will be overwritten. |
Aisle1 |
|
Snap distance |
Distance in meters from the line segment, which defines the snap space around it. This value is necessary and meaningful only for tags, for which the 1D mode is set to “FREE”. For tags with 1D mode “ON” or “OFF”, this value has no meaning. If no tags with “FREE” mode are used, this value may be left empty or set to 0. |
1.5 |
|
Keyword “ANCHORS” |
Keyword that specifies that a list of comma-separated anchor serial numbers will follow. |
ANCHORS |
|
List of anchor serial numbers |
A comma-separated list of anchor serial numbers, which are used for 1D calculations in this 1D area. At least one anchor should be specified here. Anchors may be attached to multiple 1D areas, but the list of used anchors can’t be identical for multiple 1D areas. |
0x000123,0x0002A6 |
|
Keyword “P1” |
Keyword that specifies that the X, Y and Z coordinates of the first endpoint will follow, separated by commas. |
P1 |
|
First endpoint’s X, Y and Z coordinates |
X, Y, Z coordinates (in meters) for the first endpoint. The two endpoints define the location and orientation of the line, along which the 1D movement of the tag takes place, as well as they define the usable segment on the line. |
1.2,-0.51,28.22 |
|
Keyword “P2” |
Keyword that specifies that the X, Y and Z coordinates of the second endpoint will follow, separated by commas. |
P2 |
|
Second endpoint’s X, Y and Z coordinates |
X, Y, Z coordinates (in meters) for the second endpoint. The two endpoints define the location and orientation of the line, along which the 1D movement of the tag takes place, as well as they define the usable segment on the line. |
11.12,5.51,-2.25 |
A full example of client request would be:
$PEKIO,ADD_1D_AREA,aisle1,1.5,ANCHORS,0x000234,0x0012AB,P1,0.5,1.18,11.24,P2,-15.11,0.99,6.65
If the request was successful, the system responds:
$PEKIO,OK
If there was an error while processing the request, the following response will be sent:
$PEKIO,NOT_GOOD,<error ID>
<error ID> can be one of the following:
|
Error ID |
Explanation |
|
NO_ID |
The area name field is missing from the request. |
|
ID_TOO_LONG |
The area name is too long (more than 100 symbols). |
|
UNACCEPTED_ID |
The area name is a reserved keyword. |
|
NO_ANCHORS_SECTION |
The “ANCHORS” keyword is missing from the request. |
|
LESS_THAN_ONE_ANCHOR |
The anchor’s section in the request is empty (at least one anchor needs to be attached to the 1D area). |
|
UNKNOWN_ANCHOR,0x000123 |
Attempt to use an anchor that is not known to the system or has its coordinates never set. The serial number of the anchor is shown as an additional parameter (0x000123 in the example). |
|
ANCHOR_MORE_THAN_ONCE |
Attempt to list an anchor more than once. |
|
IDENTICAL_ANCHOR_LIST,aisle2 |
The mentioned 1D area (“aisle2” in the example) has exactly the same anchor list as this 1D area. |
|
P1_ERROR |
The “P1” keyword is missing from the request or the X, Y, Z coordinates could not be parsed. |
|
P2_ERROR |
The “P2” keyword is missing from the request or the X, Y, Z coordinates could not be parsed. |
|
RADIUS_PARSING_ERROR |
The snap distance field could not be parsed as a decimal value. |
|
RADIUS_LENGTH_:ERROR |
The snap distance value could be parsed, but the value is not mathematically usable, taking into account the length of the defined line segment. |
A full example of the system’s error response would be:
$PEKIO,NOT_GOOD,NO_ID
GET_1D_AREA
This request can be used to read back the 1D areas defined by the ADD_1D_AREA requests.
Client sends:
$PEKIO,GET_1D_AREA,<parameter>
<parameter> has the following meaning:
|
Field name |
Explanation |
Example |
|
Area name |
The user-defined area name to request information for OR the keyword ALL |
Aisle1 |
A full example of client request would be:
$PEKIO,GET_1D_AREA,Aisle1
If processing the request was successful, the system responds:
$PEKIO,1D_AREA,<parameter list>
The <parameter list> is exactly the same as described in request ADD_1D_AREA.
A full example of the system’s response would be:
$PEKIO,1D_AREA,aisle1,1.5,ANCHORS,0x000234,0x0012AB,P1,0.5,1.18,11.24,P2,-15.11,0.99,6.65
If the client used the request with the “ALL” keyword, a list with all the defined 1D areas will be responded, one per row and terminated with the EOF marker:
$PEKIO,1D_AREA,<parameter list>
$PEKIO,1D_AREA,<parameter list>
...
$PEKIO,EOF
If there was an error while processing the request, the following response will be sent:
$PEKIO,NOT_GOOD,<error ID>
<error ID> can be one of the following:
|
Error ID |
Explanation |
|
NO_ID |
The area name was missing from the request. |
|
UNKNOWN_ID |
The area with specified name does not exist in the system. |
REMOVE_1D_AREA
This request allows to remove a 1D area defined by the ADD_1D_AREA request.
Client sends:
$PEKIO,REMOVE_1D_AREA,<parameter>
<parameter> has the following meaning:
|
Field name |
Explanation |
Example |
|
Area name |
The user-defined area name to request information for OR the keyword ALL (for removing all the 1D areas present in the system). |
Aisle1 |
A full example of client request would be:
$PEKIO,REMOVE_1D_AREA,Aisle1
If processing the request was successful, the system responds:
$PEKIO,OK
If there was an error while processing the request, the following response will be sent:
$PEKIO,NOT_GOOD,<error ID>
<error ID> can be one of the following:
|
Error ID |
Explanation |
|
NO_ID |
The area name was missing from the request. |
|
UNKNOWN_ID |
The area with specified name does not exist in the system. |
Positioning with one side anchors (corridor mode)
Introduction
The corridor mode, also known as positioning with one side anchors, can be used in use cases where there are restrictions on anchor placement in the tracking area, e.g. anchors may be only installed on one wall in a tunnel or a corridor. When the restricted side or wall is known, a polygon can be created within the room borders. By knowing the polygon borders the system can calculate the tag’s coordinates even with 2 anchors instead of minimum 3-4 required for regular 2D positioning mode.
For more information about the corridor mode in the Eliko RTLS, please refer to the feature description in the Eliko Knowledge Hub.
SET_MPM
This is a global switch which enables or disables the corridor mode subsystem.
To switch the corridor mode subsystem ON, the client sends:
$PEKIO,SET_MPM,ON
To switch the corridor mode subsystem OFF, the client sends:
$PEKIO,SET_MPM,OFF
If the request was successful, the system responds:
$PEKIO,OK
If the supplied parameter was not ON or OFF, the system responds:
$PEKIO,NOT_GOOD,CANNOT_UNDERSTAND_PARAMETER
GET_MPM
This request allows to read back the global switch set by SET_MPM.
Client sends:
$PEKIO,GET_MPM
When enabled the system responds:
$PEKIO,MPM,ENABLED
When disabled the system responds:
$PEKIO,MPM,DISABLED
ADD_MPM_AREA
This request allows to define a corridor area, which is a non-self-intersecting polygon formed by a set of at least three vertex points (the same concept as in case of geofence zones) and associated with minimum two anchors.
Client sends:
$PEKIO,ADD_MPM_AREA,<parameter list>
<parameter list> is a comma-separated list with the following fields:
|
Field name |
Explanation |
Example |
|
Area name |
A user-defined name (string) for the given corridor area. Must be unique within the RTLS and contain maximum 100 characters. When using an area name that already exists, the parameters for this area will be overwritten. |
Corridor1 |
|
Keyword “ANCHORS” |
Keyword that specifies that a list of comma-separated anchor serial numbers will follow. |
ANCHORS |
|
List of anchor serial numbers |
A comma-separated list of anchor serial numbers. At least two anchors should be specified here. |
0x000123,0x0002A6 |
|
Keyword “POLYGON” |
A keyword that specifies that the polygon definition will follow. The polygon is defined by a list of at least three vertices (corner points), each defined by their X and Y coordinates. |
POLYGON |
|
V,x,y, V,x,y, ... V,x,y |
A list of vertices (corner points) that define the polygon. A minimum of 3 vertices are required. Each vertex contains 3 comma-separated fields: the fixed letter “V” and the X and Y coordinates of the vertex. |
V,2.1,3,V,4.14,5.22,V,5.99,2.2 |
A full example of client request would be:
$PEKIO,ADD_MPM_AREA,Corridor1,ANCHORS,0x000234,0x0012AB,POLYGON, V,0,0,V,0,15,V,15,16,V,14,-0.2
If the request was successful, the system responds:
$PEKIO,OK
If there was an error while processing the request, the following response will be sent:
$PEKIO,NOT_GOOD,<error ID>
<error ID> can be one of the following:
|
Error ID |
Explanation |
|
NO_ID |
The area name field is missing from the request. |
|
ID_TOO_LONG |
The area name is too long (more than 100 symbols). |
|
UNACCEPTED_ID |
The area name is a reserved keyword. |
|
NO_ANCHORS_SECTION |
The “ANCHORS” keyword is missing from the request. |
|
LESS_THAN_TWO_ANCHORS |
The anchor’s section in the request is either empty or contains only one anchor (at least two anchors need to be attached to the corridor area). |
|
UNKNOWN_ANCHOR |
The anchor with the given ID does not exist in the RTLS |
|
PARSING_ANCHORS |
Error in parsing the anchor serial number values |
|
NO_POLYGON_SECTION |
Polygon definition is missing from the request |
|
LESS_THAN_THREE_POINTS |
Less than 3 vertices (which is the minimum to define a polygon). |
|
POLYGON_SELFINTERSECTING |
Error in polygon definition, the polygon can’t be self-intersecting. |
|
PARSING_POLYGON |
Error in parsing the polygon definition |
A full example of the system’s error response would be:
$PEKIO,NOT_GOOD,NO_ID
GET_MPM_AREA
This request can be used to read back the corridor areas defined by the ADD_MPM_AREA requests.
Client sends:
$PEKIO,GET_MPM_AREA,<parameter>
<parameter> has the following meaning:
|
Field name |
Explanation |
Example |
|
Area name |
The user-defined area name to request information for OR the keyword ALL |
Corridor1 |
A full example of client request would be:
$PEKIO,GET_MPM_AREA,Corridor1
If processing the request was successful, the system responds:
$PEKIO,MPM_AREA,<parameter list>
The <parameter list> is exactly the same as described in request ADD_MPM_AREA.
A full example of the system’s response would be:
$PEKIO,MPM_AREA,Corridor1,ANCHORS,0x000234,0x0012AB,POLYGON,V,0,0,V,0,15,V,15,16,V,14,-0.2
If the client used the request with the “ALL” keyword, a list with all the defined corridor areas will be responded, one per row and terminated with the EOF marker:
$PEKIO,MPM_AREA,<parameter list>
$PEKIO,MPM_AREA,<parameter list>
...
$PEKIO,EOF
If there was an error while processing the request, the following response will be sent:
$PEKIO,NOT_GOOD,<error ID>
<error ID> can be one of the following:
|
Error ID |
Explanation |
|
NO_ID |
The area name was missing from the request. |
|
UNKNOWN_ID |
The area with specified name does not exist in the system. |
REMOVE_MPM_AREA
This request allows to remove a corridor area defined by the ADD_MPM_AREA request.
Client sends:
$PEKIO,REMOVE_MPM_AREA,<parameter>
<parameter> has the following meaning:
|
Field name |
Explanation |
Example |
|
Area name |
The user-defined area name to request information for OR the keyword ALL (for removing all the corridor areas present in the system). |
Corridor1 |
A full example of client request would be:
$PEKIO,REMOVE_MPM_AREA,Corridor1
If processing the request was successful, the system responds:
$PEKIO,OK
If there was an error while processing the request, the following response will be sent:
$PEKIO,NOT_GOOD,<error ID>
<error ID> can be one of the following:
|
Error ID |
Explanation |
|
NO_ID |
The area name was missing from the request. |
|
UNKNOWN_ID |
The area with specified name does not exist in the system. |
Proximity mode
Introduction
The proximity mode or the proximity detection mode is a special function of the Eliko RTLS, which allows to reduce the anchor count in environments, where full X, Y, Z coordinate is not necessary. The usual RTLS setup expects that the anchors are placed in a way that the tags would “see” at least 4 anchors from everywhere in the tracked area. The proximity mode, on the other hand, uses only one anchor per room or area to detect if the tag is near this anchor or not. When using the proximity mode, the user is able to define a distance between the anchor and tag, which is considered as the proximity radius. When the tag is more near to anchor than the set distance, it is considered to be in the proximity range of that anchor.
When a tag is considered to be in a proximity of an anchor, but it is not possible to calculate its exact coordinates with the regular method, the RTLS Ranging software creates a randomized fake coordinate for it, so the user interface would still place the tag approximately at the right location on the map. The reason to randomize it is not to overlap multiple tags in the RTLS Manager web interface, which would make it hard to visually monitor or handle them. The distance from the anchor, in which area the randomized coordinate is created, is configurable by the SET_ANCHOR_RADIUS request.
When there are multiple anchors with overlapping proximity detection areas and there is a tag in that overlapping area, the system snaps that tag to the closest anchor of them.
When the client needs to distinguish if the coordinate reported by the system was actually calculated or just randomized near a proximity anchor, they need to use the ADD_CUSTOM_REPORT_TYPE request to define a custom report and use the COORD_TYPE field there.
For more information about the proximity mode in the Eliko RTLS, please refer to the feature description in the Eliko Knowledge Hub.
SET_PROXIMITY_MODE
This request allows to switch the proximity mode functionality ON or OFF. If switched OFF, the proximity mode is not used, only the regular coordinate calculations will be done.
To enable the proximity mode, the client sends:
$PEKIO,SET_PROXIMITY_MODE,ON
To disable the proximity mode, the client sends:
$PEKIO,SET_PROXIMITY_MODE,OFF
If processing the request was successful, the system responds:
$PEKIO,OK
If the client provided an invalid parameter, the system responds:
$PEKIO,NOT_GOOD,CANNOT_UNDERSTAND_PARAMETER
GET_PROXIMITY_MODE
This request allows the client to read back if the proximity mode is currently enabled or disabled.
Client sends:
$PEKIO,GET_PROXIMITY_MODE
If proximity mode is currently enabled, the system responds:
$PEKIO,PROXIMITY_MODE,ENABLED
If proximity mode is currently disabled, the system responds:
$PEKIO,PROXIMITY_MODE,DISABLED
SET_ANCHOR_RADIUS
This request allows the client to switch an anchor to use the proximity detection mode. When a tag approaches an anchor in this mode, the system does not calculate its actual position any more, but a fake position near this anchor is presented. This mode allows to reduce the needed anchor count and install only one anchor in these rooms, where accurate position is not required.
Client sends:
$PEKIO,SET_ANCHOR_RADIUS,<parameter list>
<parameter list> is a comma-separated list with the following fields:
|
Field name |
Explanation |
Examples |
|
Anchor’s Serial Number OR The keyword “ALL” |
May be one of the following:
|
0x003464 ALL |
|
Enter Radius |
Radius in meters. If the tag approaches this anchor and the distance between becomes less than this value, the usual coordinate calculations are not performed any more, but a fake position near this anchor will be presented. To disable the proximity detection mode for this anchor, the value of “0” should be used here. This is also the default behavior for all the anchors. |
2 |
|
Exit Radius |
Radius in meters, that should be equal or larger than the Enter Radius. If the tag is moving away from this anchor and the distance between them becomes larger than this value, the usual coordinate calculations will be performed again. The idea to set this value larger than Enter Radius is to avoid jumping back and forth between these modes when the tag is on the borderline distance from the anchor. To disable the proximity detection mode for this anchor, the value of “0” should be used here. This is also the default behavior for all the anchors. |
2.5 |
|
Randomized Point Radius |
This is an optional parameter that allows to set the area radius in meters, in which the RTLS Ranging software creates the randomized coordinates for the tags that are considered to be in the anchor’s proximity range. If this parameter is omitted, a default value of 0.75 * (Enter Radius) is used. When using a value of 0 here, all the tags within the proximity range of the anchor will be placed exactly at the anchor’s coordinates (which could be complicated to handle in graphical environments). |
1.3 |
Some full examples of client requests would be:
$PEKIO,SET_ANCHOR_RADIUS,0x003464,2,2.5
$PEKIO,SET_ANCHOR_RADIUS,0x003464,2,2.5,1.3
$PEKIO,SET_ANCHOR_RADIUS,ALL,0,0
If processing the request was successful, the system responds:
$PEKIO,OK
If the system encountered an error when processing the request, the following response will be sent:
$PEKIO,NOT_GOOD,<error ID>
<error ID> can be one of the following:
|
Error ID |
Explanation |
|
ENTER_RADIUS |
The enter radius specified in the request was missing, could not be parsed or was negative. |
|
EXIT_RADIUS |
The exit radius specified in the request could not be parsed or was negative. |
|
POINT_RADIUS |
The randomized point radius specified in the request could not be parsed or was negative. |
|
RADIUS_ORDER |
The exit radius was smaller than enter radius. |
|
<anchor addressing errors> |
If there was a problem with anchor addressing, the common error messages described in chapter “Anchor Addressing” may also appear. |
Some full examples of the system’s error responses would be:
$PEKIO,NOT_GOOD,EXIT_RADIUS
$PEKIO,NOT_GOOD,UNKNOWN_ANCHOR
GET_ANCHOR_RADIUS
This request allows the client to read back the values configured by request SET_ANCHOR_RADIUS.
Client sends:
$PEKIO,GET_ANCHOR_RADIUS,<parameter>
<parameter> is defined as follows:
|
Field name |
Explanation |
Examples |
|
Anchor’s Serial Number OR The keyword “ALL” |
May be one of the following:
|
0x003464 ALL |
Some full examples of client requests would be:
$PEKIO,GET_ANCHOR_RADIUS,0x003464
$PEKIO,GET_ANCHOR_RADIUS,ALL
The system responds with one row per anchor and terminates the list with special EOF marker:
$PEKIO,ANCHOR_RADIUS,<parameter list>
$PEKIO,ANCHOR_RADIUS,<parameter list>
...
$PEKIO,EOF
Note that in case the client requested information with the “ALL” keyword, the system does not output the list of all the anchors in the database, but only these, for which the client has at least once used the SET_ANCHOR_RADIUS request.
<parameter list> is a comma-separated list with the following fields:
|
Field name |
Explanation |
Example |
|
Anchor’s Serial Number |
Serial number of the anchor for which information was requested. |
0x003464 |
|
Enter Radius |
Radius in meters. If the tag approaches this anchor and the distance between becomes less than this value, the usual coordinate calculations are not performed any more, but a fake position near this anchor will be presented. If this value has not been ever set for this anchor, an empty field will be sent. A value of “0” indicates that the client has disabled the proximity detection mode for this anchor. |
2 |
|
Exit Radius |
Radius in meters, that should be equal or larger than the Enter Radius. If the tag is moving away from this anchor and the distance between them becomes larger than this value, the usual coordinate calculations will be performed again. The idea to set this value larger than Enter Radius is to avoid jumping back and forth between these modes when the tag is on the borderline distance from the anchor. If this value has not been ever set for this anchor, an empty field will be sent. A value of “0” indicates that the client has disabled the proximity detection mode for this anchor. |
2.5 |
|
Randomized Point Radius |
The area radius in meters, in which the RTLS Ranging software creates the randomized coordinates for the tags that are considered to be in the anchor’s proximity range. In case this parameter is omitted, a default value of 0.75 * (Enter Radius) is used. When using a value of 0 here, all the tags within the proximity range of the anchor will be placed exactly at the anchor’s coordinates (which could be complicated to handle in graphical environments). |
1.3 |
A full example of the system’s response would be:
$PEKIO,ANCHOR_RADIUS,0x003464,1.25,2.5,0.8
$PEKIO,ANCHOR_RADIUS,0x0009AA,2.53,0.9,0.5
$PEKIO,EOF
If there was an error when processing the request, the following response will be sent:
$PEKIO,NOT_GOOD,<error ID>
Possible values for the <error ID> field are defined in chapter “Anchor Addressing”.
A full example of error response would be:
$PEKIO,NOT_GOOD,UNKNOWN_ANCHOR
A full example of the system’s response would be:
$PEKIO,ANCHOR_RADIUS,0x003464,1.25,2.5,0.8
$PEKIO,ANCHOR_RADIUS,0x0009AA,2.53,0.9,0.5
$PEKIO,EOF
If there was an error when processing the request, the following response will be sent:
$PEKIO,NOT_GOOD,<error ID>
Possible values for the <error ID> field are defined in chapter “Anchor Addressing”.
A full example of error response would be:
$PEKIO,NOT_GOOD,UNKNOWN_ANCHOR