YarnMaster
Ahem... I guess we best do some checking before pestering Colin on this point.Originally Posted by LOVEMYRANGIE
I knew I'd seem this somewhere before. From the SLABS pdf:
andDIAGNOSTIC FUNCTIONS OF THE ABS-SLS SLABS (DiscoveryII)
All the diagnostic functions have to be performed with the Ignition turned on to the second step and the engine may be running or stopped. In many vehicles the communication with this module can be noisy and this will not allow the Nanocom to communicate with this module when the engine is running. It is possible to perform the diagnostic function also with the engine stopped, moving the wheel by hand; the only parameters that results unreadable are the engine speed and the engine torque.
This problem can be in some case fixed by checking the ecu’s ground connection and the OBD socket’s ground connection. If the ground is well connected and the problem is still present we suggest to ask us the hardware adaptor that improves the noise reduction of the Nanocom OBD port.
:: FAQ - Nanocom ::
It always pays to RTFM, I wish I remembered to more often
Hello everyone,
Got my Td5 back on the road again, re-flashed the Evo2 with new firmware, and everything good but getting a temp alarm at 42 degress set the alarm to 94 degress but keeps going off at 39-42 in live data when running it is steady at 91 degress any one get any ideas ? The temp gauge on the car has hardly moved when it goes off. water level in the expansion tank normal a little lost here.
Ian
YarnMaster
Don't worry too much about it at the moment, theres still a glitch in it.
Is still haven't tested it at a given temp yet, I have mine set at 93C but it goes off all over the place. Still makes me look though
Using Capitals, the difference between helping your Uncle Jack off a horse or helping your uncle jack off a horse...
Master
Hiya Guys
As you all know, we have pretty much nailed most, if not all, the known bugs in the software over the last few months, and have in the last couple of upgrades added coverage for the P38 Range Rover.
But I just wanted to let you all know about another improvement we have recently added to the Nanocom Evolution, which is the direct result of a couple of you putting it on the "wish list" part of this thread.
Namely 180 degree screen rotation
It was not easy, as there simply is not the space to implement this as a user selectable option in the graphics code over being hard coded.
However by changing the hard coded bits, we can compile a separate version of the Graphics firmware that provides a 180 Degree rotated version as well as the normal one.
The selection of which gets loaded is made with a new option in the kernel manager updating program.
It will be in the BBSV1.06 release which should be available in a few days
I still have it in mind to try and find a way to stop spurious values being sent by the ECU prematurely setting the temp alarm off and an auto changing option for the Instrument mode screens.
I am really pleased and proud to have reached a stage (the fifth IIRC) where we are now able to start accommodating wishes and adding new features rather than just fixing problems. It's certainly a huge turn around from how things were last year, and although my team get a big pat on the back for all their hard work, i sincerely thank the members and participants of this forum who have supported us in helping improve the Nanocom.
YarnMaster
I've come across a couple of issues with the ACE module in V1.06.
First, when recording the ACE inputs, the saved file shows incorrect speed. No way was my D2 doing 327km/h in the back streets of Brunswick- you'd be lucky to get much over 50 most of the time.
ACE capture.jpg
Second issue the bleed screen in ACE > Utility. I'm seeing blank black boxes, stop and start buttons and "step 3" but no other text.
ACE bleed screen.jpg
cheers
Paul
Master
SupporterThought I was the only one... my ACE road speed is roughly about 6x actual road speed. In hindsight, I am quite certain it has been like that for a while, i.e. not necessarily associated to v1.06?I've come across a couple of issues with the ACE module in V1.06.
First, when recording the ACE inputs, the saved file shows incorrect speed. No way was my D2 doing 327km/h in the back streets of Brunswick
And since we touch on it I have in addition ran into a couple of glitches within the autobox module:
- Engine running temp is showing incorrectly, typically about 60% of actual coolant temp (e.g. with engine at running temp would not go above 58 C)
- About 8 out of 10 times, on entering input data then either Pressures or General, Evo displays an initial set of values then it immediately freezes. On trying to going back one level the message "ECU communication error" pops up after which all menus disappear and I end up with just the background image & a hanged up Evo.
For reference have tried other systems (HawkEye & DEC) and was able to get correct engine temp readings as well as read real time autobox data uneventfully.
Rgds
Matt
Last edited by mturri; 27th February 2012 at 03:14 AM. Reason: spelling mishap
YarnMaster
Good to have corroboration.
It could well predate v1.06. I've only had the EVO since January this year and hadn't really tried recording inputs until I had v1.06 installed.
cheers
Paul
Master
Cheers Paul
The Ace speed in recording problem is likely to have been there all along and only been missed as our test rig is quite stationary
But thanks to you reporting it and mturri's corroboration, we now know it is there i am sure it will be a simple thing to find and fix.
Regards the bleed screen problem, i am pretty sure this would have been noticed, especially since no work has been done to the ACE in the last few upgrades.
Did you have an SD card installed at the time and if so, try it with the card removed, because we have seen issues with certain cards affecting the text.
In the meantime, i will have it looked at anyway.
Matt, regards your Auto Box problems, just to be sure, can i just ask you to confirm you are indeed on 1.06 and can i ask if anyone else has this problem and can corroborate this, just in case.
Cheers
Colin
Master
SupporterColin,
the ACE road speed mismatch is there all the time not just in recording mode.
Re the autobox module problems, yes I am running 1.06 and have also tried with & without the SD card. Don't hold my feet to the fire on this one, but the problems seem to have started with 1.06.
May I slide one for the wishlist: while in live data mode there's currently no way to tell whether Evo is recording or not (other than hitting the record button and finding out), would be nice if once pressed the record icon could change to something different or possibly show a (flashing?) red spot on top.
Cheers
Matt
Master
Cheers Matt
That actually makes a bit more sense to me with the road speed mismatch from ACE being there all the time rather than just in Recording mode.
Regards Autobox problems, Thanks for confirming the 1.06 aspect, however 1.06 definitely had no changes i know of over 1.05 to the Auto Box
The SD card aspect i mentioned would only affect text displays, not operation aspects.
Don't worry about your feet being toasted
Although i understand this can be nice on a cold night with the missus and a decent bottle.
We are all ultimately on the same page and looking to achieve the same goal.
I cannot stress just how valuable and appreciated yours and others inputs are in helping us to achieve a 100% correct result even if it is just the niggly detail.
I will certainly add it in the wish list to add something that tells you that the Evo is recording.
| Search AULRO.com ONLY! |
Search All the Web! |
|---|
|
|
|
Reply With Quote
Bookmarks