New update comming for Nanocom EVO

Hiya clubagreenie

Glad to hear that your adding an external power input is currently showing that this is indeed looking like where your current problem is.

Without any supply connected, the nanocom is not able to run any code and the supply and design is such that it cannot differentiate between OBDII and external supplies.

For those interested in following news about our progress on the CAN BUS coverage we are adding to the Nanocom, we have just released another new video on you tube that demonstrates the Nanocom Evolution being used to Flash a CAN BUS ECU.

[ame="http://www.youtube.com/watch?v=vEUF3zK7JFc"]Flash File Download final - YouTube[/ame]

Speaking too soon.

Still behaving badly sorry to say. Am mounting the video camera inthere to record what it's doing (not that you'll see much except it freeze ot shutdown).

So how are keys programmed on D3? And is this a feature that nanocom will have after the update?

clubagreenie, sorry to hear that, i have been doing some checking and don't hear of anyone else with the same EMS having the same problems, so would you possibly be able to try another EMS ECU ?

Jafir

Quote:

---

So how are keys programmed on D3?

---

Not quite sure exactly what you mean by this question, can you possibly elaborate a little.

Quote:

---

And is this a feature that nanocom will have after the update?

---

Possibly not in the first software update with CAN BUS coverage, as we are struggling to get this released before Christmas this year (2013), but it will certainly be included not long after in subsequent upgrades

We will be producing a document detailing exactly what diagnostic functionality and capabilities are provided in the first upgrade as well as what we intend to add later.

In the meantime, here is another video demonstrating the CCF edit function

[ame=http://www.youtube.com/watch?v=l22oq-A4GnQ]CCF Edit - YouTube[/ame]

Quote:

---

Originally Posted by BBS Guy

Jafir

Not quite sure exactly what you mean by this question, can you possibly elaborate a little.

---

Sorry that was a little vague. I just wasn't sure how they were programmed, if that was part of the CCF or some other routine had to be added. You have successfully answered my question even if I wasn't clear in asking it. :)

Thanks!

Ah now i understand better Jafir ;)

Key programming for CAN BUS vehicle is a specialist function that will require its own dedicated Key Programming app on the Nanocom, which will likely be entitled Key programming and has yet to be added and written. Hence you don't currently see this on the demo videos, But since we already provide this capability on the MSV-2, we are not exactly starting from scratch and re inventing the wheel.

As with all other functionality based apps it will intelligently self detect the vehicle model and provide a number of appropriate options to the user depending on the model.

Colin,

on a completely different subject, would it be at all possible to include a trip computer to the instrument mode for Td5?

I believe a trip computer that would measure fuel consumption (current and average plus some fancy data that are easy to do like average speed etc) is something that many of us miss in Td5 world. Even if this would be a paid update i think many Nanocom Evo users would love to pay for that.

thanks

Peter

Quote:

---

Originally Posted by BBS Guy

Ah now i understand better Jafir ;)

Key programming for CAN BUS vehicle is a specialist function that will require its own dedicated Key Programming app on the Nanocom, which will likely be entitled Key programming and has yet to be added and written. Hence you don't currently see this on the demo videos, But since we already provide this capability on the MSV-2, we are not exactly starting from scratch and re inventing the wheel.

As with all other functionality based apps it will intelligently self detect the vehicle model and provide a number of appropriate options to the user depending on the model.

---

Hiya Peter.

The instrument mode that the nanocom Evolution provides as an additional extension of it's main function of being a Diagnostic tool is pretty much based around it simply keeping constant diagnostic diagnostic communications with the Engine management ECU, which is used to read read and supply live data information from it.

What you propose is something very different and would involve live swapping between communications to different ECU's, collecting data and combining this which is not really realistically that viable to do in real time anyway.

Colin,

no, actually you need two values only. There is no need to swap communication to different ECUs. You need your fuel consumed value (this can be easily derived from injectors open time x fuel constant) and the road speed. I believe both of these are provided by Td5 ECU and can be read via its OBD interface. The calculation of fuel consumption from these two values is a simple maths. I think Nanocom Evo should have more than enough processing power to do this.

Peter