What silly thing have you done recently?

CaliGem

CaliGem

VIP Member
Messages
283
Location
Cheshire
Vehicle
T5.1 se 180
1) Went to fill up today to find the cap wasn't there ‍♀️ not been handed in at my usual garage. Replacement ordered. ££

2) two tiny soil marks on the rear mattress from bottom of my bag. Went and cleaned them, didn't I! This is how it has bloody well dried Any suggestions for to now get rid of suss stains Very welcome! 1000048546.jpg1000050140.jpg
 
That's what you call a bad day... !!

Can't think how you'd have lost the diesel cap when its attached but hey... guess it can (and you're the proof)

For the mattress, I'd remove the cover and give it a full wash with some Vanish Gold Oxi Action - great for whites.

Good luck.
 
That's what you call a bad day... !!

Can't think how you'd have lost the diesel cap when its attached but hey... guess it can (and you're the proof)

For the mattress, I'd remove the cover and give it a full wash with some Vanish Gold Oxi Action - great for whites.

Good luck.
The clip attachment connecting the cap to the van broke a long time ago, sadly. I've had the van many years and never lost it. I filled up last a week and a half ago so guess that is when I left it behind. So annoyed with myself
 
Could be worse, replacement filler cap is only £8.99 on ebay.
They look a bit rubbish tbf and if they're anything like the awful replacement engine battery cover knock-off replacements (my van didn't come with one from the previous owner!) then I'll pass.
Some things I'd rather replace like-for like so it's more like £60.

At least it'll have a new attachment for the van so I shouldn't lose it again!
 
Having said this, I found a £19 genuine one which looks ok. The cheaper genuine one looked rubbish.
 
Well, after owning our van for seven years since it was brand new and not putting so much as a chip on it in all that time, I recently drove into my covered car trailer that is parked on the other side of our drive. I have made this manoeuvre many many times without incident, so why this time?

Before explaining, I must just say that the damage was very minor but annoying none the less. Since repaired.

Having thought about it I think the answer is very much a case of "pilot error".

We own two modern cars, a 2017 Skoda Yeti and a 2019 VW California Beach. Both are fitted with what I believe is called Park Distance Control or something like that - (front and rear parking sensors linked to a graphic plan view of the car displayed on the screen of the infotainment system. When you get close to something it starts to beep and the point on the car that is close to the obstruction turns orange on the graphic. If you go closer it beeps more furiously and as the gap closes the colour changes to red on the graphic. If you continue on past that point the system emits a loud crunching sound).

Anyway, on the Yeti, which we use way more often, this system always seems to activate when the front gets close to something thereby alerting you to the close proximity of an object in front or so I thought. However, as a result of this incident, I discovered that the Beach does not do this and as it turns out, neither does the Yeti.

Initially, I thought that the system on the Beach had developed a fault but no. Upon reading the owners manual I discovered or more accurately, remembered that the front sensors are deactivated when the vehicle goes over 10mph and do not come back on unless you manually press the systems button on the dash or engage reverse.

So, having scanned the owners manual seven years ago, by the time of the said incident, I had completely forgotten all about this feature. I therefore assumed that it wasn't beeping because I wasn't about to hit the trailer. Wrong!

So why, I thought, does the system deactivate when you get above 10mph? Apparently, it's to prevent it from beeping when you are in stationary or in slow moving traffic.

Frankly, I would rather it reactivated when it drops below 10mph or stayed active all of the time. It shouldn't beep unless you get too close to the car in front and it would enable muppets like me to realise that they were about to hit something. In fact I think it can be altered to work all of the time by using one of those fancy code reading diognostic tools. I may have that done when I have the van serviced on Wednesday.
 
Well, after owning our van for seven years since it was brand new and not putting so much as a chip on it in all that time, I recently drove into my covered car trailer that is parked on the other side of our drive. I have made this manoeuvre many many times without incident, so why this time?

Before explaining, I must just say that the damage was very minor but annoying none the less. Since repaired.

Having thought about it I think the answer is very much a case of "pilot error".

We own two modern cars, a 2017 Skoda Yeti and a 2019 VW California Beach. Both are fitted with what I believe is called Park Distance Control or something like that - (front and rear parking sensors linked to a graphic plan view of the car displayed on the screen of the infotainment system. When you get close to something it starts to beep and the point on the car that is close to the obstruction turns orange on the graphic. If you go closer it beeps more furiously and as the gap closes the colour changes to red on the graphic. If you continue on past that point the system emits a loud crunching sound).

Anyway, on the Yeti, which we use way more often, this system always seems to activate when the front gets close to something thereby alerting you to the close proximity of an object in front or so I thought. However, as a result of this incident, I discovered that the Beach does not do this and as it turns out, neither does the Yeti.

Initially, I thought that the system on the Beach had developed a fault but no. Upon reading the owners manual I discovered or more accurately, remembered that the front sensors are deactivated when the vehicle goes over 10mph and do not come back on unless you manually press the systems button on the dash or engage reverse.

So, having scanned the owners manual seven years ago, by the time of the said incident, I had completely forgotten all about this feature. I therefore assumed that it wasn't beeping because I wasn't about to hit the trailer. Wrong!

So why, I thought, does the system deactivate when you get above 10mph? Apparently, it's to prevent it from beeping when you are in stationary or in slow moving traffic.

Frankly, I would rather it reactivated when it drops below 10mph or stayed active all of the time. It shouldn't beep unless you get too close to the car in front and it would enable muppets like me to realise that they were about to hit something. In fact I think it can be altered to work all of the time by using one of those fancy code reading diognostic tools. I may have that done when I have the van serviced on Wednesday.
Strangely enough, my wife's VW golf does have the front sensors live (on) all the time.

I agree it would be useful to have the fronts live all the time.
 
Well, after owning our van for seven years since it was brand new and not putting so much as a chip on it in all that time, I recently drove into my covered car trailer that is parked on the other side of our drive. I have made this manoeuvre many many times without incident, so why this time?

Before explaining, I must just say that the damage was very minor but annoying none the less. Since repaired.

Having thought about it I think the answer is very much a case of "pilot error".

We own two modern cars, a 2017 Skoda Yeti and a 2019 VW California Beach. Both are fitted with what I believe is called Park Distance Control or something like that - (front and rear parking sensors linked to a graphic plan view of the car displayed on the screen of the infotainment system. When you get close to something it starts to beep and the point on the car that is close to the obstruction turns orange on the graphic. If you go closer it beeps more furiously and as the gap closes the colour changes to red on the graphic. If you continue on past that point the system emits a loud crunching sound).

Anyway, on the Yeti, which we use way more often, this system always seems to activate when the front gets close to something thereby alerting you to the close proximity of an object in front or so I thought. However, as a result of this incident, I discovered that the Beach does not do this and as it turns out, neither does the Yeti.

Initially, I thought that the system on the Beach had developed a fault but no. Upon reading the owners manual I discovered or more accurately, remembered that the front sensors are deactivated when the vehicle goes over 10mph and do not come back on unless you manually press the systems button on the dash or engage reverse.

So, having scanned the owners manual seven years ago, by the time of the said incident, I had completely forgotten all about this feature. I therefore assumed that it wasn't beeping because I wasn't about to hit the trailer. Wrong!

So why, I thought, does the system deactivate when you get above 10mph? Apparently, it's to prevent it from beeping when you are in stationary or in slow moving traffic.

Frankly, I would rather it reactivated when it drops below 10mph or stayed active all of the time. It shouldn't beep unless you get too close to the car in front and it would enable muppets like me to realise that they were about to hit something. In fact I think it can be altered to work all of the time by using one of those fancy code reading diognostic tools. I may have that done when I have the van serviced on Wednesday.
Oh no. A human error, easily made by the sound of things. My van reverse sensors have never worked and the front ones only very occasionally.... Maybe that's down to the flashing cone button thingy on the dash you mention!

I took would would prefer they're on all the time as it'd make more sense that way. I am adept now at jumping out and checking the last few inches before committing to a parking spot. It's become a habit.
 
So why, I thought, does the system deactivate when you get above 10mph? Apparently, it's to prevent it from beeping when you are in stationary or in slow moving traffic.

Frankly, I would rather it reactivated when it drops below 10mph or stayed active all of the time. It shouldn't beep unless you get too close to the car in front
One of our cars has the fronts permanently on, it drives me mad driving round London, every queue it goes off unless you are at the front, then it’s fine until the inevitable cyclist pulls in front. It also picks up the vehicle alongside in narrow traffic lanes.

Get out in the sticks & every verge & oncoming car on the country lanes sets it off.
 
One of our cars has the fronts permanently on, it drives me mad driving round London, every queue it goes off unless you are at the front, then it’s fine until the inevitable cyclist pulls in front. It also picks up the vehicle alongside in narrow traffic lanes.

Get out in the sticks & every verge & oncoming car on the country lanes sets it .
So, there's no way of turning it off? That must be very annoying for you.

On my van the front sensors deactivate when the speed rises above 10mph. You can press the button to reactive the whole system but if your still above 10mph it will come on for a second or two and then drop out again, which is equally annoying.

20261013_094743.jpg
 
So, there's no way of turning it off? That must be very annoying for you.

On my van the front sensors deactivate when the speed rises above 10mph. You can press the button to reactive the whole system but if your still above 10mph it will come on for a second or two and then drop out again, which is equally annoying.
It works the complete opposite to the van, you can use a button to cancel it but as soon as you go over about 10mph it resets & you have to use the button again to cancel again.
It’s not just the beep that’s annoying, it turns on all the cameras & displays them instead of the sat nav, & mutes the radio as well.
 
It works the complete opposite to the van, you can use a button to cancel it but as soon as you go over about 10mph it resets & you have to use the button again to cancel again.
It’s not just the beep that’s annoying, it turns on all the cameras & displays them instead of the sat nav, & mutes the radio as well.
I wonder if your system could be reprogrammed to do what you want it to?

I'm certainly going to look into having ours looked at. If that button could turn the system on or off to your command but reactivate automatically at speeds below 10mph, that would suit me.
 
One of our cars has the fronts permanently on, it drives me mad driving round London, every queue it goes off unless you are at the front, then it’s fine until the inevitable cyclist pulls in front. It also picks up the vehicle alongside in narrow traffic lanes.

Get out in the sticks & every verge & oncoming car on the country lanes sets it off.
New cars drive me mad with all their beepings and warnings. First thing we did in our ST was switch as many of the assist thingies off as possible.
 
switch as many of the assist thingies off as possible
No matter which assists are switched off, they all come back on as ‘default’ next time I switch on ignition. So it’s become a ritual when I start the engine to go through the assists I don’t want …. and switch them off (again).

If anyone has found a way of changing the ‘default’ set of assists, I’d love to know!
 
No matter which assists are switched off, they all come back on as ‘default’ next time I switch on ignition. So it’s become a ritual when I start the engine to go through the assists I don’t want …. and switch them off (again).

If anyone has found a way of changing the ‘default’ set of assists, I’d love to know!

Thankfully the T6.1 is too old to have the annoying bongs but my other car (eletric Corsa) does so I also have to ritually turn the speed bong thing off everytime I start. I don't condone speeding but getting bonged at for being 1km over the speed limit is daft and half the time it doesn't know the correct speed limit wherever I'm driving. Sadly, there probably isn't any way of changing the defaults. A couple of manufacturers (Renault, Kia, maybe more) do have one button to turn all the silly bongs off but you still have to press it each time.
 
No matter which assists are switched off, they all come back on as ‘default’ next time I switch on ignition. So it’s become a ritual when I start the engine to go through the assists I don’t want …. and switch them off (again).

If anyone has found a way of changing the ‘default’ set of assists, I’d love to know!
Exactly why I love an older manual vehicle. Electric vehicles especially can get in the bin

Give me my 2010 T5 anyday
 
No matter which assists are switched off, they all come back on as ‘default’ next time I switch on ignition. So it’s become a ritual when I start the engine to go through the assists I don’t want …. and switch them off (again).

If anyone has found a way of changing the ‘default’ set of assists, I’d love to know!
I do the same every trip, we live in the country with small lanes and it drives me nuts when I forget and the steering try’s to auto correct my driving line…..don’t get me started on the fantastic reverse feature……
 
Silly things. I once forgot to put the hand brake on in our old T5 panel van, I was half way back to the house when I saw it roll past me, it picked up speed, narrowly missing several parked cars on either side of the road, before finally parking itself into the side of my wife’s Vw polo.
 
Ok, me again!

well, not my mistake but the OH came to meet myself and son who were camping last week. Hubs left on the morning I was packing up the van. He had been driving down the M5 and then just onto the M6 for about 1hr 15 when I called to tell him he'd taken my keys with him.

He has to come all the way back. What a sausage!

Thank goodness I have my Tile tracker in my keys.... Instantly realised he had them
 

Similar threads

ClanTimmins
Replies
25
Views
10K
Roger_rioja1969
Roger_rioja1969
Back
Top