Nanocom (Evolution) Bug Report and Wishlist

**bell1975** · 16th October 2011, 11:11 AM

Originally Posted by BBS Guy

Bit of a worrying mystery so far bell1975.
And of course have been there behind the scenes discussing this with Ron. In fact just before we closed, i sent you an E-mail with some suggestions and a link to a restore file, as since we fixed this in V1.01 you should now be able to use.

Cheers Colin, it's worked for me now. Many thanks again for troubleshooting this for me on your weekend too.

What are you like with electronic washing machines?

I forgot to add: it seemed to want the "Overwrite Settings" option to be checked. Otherwise it failed to proceed past "Reading...".

**greg-g** · 16th October 2011, 03:00 PM

My upgrade went without a hitch, it's nice to see the turbo boost back at 2 decimal places.

While the temperature alarm is now working, I'm having issues with false ? triggering. My working temperature on highway hills is typically 93 - 94 and I've never seen a stable reading above 95 so the alarm is set to 98, but I'm now getting frequent temperature alarms.
I see two possible issues here, the first is that my readings, especially voltage aren't totally stable. The temperature often jumps by .2 or so, but occasionally by 1 or more degrees for a single reading, then back to the stable value. I suspect this may be due to earthing problems, but other than tightening bolts I haven't tried any other trouble shooting. Any thoughts anyone???.
The other issue is that if it's these spikes that cause the false triggering, then there can't be any signal filtering before peak detection.

**Pedro_The_Swift** · 17th October 2011, 08:47 AM

check the continuity of the cable?

**madtom** · 18th October 2011, 03:28 PM

Hi,
I made the last firmware upgrade of my EVO 1 without any problems, but a friend has now a not working plastic box. He pulled out the USB cable during programming of the new firmware, after cca 5 minutes long stop of programing progress. Now he can use it only as SD card reader. He cannot get any response like pictures on LCD, beeps or response to pressing the touchscreen, also he cannot connect to the fimware disk through USB. Is there a solution how to repair this problem?

**bell1975** · 18th October 2011, 08:23 PM

Originally Posted by madtom

Hi,
I made the last firmware upgrade of my EVO 1 without any problems, but a friend has now a not working plastic box. He pulled out the USB cable during programming of the new firmware, after cca 5 minutes long stop of programing progress. Now he can use it only as SD card reader. He cannot get any response like pictures on LCD, beeps or response to pressing the touchscreen, also he cannot connect to the fimware disk through USB. Is there a solution how to repair this problem?

Best to send an email to the support team at BBS. They'll have a fix for sure. But there may be some other Evo 1 owners along soon with some ideas too.

justfishing · 19th October 2011, 09:32 PM

Hello,
I have updated to the new firmware, but having trouble with the autobox function. Most times when the car is running it cannot commicate with the ECU, then when it does and I exit the screen goes blank and nothing have to pull out the plug and re-start, still having troubles freezing in instapp.TD5
Any one got any advise as to what to do ??
Ian

**bell1975** · 20th October 2011, 03:13 PM

Originally Posted by justfishing

Hello,
I have updated to the new firmware, but having trouble with the autobox function. Most times when the car is running it cannot commicate with the ECU, then when it does and I exit the screen goes blank and nothing have to pull out the plug and re-start, still having troubles freezing in instapp.TD5
Any one got any advise as to what to do ??
Ian

Best to send an email to the support team at BBS.

I have noticed a few random instances of this 'screen freezing' too. This is post-v1.02 update.

I am not getting any values in my "Pressures" section of the Autobox module. They are all 0 apart from one that is 253. It's been quite a few weeks since I reset the "Adaptive Values" on the 'box so I would have thought it would be reading more values in that section by now.

Perhaps someone else can check theirs and compare?

I'd suggest removing the OBDII cable from the OBDII plug rather than removing the cable from the Nanocom as this was what caused mine to short and blew the fuse.

**OffTrack** · 20th October 2011, 04:12 PM

Originally Posted by bell1975

Best to send an email to the support team at BBS. They'll have a fix for sure. But there may be some other Evo 1 owners along soon with some ideas too.

Evo 1 and 2 are the same circuit design. The Evo 2 has a revised layout to make it easier to produce. In other words the Evo 2 is basically an Evo 1 with an improved case design. That's not to diminish the amount of effort BBS have put into repackaging the Evo.

