New Nanocom Evolution News

Printable View

Show 40 post(s) from this thread on one page

22nd March 2011, 02:55 PM
Basil135

Well, I am now on my second SD card, as the Kingston that I was using kept coming up with an error.

Paul, could you give a basic run-down on how to do the backup of the files?

This is the sort of information that I expected to read in the comprehensive user manual that came with the unit....:eek:

Even a $40 DVD player comes with a multi page manual....:mad:
22nd March 2011, 04:58 PM
Mellow Yellow

If you've downloaded the Nanocom Evolution Quick Reference Guide from the Nanocom website it's set out on page 4.

The only thing with Page 4 is that the paragraphs are out of sequence. That is, before creating a restore file you've got to format your SD card but this paragraph is the second of the two relevant paragraphs.

With my SD card, I didn't format it in the Evo, I used a card reader as my PC runs Windows 7 64 bit which can be temperamental when you plug uncommon things into it.

After formatting your SD card, if you go to the "Restoring file creation" paragraph in the Quick Reference Guide and the screens it points you at, you'll find the process quite straightforward.
22nd March 2011, 10:24 PM
PaulP38a
Quote:

Originally Posted by brookvale

Thanks for these tidbits Paul.
Is there a 'correct' folder structure and file content list for the firmware somewhere for us to compare our own systems with?
I'd be trying to do this now but my Evo is sitting here in a courier box waiting to fly to Cyprus.

If you remove the SD card and plug the Evo in to your PC via the USB cable, the NC_FIRMWARE flash disk should mount as a new drive and have the following files:
APPMAN.app
AS10.app
DEFABS.app
DISCOACE.app
FILEMAN.app
MAINEXEC.mex
MAINMENU.cfg
NCSET.app
SLABS.app
TD5ENG.app
TD5ENG.BIN
TD5INST.app
TD5MAP.app
TXTEDIT.app
VALBCU.app
VALBCU.bin
PUMAENG.app
PUMAIPC.app
PUMAINST.app

In addition to these files is a folder called CFG containing:
NANOCOM.CFG
TD5INST.CFG
UNLOCK.TXT
PUMAINST.CFG

if you now dimount/eject the NC_FIRMWARE drive (via Windows "safely remove hardware"), disconnect the USB cable, insert the SD card in to the Evo and then reconnect the USB cable, a drive will mount again. This may or may not have a volume name... I called mine EVO-SD.

If you have done a backup there should be a folder on the SD card called NCRF containing a RESTORE.BIN file.

BTW: after restoring the Evo last night, I subsequently found that all of the SD cards I had worked fine.

Quote:

Originally Posted by Basil135

Paul, could you give a basic run-down on how to do the backup of the files?

This is the sort of information that I expected to read in the comprehensive user manual that came with the unit....:eek:

As Mellow Yellow suggested, the manual is available at http://web.nanocom.it/download/NANOC...NCE%20R1.0.pdf
or a copy that may be less confusing to some web browsers at http://hardrange.com/downloads/manua...ickRefR1.0.pdf

Basic steps are:
1. have the SD card inserted in the Evo
2. boot the Evo
3. from the main menu select the NANOCOM item
4. select SETUP
5. scroll to the last item RESTORING FILE
6. select CREATE RESTORING FILE
7. watch the green bar fill left to right. You should get a Restoring file created message when it is done.
Hopefully BBS will fix the English menus (and manual) in a future software update... all credit to Mattia though, his English is much better than my Italian ;)

Cheers, Paul.
23rd March 2011, 07:02 AM
Basil135

Thanks Paul.

Very much appreciated.
23rd March 2011, 07:05 AM
disco_thrasher

Gee looks like these evo are causing alot of troubles :(
23rd March 2011, 09:58 AM
LOVEMYRANGIE

Paul, mine will be coming back to you via mail. Screen still blanks when you power up. Backlight comes on and it beeps but nothing else.

Cheers

Andrew

Sent from my backyard TeePee using smoke signals.
23rd March 2011, 10:35 AM
peter5111

Quote:

Originally Posted by disco_thrasher

Gee looks like these evo are causing alot of troubles :(

You could say the same thing about the TD5 engine. ;)

It is just a new tool that folks aren't used to using. I think the biggest factor that makes it look really problematic right now is there are 23 ish brand new Evo's that have all hit the street at exactly the same time.

So there are 23 owners all learning the same things at the same time.

Personally I think it is great to see the issues being aired in public - that is the only way to build up a knowledge base. And in true Landrover owner form we seem tell the story warts and all. :angel:
23rd March 2011, 05:34 PM
999

Just checked the SD card in mine it's sandisk microSD 2GB with a microSD to SD adapter.:)
23rd March 2011, 07:13 PM
brookvale

Quote:

Originally Posted by peter5111

You could say the same thing about the TD5 engine. ;)

It is just a new tool that folks aren't used to using. I think the biggest factor that makes it look really problematic right now is there are 23 ish brand new Evo's that have all hit the street at exactly the same time.

So there are 23 owners all learning the same things at the same time.

Sorry, not so right sir (polite).
The Evo user guide does not say "make sure the SD card is inserted in the unit before powering up or connecting/plugging into the OBD port... "
Almost like the LR book for Td5 vehicles forgot to say "make sure you have oil in the sump before trying to start your engine".

These are fundamentals which, if critical, must be told for users of a device which appears, on the surface to have a standard style USB connection, but has actually has issues when it should/should not have the card plugged in.

I think the Evo software person wrote the user guide themselves rather than having a real user try them out and reporting back - they did not remember that we would treat the Evo as 'card reader' and plug/unplug the card in at anytime we fancy (as it should be)

And it seems peculiar that User A has no problems with an Acme Cheapo SD card but User B with a 'high spec, reliable' Sandisk one, does.

Odds seem to be stacking up that the quality control is lacking somewhere with the hardware or the software's implementation.

One weeks' testing by an ordinary LR owner would have surely picked up these issues before the unit went on the market.
Neil
23rd March 2011, 08:22 PM
peter5111

Apologies if I came across a little flippant. The comment was intended to be a light hearted observation. I have been using one of Mattia's original batch of Evo's now since September last year and it has been rock solid for me.

Having said that, I have caused SD card issues on my Evo recently but only by doing things that after 20 years of working with computers of all shapes and sizes from mainframes to and micro controllers, are totally unnatural to me and used to be for all computer owners up until ~Windows XP era. (like pulling out an SD card while it is in use). The code needs to be made more robust. Putting a warning in the documents is only a temporary measure.

I DO agree that the Evo has been prematurely released on an unsuspecting user base with an unacceptable lack of Beta testing and woeful documentation.

Hopefully BBS are paying attention and will roll all the good suggestions here into a revision of the manuals and a decent Beta testing program. The Evo has too much potential to ruin it's name by releasing a half baked product.

I have no connection to Mattia or BBS but I do believe in the potential of the Evo. I have put a stack of time into helping new users both in the forum and in private, and I will continue to give whatever help I can.

As I have mentioned previously, we are rapidly building a decent base of knowledge and knowledgeable users. I think we need to start a good-oil thread with links to the important stuff in this and other Evo threads.

Regards,
Pete

Show 40 post(s) from this thread on one page