Nanocom 2.05

[bluerazor]

Hi Everyone
Just a reminder that there is a new Firmware release for the Nanocom now V2.05
Bug Fixes for Defender ABS rear wheel speed, Accelerator sensor type in standalone mode , Injector Code fixed for euro 2 models. Language pack added English / Italian other languages available on request

[Zute]

Just been trying to load new firmware 2.05. After having heaps of trouble getting the Nanocom to hookup to the PC (uninstalling and reinstalling drivers and wot not) got it working better than ever. Now when I go to load the new firmware it says the file to large ? (no files stored in Nanocom, I checked )Tryed loading anyway but comes up error.
Anyone else having this problem ? or know what Im doing wrong ?

[discv]

Just been trying to load new firmware 2.05. After having heaps of trouble getting the Nanocom to hookup to the PC (uninstalling and reinstalling drivers and wot not) got it working better than ever. Now when I go to load the new firmware it says the file to large ? (no files stored in Nanocom, I checked )Tryed loading anyway but comes up error.
Anyone else having this problem ? or know what Im doing wrong ?
Don't know if this is any help. I have found when saving files to Nanocom it will often report 'file too large'. What it in fact means is file name too large.
Tony

[Zute]

Loaded new firmware, but at the end it says "Unable to cennect the Nanocom boot loader"
The Nanocom says "push a key, but when I do, nothing happens. It shows its connects with PC every time straight up, but nothing.:wallbash:
Help.

[bluerazor]

Hi Guys i had the same problem at first attempt to try the upgrade
The problem was that the Com port setting was incorrect.
First connect the Nanocom as usual via USB to the Pc
when it has detected that the Nanocom is connected "reduce this window" Note do not close!
Then go to My Computer Right Click and open Systen > Hardware
Here you will see the the Nanocom listed in the Com Ports section
Now click on this Port where nanocom is
go to port settings/configuration > advance settings and see what port setting is. Remember that this port MUST be the same as the main Window
of the Nanocom Application So in other words NOT to select USB but the Com port found in the configuration settings.
At this stage it's now possible to make the download for upgrade.
Hope this is of Help
Best Regards
Vince

[Zute]

Hi Vince,
Did you get the small window saying "Unable to connect the Nanocom boot loader" message ?

[bluerazor]

Yes that was my initial error, then after setting the correct com port it worked fine

[Zute]

Ive been talking to Mattia at Nanocom via email, and he thinks it might need a boot thingy attached to fix it. That would mean a trip for it O/S.
I will try what you have suggested tomorrow morning when I have a clearer head.
Peter.

[bluerazor]

Ok Good Luck Peter
As i said before i had the same error message so give it a try before you send it back.
Keep me informed how it goes.
Cheers Vince

[Zute]

Nope, didn't work. still came up with boot loader error. Mattia said it needs to have the boot loader attached to reload it, as it may have lost a file or something. So looks like its going on a trip.
Peter.

[Rosscoe68]

mine had same error trying to load, and i to changed the com port to 2 and away it went. also dont forget to switch off the startup mode to instrument f thats what you have as default setting, it will connect to pc nanocom software but wont load the firmware update in the instrument mode.

[Zute]

Thanks, Ive tried changing the comport setting and made no difference. I'm pretty sure it was in instrument mode before I started, anyway doesn't matter now as I get no response when pushing the buttons.
Peter.

[LandyAndy]

Hi Zute
ME TOO:mad::mad::mad::mad::mad:
Was about to fit my new chipped ECU and decided to upgrade my Nanocom to the new firmware first.
NOPE,same as yours it gets as far as boot loader and freezes.Nanocom screen says run firmware.It no longer works at all.
Sent an Email to Mattia.
In the news section on Nanocoms website it says there are issues with the new firmware.
Andrew

[Timka21213]

Hi,

I did upgrade to 2.05 without any problem from the first try following by the manual from the site.

Tim

[Zute]

