How Can I Accurately Measure PTO Times for Future MyGeotab Reporting?

HomeCommunityMyGeotabReportsHow Can I Accurately Measure PTO Times for Future MyGeotab Reporting?

How Can I Accurately Measure PTO Times for Future MyGeotab Reporting?

Original Poster

Edited by Genevieve-1051

I am trying to measure PTO time for a client of ours. Currently I am matching the truck number to their Device_Name, grabbing the Device_Id from there, and pulling the statusData with their Device_Id within a specific time window for their stop.

The problem I am running into is that PTO Engaged always seems to flip on and then off within a second, so that is not helpful. So, we assumed we should use the Total Power Takeoff Time where previously noted, and take the following TPTT to find the difference in time. This works sometimes.

I will attach a screenshot below so that you can follow along with my concerns.

We had a driver who reported that PTO work was completed between 8:56 - 9:46 (Adjusted for time difference). We can see that the PTO was engaged several times in this window. From this, I am able to grab a TPTT value of 7126740 at 9:58, but due to the holiday weekend, the previous reliable TPTT value is from 7/3 several days prior, with PTO events occurring before the next report on 7/6.

Is there a more precise or granular was to measure this PTO event? I have read about the other device on the forums that can be installed, but our client has the premium package for Geotab so we assumed they would not need any other hardware.

Thank you in advance for your time, any assistance would be appreciated.

0692J00000AJgNUQA1.png

Join the conversation

You need to be logged in to reply to this post and participate in the Geotab Community discussions.

4 Replies

FleetNavSystems-1081

Hey, @JPurv-1275!

From what I've seen working with PTO installations, the engine often reports false reads on these (those really short ones). I'd almost always recommend using an IOX-AUX for accurate PTO readings, as this wouldn't get those weird false reads that the engines tend to catch for whatever reason.

Best,

Joy @FleetNavSystems-1081

JPurv-1275

Original Poster

All of our PTO Engaged events show that though. They all have a quick - within the same minute - on and off cycle. But we typically only find them within our Arrival / Depart windows where we know PTO activity is occurring. I believe PeopleNet used to handle our reporting for us with this data, but for some reason we now have to figure out how to do it on our own.

Knowing the potential for false reads creates new concerns for how accurate the Total Time is.

I appreciate the feedback, while it wasn't the answer I wanted, it does help!

Genevieve-1051

Geotabber

Hi @JPurv-1275 !

Thank you for providing such context in your question. It's always very helpful when trying to find the answer myself or when I need to ask for some help from the MyGeotab experts at Geotab. Could not find another way to measure the PTO event, but I'll ask the team and see if someone can jump in and answer you tomorrow.

Warm Regards,

Genevieve

MVS-1034

Edited by EishiFUN

@JPurv-1275 Hi,

We have a custom parameter that solves this "Pulsing" PTO is Engaged, essentially it will Delay the time period before the Go Device reports the PTO.

This has solved the issue for many of the vehicles with this issue, custom parameter is :

If this does not work then an IOX-AUXM would be the best way to sense PTO, here is a Installation guide I created for installers needing to connect the IOX to the PTO.

Best Answer

Geotab Verified

Still have questions?

Learn with Academy Browse documents