why do digi tachos count p.o.a in with breaks
the other night i got driving and checked my driving time only to see id got 25 mins break banked but id not had any break, i then had a 22 minute break and the screen showed 47 mins break so i thought, i then started driving and my driving time had gone back to zero.
when i checked my print out at the end of the night it showed 22 mins break and the 25 mins i thought were break were p.o.a
surely it should only count breaks and not p.o.a
this sheet i was given today probbaly explains it better
please note that the annex 1 b regs state that the continuous driving time and ■■■■■■■■■■ break is computed within the recording equipment as
the current accumulated driving times of a particular driver, since the end of his last AVAILABILITYor BREAK/RESTor UNKNOWN period of 45 mins or more[this period may be split into several periods of 15 mins or more].
■■■■■■■■■■ break time is computed within the recording equipment as the current accumulated AVAILABILITY or BREAK/REST or UNKNOWN times of 15 mins or more of a paticular driver, since the end of his last AVAILABILITY or BREAK/REST or UNKNOWN period of 45 mins or more[ this period may have been split in several periods of 15 mins or more].
what im trying to say is why is it computing[ adding ] availability[p.o.a] together with rest/break as there too different things
I think it’s because the prats that programmed the digi-tacho firmware didn’t speak to Davey Driver first.
To be honest, I’ve got no idea.
Ady 1 is correct.
The reason that VU’s count Availability and Break together is because that is what the Regulations (Annex 1B of 3821/85) says they will do.
Basically they add any periods of 15 minutes or more of; availability, break/rest or unknown together. Once they reach 45 minutes total the driving total is reset to zero and starts counting towards the 4 hours 30 minutes warning again.
The problem as far as we’re concerned is that Availability is not break/rest, so you have to be careful that you don’t accidently drive over the 4.5, it could happen like this;
01:30 drive
00:15 break
01:20 drive
00:32 Availability (accumulated driving counter resets to zero)
02:45 drive
You have now committed an offence, you have driven for 5:35 and had a break of only 15 minutes. And the VU didn’t warn you :shock: 
Simon; It wasn’t the poeple that programmed the VU’s, it was the people that wrote the Legislation and passed it 
geebee45:
Ady 1 is correct.
The reason that VU’s count Availability and Break together is because that is what the Regulations (Annex 1B of 3821/85) says they will do.
Basically they add any periods of 15 minutes or more of; availability, break/rest or unknown together. Once they reach 45 minutes total the driving total is reset to zero and starts counting towards the 4 hours 30 minutes warning again.
The problem as far as we’re concerned is that Availability is not break/rest, so you have to be careful that you don’t accidently drive over the 4.5, it could happen like this;
01:30 drive
00:15 break
01:20 drive
00:32 Availability (accumulated driving counter resets to zero)
02:45 drive
You have now committed an offence, you have driven for 5:35 and had a break of only 15 minutes. And the VU didn’t warn you :shock:Simon; It wasn’t the poeple that programmed the VU’s, it was the people that wrote the Legislation and passed it
you could even drive then 9hrs without a break without a warning if you used p.o.a , doesnt make sense to me to design something to warn you you need a brake then put a glitch in it 
now going to use break/rest and not p.o.a so should be o.k