Hi Andy,
Have you had a reply from Mattia yet ? If you need the new boot loader it might be better for us, to have him send it out. But Im not that tech and might need help.
I haven't heard back from him yet though.
My wife says there is a risk in posting things to Itally. I think thats where he is .
Peter.

[strangy]

Hi, I am no computer expert, but I found I had to disable my anti virus protection to carry out the upgrade.

Every thing went ok then.
Dont know if that may help you.

Cheers

[LandyAndy]

Zute
No response from Mattia yet:mad::mad::mad::mad:
About to try installing the old firmware just to get it going.I WANT TO INSTAL MY NEW CHIPPED ECU!!!!!
Strangy did you get no bootload after the upgrade was sucsesfully downloaded to Nanocom as Zute and I have????
Andrew

[LandyAndy]

Just tried re-loading the 04 firmware,same result.COMPUTER SAYS NO:mad::mad::mad::mad:
Andrew

[Trippo]

Hi Zute
ME TOO:mad::mad::mad::mad::mad:
Was about to fit my new chipped ECU and decided to upgrade my Nanocom to the new firmware first.
NOPE,same as yours it gets as far as boot loader and freezes.Nanocom screen says run firmware.It no longer works at all.
Sent an Email to Mattia.
In the news section on Nanocoms website it says there are issues with the new firmware.
Andrew

Hi guys , just read this thread and ditto, I also got stumped at the "Boot Loader Freeze" point but finally succeeded with a 2.05 firmware install.
My nanocom unit is the early com: port type and I did purchase and install the hardware upgrade kit which includes a boot loader - the software for it is available on the site.
Also I read on the site somewhere that the supply voltage for programing the unit is fairly critical.
To achieve the succesful 2.05 firmware upgrade I did the following -
1. Turned antivirus off
2. Got my old variable bench power supply out and set it to 13.4V when connected to nanocom ( a fully charged battery is OK too)
3. Re-run the boot loader procedure (I think this erases the firmware also)
4. Installed the latest firmware(2.05)
5.Started unit up = all good including connecting to PC
Detailed instuctions are on the site for these operations
Soon I will test in vehicle
Hope this helps , Chris

[Zute]

It say's that the firmware has loaded, But unable to connect Nanocom boot loader.
I got a reply from Mattia today.

[Col.Coleman]

Does anyone know what happened to Firmware 2.05 on the nanocom.it site?

I have just uploaded 2.4 onto my nanocom, and 2.05 on the computer software, but there doesn't seem to be a firmware 2.05 download for the nanocom.

Does anybody have a copy of it? or will 2.04 do.

CC

[999]

Does anyone know what happened to Firmware 2.05 on the nanocom.it site?

I have just uploaded 2.4 onto my nanocom, and 2.05 on the computer software, but there doesn't seem to be a firmware 2.05 download for the nanocom.

Does anybody have a copy of it? or will 2.04 do.

CC

Download from here http://www.aulro.com/afvb/1372200-post15.html. (http://www.aulro.com/afvb/1372200-post15.html)

[BBS Guy]

Does anyone know what happened to Firmware 2.05 on the nanocom.it site?

Yes i do. It was removed by Mattia, the previous owner of Nanocom, as soon as it was identified that 2,05 had a strange bug that had the ability to corrupt the boot loader in such a way that that future upgrades could then not be uploaded in the usual way.

The activities of those pointing to cached copies of 2.05, as you have just seen, has meant that so many have installed this, that future upgrades to Nanocom 1's will likely now be only via the purchase of directly and physically connectable programming hardware.

[djam1]

Colin
How is the next generation Nanocom going ??

Duane

[Col.Coleman]

Yes i do. It was removed by Mattia, the previous owner of Nanocom, as soon as it was identified that 2,05 had a strange bug that had the ability to corrupt the boot loader in such a way that that future upgrades could then not be uploaded in the usual way.

The activities of those pointing to cached copies of 2.05, as you have just seen, has meant that so many have installed this, that future upgrades to Nanocom 1's will likely now be only via the purchase of directly and physically connectable programming hardware.

Colin,

I see that you are the new owner of Nanocom. Thank-you for the information regarding 2.05.

