Thread: Nanocom One update to 2.06

Try this....

http://www.aulro.com/afvb/attachment...re-upgrade.pdf

I've also got a programmer, (It didn't come with instructions) but alas no Version 2.06 software yet.

Hiya Guys

At last the day has finally arrived and the V2.06 upgrade for nanocom one's is now released and availaible for download on the Nanocom.it site. We have also posted up some instruction documentation too

A few extra fixes got squeezed in at the last minute, but some got left out for the next upgrade.

Most notably we have identified a significant problem that may affect some regarding the BCU settings doing odd things when you change just one setting with the nanocom and affecting other settings.

Clearly we have a long way to go to get the Nanocom totally up to BBS standards but V2.06 is a very good start.

Colin,

Thanks for getting this update out.

If anyone needing the update installed is within "dropping by" distance of Brunswick West, drop me a PM and we can work something out. It's a pretty quick process and only takes 5 minutes to do.

Can I put in a few of feature requests for 2.07?
- The ability to record "inputs general" in the Auto Box module would be useful.
- The other thing that would be really handy is some means of converting the recorded files to csv for modules other than fuelling.
- Ability to read/write VIN in SLABS module (which I think may be required for exchanging units between vehicles?)

cheers
Paul

I have downloaded the 2.06 update and instructions, extracted the files and attempted to update my USB type Nanocom on two different computers following the software upgrade manual (instructions). Both computers "see" the programmer on the USB connection (installed and ready for use). The device manager HID compliant device properties indicates the device is working properly (it is enabled). The programmer power led comes on and it is connected to the correct pins on the nanocom, however when I run NCUK.exe (USB version) I get the status message "NCUK programmer not found"

Anyone else having this problem?
Maybe I have a faulty programmer?

No worries Paul, it was getting a bit overdue and put off. So i was determined to get it out before this weekend.

I will put your feature requests on the list, but we have a lot on our plate at the moment, not least of all still a fair bit of settling in, and this problem with the BCU settings is quite significant and affects the EVO's too, so it has to take priority.

gazk, as per my reply to your PM, the probem looks like nothing more than one of my guys neglecting to program your Programmer with the custom firmware it requires before shipping it. I have sent you the info to fix this.