Member Since: 15 Jun 2007
Location: Sunny Cyprus
Posts: 3054
Nanocom News
In the last few weeks, in line with our continuing ongoing and constant efforts to make the Nanocom the best and most self intelligent Diagnostic system on the market, we have released at least a couple of quite significant improvements to it, that I think are worthy of mention, most of which are currently only avaliable in the Beta Version 1.30.3.
The first is that by heavily re working the Flashing capablity, streamlining the process and removing un required delays, and shortening others, we have actually been able to reduce flashing times by a minimum of 25% and in some cases up to 50% from previous times.
Of course we still have a very small number of ECU's that can be flashed with the Nanocom to make a full set, but right now only the MSV-2 beats it and along with the MSV-2 it can also be used to Flash in BAS performance remaps.
Of course faster flashing significantly reduces power requirements, but if things should go wrong to the worst possible case of someone ending up with an un responsive ECU our next improvement may be of interest.
Secondly, in the very worst case, Flashing fails for any reason, can result in a non responsive ECU. Such non responsive ECU's can usually be recovered by a combination of attempting communications is a very short time period after they are powered up.
Without going into detail, we have modified the Nanocom flashing capabilities to provide specialised functions automatically when required that then allow super easy and non time related recovery of a un responsive ECU.
We have also added Freelander 2, completely sorted D3 Key learning, added injector values, a save all for ECU Info and so many other things I loose track.
Member Since: 15 Jun 2007
Location: Sunny Cyprus
Posts: 3054
Apparently not Robbie
Although it was quite some time ago that like many, we discovered that there was indeed a feature using fuses 15 and 16 to disconnect power to a BCU which could then by re inserting the fuses at just the right momement, for which LR advise having 2 people, could then allow recovery of a non responsive BCU caused by a failed flash that happened to leave an operating system in place such that it crashed the CPU to a degree that it was totally un responsive even in respect of diagnostic communications.
Since then we have extensively researched this and discovered that this is a feature which is mandatory on all CAN BUS ECU's.
However although a solution of re powering an ECU by re inserting applicable fuses within a very short time frame (milliseconds) of starting a flashing attempt is possible and a sufficient solution for others, as I have stated our entire aim with the Nanocom is to make it the smartest and most advanced and self intelligent diagnostic system there is bar none.
Interestingly enough, the hardest part of developing this new recovery function was finding a way to make an ECU fail such that it actually became diagnostically un responsive.
On our first test, my staff had made the EAS ECU unresponsive on my 2010 RRS.
The Nanocom was connected with an external power source and an attempt to flash the EAS ECU was made. When this failed due to the EAS ECU not responding the Nanocom went into the new recovery mode whicjh only ends if the user opts to do so. The new documentation we are providing does indicate the respective fuse that should be removed and re fitted for the EAS, however we yanked the Positive battery terminal and went for a brew.
When we got back, we re attached the vehicles battery and the Nanocom immediately establised communications with the EAS ECU as it should and flashed the EAS ECU as normal, which due to the improved flashing times of course happened very quickly.
Thankfully of course, especially due to the new much faster flashing times and absolute rarity of anyone ending up with a non responsive ECU in the first place, most Nanocom owners will never see or encounter this new functionality and capability in action.
But we feel much happier in having added it to the Nanocom.
10th Apr 2015 4:14 pm
Disco_Mikey
Member Since: 29 May 2007
Location: Dundee, Scotland
Posts: 20853
Quote:
Although it was quite some time ago that like many, we discovered that there was indeed a feature using fuses 15 and 16 to disconnect power to a BCU which could then by re inserting the fuses at just the right momement, for which LR advise having 2 people, could then allow recovery of a non responsive BCU caused by a failed flash that happened to leave an operating system in place such that it crashed the CPU to a degree that it was totally un responsive even in respect of diagnostic communications.
Was this before, or after GAP put the recovery instructions on the forum, for all to see?My D3 Build Thread
I am just happy that Gap & BBS are pushing the boundaries of our diagnostic tools, there is nothing like good competition to push technology along. In the end we all win.
Flack
10th Apr 2015 8:46 pm
BBS SPY Site Sponsor
Member Since: 15 Jun 2007
Location: Sunny Cyprus
Posts: 3054
Sorry to have not responded sooner on this thread, but besides me and my staff having a whole 10 off for our Easter Break, I am also simultaneously juggling the handling of discounted Group Buy events on multiple forums.
I have linked all our dev staff to this post, because motivation comes in many forms and as stated by many, ultimately motivation drives improvements and competition that in the end benefits everyone.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