I own a nanocom, purchased in the first group buy on Aulro, and have registered on the nanocom site to download upgrades. The upgrades up to now have been provided to registered owners free of charge. Through this, yes there has been some bugs, but it has been worked out.

I also see you have purchased Nanocom as a commercial venture. I support this, and understand you have to get returns for your investment, but I am a little confused at your last paragraph. Could you please clarify your intention.

You are upset that there are cached' copies of 2.05 and want to restrict further upgrades on a pay for a copy because
1: you are not making any money out of these upgrades which up until now have been provided free as part of the R & D of the product to improve it and make others want it more
2: You don't want to have to cop fixing repairs of a corrupt version
3: You are upset someone has saved and distributed what was originally free in the first place

Because as I read it, you are just jumping up and down about someone letting someone else have a copy of a program that was free in the first place.

I went to your website, registered as a bona fied owner and downloaded from you. If there is a major problem with 2.05, and it has been pulled, you know it is out there, put a reference and warning on your website. The reason I wanted 2.05 was for the temp alarm. I installed the Bell Auto's Readall firmware version.

Every other software company is pay for upgrade, which makes sense as your business is developing and selling your product which is the hardware AND the software. You just may find the transition a bit rough from people that do not understand why, what is involved, or the cheap ass nature of us Landy owners that lead us to purchasing a Nanocom in the first place. They used to get it free, and now will have to pay. You also need to explain yourself better, rather than coming on jumping on someone as a disgruntled Vendor who missed out on some coin.

CC

[LandyAndy]

If anybody in Australia needs to re-load the boot sector after failure I have the tool needed to get Nanocom going again,supplied by Mattia.
I fixed mine and 2 others after 2.05 failures.
Colin,it would be good to know if you intend doing much with the original Nanocom.
Have had a go of the new one,NICE!!!!!
Is it possible to introduce the wheel size/speedo matching in the new Nanocom to old???
Cheers
Andrew

[peter5111]

I vaguely recall seeing a reference on the nanocom.it website about the 2.05 firmware saying do not use it. Can't find the link now though.

CC, my understanding of what Colin has said comes down to this;

*Don't install 2.05 because it breaks the ability to perform any further firmware updates.

*2.05 is still out in the 'wild', being available on owners caches. Because of this, 2.05 is still being installed and still breaking the upgrade path. It was removed from the website for a good reason (Though there really needs to be an obvious explanation posted on the website. Colin?)

*If 2.06 ever gets released then it can't be installed on a Nanocom with 2.05 firmware using the documented firmware updating process.

*A Nanocom with 2.05 firmware can still be upgraded but it requires other software and hardware tools, opening the case (I believe), and a reasonable level of computer literacy.


LandyAndy, could you send me the info you have for the firmware repair hardware ? It may be useful to have the information out there for when (if) 2.06 gets released, and I would like to build up my knowledge bank in case somebody in SA needs help.

Pete

[Rosscoe68]

Yes i do. It was removed by Mattia, the previous owner of Nanocom, as soon as it was identified that 2,05 had a strange bug that had the ability to corrupt the boot loader in such a way that that future upgrades could then not be uploaded in the usual way.

The activities of those pointing to cached copies of 2.05, as you have just seen, has meant that so many have installed this, that future upgrades to Nanocom 1's will likely now be only via the purchase of directly and physically connectable programming hardware.


Colin,

I see that you are the new owner of Nanocom. Thank-you for the information regarding 2.05.

I own a nanocom, purchased in the first group buy on Aulro, and have registered on the nanocom site to download upgrades. The upgrades up to now have been provided to registered owners free of charge. Through this, yes there has been some bugs, but it has been worked out.

I also see you have purchased Nanocom as a commercial venture. I support this, and understand you have to get returns for your investment, but I am a little confused at your last paragraph. Could you please clarify your intention.

