They Yabby parameters are based upon Remora/Oyster Parameters - and operate in much the same way, with some key differences.
The Yabby GPS and Yabby Wifi operate in the same way aside from the WiFi or GPS parameters
Descriptions of most parameter tabs are given below - many parameters are self-explanatory and can be summed up by the description that appears in OEM. Where applicable, a brief discussion on the effect of each parameter is given.
General Parameters (common to GPS and Wi-Fi versions)
The following settings are available under the Basic Tracking tab - defaults are shown
Hearbeat Upload Period (min):
When the Yabby is not tracking movement - it will sleep. It will schedule a regular wakeup on the heartbeat period. Keep in mind if the device is inactive, the heartbeat period is the maximum time you may have to wait for the device to receive a message from the server (set recovery mode, change parameters etc)
GPS Fix Timeout (s) (GPS Version Only)
Maximum time to wait for a valid GPS fix before giving up. This parameter can be used to limit the amount of time the GPS spends on (draining battery) in poor signal conditions.
Periodic Tracking Only
Set to Yes to configure the device to only wake up and report it's postion each Heartbeat Period.
E.g. for a postion every 3 hours - set Heartbeat Upload Period to 360, and Periodic Tracking Only = YES
The following Parameters are available - defaults are shown (Last 2 parameters are the GPS version only)
When movement is detected, this input is set - leave this as default (0)
Assumed Start Point Range
As in image
Example - to record a GPS position every 10 minutes in trip, and upload every hour, set the Movement Logging Period and Movement Upload Period to 10 and 60 respectively.
Uploads are relatively more energy expensive than GPS fixes - so it makes sense to upload positions in batches when possible. These settings are a trade-off between battery life and tracking granularity.
Setting these parameters to zero, disables them. This is beneficial if you want to maximise battery life and only care about where the asset was when it started moving, and where it ended up when it stopped.
Upload on Movement Detection
Upload when movement is detected by the device. See "Disable Wake Filter" for what constitutes 'movement'
Set to Yes to allow for Movement Alerts
If you don't require movement alerts this can be set to NO, as setting to Yes is usually a wasteful option, since the start position is generally already known from the end of the previous trip.
Upload on Movement End
When set to Yes, when movement ends the device will upload it's position. This will give the location where a device has ended up once it has stopped moving.
Disable Wake Filter
Set to disable the trip-start filtering. The wake filter rejects small disturbances, requiring sustained jostling before a trip starts. This is good for battery life, but if you require higher sensitivity, or the filtering is causing too much latency for your application, you can disable it. The filter only registers movement when it has seen 1 seconds worth of above-threshold movement in a 4 second period, or repeated short movements over several 4 second periods. The default is No (not disabled). Setting to Yes, and Upload on Movement Detection = Yes will allow the device to send an alert on tiny amounts of movement - any small jolt will trigger an upload.
Suppress GPS Wander (GPS Version Only)
Generally leave this on default - No. When enabled, it filters out small GPS movements (in the order of 0-100s of metres)
Optimise for High Frequency Movement Logging (GPS Version Only)
This option enables speculative 'freshening' of the GPS satellite information. If enabled, the GPS is kept on for a bit longer than necessary after getting a position fix, downloading all outstanding satellite information. This speeds up the next GPS fix. This option should improve battery life for trip tracking applications, but should be left disabled for applications that will generate very few (< 4) position updates in-trip. The default is No i.e disabled.
After Hours Parameters
The After Hours Basic Tracking and After Hours Movement Detection tabs enable different settings to be used for different times of the day. I.e. Only alert based on movement after business hours - to detect theft.
Parameter set up is the same as the Basic Tracking and Movement Detection tabs. The times that are considered "After Hours" each day are configured via the After Hours Setup Tab. Settings are self explanatory - a start and end time each day can be set. Contact DM if you are unsure.
These can be adjusted if the device is likely to go out of coverage for extended periods - to prevent it trying to connect, and leaving the modem on for long periods of time when there is no chance of a connection.
More about them here:
Remora Upload Timeouts (applies to Yabby) - defaults are also the same
Recovery Mode Setup
The tracking parameters while in Recovery Mode can be adjusted. The article on the Remora Recovery Mode applies - defaults are the same:
Battery Good Digital Input
Which digital input the 'Battery Good' status flag will be mapped into. Default is Digital Input 2. This is High/On when the battery is OK, and takes into account battery chemistry characteristics.
The following parameters are available, defaults are shown:
Wakeup Threshold/Wakeup Count
Allows for tuning of the accelerometer to determine its sensitivity. Article on the Remora applies:
See this article on how to set up for High-G Event Detection
All SMS Commands are enabled by default, but can be chosen to be disabled - to prevent unauthorised changes being made to the device via SMS.
The Man Down feature will set a digital input when the device has not moved for the configured period of time.
The following settings are available, defaults are shown
Man Down Digital Input
Digital Input bit to set when man down is activated
Man Down Timeout Settings
If the Man Down Timeout will be Disabled, or in Minutes, Hours or Days
Man Down Timeout
Number of minutes/hours/days until Man Down DI is activated
Man Down Set/Clear
What to do when Man Down is set or cleared. Options are:
Disabled - Do nothing
GPS - Trigger a GPS fix, to be uploaded at a future event (heartbeat, movement detection, etc).
GPS and Upload, Once - Trigger a GPS fix and attempt an upload. If the upload fails, then it will wait until the next event (heartbeat, movement detection, etc).
GPS and Upload, Retry - Trigger a GPS fix and attempt an upload continually, until it successfully connects to the server.
For the Wi-Fi version - "GPS" is replaced by "Wi-Fi" and is equivalent.
For the Yabby Cellular/GPS the GPS fix settings are configurable.
Defaults are shown:
The PDOP is a measure of how imprecise a GPS fix is, due to the satellites used being too close together to triangulate effectively. This parameter sets an upper bound on the imprecision, for a fix to be considered valid. You can use a large value, and specify the Position Accuracy instead. The default is 5, which is conservative. Relaxing it to 10 will allow fixes with a more restricted view of the sky, at slightly increased risk of reduced accuracy.
This is the required position accuracy for a position fix to be considered valid. It provides a lower bound on accuracy. Please note that it works on the estimated accuracy, and it is not uncommon for position fix errors to occasionally be two or three times larger than this value. Also note that values lower than 20 will be difficult to achieve in practice. The default is 50 meters.
This is the required accuracy of the speed component of a fix, before the fix is considered valid. The default is 10 km/h.
If the GPS measures its speed as below the Static Hold Threshold, it will set it's speed to 0 and consider itself stationary. This helps to prevent GPS drift.
This informs the GPS module of what sort of motion to expect from the asset, allowing it to make better estimates when moving. The Automotive setting is a safe default, but the Pedestrian and Stationary settings may be useful as well. Setting the model appropriately allows the GPS to filter out noise more effectively.
Require 3D Fix
This requires that a position fix use 4 satellites, and calculate a height as well as latitude and longitude, before being considered valid. It is recommended, as using only 3 satellites gives less redundancy in the rare event of a satellite failure, increasing the risk of a position fix giving an erroneous result. However, disabling this option can allow fixes to proceed faster, and in adverse conditions such as urban canyons. The default is YES i.e. True
Discard First N Fixes
This option discards the first few valid position fixes from the GPS module. This gives the module some time to refine and cross-check its estimate, reducing the risk of an erroneous fix in the rare event of a satellite failure. We recommend the default value of 3.
For the Wi-Fi version, the following parameters replace GPS settings:
Maximum Number of Access Points
Maximum number of detected Wi-Fi access points to send to the server for geolocation. Default is 15 - decreasing this parameter will result in less accurate fixes, but use less data. Increasing above 15 will only result in marginal increases in accuracy, and is not recommended.