Nanocom evo problem

[acgmarketing]

Hi all. I decided to upgrade from the old Nanocom to the new Evolution (metal) version. Buying and importing were just fantastic. Very quick service and very quick delivery and no importation issues at all. I plugged it in and it worked a dream with only minimal delay between screens as I cycled through. Then yesterday it suddenly (I had it working well for 3 days before then just plugging it in before a drive and monitoring live autobox data as I drove), took a long time to boot up (as in a few minutes) and a long time to switch screens (like again a few minutes from a selection to showing the screen). It also reports failure to communication with ECU when I try to read any ECU - even just engine faults (yes engine is running!!).

Support service has been good and suggests I reload the firmware to check out that being an problem. I am now trying to do that.

I have got the firmware file (latest). I have unzipped it. I have connected the Nanocom by USB to the computer and it has allowed me to enter the Kernal mode (it's screen says it is entering the kernel mode and then goes blank as expected). The problem is that the kernel update manager program on the PC will not report that the Nanocom is connected and so I can't start the process. I have tried a few different USB ports and now two different computers (both windows 7). Any one got some clues for me???

[acgmarketing]

Anyone had experience with a Nanocom Evo failing to be recognized by a PC by USB? I'm having trouble getting any PC to recognise the Nanocom. Due to some issues I've experienced in the first few days of owning my new shiny, nanocom advice has been to reinstall the firmware. I've had no problems getting the unit into the kernel manager/update mode but the PC kernel manager program just will not switch to recognizing the nanocom is attached so I can update. Nanocom support now tell me it is the PC not the nanocom. However, having tried on 3 computers, a range of USB ports and a couple of cables (known working), I have trouble accepting the diagnosis. Anyone had thus experience or know the tricks?

[OffTrack]

Have you had a look in System > Hardware > Device Manager (I'm running XP so you'll have to excuse me if that isn't correct on later versions) to see if the Nanocom is actually being recognised by the computer?

cheers
Paul

[justfishing]

Hello,
I know it sounds silly but is your SD card still installed ?
Usually I download update, open and run the Kernel Manager then once the program is running then I plug in my Evo to the laptop after couple of seconds it sees the EVO and push update. If I plug the Evo before it doesn't see it I am running Windows 7. With my laptop with no SD card in the Evo my laptop doesn't see either, once running Kernel Manager no problems hope this helps..............
Ian

[acgmarketing]

Just fishing, no there is no SD card installed. I followed the instructions on the installation PDF very carefully and no luck. I've now tried pulling out the mini USB cable when the unit powers down after showing "kernel bootloader activated" (the words stay on screen for about 40 seconds before the screen goes blank) and putting it back in as another forum suggests doing that a few times can eventually trigger the Nanocom to become attached to the PC. Nope no good either. Do you recall for yours how long the "kernel bootloader activated" message stays visible on the screen before the PC recognises the unit?

OffTrack, yep I've looked there and there is no record or any indication of the Nanocom being connected in any of the 3 PCs, in any of their USB slots or using any of 3 cables I've now tried.

Going slowly mad with a diagnosis of the PC being the problem despite these experiences. Any other clues? RMA is being arranged but I really don't like sending the device back for fixing when I've been advised that it is the PC despite this experience and being told that the fix will likely be a charged fix - I only had the thing for 3 days before it stopped working! (my Nanocom One unit I should point out has been working strong now for what must be about 5 years in the same car and is back in there after a 3 day holiday while I looked to see if the Evo was worth keeping and sell the One. I don't think it's anything the car has been doing either as the One plugged straight in and worked as normal.)

[acgmarketing]

A quick update. Last night I tried putting in an SD card (first time it has had one in) and then connected by USB (again using multiple different USB leads and computers and ports). Every time the Nanocom happily went to the USB storage display screen (showing an image of a SD card on its screen) but every time the computers failed to recognise it as a storage device. Does this continue to suggest it is the PC(s) which are the problem. I'm only continuing to ask here because I've now got the RMA for a return and it states that the service support will give advice to allow tring of every possible option for the customer to get it working before issuing an RMA thus I figure it is only fair that I do as much noninvasive testing at my end also before acting on the RMA. Any clues out there?

[justfishing]

Hello,
You must be going nuts..... Sorry I cannot hook up my Evo as on a mine site for the next 3 weeks. Just a couple of things you might have tried already but here they are.
Did you try downloading the firmware and unzipping it more than once ? Maybe straight to the desktop. It might take a couple of times... It might not have any bearing but
Windows 7 has a few problems and some things do not work depends on you machine as downloading map.files I do have a few problems with them takes a couple of times to work.
Have you tried a different Evo on your computer ?
I use win RAR to unzip.
I did read some where you can remove the end of the Evo and reset it cannot remember where.
Hope you get it sorted out......
Ian

[acgmarketing]

Thanks Ian. I have tried downloading the firmware manager twice now but not to the desktop. I'll try it again and use win RAR this time to unzip. Yes in one of the user manuals (I think the online version which explains how to upload the firmware), it refers to using either the hardware or software method of upgrading. I looked briefly at the hardware method but that seems simply a mechanism to cause the Nanocom to go into Kernel mode which would be used instead of powering up by USB and selecting the kernel mode. My suggests it is going into Kernel mode (just not seen by the computer) so I don't want to open it to use the hardware method in case that then is suggested later to be the reason for the malfunction. I'll try downloading again tonight. Craig

[clubagreenie]

I did the upgrade by adding the update files to the SD card and then running locally on the Evo itself.

My issues are it works fine in any mode apart from where I want it to work, instruments. Just randomly shuts down or freezes. I'm also reticent to return it at the cost of postage for something I may end up paying to fix thats been happening from day one (but they won't acknowledge apart from "do you want a RMA?")

[justfishing]

Hello,
That was a good idea to do it that way, sorry to hear that your Evo is not doing what it should.
PM sent.
Ian

[acgmarketing]

Can you tell me how you managed it that way? I know you can create a recovery or backup version to SD at the end of installing firmware via the kernel manager and then can use that to reset it later if there are problems (why not sell it with an SD card complete with a firmware backup????) but I've not heard how else it can be done via an SD card.

[jabber]

I had similar issues, but mine turned out to be the hardware.

Have you tried switching the NanocomEvoKernelManager.exe to XP compatibility mode?

- right click the executable, click on properties
- click "compatibility" tab
- set to XP

This may help the software in recognizing the Evo.

I also found, within Windows XP; you need to install Microsoft's .NET support/software to run the Kernel Manager.

[acgmarketing]

Hi Jabber. I'm running windows 7. Did you run in comparability mode for running on windows 7 or windows XP? Cheers and thanks for the idea.

[jabber]

For win 7.

Xp works well once .Net is installed.

[acgmarketing]

Ta Jabber, I'll give it a go this morning.

Craig

[towe0609]

I did the firmware upgrade on my evo last night using Windows 7 without any of the problems you are expriencing. Sorry to hear you are having trouble, and hope you work it out. I don't have any advice for you sorry, just the experience that tells you it is possible!

[acgmarketing]

Thanks towe - I'm sure it can be done. Just that I've been advised that it is my computer (4 now) that are causing the problem rather than the unit itself so I'm trying any possible software solution before sending it back. I tried on my fathers computer last night using a fresh download of the 1.12 from the website on an XP running machine - no good. I also tried my 1.12 in XP compatability mode - no good (all on different cables and different USB sockets and with all other non-essential USB devices unplugged. This morning I tried a version of the 1.11 manager and firmware and again no good. It always opens the manager on the PC, always (eventually with much slowness) gets to the screen on the Nanocom where it has a one line of text saying it is in kernel mode but has NEVER changed the "device not attached" message in the manager thus I can not start the upload.
Clubagreenie has the only lead I I think I have left now - save files to an SD and run on Nanocom itself. Anyone know which files from the firmware upload need to be saved to what directory on a how big SD card formated to what format to try that one? (My Nanocom won't even operate as a file storage device connected to a PC by cable with an SD card in it so I'll have to put the SD card in a card reader to transfer files to it).

[clubagreenie]

There's a limit (<8gig) currently I think as there's a new update by the look of it that allows 8-16gig cards to be used.

I'm using a 2gig micro card in an adaptor left over from a phone.

[OffTrack]

There's a limit (<8gig) currently I think as there's a new update by the look of it that allows 8-16gig cards to be used.

I'm using a 2gig micro card in an adaptor left over from a phone.

8Gb is the maximum. Nothing in recent updates has changed that afaik.

My 8gb sdcard fell apart at the seams recently. Now using a 2Gb micro card in an adaptor - $6-8 from the local supermarket is a bargain when nothing else is open. The only compelling reason to use a card larger than 2Gb is lack of availability of 2Gb sdcards.

cheers
Paul

[OffTrack]

Clubagreenie has the only lead I I think I have left now - save files to an SD and run on Nanocom itself. Anyone know which files from the firmware upload need to be saved to what directory on a how big SD card formated to what format to try that one? (My Nanocom won't even operate as a file storage device connected to a PC by cable with an SD card in it so I'll have to put the SD card in a card reader to transfer files to it).

You can only restore a rescue version of your current firmware version from SDCard. You can't restore to previous versions, or use this method to upgrade. The ONLY way to do the upgrade is using the firmware installer app.

cheers
Paul

[clubagreenie]

I don't recall using an app but could be wrong.

Happened once back in '72, when I decided to be conceived.

[acgmarketing]

I'm not trying to upgrade just reinstall current firmware on advice of BBS support that it might solve the "very slow running" problem I've got. I've got the 1.12 firmware on the Evo and trying to reinstall the same. Anyhow I've tried all options so far presented (thanks all for the input so far) with no luck. I think all I have left before returning is to see if any one in Brisbane has an Evo with firmware 1.12 which they have put on an SD for future restoring which I could come and try in my Evo. I did manage to navigate to the restore section on the Evo but of course my 2Gb SD card had no files saved to it but it did successfully report no files found. Anyone in Brisbane got a 1.12 backup available? Or interstate, I could post an SD card to you, you copy over the SD files and post back.

[goingbush]

I'm not trying to upgrade just reinstall current firmware on advice of BBS support that it might solve the "very slow running" problem I've got.

I had that very slow running fault on mine, sometimes a minuite or so between screens, sent it back using RMA process and it was fixed under warranty, about 6 months ago

[acgmarketing]

Thanks for that one Goingbush. I know that the BBS guys watch this forum and in fact made the comment in the email for which I received an RMA that I might yet find a solution which I'm happy with on this forum and that sending it for the RMA may end up costing me. Now that I see on this forum that a member has had the same slow running problem and had it fixed under warranty (which matches other stories in other locations) and I know that BBS will have seen that response I'm more comfortable in sending it back overseas expecting it is a hardware fault not software with my PC has I have been told a couple of times by BBS support.

Unless anyone has an SD with 1.12 firmware which I can borrow to copy to mine and try to install directly from the Evo or an Evo in Brisbane to which I can bring an SD card to create a backup on my SD card I guess I'll now be sending it back for repair and point out the similar experience you have had.

Anyone with an SD backup of 1.12 firmware or an with 1.12 firmware Evo in Brisbane (northwest better but I can travel) I can visit to try?

[goingbush]

the slow running fault on mine was in the hardware, a firmware update at the time didnt fix it.


edit:
time flies, it was longer ago than I thought, heres my original post asking about same issue
http://www.aulro.com/afvb/electronic-diagnostic-systems/139250-nanocom-evo-faulty.html

the ghost faults that I mentioned it picked up in that post were from the Tombie remap, they have only just disappeared now that I've got a new Td5-Inside remap.

[clubagreenie]

My issues of freezing or shutting down have been relieved somewhat by using a memory card (2gig micro SD in adaptor). But it still will do it if setup in the settings to boot into instrument mode directly. Also if it's left unplugged and not used for a few days it runs better than if it's been used continually for a few days straight. Like its memory is full or something and leaving it unplugged and unpowered clears it. Which kind of correlates to adding the memory card.

But in the last few days it's been freezing with a message about ECU communications failure and turns itself off. Which doesn't make sense as it still has power (its still on) but theres a fault in another wire?

[djam1]

Not sure if it helps anyone but I have learn't a bit with my Nanocom's Nanocom 1 was used as an instrument for a while due to the placement in the car it often got very hot. The end result it trashed many ECUs when trying to write maps even with the new firmware. I got fed up and it was cheaper for me to buy a new one than send mine back to Cyprus. Colin was very generous with his discount when I purchased the new one the new one has been perfect. Consistently writing maps without any issues at all. Lesson 1 don't let your Nanocom get too hot