You are upset that there are cached' copies of 2.05 and want to restrict further upgrades on a pay for a copy because
1: you are not making any money out of these upgrades which up until now have been provided free as part of the R & D of the product to improve it and make others want it more
2: You don't want to have to cop fixing repairs of a corrupt version
3: You are upset someone has saved and distributed what was originally free in the first place

Because as I read it, you are just jumping up and down about someone letting someone else have a copy of a program that was free in the first place.


CC

umm, did i miss something, i didnt see any "jumping up and down"
just a simple statement that was quite matter of fact.

[BBS Guy]

Hiya Duane
Thanks for asking, all prototyping is done, just waiting for the cases and PCB's to be supplied to us, then i have to get them actually built. I will try to keep folks on here updated on the verandah thread as soon as i have any more concrete news and especially some piccies. ;)

I appreciate it is an agonizing wait, but it will be worth it.

Hiya CC
I am sorry that you have so easily jumped to such a negative conclusion and formed some very negative opinions of me, and besides the fact that i really can't see the justification, you actually could not be further of the reality of the situation if you tried.

I have absolutely no financial incentive to do anything to help previous Nanocom owners, but i am certainly not that sort of chap. I got into this business to help people, and that's also why i took over Nanocom.
So although such comments may not be exactly inspiring, I am and will certainly be doing my very best and have already done and invested quite some time and money already for all Nanocom one owners.

In fact any upset you may have detected in my post was simply because 2.05, with it's further upgrade incapacitating bug (damned upsetting in its own right), coupled with an inability for Mattia to effectively stop it from spreading, despite best efforts, has ultimately made providing a large number of Nanocom one owners with 2.06 without any possible cost, and of course further upgrades and the many bug fixes they need, really difficult for me. In essence i am annoyed only that i cannot help you better, not that i can't rip you off.

Hiya Andrew (LA)
Thanks for posting up your offer to help others get past this broken upgrade path.
TBH it gives me some hope in that not everyone will need to buy a hardware programmer if others are so helpful and generous as you, and i note Pete already seems willing to do as much.
Thanks Guys.


Colin,it would be good to know if you intend doing much with the original Nanocom.
Given the 2.05 upgrade path breaking problem, you can hopefully appreciate that i have had quite some initial ability problem dropped into my unsuspecting lap, never mind intent. We are however working hard on ways to fix this and i am confident that Nanocom one owners will not be dissapointed.

Re the EVO:
Yes it is nice but just wait till you see the EVO II ;-)

Once we have the upgrade path restored, we should easily be able to translate any function on a system on the EVO to the Nanocom one, but for the moment, i an sure you appreciate I have to focus on the bigger picture and steer this particular ship of the rocks first.

Hiya Pete
Very accurate summation there.

I will have a warning about 2.05 added to the Nanocom site :D
Its previous mention there seemed to just make more folk ask for it :eek:

Documentation about doing a firmware upgrade via Hardware on a Nanocom 1 is already being completely re written. ;)

[djam1]

Hiya Duane
Thanks for asking, all prototyping is done, just waiting for the cases and PCB's to be supplied to us, then i have to get them actually built. I will try to keep folks on here updated on the verandah thread as soon as i have any more concrete news and especially some piccies. ;)

I appreciate it is an agonizing wait, but it will be worth it.


I hope so and do acknowledge that it is agonizing quick quick work faster lol :wheelchair:

[Col.Coleman]

Hello All,

Some clarification.

Colin, for starters. I did not form a negative opinion of you, I merely asked for clarification as this is how I see it.

I was upgrading my Nanocom, I had looked at the nanocom site, and read and searched the forum on the subject. I had upgraded to 2.04 in the normal way and upgraded the computer software. Through the forum I became aware of the 2.05 version and the fact it had a temp alarm, and given that I have just had an overheat episode in my Td5, this is now desireable.

I hadn't read of a catastrophic failure, just a few isolated bugs. I asked the question if 2.04 would do and was pointed in the direction of 2.05. I had also read about Bell Auto's rewrite and the readall application. Now without the knowledge of what 2.05 is supposed to do to your boot loader, reading your reply came off as a disgruntled new vendor saying that if people are out there loading this software, from now on you are going to have to pay for upgrade. This is why I asked for you, and you have thank-you, to explain the situation better.

