Note: If a System parameter tab is not shown in the device, it will be set to defaults. This is the same as showing the tab and not changing any values.
Heartbeat: Time period in minutes of inactivity before a heartbeat upload - how often the device will report when sitting stationary or not in trip.
In Trip Upload Period: Time between uploads in a trip
In Trip Logging Period: time between GPS Fixes while in trip
E.g. defaults of 2 min/30 min for these parameters mean while moving, a GPS position is recorded every 2 min, and all of these records are uploaded every 30 min (you only see movement on the platform every 30 min)
GPS Fix Timeout: Maximum time spent trying to obtain GPS Fix
Geofence Tracking is available on the Remora2 and allows for a separate set of Basic tracking settings especially for downloaded Geofences. These settings will be used when inside selected Geofences,
After hours Tracking
After hours tracking gives you the option to enable higher or lower rates of tracking during 'out of hours' operation. e.g. If you only want high levels of heartbeats between hours of 9am and 5pm, you can enable slower heartbeats and in trip logging outside of these hours. This can be used to conserve battery life when updates may be of less use or interest. You can set up the After Hours parameter in the 'After Hours Setup' tab.
This tab has the options to change the type of tracking the unit uses.
Periodic Tracking: Heartbeats only, no movement/trip tracking enable
Jostle Based Tracking: Uses the Accelerometer to measure movement, trip starts and ends
Upload on Trip Start: Yes/No
Upload during Trip: If yes, Time period for Upload is in 'Basic Tracking' tab
Upload on Jostle: Yes/No - see article on Jostle Mode for a description.
Suppress GPS Wander: This option filters out small scale GPS movements
Optimise for Low Signal: Yes/No.
In this case, the first GPS fix will be more likely to detect movement.
2. If too many jostle event are detected without any real movement being detected, the Remora2 will temporarily ignore the accelerometer, and sleep for a longer time before checking the GPS for movement. This provides a stricter limit on the maximum rate of wakeups.
Wakeup Delay: Amount of time sleeping after initial jostle until device will try to obtain a GPS fix. generally recommended to be set between 10-60 seconds.
No Movement Limit: Amount of times accelerometer has detected movement but no trip has been started before unit ignores Accelerometer.
Jostle Upload Delay : This is the number of seconds to wait after a jostle before scheduling an upload.
Maximum Jostle Upload Delay: This prevents the upload being rescheduled (delayed) indefinitely during continuous jostling, by forcing it to take place within a specified number of seconds after the jostling begins.
Digital Input: This is usually bit 0 for ignition, if you have a third party platform which requires a different bit, you'll need to change it.
Movement Threshold (m): This is the minimum amount of distance for the device to register until movement counts are started.
Movement Count: This is the number of positions over the threshold before a trip starts. The GPS samples second by second until movement count is reached.
Assumed Start Point Range (m): Set this distance to determine whether to retroactively move the start point of trips if it is within x metres of previous end point.
Trip End Time(s): Amount of time with no movement detected until end trip is set
Trip End Time, GPS Lost: Amount of time with no GPS signal until end trip is set.
This section allows you to fine-tune the requirements for jostle based trip detection. It is relevant when Advanced Tracking -> Jostle Based Tracking is set.
In Jostle Based Tracking mode, a trip is started by significant sustained jostling, and continues as long as occasional jostling or significant GPS speed continues. The default jostle trip parameters will work for most applications, but should you need to, you can configure them.
The Settings are the same as explained above in Movement Trips.
For a greater detailed explanation of Upload Timeouts, please view this page on our knowledge base
Recovery Mode Setup
- Recovery mode has a severe impact on battery life. Remember to bring the device out of recovery mode as soon as possible. These settings will override normal parameters when Recovery mode is activated.
Digital Input to set for 'Good' battery voltage level.
PDOP, Position & Speed Accuracy: These settings allow you to configure the minimum accuracy accepted for a fix. The PDOP is a measure of how imprecise a GPS fix is. This is due to the satellites that are used being too close together to triangulate effectively. Please note that values lower than 2.0 for PDOP will be difficult to achieve in practice. Default Position Accuracy is 50 metres.
Static Hold: If a device is measured to be going less than this speed, it will set it to stationary and it's position fixed.
GPS Model: This selects a statistical module used by the GPS hardware when filtering out noise during GPS fixes. Generally choose Automotive
Discard First N Fixes: This option discards a configurable number of points from the GPS if the PDOP is above 2.3. This gives the GPS some time to improve its accuracy, and lowers the chance of outlying GPS fixes slipping through the filters.
Wakeup Threshold: This option sets the G force required on any of the accelerometer axes to trigger a wakeup.
Wakeup Count: This sets the required duration of the force, with 0 being a single sample
Accelerometer wakeups are used in several circumstances:
1. To trigger a GPS movement check, in regular GPS tracking mode
2. To detect a trip, in Jostle Based Tracking mode
3. To schedule an upload, if Upload On Jostle is configured, the default setting is for maximum sensitivity, and is appropriate for light vehicles.
If you have a problem with constant wakeups in GPS tracking mode, false trips in Jostle Based Tracking Mode, or excessive heartbeat uploads with Upload On Jostle, it may be necessary to increase the thresholds. Increasing the thresholds may improve battery life by lowering the number of unnecessary wakeups, but it increases the chances of a trip start being missed
The SMS tab has the option to enable or disable SMS commands. for more information please view the attached support article.
You may want to disable SMS to prevent others from adjusting device settings via SMS
Battery Capacity Settings
The Remora2 has a coulomb counter, which tracks energy (in mAh), used by the battery. This can be used to estimate the battery percentage, and remaining battery life. However these estimates rely on an assumption of the total capacity of the batteries. This can vary per battery type, and even on a single type quite significantly due to temperature variations.
The assumed battery capacity can be edited in this section.
Bluetooth®/BLE Global Settings, BLE Tag Scanning, BLE SensorNode1 &2
Please view the Bluetooth guide here for more information on these settings.
BLE SensorNode1 &2
Please view the SensorNode Bluetooth guide here for more information on these settings.
BLE iBeacon, BLE Eddystone, BLE MAC Filter
Please view the Tag Filtering guide here for more information on these settings.
BLE Advanced Scanning
Please view the Advanced Scanning guide here for more information on these settings.
BLE User Integrated Tags
Please view the Tag Integration guide here for more information on these settings.
The Inactivity Timer is a new function on Firmware 1.13v or newer and functions as a timer where the 'Inactive' Digital input is set when an asset has not registered a trip for the set time.
Please note this is different to a device not connecting report, where a device has not been able to connect & Commit to the server in x amount of time.