PDA

View Full Version : Nanocom evo - instrument pack



Sandlover
21st August 2011, 08:51 PM
Hi, does anyone have experience using the evo's coolant temperature warning feature. I tried setting it up yesterday when driving in sand with the alarm set to trip at 95 degrees,(just to see if it worked). The temp got up to 97 and no alarm went off.

Anybody else used this feature of the NC evo.
Most of the time my NC is used for fault finding and servicing. Just thought this might be a handy tool when driving the truck in hard going.

djam1
22nd August 2011, 05:35 PM
Mine is exactly the same

greg-g
22nd August 2011, 07:09 PM
Mine works fine, it was initially set at 95 and I took a while to work out what was going on as I didn't realise it existed. It's now set at 100 as it was sounding on long hills at 97. It's probably a bit high, but the computer controlled main temperature gauge doesn't move at 97.

Sandlover
23rd August 2011, 08:54 PM
Ok. So there are no other settings, other than the value itself and then drive.
Do you have a setting to turn it on.

bell1975
25th August 2011, 05:21 PM
Ok. So there are no other settings, other than the value itself and then drive.
Do you have a setting to turn it on.

Based on the quick look I've had at mine this arvo it's always on. Perhaps a value of '0' might disable it?

djam1
25th August 2011, 05:37 PM
Mine has been set at 102 and 89 and it still doesnt go off so it is disabled already lol

Sandlover
25th August 2011, 10:10 PM
Yep. Reakon this is one of the features on the evo that is off regardless of the settings. Drove around today with it set at 50 and no alarms went off. Not even a chirp.

The other thing that happens if you play with the temp setting is it will crash after changing the temp with the engine running.

Oh well. Good job most of the other bits work. hang on, no error codes loggEd on the landie today. That can't be right .........:D

bell1975
11th September 2011, 07:49 PM
Mine works fine, it was initially set at 95 and I took a while to work out what was going on as I didn't realise it existed. It's now set at 100 as it was sounding on long hills at 97. It's probably a bit high, but the computer controlled main temperature gauge doesn't move at 97.

I'd love to know why yours works Greg and there are others, including mine, that don't.

I can't think of any other settings that are able to be adjusted with the Nanocom that could assist either.

I'm unsure if Colin is watching this thread - if he is maybe he can pass the issue onto his technical team for some investigation? I'll probably send them a link to this thread in the coming week and log it as a job anyway as it would be quite useful to know that it is functioning (until I can convince the wife the Disco needs the new EMS2...).

greg-g
11th September 2011, 08:28 PM
I probably should correct my initial comment and it's been a while since its activated. It doesn't actually sound, all that happens is in instrument mode all readings are replaced by a screen with a big red cross. At first I thought the device was faulty but then realised it was overtemperature.
I'll have a play and get back.

davrac
11th September 2011, 08:51 PM
Hi All

I hope these Nanocoms are worth their money:)

I just forked out the half a grand to get my own today.:(

Can't wait until it arrives though. Will have a good excuse to disapear to the shed for a while:D

bell1975
11th September 2011, 09:15 PM
I probably should correct my initial comment and it's been a while since its activated. It doesn't actually sound, all that happens is in instrument mode all readings are replaced by a screen with a big red cross. At first I thought the device was faulty but then realised it was overtemperature.
I'll have a play and get back.

Excellent, thanks for having a look for us. It's much appreciated.


Hi All

I hope these Nanocoms are worth their money:)

