Statusreport

Ron de Vries
Ron de Vries Community manager
  • Updated

You have received a status report about the functioning of your FleetGO unit(s). Multiple notifications can be mentioned per vehicle. That doesn't necessarily mean that your unit isn't working well, but we do advice you to be alert on the status reports. In this article we would like to explain the existing notifications and the cause of it. 

Notifications:

  1. Correction reminder
  2. Disconnected ride
  3. Long ride
  4. Lost data packets
  5. Low satellite count
  6. No server contact
  7. No driver
  8. No ignition signal
  9. No rides
  10. Power failure
  11. Stationary rides
  12. No particularities

Correction reminder

If measured by GPS, a correction will have to be performed to correct the difference between the two methods of measurement. This does not apply to systems connected to the CAN bus.

Disconnected ride

Notification: The ride with starting location 'city & address' that started on 'date & time' does not connect to the ride with end location 'city & address' that ended on 'date & time'. Some data might be lost or manually deleted.

This message is generated when the last GPS position is not the same as the start GPS position. This could have several causes. Some examples:

  • Vehicle was parked in a covered car park. GPS satellites are not available. No further action is needed. 
  • When a vehicle has been moved with a ferry and/or trailer. No further action is needed. 
  • The message can also be caused by a delay at the start of the trip with the GPS receiver of the blackbox. Is the trip correct? The message can be ignored.
  • If the message occurs systematically with the same vehicle, it is possible that the GPS receiver does not function properly. In this case, please contact us.

Long ride

Notification: The ride with starting location 'city & address' that started on 'date' at 'time' was started more than 12 hours ago. This could indicate a problem with the ignition start/stop signal.

This notification is generated when the trip of an administration takes longer than 12 hours. 

  • If this trip isn't correct, and you use the FleetGO Dongle, please check the connection. 
  • Other FleetGO blackboxes: Please contact us.

Lost data packets

Notification: Distance or time between FMS data packets exceeds maximum thresholds. This could indicate a problem with the GPS signal reception or an antenna or unit malfunction.

  • Please contact the Support department.

Low satellite count

Notification: the average amount of 0 satellites is below the given threshold for this unit type in the previous period. This could indicate a problem with the GPS receiver.

During a trip the GPS receiver will search for all available satellites to define the location as accurately as possible. If the amount of satellites is too low; wrong locations can be plotted in your trip log. Often you can notice this after opening a trip, the related map shows straight lines. We call this a GPS jump. This message can occur in the following situations:

  • Areas with low GPS coverage. This can be recognized by a single trip that is displayed inaccurately. The rest of the trips are well displayed. You can ignore this message.
  • The locations within your trips are often not correct. Please send us the trip information (date, time) and your licence plate number in a request.

No server contact

Notification: Units have made no contact with our servers for more than 3 consecutive days.

If a vehicle is turned off for longer than 30 minutes, "sleep mode" will be activated. This ensures minimum battery consumption. The connection with the live server will be disconnected. After more than 72 hours of sleep mode this message will be generated at your status report. This does not necessarily mean that something is going on. This message can occur in the following situations:

  1. When a vehicle has not been used in three days. You can ignore this message.
  2. If option 1 is not the case and the vehicle has been active, please contact the Support department.

No driver

Notification: One or more rides have no driver identification.

If you use driver identification, the driver must authenticate with a key tag or sticker before driving. When the vehicle starts, a buzzer goes off, this alerts the driver to authenticate with the tag or i-button. This notification be caused by the following reasons:

  1. A small movement of the vehicle, therefore the driver hasn't used his tag/sticker, The driver starts vehicle without using tag or sticker. Please pay attention to the kilometres driven. If this concerns 0 km, you can ignore this message.
  2. The driver uses a defect tag or i-button, the buzzer continues. This can happen when the tag is not being recognized by the reader. Please check if other tags causes the same problem. If the problem appears with other tags, please contact us.
  3. The driver uses tag or i-button, the buzzer turns off but no driver is shown in the trip log. Please restart the vehicle and use tag again. If the tag is not being recognized by the reader, please contact the Support department.

No ignition signal

Notification: No ignition signal was received while unit was registering movement. This could indicate a problem with the ignition IO signal.

This message is displayed to exclude the possibility that the contact signal is not coming through properly. 

  • Poor GPS coverage, for example in a covered car park. In this case you can ignore this message.
  • If this is not the case, please contact the Support department.

No rides

Notification: No rides were found in the past … days.

This notification appears in the status report when the vehicle has not logged any trips for a few days.

Power failure

Notification: Power failure in one or more units has been detected. This could indicate a problem with the power supply.

This notification is generated when the unit detects a power failure. A power failure notification could be generated by:

  • Reset of the FleetGO unit due to a software update.
  • Power cut:  Empty car battery, car garage visit, bad connection, sabotage. If you need help with solving the issue, please contact us.

Stationary rides

Notification: Number of complete stationary rides is (number) and exceeds maximum threshold. This could indicate a problem with the GPS receiver or unit malfunction.

No movement of the vehicle within the trip log. This message could occur in the following situations:

  • When a vehicle runs without movement. If this is the case there is no further action needed.

  • If you receive this message for each trip. Please contact the Support department.

No particularities

No issues have been detected. The trip log is working properly. 

Tip: Please check your trip logs frequently to make sure the logging is correct. 

Was this article helpful?