**OffTrack** · 20th October 2011, 04:21 PM

Originally Posted by bell1975

I am not getting any values in my "Pressures" section of the Autobox module. They are all 0 apart from one that is 253. It's been quite a few weeks since I reset the "Adaptive Values" on the 'box so I would have thought it would be reading more values in that section by now.

Perhaps someone else can check theirs and compare?

Same thing on the Nanocom One with v2.07 Firmware. All values read 000 with no change if car is running or stopped.

The main difference between the One and Evo is the way they display data but the underlying module code is basically the same. This is one of the reasons BBS are able to make firmware updates for the Evo and One almost simultaneously.

Unless there is something that is a purely display related issue there is a good chance that it will apply equally to both the One and Evo.

**BBS Guy** · 21st October 2011, 03:22 AM

Bell1975

Cheers Colin, it's worked for me now. Many thanks again for troubleshooting this for me on your weekend too.

You are welcome

Electronic washing machines, errm actually not bad, i recently fixed ours which started to leak. The cause was actually really amazing.
The detergent / soap box that takes the slide in tray has a short overflow stub pipe at the back. A mouse, that obviously had an addiction to soap or maybe wanted to get himself extra clean ;-) could not fit down this pipe so chewed down the lower part of it and then chewed the hole in the box a bit lower so he could fit through it. This caused the leak as the hole was now just slightly below the normal water level. He also chewed through some internal baffles and even enlarged a hole in a plastic grille on the top of the Tray.

it seemed to want the "Overwrite Settings" option to be checked. Otherwise it failed to proceed past "Reading...

Interesting.
I can understand this happening if the NC_Firmware Fat drive contents, notably the Config files were missing or corrupted so not readable, But if this were your only problem the unit would still boot and allow you to re do the upgrade, so clearly you had a problem with the kernal processors firmware.

But as each of the 5 memories in the unit is erased and then replaced in turn by the upgrade process, any interruption in the upgrade process could only leave one memory empty or only partly programmed, not two.

greg-g
The Temp sensor is resistive, giving a varying input voltage which the ECU simply uses an A to D convertor to turn into a Numeric value it stores in RAM. When we diagnostically request the water temperature, we are given this value which we then have to mathematically convert into the temperature. This actually is not that easy as if you plot the temp against the value on a graph you get an "S" curve. The Alarm function is simply comparing the read temperature against the set one and if the temp value given by the ECU equates to a temp above the set limit, the alarm is triggered.

Madtom
I am sorry to hear of your friends problem, It turns out your friend seems to be the very case i mentioned earlier.

Obviously, with two cases being reported so close together, we are quite concerned as to how common this is, however, although we appreciate that many have stated here that they had no upgrading problem, for which i thank them, typically we tend to only hear from anyone who has encountered a problem, giving quite a distorted view as to how common it is. And for sure we would almost certainly hear from anyone who has experienced this kind of a problem

So i checked the Nanocom.it site stats and have discovered that over 100 people have downloaded the V1.02 upgrade
And as the code and process is identical for V1.01, i looked at that and discovered nearly 200 have downloaded that.

However we appreciate that no matter how low the chance of it happening, it is no consolation if it happens to you.

So today we all had a long meeting in my office to discuss any and all possible causes, and came up with a list of things we could possibly improve and implement to hopefully overcome the problem.

Regards ongoing freezing or exit problems.
Clearly we have mostly fixed this from BBS V1.01 by slowing down the access rate, and most reporting this kind of thing on various ECU's are now either in the occasional or more related to a specific vehicle over software issue.
However as these early ECU's can often be problematic, which most can accept and appreciate, and the ECU's can often stop communicating, i think the real problem we now need to sort out and attend to is why the system totally freezes up and effectively crashes, requiring that you need to unplug it, rather than properly handling a simple loss of comms to an ECU with an error box that upon clicking OK to, just returns you to the menu

Regards Pressure values on the Auto box.
It is possible that an error exists in the code for this which as Offtrack notes is re used between Nanocom One's and the Evolution. He is also correct on his EVO1 V EVO2 assessment.

We are checking this out and if a problem exists we will certainly find and fix it as always.
Thanks to all for bringing it to my attention

Thread: Nanocom (Evolution) Bug Report and Wishlist

Thread Tools

Evo2 Autobox mode

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions