Make it 1.05 then as they weren't spread that far in time :pQuote:
Originally Posted by BBS Guy
Had even been tempted to downgrade to 1.04 to try prove it but unsure it could be safely done.
Cheers
Matt
Printable View
Make it 1.05 then as they weren't spread that far in time :pQuote:
Originally Posted by BBS Guy
Had even been tempted to downgrade to 1.04 to try prove it but unsure it could be safely done.
Cheers
Matt
Went to check this out and almost came badly unstuck.Quote:
Originally Posted by BBS Guy
Made the mistake of plugging cable into the obdII port and then the Nanocom and got a nasty spark between the cable and metal work of the Nanocom. Fortunately I'd only blown Fuse 20 in the passenger fuse box, but I won't be tempting fate again.
I was able to confirm that the ACE bleed screen is still missing text items even with the SD card removed.
cheers
Paul
I must confirm the missing ACE bleed texts - EVO 1 and 1.06 firmware with SD card installed.
One idea - in the Nanocom ONE software it is possible to save current settings of ECU into a text file. I'm missing this in EVO. With TD5 ECU it was very nice just to look into a file with ALL and CORRECT setting. It is very easy to make a mistake during writing the settings on a paper or just lose the paper.
Madtom,
The EVO can save user configurable settings for TD5 ECU, SLABS, and BCU.
I'm guessing that you are referring to is the ability to save out the non-configurable settings listed under TD5 > Settings > Info. The Nanocom One let the user save this information along with the injector codes as a .txt file but this doesn't seem to be an option in EVO.
The information on this screen reflects the options hard coded into the current ECU firmware so I'm not sure what benefit there is in being able to save to file?
cheers
Paul
The screen shot below shows the instrumentation screen on my P38 while travelling on the motorway.
https://www.aulro.com/afvb/
This all looks pretty reasonable except the tacho "Engine Speed" read-out will not go above 2550rpm. Below 2550, the revs display seems to match the tacho ok.
I did have the tyre correction set to 1.15 to account for my larger than standard tyres. Wonder if this makes a difference?
Cheers, Paul.
Downgrading is not possible with the EVO Matt ;)Quote:
Had even been tempted to downgrade to 1.04
Since we are now so pro active with debugging we are totally confident that any problem found and reported to us is going to be quite minor and fixed quite quickly.
The standard computer type D connectors in 9 way, 15 way and even 25 way are very commonly used by almost every diagnostic system, but they do have the drawback that the pins of the plug can inadvertently be shorted against the outer metalwork shell of the socket if they are plugged in while live. You can also get a case where the Positive is momentarily connected before the ground which can cause a voltage differential that damage possibly damage the unit.Quote:
Made the mistake of plugging cable into the obdII port and then the Nanocom and got a nasty spark between the cable and metal work of the Nanocom.
You may note that in the OBDII plug the 2 Earth pins are slightly longer so they always mate first.
Luckily, as in your case, this typically just blows the vehicles Diagnostic socket fuse.
Well thanks for the confirmation. I must confess i have not looked myself yet. But its been one of those weeks :eek:Quote:
I was able to confirm that the ACE bleed screen is still missing text items even with the SD card removed.
I will definitely get on the case early next week though :)
That sounds like a definite bug to me Paul and if you think about it the cause in respect of incorrect coding and maths seems quite obvious, except for one detail. If i am correct about the cause of the problem what should be happening is that after 2550 RPM the value should restart from zero and climb again.Quote:
the tacho "Engine Speed" read-out will not go above 2550rpm
The 255 value is the maximum decimal value one Hex byte can hold (0 to 255), in this case also multiplied by 10, after that you have to add a second byte, which would be multiplied by 2560 to the value from the first.
IE 00 FF would give 2550 RPM and the next increment would be 01 00 which would give 2560 RPM.
I can understand a coding error of not including the second byte in the calculation, it is not uncommon and easily fixed, but not why you would still see 2550 RPM instead of Zero if this were the case.
I can't wait to check the code :)
But no matter what, cheers for finding and notifying us about this.
Another easy fix and a step closer to being absolutely 100%
Cheers
Colin
Hi Paul. Assuming that is a slightly "squashed" photo of an evo 2, can you advise where you got the holder from - or is it something you made up yourself?Quote:
Originally Posted by PaulP38a
Don't think it is "squashed". The bracket is just a phone holder from Officeworks extended to the max width and rotated. Cost around $30 from memory.Quote:
Originally Posted by gavinwibrow
Cheers, Paul.
Many thanks for info - my evo seems more rectangular - must be the angle. cheersQuote:
Originally Posted by PaulP38a
I think I have found an issue with BCU > Outputs > power wash. After trying to test the power wash with the Nanocom and getting no response, I wasted the best part of the afternoon trying to see why the power wash wasnt working before coming to the inescapable conclusion that the Nanocom doesn't activate the power wash pump, and actually disables the pump until BCU resets.
I won't share the sorry tale of three hours spent engaged in bumper removal, refit, and circuit checking with a multimeter.
Maybe other Nanocom owners can check this out. I have a suspicion this has never worked on my D2 going back to 2.04 on the Nanocom One.
Cheers
Paul