Guide Purpose:

• This guide IS designed to:
  • Show how to pull Ignition events
  • Explain the types of ignition events.
  • Explain how we can use Ignition event to troubleshoot.
• This guide IS NOT designed to:
  • Explain how to write, read, and define fields in JSON.

How to Pull Ignition Events

1. Input ignition in the Type section.
   1. This brings up all ignition events.
      

Review Ignition_Power_On

1. This is the start of the ignition cycle.
   1. This signal identifies we have received power from the ignition line.
2. Ignition will be on for 20 seconds before the status changes.
   1. The next signal is ignition_on_confirm and will always be 20secs after ignition_power_on.
   2. The only time you will not see ignition_on_confirm is when power is lost to the ignition creating an ignition_power_off.

*The signal also sends power to the gateway.

Review Ignition_On_Confirm

1. This signal shows the gateway is powered on.
   1. If you do not see this signal, the gateway is not running.
2. Once ignition on is completed it will capture the battery voltage (VBAT) and the backup battery voltage (BBAT).
   1. The next signal is ignition_power_off and this can happen any time after ignition_on_confirm.
      

Review Ignition_Power_Off

1. This signal shows the gateway power is about to be lost from the ignition line.
2. Ignition will be off for 20 seconds before the status changes.
   1. The next signal is ignition_off_confirm and will always be 20secs after ignition_power_off.
   2. The only time you will not see ignition_off_confirm is when power is received from the ignition creating an ignition_power_on.
      

Review Ignition_Off_Confirm

1. This signal shows the gateway is not powered by the ignition line.
   1. If you do not see this signal, the gateway is still running.
2. Once ignition off confirm is completed, it will capture the battery voltage (VBAT) and the backup battery voltage (BBAT).
   1. The next signal is ignition_standby and this happen 300secs(5mins) after ignition_off_confirm.
   2. The only time you will not see ignition_standby is when power is received from the ignition creating an ignition_power_on.
      

Review Ignition_Standby

1. This signal shows the gateway is using battery to stay on.
   1. This allows connection to the gateway and data can be retrieved during this period.
   2. While the signal is on ignition_standby, the camera units on the vehicle are no longer recording.
2. Once ignition is on standby, it will capture the battery voltage (VBAT) and the backup battery voltage (BBAT)
   1. The next signal is ignition_low_power and ignition_shutdown, this happens 2400 secs (40mins) and 20 secs respectively after ignition_standby.
   2. The only time you will not see ignition_low_power or ignition_shutdown is when power is received from the ignition creating an ignition_power_on.
      

How to Read This Data for Troubleshooting

This troubleshooting should only be done when other ways to determine what the problem is has been exhausted.

1. This activity is a typical activity during the cause of day. We can see the vehicle was in the off cycle for about 22 mins.
   1. This could be due to the driver taking a quick break, making a pit stop, or for other reasons.
2. This is a complete cycle which typically takes place when the driver is on lunch or done for the day.
3. This activities are not typical and its one to draw attention to.
   1. Turning on the ignition and turning it off 2 to 3 times in row could be overlooked.
      1. This could be due to driver turning on the ignition and then shutting off during daily pre-inspection and other situations.
   2. A multiple occurrence of the same activity (that means more than 5 times) in a row would signify there is a problem with the ignition line.
   3. Clusters of this event (5 to 10 times) within the same day could also signify there is an issue with the ignition line.