Do you know what it means this fault? I thought that it was a vehicle fault code, but when I looked for the source I saw that it's the telematics device
Best regards!
Skip to main content
CristianGarza-1088
Original Poster
Edited by EishiFUN
Join the conversation
You need to be logged in to reply to this post and participate in the Geotab Community discussions.
Top Answers
Genevieve-1051
Community Administrator
Edited by EishiFUN
Hi @CristianGarza-4486 !
Great question! The low priority warning light on fault indicates that the GO device is reading a pending fault code from the ECU of a vehicle. This fault is reported with another fault or engine measurement which can provide more information on the pending fault code reported.
To determine what specifically is causing this fault:
- Go to Safety > Log Data & Collisions
- Click Options
- Select a Date Period and Vehicle
- Click Apply changes
- Scroll down to the "Low priority warning light on" fault log.
- Look for the next EngineStatusRecord or EngineFaultRecord log reported.
The "Reason for the record" of the EngineStatusRecord or EngineFaultRecord log reported immediately after the "Low priority warning light on" fault is what caused this fault to be reported.
Hope this clears things up a bit,
Genevieve
11 Replies
Genevieve-1051
Community Administrator
Edited by EishiFUN
Hi @CristianGarza-4486 !
Great question! The low priority warning light on fault indicates that the GO device is reading a pending fault code from the ECU of a vehicle. This fault is reported with another fault or engine measurement which can provide more information on the pending fault code reported.
To determine what specifically is causing this fault:
- Go to Safety > Log Data & Collisions
- Click Options
- Select a Date Period and Vehicle
- Click Apply changes
- Scroll down to the "Low priority warning light on" fault log.
- Look for the next EngineStatusRecord or EngineFaultRecord log reported.
The "Reason for the record" of the EngineStatusRecord or EngineFaultRecord log reported immediately after the "Low priority warning light on" fault is what caused this fault to be reported.
Hope this clears things up a bit,
Genevieve
What does it mean when you do the process described above and you only see:
06/30/20 16:23:49
Record Value:Reason for the record: Low priority warning light onRecord Type: EngineFaultRecord
What does that mean. Doesn't seem to be telling me what the reason for the engine light was at all.
Hi @Genevieve-1051 ,
Following your instructions above, I see that the next EngineStatusRecord or EngineFaultRecord log reported following our 'Low priority warning light on' fault message reads: "Telematics device voltage"
Can you tell me what this means or how we should address it?
Genevieve-1051
Community Administrator
Hi @KELKO-1517 ,
Welcome to the Geotab community! First, the image you shared shows the previous EngineStatusRecord or EngineFaultRecord log reported. Is there any way you can check what the next one to come after or below the "Low priority warning light on" is and share that?
Best,
Genevieve
Thanks for the quick reply @Genevieve-1051
Here are the sequence of EngineStatusRecords beginning with the EngineFaultRecord. They are sorted such that the older records are listed from the bottom going up.
Genevieve-1051
Community Administrator
Edited by Genevieve-1051
Hi @KELKO-1517 ,
Thank you for the expanded image!
Just wanted to confirm that we were on the right track with "Telematics device voltage" because the only information I was able to find didn't seem to be telling us much about what this actually means or how to address it. But I will follow up with the team to see if there's more known information about this engine measurement, and how it should be addressed.
If they don't have more information, Unknown diagnostics will often need to be reviewed by a professional mechanic. But first, let's check with the team.
I'll let you know what they say next week or today if I hear back by the end of the day.
Have a great weekend,
Genevieve
Genevieve-1051
Community Administrator
Hi again @KELKO-1517 ,
After talking with the firmware team, Telematics Device Voltage is the measured voltage the GO records from the diagnostic port; usually this will be the voltage from the vehicle's battery. They also said that there is nothing you should need to do - this record is pretty common if the ignition is off.
It was mentioned that you can use a MyGeotab rule as well as a GO device fault that will trigger at difference thresholds to indicate if low voltage is actually detected. If you'd like more information on how to set this rule up, please let me know?
Best,
Genevieve
CristianGarza-1088
Original Poster
Thank you so much Genevieve,
I'm so surprised with the answer. And I really appreciate the passion and attention that you are giving to the community, even, I couldn't wait to tomorrow to see your comment, I think that all your vibes are contagious 😀
Keep going and warm regards!
Genevieve-1051
Community Administrator
Thank you @CristianGarza-4486 your kind words made my entire day! We're trying really hard, so it's always so great to hear positive feedback like that! Clearly, I'm not the only one with contagious positivity because your comment genuinely made me smile sooo big!
Thank you again and I'm happy to help you anytime!
Best,
Genevieve
It confuses me a little, since that specific code appears with "telematics device" as source (and not j1939, OBD or other protocol from the vehicle). But it makes sense now that we understand we have to look at next log.
Thanks a lot
Genevieve-1051
Community Administrator
Anytime @César Ortiz ! Love helping a brilliant man like youself gain even more knowledge 😁
Still have questions?