Con Guring And Reading O Variables Using The Data Platform; Table 34: Geofence De Nition; Table 35: Geofence Status - Danfoss TFX Installation And Operation Manual

Operation

Table 34: Geofence de nition

Variable Function
0 = Geofence disabled
1 = Geofence enabled, circle center and radius
de ned
2 = Geofence enabled, circle center, current
position, and de ned radius
G - M 3 = Geofence enabled, rectangle
EOFEN C E O DE
G - C 1 Longitude for center of the circle or rst corner
EOFEN C E OOR DINATE
> L of the rectangle
ONGITU DE
G - C 1 Latitude for center of the circle or rst corner
EOFEN C E OOR DINATE
> L of the rectangle
ATITU DE
G - C 2 Circle radius in meters or longitude for the
EOFEN C E OOR DINATE
> L / R second corner of the rectangle
ONGITU DE A DIUS
G - C 2
EOFEN C E OOR DINATE
> L Latitude for the second corner of the rectangle.
ATITU DE
GEOFENCE STATUS
With the geofence status, you can trigger an event
internally. The geofence status is updated every 2 seconds.
Every time the geofence status changes, the time is written
to a variable.
The variables belong to the object dictionary group
D V .
EVI CE ARIA B LES

Table 35: Geofence status

Variable
G
EOFEN C E STATUS
G - S C UT C
EOFEN C E TATUS HANGE
T
IME
Geofence status
For detailed information on creating objects, see chapter
Creating object dictionary groups and objects.
5.7 Con guring and reading o variables using
the Data platform
You can send special les to the device via the Data
platform to con gure or read o variables.
In the following, the les and their structure are described.
NOTICE
Restrictions apply to the le names. See chapter File
transfer restrictions.
OBW FILE
The OBW le (*.obw) writes a value to a variable.
The le has the following structure:
> The line starts with a colon (:).
> Object index (e.g. 0x5353)
> Comma (,)
> Sub-index (e.g. 0x00)
34
TFX INSTALLATION AND OPERATION MANUAL
Function
00 = device is outside the fence
01 = device is inside the fence
FF = status unknown (e.g. because
no position data is available)
Time of geofence-status change
> Comma (,)
> Value to be written to the variable. All number values
(signed / unsigned-integer variables 8 ... 32 bits, oat 32
bits). The format for oating-point values is "123.45" . You
can use decimal or hexadecimal formats.
NOTICE
Do not use commas (,) or semicolons (;) when
transferring texts.
> Semicolon (;)
> Comment
> End of line <CR><LF>
Several lines can be written in one le. The lines can have
comments. A comment is preceded by a semicolon (;).
Example:
: 0x5353, 0x00, 0; Set File Transfer mode
NOTICE
Function restriction due to faulty OBW le.
It is necessary to check the OBW le.
Use a local device with CAN access to test the OBW le
•
before transmitting it to a remote device.
OBR FILE
OBR les (*.obr) are used to read out a value from a
variable. The device transmits the answer as an OBC le.
The le has the following structure:
> The line starts with a colon (:).
> Object index (e.g. 0x3333)
> Comma (,)
> Sub-Index (e.g. 0x38)
> Semicolon (;)
> Comment
> End of line <CR><LF>
Several lines can be written in one le. The lines can have
comments. A comment is preceded by a semicolon (;).
Example:
: 0x3333, 0x38; Read last error state
OBC FILE
The OBC le (*.obc) is transferred by the device as a
response to the instruction of an OBR le. The le name is
identical to the le name in the OBR le.
6046279-001 March 2020