

VintageSpecial
Members-
Posts
103 -
Joined
-
Last visited
Converted
-
Local Area
Wellington
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
VintageSpecial's Achievements

Advanced Member (3/5)
247
Reputation
-
I did try that, even after 24 hours disconnected and no, doesn't work unfortunately. The workshop manuals do actually say if the light is on you have to go to the dealers to use special equipment to get it reset. The dealership in Wellington won't say if they can fix it or not, or even if they have the equipment to do it when I asked. All they will say is you have to book it in for a service for $342 and they can have a look at it and then tell me. But my local WOF chap recommended a local auto electrician who I rang and they did say they have various old scan tools. I am taking it to them on Friday for them to have a look. Even with one of the correct old scanners called a Hawkeye made by a company called Bearmach (who has since gone bust) you need a special dongle to swap pins around to get it to connect. Luckily someone figured that out and posted the pin outs: https://www.aulro.com/afvb/discovery-1-a/279364-95-disco-resetting-reading-srs-airbag-codes.html I did find the correct plug under the dash. All the SRS wiring is easy to spot as it's covered in bright yellow shielding. Will see what the sparky says on Friday.
-
Thanks for the replies, I do want to fix it properly and haven't rang around dealers/auto electricians yet because 1, it's the weekend and 2, it's unlikely they can do it these days. The equipment they used to use is now all well out of date and they probably don't have it anymore. It was bespoke equipment. Some kind of laptop or computer with special software and hardware. Those stopped being supported decades ago. I am not a hard core Landy person but from what I have found online the 'official' ones were called Testbook and another called T4. Testbook is long gone. T4 is still around but only for OBDII equipped cars not early Discos. And they cost about 2kUS$! There were other cheaper after market units, Hawkeye and Nanocom, but even those are now old and hard to find or not made to support pre OBDII cars anymore. NickJ has the right idea, hence asking here, in a forum, in case someone can point me at the right kind of club/person that might do it. I don't have Facebook unfortunately. Am going to ask my local WOF guy when he's open tomorrow too, he's a practical country sort so might have some leads. And I am waiting to hear from the Land Rover owners club too. I need someone who has one of those old, aftermarket reset units I imagine. Probably the kind of thing where there is one person in a club somewhere everyone goes to. Again, I asked here in case someone knows who that is. As for official dealers, there is one reasonably close to me in Wellington, Armstrongs. Unlikely they can do it but I'll ask them tomorrow. They might have someone they send people to so there might be some independent place, again that's why I am asking here, someone might know already. But I need somewhere who understands this is a pre OBDII car or else they will assume they just need to plug in any old scanner to reset the code which isn't the case. The reason I mentioned certs isn't for mine, more a general question I asked in my original post, "What happens when cars get to the point where a simple software failure means you can't get a warrant anymore since the tech is too old but the vehicle still perfectly good?". At some point systems in cars won't be able to be fixed since the tech to do it won't be around. Cars that get software updates will eventually stop being supported. It's in the car manufacturers interests to be like Apple and encourage continual upgrading/selling new vehicles. It's always in governments interests to encourage new cars for safety reasons, environmental, more sales tax, lobbying from new car makers, etc. Old car like vintage ones you can always get going again. Even very bespoke parts can be remade. Things get a lot trickier when software is involved. Anyone who works in I.T. knows supporting old tech is a pain in the neck. It's not just the cars themselves. Cars that use OTA updates talk to servers and those also require maintaining over time. There must be a hell of a lot of infrastructure behind all that, all constantly needing updates and changes. Simon
-
I have a 1997 Land Rover Discovery 1 and recently had a totally flat battery. A jump got it running again fine but now the SRS warning light on the instrument panel is on and stay on. It seems in these early Discos the system will have done a check, found a low voltage and so it lights the lamp. But apparently it is not self resetting. The only way to reset it is with a dealer code reader. Not sure any dealers will have the old equipment about to do that now (I need to try try ringing them still). These cars are pre OBDII ports. There apparently is a connector to hook to but then it's a proprietary protocol so you still need a special reader to clear the code. There used to be readers available (Hawkeye and others) but they don't seem available now. There are cheap readers that claim to do it but I think most won't do the 96/97 Discos. It was only in about 1998 things started standardising. There might be someone around who has the gear to do it, maybe in a Land Rover club? I am in the Kapiti area if anyone can suggest someone. But what happens if no one can do it? As far as I can see that warning light would be a WOF failure. Is it possibly to have the system removed? Does that then need certing? Not sure how good 26 year old early air bags would be now anyway? What happens when cars get to the point where a simple software failure means you can't get a warrant anymore since the tech is too old but the vehicle still perfectly good? Simon
-
Won't that come down to if it's a modified production vehicle or a scratch built? If modified but you haven't changed the fuel tank or battery from production then it's fine. As soon as you start modifying anything then all the rules in that section of the manual seem to apply. That's how it seems to work to me but I read it through a vintage car lens. A lot of vintage cars have their fuel tanks scuttle mounted right next to a battery in the engine bay. Mine has both in the tail. The manual talks a lot about compartments which doesn't really apply to some vintage cars. Mine is basically a metal tube on a chassis. For a scratch built historic replica the rules get a bit odd since if you had to follow them all you end up something with is neither historic, nor a replica! This is recognised, and called out in some of the Info sheets (#01-2008 mainly). So I try to keep everything as factory original as possible. Simon
-
I've always wondered what the story is for vintage cars like mine with a long, pointy tail. Traditionally the number was painted on the tail side. Can't do that now. I can mount the rear plate to one side or the other but the tail means it is only visible from one side. You can't really put it under the tail. Might have to do like they did on Austin 7 Speedy cars where it's on a board sitting on top of the tail (with stop lamps either side)? The front is easy at least, it fits between the front dumb irons.
-
I am wondering similar for my scratch built Riley build. As far as I can tell I need to finish the whole car before I can take it to VTNZ to get a VIN then to the certifier for LVVTA cert then back to VTNZ for Entry certification. I had the same question as Zep. When I last saw the certifier he said finish the whole car then bring it back.
-
To be fair, stickers work the other way around too! https://www.drivingtests.co.nz/resources/notices-ordering-a-vehicle-off-the-road-pink-sticker-green-sticker-and-yellow-sticker/
-
A chap I know thinks there is a conspiracy involving Dekra and the car manufacturers (big car?) to try to get all old cars off the roads faster saying it's in the name of safety but really so the manufacturers can sell more new cars. As a software guy my concern isn't parts but what happens when the software in cars stops being updated and you could end up with vehicles no longer compliant due to not having some vital update or patch. Someone can always make mechanical parts, but software is all protected by copyright and licensing restrictions so it's not so easy to get around (legally). See all the fights with John Deere about the right to repair around this. It's a bit like how Apple use planned software obsolesce to force people into new iPhones. Owners of older Teslas will find it starts happening to them soon too I imagine. It's made worse with the way cars seem to becoming more like appliances these days. 14 years is a long time in software terms. That's how long it was between Windows XP being released and the end of life support date for it for example. We do Agile now, people seem to expect the software to change every two weeks
-
I was considering that but that page does sort of explain the thinking of this particular change. You'd just get that back to an OIA. They are basically saying vehicles are built and tested to a standard and you're adding something that now changes that so it needs to be inspected to see what the impact of that is then that makes sense. NZTA check vehicles are to the standard, LVVTA are there to check vehicles that fall outside that (and in turn have their own standards). That makes sense. I am not picking on NZTA here, this is just an interesting example of change. I am more interested in how they decided that this was a thing to change now rather than some other thing or problem. Where I work, I wonder the same thing - what drives the work we do and the pace we have to do it. It's quite hard to find out! The larger an organisation the harder it is to find out. The people at the top have a vision but no idea of the practicalities, the people at the bottom know the practicalities of their small area but don't know how it all needs to piece together and so you have to have layers and layers in the middle trying to co-ordinate/deliver it all. And in really big orgs you have whole departments whose job it is to communicate what's happening in the middle bits so people understand why they are there and what they are doing. Especially across orgs, say between NZTA and LVVTA. Politicians of all flavours often campaign on removing those middle bits (and the communicators) as wastage.
-
I'd like to know what drives (no pun intended!) these sorts of changes at NZTA? They seem a bit vague: "There's some evidence..." "Bullbars can cause airbags..." Would be interesting to see some of that evidence. It seems odd they focus on the drivers safety when you'd think the risk from bull bars is far greater to a pedestrian or cyclist and that adding bars to the front of a vehicle will affect any of the Vulnerable Road User safety features a vehicle has. Australia has done some research on this but it's tricky to get solid conclusions since the data from real crashes lacks certain information and the sample sizes are quite small. But generally it seems accepted that bull bars increase the risk to pedestrians. But it's hard to find much about how they affect they affect the internal safety systems, like air bags, of vehicles fitted with them. I think partly since some of those systems are quite new so again there isn't enough real world data and that studies on that specifically haven't been done. With all the things they could be doing/looking at, how does something like this get chosen as the change NZTA spend time working on?
-
I 'fixed' the leaking sunroofs in my Disco a by covering them completely with clear PPF. I need to redo it as it has split on one part though. Definitely stopped the leaks though. The headlining on mine was ruined so I replaced it with grey polar fleece bought from Spotlight. You can get it in extra wide widths so can do the whole headliner in one shot. It's stretchy and glues well (but use high temp contact glue) and looks pretty good. On mine the interior is grey so it blends right in. You don't need foam underneath it which is what goes on the original headliners. If anyone asks I tell them it's headlined in Muppet hide! Simon
-
I seem to have been locked out of my account for some time but finally got back in. I updated the project mainly on YouTube so look there to see all the progress but to finish this off I should at least post a picture of the finished bike. Goes very well. At least puttering around the garden that is. I have a new bike project to do now. A 1953 Velocette LE Mk2. Simon
- 24 replies
-
- 11
-
-
Next in the saga: I cleaned all the rust off the forks then put layers and layers of anti rust paint on them and sanded it off again. Should save the seals I think. Also the frame is back from the blasters and is all painted. And I stripped the wheels and will get new bearings for them. Does anyone know what the top steering bearing is? Simon
-
That beer cooler was YEARS ago! I actually have a tiny turbo and parts sitting on the shelf as another project I should do sometime. I always wanted to make a much smaller, more portable jet engine, to be able to more easily take places to show. Simon
-
More progress and another little film. I stripped the front forks. Not totally, I didn't strip the internals, just got them out so I could clean and check everything. The insides don't quite match the manual/parts books I have. One was worse than the other. Looked like the oil had never been changed. Springs were within serviceable limits. I cleaned the internals in the ultrasonic cleaner and they cleaned up nicely. I will fit new oil seals and have new dust covers coming (I hope). The tubes I wire brushed and have sitting in Evaporust to get all rust out of the rust pits. I will fill the slight depressions with epoxy then sand them smooth to make a nice surface for the seal to ride over. Luckily most rust was not where the forks pass the seals. I made a tool to hold the inside bolt to allow you to undo the Allen bolt in the base to get it all apart. A small film is here: https://youtu.be/bHCRbjLJTvk Simon