am i screwed on my 34?

Here ya go:

Can a user edit or change driving time that has been recorded by an ELD to non-driving time??

 

Yes, i seen the faq. Now do you have an answer to the question? Heck I can post a guidance that states one must be in sb 8 hours a night, or one talking about 10 hours drive time.
Doesn't make it correct.
Oh, and same faq says drive time can be edited to assign correct time in team operations, so as an absolute rule the same faq disagrees.
So again, where is the regulation for editing drive time.
Another thing. That faq says it cannot be changed to non driving time. Nothing about changing to driving, off duty (pc)

 

Whenever I use PC the time is recorded on the "off duty" line 1 with a hatched line instead of a solid line. It never goes to the "Driving" Line 3 in as long as its PC, So it can be edited there. But if it goes to Line 3 because I forgot to activate the PC button after I stopped at WM then got back in for the return trip, I can't edit it, but I can put lots of annotations explaining the screw-up. But that don't get my time screw-up fixed. When I try to delete or otherwise change the line 3 time, I get a error box saying I can't make any changes to Line 3. I think that was the whole purpose of the ELD Mandate wasn't it? To keep the driving time truthful?

 

Well, it's to record all driving time. There is no way to keep it truthful when there are stuff like yard moves and pc that are user select able....
It is simply a more accurate way to record hos, but it's still far from 100%.

And again, simply call the office tomorrow and get them to fix it. They have the ability (maybe not the willingness, but the ability anyway)

 

Mine will put PC time as "Off Duty" while the Yard Move is "On Duty". Each with hatched line instead of solid line. Never on the "Drive Line" Line 3. Once it gets on the Line 3 "Drive Line" it can't be edited. If he has an AOBRD big difference because those will allow edits to the Line 3. I would look in the rules dictating the "self-registration" of ELDs to find the rule about Driving Time to be non-editable. I will try to find time to research that. I tend to get lost when pouring through the regulations looking for a few key words. Searchable PDFs help in that regard though.

 

What kind of device are you you running? ELD or AOBRD? What brand? I see you said "and noticed that my ELD had switched over to drive time" but some here say you might have an AORBD.

 

Again another "Company Policy". Does he work for the same company you do? I don't know.....

 

You have to look at the ELD rule. Section 4.3.2.8.2 (b) reads:

"(b) An ELD must not allow automatically recorded driving time to be shortened or the ELD username associated with an ELD record to be edited or reassigned, except under the following circumstances:

(1) Assignment of Unidentified Driver records. ELD events recorded under the ‘‘Unidentified Driver’’ profile may be edited and assigned to the driver associated with the record; and

(2) Correction of errors with team drivers. In the case of team drivers, the driver account associated with the driving time records may be edited and reassigned between the team drivers if there was a mistake resulting in a mismatch between the actual driver and the driver recorded by the ELD and if both team drivers were respectively indicated in each other’s records as a co-driver. The ELD must require each co-driver to confirm the change for the corrective action to take effect. "

 

From the KT web-site:

Can’t see the edit button for your Drive time? That’s because you have recently been enable to use an ELD. As per DOT / FMCSA regulations for the ELD mandate, compliance requires all Driving events to be recorded directly through the vehicle via engine-connected hardware, and Drivers cannot have the ability to manipulate or change such events. Make sure you cite the rule! “DOT/FMCSA rule 395.15”.

I also looked at the Admin instructions to edit logs, and there it tells how to edit on duty, off duty, but not driving time.

 

AhHa,,,There it is:
49 CFR Appendix A to Subpart B of Part 395, Functional Specifications ...
Thanks to Jeff Waterstreet!
That CFR spells it out clearly, Now whether the "self-certified" devices comply with it is questionable for sure....