PDA

View Full Version : Updated Nanocom Evo and now issues?



gavinwibrow
7th June 2017, 02:11 PM
Well 2 years on, I finally updated the Nanocom to the latest version (not that I need the CAN/P38 stuff with a D2a TD5)

I hope its only teething issues, but the unit keeps freezing once I finally get it on to Instrument mode.

I tried the standard setup in instrument mode approach (which I had before, along with 180 degree turned display), but it now keeps starting up in the main page once I press the screen. I also thought there had been an enhancement so it would now start up automatically once ignition was on, but no, I still have to press the screen.

So should I go back to my previous version, or retry loading the latest or ? Haven't tried to clear any faults yet, just in case I get some good alternate info from the wise here first. Wasn't planning on even going to test the other new replacement after stolen Evo (LSE converted to almost defacto D2 TD5) until this one is resolved. But that is an option ie try No 2 on the D2a.

Ladies and Gentlemen of the jury - your thoughts?
Cheers Gavin

gavinwibrow
15th June 2017, 12:47 PM
Well 2 years on, I finally updated the Nanocom to the latest version (not that I need the CAN/P38 stuff with a D2a TD5)

I hope its only teething issues, but the unit keeps freezing once I finally get it on to Instrument mode.

I tried the standard setup in instrument mode approach (which I had before, along with 180 degree turned display), but it now keeps starting up in the main page once I press the screen. I also thought there had been an enhancement so it would now start up automatically once ignition was on, but no, I still have to press the screen.

So should I go back to my previous version, or retry loading the latest or ? Haven't tried to clear any faults yet, just in case I get some good alternate info from the wise here first. Wasn't planning on even going to test the other new replacement after stolen Evo (LSE converted to almost defacto D2 TD5) until this one is resolved. But that is an option ie try No 2 on the D2a.

Ladies and Gentlemen of the jury - your thoughts?

Cheers Gavin


Well I woke up and posted there and BBS has answered my question.

Posted below FYI - I'm sure they won't mind.

I'll try this when I find time over the next few days. Having sick grandchildren staying puts a damper on any personal time for projects until late in the night, and only then after all other daily deferred jobs sorted!!!

======

Please redo the firmware upgrade with the Overwrite Target Config selected. That will fix the issue on the Instrument mode.

To start in the Instruments mode, you need to select the option for the startup, once the upgrade will finish.

Indeed, the screen must be pressed, but you can add a small relay on the OBD port that will activate the power with the ignition and when you turn to stage 2, it will power the nanocom, therefore booting it up.

The overwrite target config will reset and reprogram the core, solving most of the issues, also note that the older versions cannot be installed once a newer one is applied.

Kind regards, Adrian

Eevo
15th June 2017, 12:51 PM
that good support from them

gavinwibrow
15th June 2017, 12:57 PM
that good support from them

Yep, once I remembered to check the forum. I've always been impressed with Colin and his crew - they have worked out to keep the few customers with issues supported and the rest will come!

Adrian has been there for years and was very patient when I bought my first Evo, but could not get it to register - yes the dreaded "misread a letter or number in the code" issue!! So what colour is a red face!

gavinwibrow
18th June 2017, 08:05 PM
Update

I have somehow managed to get the new Evo working in the D2 (after I realised that overwirite configuation also means you have to redo your unlock codes, and specials like speedo adjustment for non standard tyres etc), but for the original Evo, it appears there is either a problem with the unlock codes, or ??
Will Have to talk more with BSS.

gavinwibrow
20th June 2017, 02:20 PM
Well, thanks to Adrian at BBS, I now have both Evos working - slight glitch with misreading one letter in the access codes! :bat: