Results 1 to 8 of 8

Thread: Nanocom Reset.

  1. #1
    Join Date
    Aug 2007
    Location
    Mandurah WA
    Posts
    597

    Nanocom Reset.

    The Nanocom Evo has failed to complete its boot up sequence.Plugged into a TD5 D2 it initially got as far as selecting the vehicle then froze.....could not close it down properly so pulled the obd plug.Tried again but only got as far as unlocking codes,then came a quick flashed 'Error ***[OTG?]directory not found' then the blue screen of death.Tried it on the can bus D4 same result....previously has worked fine on both vehicles.Is there a reset button on the Nanocom?

  2. #2
    Join Date
    Aug 2007
    Location
    Mandurah WA
    Posts
    597
    After a bit of thought, I tried a reinstall of the v1.34 software.It went through its procedure and when nearly finished self selected the 'Overwrite target config' and carried on until completion.I will have to reinstall the unlock codes,but least it is working again.Phew!

  3. #3
    Join Date
    Jun 2013
    Location
    Orroroo
    Posts
    670
    Quote Originally Posted by eddy View Post
    After a bit of thought, I tried a reinstall of the v1.34 software.It went through its procedure and when nearly finished self selected the 'Overwrite target config' and carried on until completion.I will have to reinstall the unlock codes,but least it is working again.Phew!
    Pm. Sent....

  4. #4
    Join Date
    Sep 2009
    Location
    Limassol, Cyprus
    Posts
    488
    Hiyas All

    We have made it ever more and more super easy to re install the Nanocom's existing Firmware / Software, if it happens to go corrupt etc, and this is the first thing to try in the event of such obvious failures that thankfully is quite rare.
    However as eddy states in this thead his seemingly worrying and strange seeming issues were easily resolved by a simple re install of his Nanocoms Firmware / Software.

    In a normal firmware / software update, the Nanocom retains the files used to hold the user configuration options and already entered unlock Codes, but we thoughtfully Included the option for users to "overwrite Target Config" which will replace these files also in the event they get corrupted, of course meaning that if this option is selected, a Nanocom becomes entirely as New and has to have the Unlock codes re enterered and any other User Customisable options re made. This is of course quite simple.

    There is lots of documents to explain in detail, step by step how this is done, the required USB lead to update Nanocoms is supplied with all Nanocoms or is otherwise very generally available and even in the case of a Nanocoms Firmware / Software being corrupt in such a way that the screen is no longer working, we have also thoughtfully implimented a way that can be used to overcome that which is documented also.

    This Process is exactly the same one used for updating a Nanocom's Firmware / Software to a newer / Later release version or perhaps even the Beta release and so something every Nanocom owner should be familar with doing anyway if they wish to keep their Nanocoms up to date and add our constant additions, Fixes and improvements.

    Numerical and logical date based Details of a Nanocoms Current Firmware / Software is shown on the screen as a Nanocom Boots and can be compared to the current Release / Beta Firmware by visiting the Nanocom-Diagnostics.com web site.

    I hope this helps
    Colin
    MD of Blackbox Solutions Ltd.
    www.blackbox-solutions.com

  5. #5
    Join Date
    Aug 2007
    Location
    Mandurah WA
    Posts
    597
    I see back in March I added unlock code 3 to my Evo and also did an upgrade to ver 1.35 with a re enter of all unlock codes.Went to use it in Sept,it failed at the unlock code stage,reloaded ver 1.35 and all codes,result working again.Yesterday,loaded codes for Puma Defender and all seemed good although when reading faults the green bar completed and that was it,would not 'Proceed.' Managed to clear all faults but they will come back.We have assumed it is leak from intercooler/hose/clip.Whilst looking at other settings,the Nanocom suddenly went blank and would not reboot.Tried on the TD5,could only load as far as unlock codes.After reloading ver1.35 and all the unlock codes it appears to be working again......for some reason it's suffering memory loss of the unlock codes.Is this a quirk in ver 1.35 anyone else had similar?
    PS Have also asked on the Nanocom forum.
    Last edited by eddy; 2nd October 2020 at 12:59 PM. Reason: PS

  6. #6
    Join Date
    Sep 2009
    Location
    Limassol, Cyprus
    Posts
    488
    Hi eddy

    Although I am struggling a little with your understanding and explaining your problem based on your somewhat diverse explanation and perception of the possible cause, i will try to assist if possible.

    As I posted in my last post on this thread, when reprogramming firmware in a Nanocom, you can voluntarily use the "Overwrite Target Config" option to delete the file(s) containing the previously entered unlock codes along with other specific user selected options such as background choice etc in the rare event that they got corrupted etc. in which case you would need to re apply the Configuration changes that include the Nanocom Specific unlock codes for your Nanocom.

    Given that your Nanocom seems to have suffered issues with going Blank and other strange and not explained functional aspects that were at least initially resolved after re installing firmware, this proving an issue with corrupted fimware, it may well be that your Nanocom has some strange and odd problem or issue with the Memory IC's, however in no way is this common to a degree we have not seen before, related to a specific version of firmware or could affect only a certain aspect such as only the Config files that contain the unlock codes.

    I am glad to read that you have asked about this, not only here but also on the Nanocom Technical support Forum as we maintain complete transparency, hence we provide the forum at all, but above and beyond this, I do of course keep an eye out to ensure if there is ANY general problem in Hardware, Firmware or even in Admin or Support, that is being reported by Nanocom owners that this gets sorted ASAP.

    If you still have future problems contact BBS support for an RMA for your Nanocom and we will change out the Memory IC's for you.

    ATB

    Colin
    Colin
    MD of Blackbox Solutions Ltd.
    www.blackbox-solutions.com

  7. #7
    Join Date
    Sep 2009
    Location
    Limassol, Cyprus
    Posts
    488
    Duplication removed
    Colin
    MD of Blackbox Solutions Ltd.
    www.blackbox-solutions.com

  8. #8
    Join Date
    Aug 2007
    Location
    Mandurah WA
    Posts
    597
    Thanks Colin.I see when it first failed to boot was back in January when running v1.34 so probably not to do with firmware version!More likely,as you suggest memory ic.
    Strange how it lost power/switched off whilst we were going through its capabilities for the Puma and then would not reboot.
    As I can work around it by reloading the firmware and codes,the unit is still usable.If it gets to the stage where it is not,I will return it for repair.
    Just noted, Alex has recommended trying v1.36 beta.

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Search AULRO.com ONLY!
Search All the Web!