I just forked out the half a grand to get my own today.:(

Can't wait until it arrives though. Will have a good excuse to disapear to the shed for a while:D

I doubt very much that you'll be disappointed.
The range of things that can be done with this device is truly amazing for the outlay.

If, like me, there is no LR dealer, even an independent, within 3 hours' drive this device can save you a heap of time and dollars troubleshooting issues your car may have.

Today I programmed a second key that had lost its association with the vehicle, turned off Single Point Entry (SPE within the Valeo BCU menu) so that all of the doors unlock with one button press, reset the EKA access code, and last week I reset the Auto's Adaptive Values that it had learned as the previous owner used to tow with it. All that in just an hour or so.

Admittedly the lack of documentation that comes with the device can make it frustrating to use. I have decided that it is worth revisiting the relevant sections in the Workshop Manual/RAVE cd in order to learn a bit more about the functions of the various ECUs in the vehicle.

If you haven't got the cd yet I can't recommend it highly enough.

One day we'll get a thread started that is a "How do I make the Nanocom do this?" affair. For example, I tried t fumble my way through the key fob programming without any reference to the literature on the web - unsuccessfully. After looking on a forum this morning I had a step-by-step breakdown of how to do it and it was actually pretty easy once the steps are done in the correct sequence.

Feel free to PM with any queries but bear in mind that there are now large numbers of Nanocoms out there in use so the collective wisdom of the forum will probably get you answers in a more speedy fashion.

Tomorrow I plan to meddle with the shift interlock as I have no idea what it's about....best to look on RAVE first!

greg-g
13th September 2011, 06:56 PM
Some photos from the temperature alarm.
When activated in instrument mode there is a quiet buzzer and the below screen display.
The alarm setting is accessed from settings frame in the 5th window. Move the cursor to the end with your finger and use the delete? button to delete the old setting and type in a new value.
Save the setting using disk symbol

https://www.aulro.com/afvb/images/imported/2011/09/766.jpg
https://www.aulro.com/afvb/images/imported/2011/09/767.jpg
https://www.aulro.com/afvb/images/imported/2011/09/768.jpg

djam1
13th September 2011, 07:47 PM
Thanks for the info but mine still doesnt work

LOVEMYRANGIE
13th September 2011, 09:33 PM
There is a kernel upgrade for the Evo1 and 2 available now. For the Evo1 owners, make sure you do the file copy first as per instructions then apply the update.

Go to the downloads section and login with your details.

Andrew

Using Capitals, the difference between helping your Uncle Jack off a horse or helping your uncle jack off a horse...

BBS Guy
14th September 2011, 03:36 AM
Hiya Guys

Only just noticed this thread.
So i apologize to be a bit slow in responding. But those in the know will appreciate we certainly have our hands full here with quite a lot of other stuff

The over temperature warning feature was not implimented or developed after BBS got involved with the Nanocom, so we have little to no practical knowledge of it's code or implimentation.

But unlike our countries government, who are currently playing the blame game on who was stupid enough to place 98 shipping containers full of decaying explosives right next to our countries main power station, which ultimately destroyed it, killing many, along with any possible chance of surviving the current economic recession.
:wasntme:

I prefer to take a leaf out of Obamas book and state that if anyone needs someone to blame, feel free blame me, as ultimately the buck stops here. :angel:

You gotta apreciate that guy sometimes.

So the bottom line is, whan does this feature work and when does it not.
We don't need moaning, as this is as much your product as mine and we all want the same result.

So we need clear facts and information.

I am thinking that it is likely that the same problem that affects Live Data gathering on the BBS V1.00 and is now fixed on BBSV1.01 might affect the temperature reading on which the over temperature alarm function is likely also based.

Can anyone confirm or dispute this theory ?

bell1975
14th September 2011, 07:48 AM
On my Evo 2 pre-firmware update the over-temperature alarm failed to trigger at 50, 75 and 95 degrees.

After the update I drove with the same 3 values entered and it still failed to trigger.

IIRC the tyre coefficient has not been changed from the default of 1.010.

djam1
14th September 2011, 10:09 AM
Colin to quote you

"So the bottom line is, whan does this feature work and when does it not.
We don't need moaning, as this is as much your product as mine and we all want the same result.

So we need clear facts and information.

I am thinking that it is likely that the same problem that affects Live Data gathering on the BBS V1.00 and is now fixed on BBSV1.01 might affect the temperature reading on which the over temperature alarm function is likely also based.

Can anyone confirm or dispute this theory ??"

I just installed the update and the over temp warning doesnt work but the live data is now working fine

Getting close

BBS Guy
14th September 2011, 02:13 PM
the live data is now working fine

Thanks Djam, i wanted to test that a lot more before release but our re location made that almost impossible, but at least we are getting somewhere.

So as you already asked the million dollar question bell1975, why does Gregs work and not yours or others.

I will have it tested and looked at, but its a bit hard on the bench with no engine attached, i will have to hook up a variable resistor in place of the sensor, so it wont be a quick one.

LOVEMYRANGIE
14th September 2011, 03:23 PM
Just one other thing with instrument mode Colin, the boost display now only shows one decimal point, not two as it originally did.
I am (was) using this as I'm fine-tuning my overboost setting after getting a remap for it, now I can't see accurately enough what the figure is for fine tuning. It makes it hard to see where in the 1.3-1.4 bar range you are beit 1.42b is overboost cutout.

Cheers

Andrew

Using Capitals, the difference between helping your Uncle Jack off a horse or helping your uncle jack off a horse...

Sandlover
14th September 2011, 08:40 PM
I have just upgraded my evo software with the kernel upgrade released a few days ago. I will go for a drive tomorrow and see if the alarm works now.

I don't get any functionality at present not even the red cross reported earlier.

bell1975
15th September 2011, 11:01 AM
I'll keep watching this thread but also plan to start a "Nanocom Evolution Bug Report and Wishlist" Thread in this section.

BBS can use it for checking what additional features their customers want it will also build up a body of information regarding the issues that people are having with their units. (I'm yet to try and register at the BBS support forums - if they have a similar thread there we can cross-link it to here)

I've not been able to find a similar thread but if a Mod wants to merge it with something that already exists that'd be great.

Sandlover
15th September 2011, 10:14 PM
Ok. So did my test today with the temp set at 87. No alarm or warning messages appeared despite temp climbing to 92.

All other functions of the nanocom did work though and twas able to change from aplications without the unit freezing like it did pre upgrade.

Overall happy with the unit and I am sure Colin will get the few bugs fixed in time.

BBS Guy
16th September 2011, 01:59 AM
Hiya guys

We are indeed very much on the case with the problems reported here and so a big thanks to all for raising our awareness of them.

The first thing we have to do for any reported problem is confirm it and replicate it here, preferably on the bench, which can make it quite difficult sometimes especially where some have a problem and some don't. After all we can't really fix something we can't see.

However today we managed to test the Over Temperature Warning feature and had it working on the older software but not on the newer versions, so now we have a definitive situation we can use to test, find and fix it.

We also discovered the loss of a second digit on the boost occurring at the same software update time.

So things are really looking very good and we should have these wrinkles ironed out in a jiffy. ;)

Bell1975:
Sadly, we do not have a nanocom forum or even a sub section of our BBS one. When i first took on the Nanocom, i did briefly consider this, but for a large number of very good reasons, i ultimately had to can the idea.

So your "Nanocom Evolution Bug Report and Wishlist" Thread sounds like a great idea, and you can certainly count on me to participate and support it as best i can.

greg-g
17th September 2011, 05:18 PM
Just to confirm BBS Guy's observations.
My temperature alarm used to work before the evo upgrade, but doesn't after.

LOVEMYRANGIE
19th September 2011, 11:24 PM
Just another thing I picked up on the same screen, the tyre co-efficient is now not working either.
A rate of 1.05 dropped the actual speed by 3-4kmh. It now shows the same as the speedo at 1.00, 1.05 and 1.10:1 ratios that I've tested.

Using Capitals, the difference between helping your Uncle Jack off a horse or helping your uncle jack off a horse...

BBS Guy
20th September 2011, 12:49 AM
Thanks LOVEMYRANGIE, i will put it on the list of things to check after we fix the Temperature Alarm.

I say this because when things like this were working and now are not, especially when they have not individually been changed, it is almost always some common thing, as it is good code efficient practice to make things modular and re used, like a hex to decimal conversion routine, so it will likely all be automatically fixed even if you concentrate on figuring out why one thing has stopped working and trace the problem to a module change that was likely made to expand it to also do some new variation for the added systems.

eg, I imagine that the Temperature alarm problem is related to the loss of resolution on the Boost pressure and so on.