New Nanocom Evolution News

Evo arrived today. 10 minutes from sending the registration email to having unlock codes and clearing ABS faults. Sweet.

Now I KNOW which wheel sensor is being stupid and why I am down on power.

The Body Computer software module is still under development by the looks of it, but there is supposed to be updated firmware comming out on Thursday. Upgrading is a matter of connecting a USB cable and copying the new files to the Evo. Simple as.

Only minor problem is clearance for the USB connector. The hole in the case is a little small, but easily fixed with a file and a phillips screwdriver. I have emailed Matia about it already.

More info to follow once I have the Body Computer firmware. Happy to answer any questions on functionality for anybody thinking of buying one. I am in Northern Adelaide suburbs if anybody wants a peek at one.

Still waiting on mine its been at the depot in melb since 5:30 am. I thought I'd get it today, Hopefully it will be tomorrow.

Quote:

---

Originally Posted by Fluids

It says on the site that the new evolution model will come will all the existing functionality of the current Nanocom 1, and will be VIN free for the Deefer & Disco II Td5 ... it the goes on to say ...

"
and soon there will be new modules:

DISCOII PETROL V8
DISCOII AUTOGEARBOX
DISCOII SRS
These 3 modules will be available also for the NANOCOM series I (COM and USB):

... available for existing Nanocom 1 units!!

YES! Auto gearbox ... hopefully, allowing adjustment of the torque converter lock-up speeds (lowering)

... holds breath ....

Kev..

---

Whenever soon is, it's not soon enough:BigCry:

Can anyone do a OBD port test on there evo I'm getting an error on line 5.:eek:

you can find the test under NANOCOM>SETUP>OBD PORT TEST

Quote:

---

Originally Posted by 999

Can anyone do a OBD port test on there evo I'm getting an error on line 5.:eek:

you can find the test under NANOCOM>SETUP>OBD PORT TEST

---

Mine is the same. Maybe flick Mattia an email ?

Communications seem to work. I wish there was a decent developers reference manual...

Quote:

---

Originally Posted by peter5111

Mine is the same. Maybe flick Mattia an email ?

Communications seem to work. I wish there was a decent developers reference manual...

---

Thanks maybe it's normal. I sent a question from there website regarding #5 line.

Have you created a restore file yet? Was the first thing I did, just in-case.

Here's a few photos of the unit.

https://www.aulro.com/afvb/images/im...010/09/624.jpg

https://www.aulro.com/afvb/images/im...010/09/625.jpg


https://www.aulro.com/afvb/images/im...010/09/626.jpg

The last image is a shot of the EVO backing up the TD5 ECU MAP to a sd card.

Sorry about the picture quality but hey its a phone.

Restore files were priority 1. Last thing I need to do is brick it.

I also made a raw backup of the complete file system. Did you have any issues with USB connector clearance ?

Can't believe how slow the file transfer was though. It is like the SD card is hanging off the end of a 56k modem.

First few items on my wish list is to be able to configure the Instrument display to show the half dozen readings I happen to care about and not the ones Mattia thinks are important. Having to flick between screens is a bit annoying.

Next on the wish list is logging of fuel flow. Integrated with time / distance etc gives a trip computer with pretty good accuracy. I used it al the time when I had the ScanGaugeII.

And finally (on the preliminary list anyway ;) ) is info on the external connector and some way to stream data too / from the connector

I got a reply from Mattia about the OBD port tests (talk about a fast response)

Quote:

---

Hi,
The OBD port test has the pourpose to test the unit without the car. it send 10 bytes to the line OBD and it check if they get back. the OBD K lines are 1 wire so data sent can be also read. It is normal that the line 5 get error because this is a 2 wire line so to test it you have to short circuit 2 wire (the 11 and the 12)to allow the data sent to loop back.It is used in the air suspension of the P38.For discovery and Defender the line used are the 7 and the 8.

Regards
Mattia

---

So no need to worry:D

Quote:

---

Originally Posted by peter5111

Restore files were priority 1. Last thing I need to do is brick it.

I also made a raw backup of the complete file system. Did you have any issues with USB connector clearance ?

Can't believe how slow the file transfer was though. It is like the SD card is hanging off the end of a 56k modem.

First few items on my wish list is to be able to configure the Instrument display to show the half dozen readings I happen to care about and not the ones Mattia thinks are important. Having to flick between screens is a bit annoying.

Next on the wish list is logging of fuel flow. Integrated with time / distance etc gives a trip computer with pretty good accuracy. I used it al the time when I had the ScanGaugeII.

And finally (on the preliminary list anyway ;) ) is info on the external connector and some way to stream data too / from the connector

---

This is all very interesting and I now wonder if a small laptop computer can be connected up to, or via the unit to facilitate using a larger screen than that of the nanocom itself? :)

Quote:

---

Originally Posted by mildred

This is all very interesting and I now wonder if a small laptop computer can be connected up to, or via the unit to facilitate using a larger screen than that of the nanocom itself? :)

---

As far as I can tell, not easily. But I have not had a close look at the layout yet. The USB connector gives direct access to the file system on ( I think) a watchdog processor that holds the .hex files for all the other micro's. So firmware upgrades a a cinch.

There does not appear to be an easy way to talk directly to the micro that handles the display and touch screen.