This document is to assist in finding the correct settings for successful use and deployment of the RhinoEdge Puck 50. All units come with a default configuration, but can differ based on the release data. So in any case all settings need to be double-checked before deployment.
These settings are provided as a baseline example to make it easier for users to find the most optimal settings per specific deployment and situation. The battery life of the device is mostly driven by actual on-time of the GPS. The on-time of the GPS is driven by the GPS interval and the actual time-to-fix (ttf). We advice to monitor the average time-to-fix for each individual device deployment add adjust the settings accordingly. In general: when the average time-to-fix is higher the 30 seconds it will significantly shorten the battery life at default settings below the 2 year goal. In this case, to reach the 2 year goal, it is advised to increase the GPS interval.
Use the available buttons to get into the needed configuration window.
LP1 GPS or Low Power GNSS does work well when used with an up to date almanac. However, as the almanac is outdated within 3 months, the LP1 GPS needs regular Almanac updates over the LoRaWAN network. In remote LoRaWAN networks it may not always reliably work to get the almanac data to the device using several LoRaWAN downlinks. Therefore we advice NOT to use this feature in remote networks. We are investigating the performance of a GNSS autonomous mode, where the device does not need almanac data to perform and we are also looking at way to update the almanac data using the the Ublox high-power GNSS function. If you still want to use or test the LP1 GPS feature. use these settings:
- LP1 GPS: - port 1: custom / 1800 seconds (which equals 30 minutes) → Experience shows this can only work reliably on the RhinoEdge Puck 50.
- LP1 GPS will send raw nav_payload data on LoRaWAN port 1 and can only be resolved to a location if the LoRaWAN server is integrated with Semtech LoRa Cloud. If your LoRaWAN deployment does not support this feature, please disable put this setting to OFF to safe power. Otherwise every 30 minutes a port 1 message continues to be transmitted by the RhinoEdge Puck 50.
- WARNING NOTE 1: Your LoRaWAN server integration needs to implement the LP1 GPS to LoRa Cloud resolver for actually processing these nav_payloads. If not done properly, this feature will not result in location updates.
- WARNING NOTE 2: For the LP1 GPS to collect enough GNSS data, the on device almanac needs to be updates at least every three months. Before the deployment, this should be do over Bluetooth using the Smart Parks Connect app. When the rhino sensor is deployed this needs to be done using the LoRaWAN downlinks. The process of collecting the up to date almanac data from LoRa Cloud, encoding this into downlinks and sending this via LoRaWAN downlinks needs to be supported by your LoRaWAN set-up. If the almanac does not get updated on the device, it will stop generating LP1 GPS fixes.
Set PIN for additional security
Clear all logs before final deployment