Send messages
Use the tracker management to efficiently send commands to multiple GPS trackers at once. You can even schedule commands for a specific time frame.
Last updated
Use the tracker management to efficiently send commands to multiple GPS trackers at once. You can even schedule commands for a specific time frame.
Last updated
Contact us, when missing a specific message you want to apply to your devices. You can also compose your own message templates.
Identify and select the GPS trackers to which you want to send commands. The tracker management targets the commands to all devices in the above list.
Ensure that the devices are switched on and currently connected with Racemap to receive commands.
Monitor the acknowledgment from each device to confirm the successful receipt of the command.
Check the messages timeline for each device to track the progress of sending commands. Inspect the message details to gather additional information on each device's response.
Time: Send the message right away ("Now") or schedule the time frame ("Not before" and "Not after") in which Racemap attemps to send the command to the device.
You can schedule commands for a group of GPS trackers to automatically adjust the devices' settings according to the time.
A couple of days before the race:
Switch on all devices manually.
Place devices for a good connection.
Select all devices in tracker management.
Check connection and location in tracker management.
Clear undelivered commands from messages timeline before scheduling new commands with the "Revoke all messages" function.
Schedule commands according to SLEEP, AWAKE and RACE profile.
Don't switch devices off after you have scheduled commands.
SLEEP profile: "heartbeat", every 10 to 20 min refreshes the connection to Racemap, if there is reception
| # | Command | Parameter | Time |
|---|---|---|---|
S1 | GPS Module | mode: 1 | Now |
S2 | GPS Report Interval | 3600; 3600 | Now |
S3 | Non-Movement Detection | 10; 3600; 3600 | Now |
Participants must not use the power button! When deploying the devices to participants the devices are turned on already.
Devices lose about 5 to 7 % battery level in 24 hrs.
AWAKE profile: It takes up to 60 min until all devices receive the new configuration. Check the tracker management if there is a device that does not establish a connection. The participant might have turned the device off. You still have time to change the device before the race starts.
| # | Command | Parameter | Not before | Not after |
|---|---|---|---|---|
A1 | GPS Report Interval | 180; 180 | 4 hrs before race starts | 3 hrs before race starts |
A2 | Non-Movement Detection | 10; 180; 180 | 4 hrs before race starts | 3 hrs before race starts |
RACE profile: It takes up to 10 min until all devices receive the new configuration.
| # | Command | Parameter | Not before | Not after |
|---|---|---|---|---|
R1 | GPS Module | mode: 0 | 1 hr before race starts | no entry |
R2 | GPS Report Interval | 10; 10 | 1 hr before race starts | no entry |
Devices lose about 5 % battery level every 1 hr.
With 60; 60 parameter setting, devices lose about 2 % battery level every 1 hr.
For stage events you can schedule subsequent SLEEP and RACE profiles for each stage.
After the race: Use the "Shut down" command to remotely switch devices off. When the device has received the shot down it must be switched on manually. There is no possibility to remotely turn on a device.
Command: Select the command.
Transport: By default, messaging with GPS trackers works via TCP connection. However, if you're running the devices with our M2M SIM cards, you can choose to send messages as SMS instead. To receive an SMS, the device must not have an open socket connection with RACEMAP server. This provides the alternative to sending SMSs to devices that are not connected, making it useful for tasks like rebooting the device or requesting the last known location.