Every other software company you pay for upgrades. Think MYOB, Quickbooks, Microsoft. We get ours for free which is great, but I also understand the cost of development so you should charge for it, is what I was saying.

Now what I actually have done.

I have Nanocom #nn7n3k, so you can track it, Colin. It is a usb version and was originally loaded with 2.01 and usb 1.01. Up until recently I have only used it in instrument mode, and by itself in the Defender. It is a 130, so the engine module covered what I needed. I have just decided to actually register it, upgrade and unlock the rest of the options.

First I upgraded to 2.04 from nanocom.it. Then from the cached files I uploaded to 2.05 the std version. Then I realised the Bell version was there so I uploaded that version. After reading that I can now , no longer upgrade, I then reloaded 2.04, but seeing that my boot loader has not died, I have now reloaded the Bell Auto's 2.05 again to gain back the temp alarm.

I do not know if I am just lucky, or it happens down the track, but I have not had the boot loader problem and have overwritten 2.05 a couple of times already.

So maybe not all Nanocoms with 2.05 will have the boot loader problem. But it is good to know Andy is available if I do. I would also be prepared to help people in SEQ if they have a problem with theirs.

CC

[LandyAndy]

I must admit I never paid Mattia for his boot loader.I was supposed too,tried several times via EFT but I got rejected via the banking system.I dont own a credit card or Paypal account so I couldnt pay.
It was only 50 euro,but I still have a debt to Nanocom.
Because I got the unit for nothing Im more than happy to use it to fix others Nanocoms,I did the other 2 free of charge,all I ask is the owner provides their own express post bag to sent the Nanocom back.
Peter,I would have to look for the saved link to Nanocom for the programme.This boot loader requires opening the Nanocom up and pluging it into the circuit board,whole operation is less than 10mins.
Andrew

[BBS Guy]

Duane:
You slave driver :p

CC:
No worries chap, i agree at least that my post could have been written a bit better, but i had downed a couple of Vino's at the time ;)

But now you know the situation more, you will perhaps understand my frustration and reason for posting exactly what i did, which was also in part to warn you about 2.05 :angel:

In any event, i have read much worse assumptions being imagined as to my motives and intent, vastly increasing the price, making everyone's Nanocom Single Vehicle (ie Locked to VIN), not supporting existing customers to name but a few. And of course many are concerned that there would / will be no further development or upgrades. All of which is of course utter nonsense.

But clearly, with the Nanocom one and it's apparent 2.05 boot loader corrupting Bug, i am starting with quite some disadvantage.

So i am really grateful for any input and help i can get and i thank you and everyone for their efforts in trying to help me find the best way to sort it.

I know very little about the Bug in practical terms, IE how many are actually running 2.05, or what the chances are the Bug has corrupted their boot loader.

So information like you have just provided really does help, as does that from everyone.


So maybe not all Nanocoms with 2.05 will have the boot loader problem.

You may be right, but you may just have not been using it long enough, and i do have to assume a worst case scenario though, as a corrupted boot loader is currently only discovered when you try to apply a firmware update and then leaves a non working unit which can then only be fixed by physical re programming.

Andrew:
Does that mean you owe me 50 Euro then [bigrolf]

[BBS Guy]

Hiya All

Just made a post of much interest to the contributors to this thread in the verandah area

http://www.aulro.com/afvb/verandah/131715-nanocom-one-version-2-06-upgrade-release.html#post1508133

Andrew (LandyAndy)
I am so utterly sorry, but despite my best wishes and efforts, i simply could not find any easy way to technically provide the capability for the old Home Brew programmer you have to be used to program in this new 2.06 and beyond upgrade.

This especially bothers me as you so seem to have the same helpful to anyone nature as i do.
I will therefore freely donate one of the new programmers to you if you would but just cover the cost of shipping ;)
I am also offering you the opportunity to become a permanent Beta tester of all future upgrades we will provide to Nanocom One owners

Colin