Printable View
Well although not specific to EVO but have just updated my Mk1 Nanocom with Rev2.06 (addition of SRS, Autobox & Motronic modules) and plugged it into swambo's auto D2a...
Here's what I got: "FAULT 005 Lock-Up Clutch Monitoring P0000"... Erased fault, reread and still there...
Rescanned with HawkEye & DEC and confirmed no fault codes stored in EAT.
Must be a Nanocom thing then...
Suppose Colin has been following through and will take note of this?
Rgds
Matt
Matt,
Thanks for confirming there is an underlying bug in the Nanocom One auto box module.
cheers
Paul
Thanks Matt,
I knew it was all Colin's fault!! ;)
Ian
I've updated my Nanocom 1 to Ver 2.07 and also have this same fault - it won't clear.Quote:
Originally Posted by mturri
I also have the auto sometimes not shifting up to 4th when it should, the MAF readings are OK - it might be time for a fluid and filter change before I look further.
yea yea yea, blame me, i can handle it ;)
The Autobox software may well still need a bit of tweeking, but at least we added it, and it's better to have something with a few bugs than nothing at all :p
Well we gotta start somewhere.
In any case, whats taken you all so long to find a problem we need to fix. We introduced the Autobox software on the Evo 2 with BBS V1.00 software over 4 months ago :angel:
In any event, it's all fixed now, alongside a shed load of other stuff, and will all be in the next software update. :tease:
I reported issues with clearing faults in the Autobox module and sent you the following on 16 July while the 2.06 update was in beta:Quote:
Originally Posted by BBS Guy
to which you responded:Quote:
The problems are in the Auto module.
....
Clearing faults allows the next fault to be read but after the initial "clear faults" I could not clear the remaining fault(s).
I suppose we should be grateful BBS have finally addressed the issue nearly 4 months after it was first reported :angel:Quote:
Yea, that had actually already been found and fixed a few days ago...
Sorry Offtrack
I am getting my Nanocom ones confused with the Evo, and the fault(s) being discussed / raised, which tends to happen mainly after a few glasses of the local plonk, which is probably why my post was a bit tongue in cheek ;)
Although you did indeed raise the fault code clearing problem with the Nanocom One Autobox software on 2.06 Beta, which we have obviously not got round to properly sorting as yet, i am fairly sure its only fairly recently the same problem has been determined to exist in the EVO, so it's obviously a common coding type problem. The EVO does also seem to have a freezing problem that the Nanocom one does not which is a timing issue.
Although coding type fixes we do on the Evo software, especially in relation to ECU communications and data processing, can of course be be instantly applied to the Nanocom one code, some fixes related to timing and some other aspects are unique to each.
I apologize that it has been an awful sounding four months before we have found the time to revisit the Autobox software since we surprised everyone by freely adding coverage of it (albeit a bit buggy), but in fairness It's still something for nothing and compared to pre BBS involvement, four months is not really a long time, and even although we have had major disruption due to constant power outages for hours on end, and our totally re locating offices, we have still managed to produce almost half a dozen updates in that time, which was no mean feat.
If I can just add something since the Evo update.
As I haven't got around to my amigos fix yet, I now don't get the sensor input error any more. On the original software, it came up LH sensor, on the first update it switched to always the RH sensor, now after the last update I get the following.
https://www.aulro.com/afvb/images/im...011/11/737.jpg
https://www.aulro.com/afvb/images/im...011/11/738.jpg
After clearing, switching off ignition and turning back on then going back into SLABS faults it flashes up this.
https://www.aulro.com/afvb/images/im...011/11/739.jpg
Looks like there might be some inconsistencies somewhere.
I'm willing to hold off on the repair if you want me to use it as a testbed.
Cheers
Andrew
Using Capitals, the difference between helping your Uncle Jack off a horse or helping your uncle jack off a horse...
LOVEMYRANGIE I can also add that I experienced this today after upgrading to V1.02 this morning.
Is anyone able to read the Autobox pressures whilst driving? Mine never seem to change and I'm having slight issues in the change from 1st to 2nd and 2nd to 3rd. 1st holds on just a fraction and there's a slight upshift in revs on the change into 3rd. 3rd, lockup and 4th are as smooth as can be......??
Filter and Fluids recently changed to no avail.
I'm geeting the picture with pump failure 1 (monitor line), when I'm checking faults in SLABS ECU, and get no fauts. With the EVO1 and firmware 1.02. I'm not sure, but I think in previous firmware, it was not showing this picture.
I have manual transmission, so I cannot test it with the transmission ECU.