Hi Colin,
Many thanks for your reply and sorry for doubling up (I thought I had read all posts on this subject).
Good to see that this idea is already being considered.
Keep up the great work.
Dave. :D
Printable View
Hi Colin,
Many thanks for your reply and sorry for doubling up (I thought I had read all posts on this subject).
Good to see that this idea is already being considered.
Keep up the great work.
Dave. :D
Hiya Dave
No worries, there are now quite a few threads ;)
It's actually no bad thing to see others thinking of / wishing for the same thing, and we certainly do intend to keep up the good work.
Thanks for the compliment, It makes it all that more worthwhile to be appreciated for our efforts in what we are trying to achieve. My thanks also extends to every other member and the moderation of this forum for all the help, participation, appreciation and support.
Speaking of which;
The Temp Alarm has been fixed in the software already Duane, along with the Turbo boost pressure and many other such things. It does still need final testing though, but i really don't expect any problems as it was a fairly simple fix once the problem was identified and re created on our bench jig.
We have also fixed the core problem that has always existed in the BCU settings i believe i mentioned before, which involved re writing a lot of it and we have added extra values to it.
This of course is being done in the origional Nanocom One's and the Evolutions, so all existing owners will benefit.
However there are so many changes and it's all so detailed, the testing is no quick job, but it's already progressing well and looking very good :)
We are also still sorting a Key programming issue affecting slots 3 and 4 only, but are struggling with this a bit to get it just right and it looks like there may still be a problem we have to get to the root of.
The BCU testing, most especially the key programming is made a bit more difficult as much of it really needs a full working vehicle rather than a Bench Test jig, and we sold the Disco 2, we purchased new in 2000 to develop on many years back, when we finished our own software, and don't have instant access to another vehicle.
I have however put the word out around my many business friends who fix and sell Land Rovers and they usually find me something fairly quickly.
In the meantime, i am also trying to use our bench test Jig and having just got a key, discovered it does not get recognized and noted this would be because our bench test Jig does not have a receiver. But this afternoon, i sussed that the Receiver for the Disco 2 is in fact the same as on the Disco 3 and i do have one of those, if only i am now able to find it after the move:(
If i can find it, i should be able to graft it onto our Bench test rig and hopefully get the rig seeing the key and so accelerate the Key programming, possibly negating the requirement to get a vehicle anyway.
So although all this bug fixing and re developing stuff is not exactly at the lightening speed i would have hoped, and in all honesty it might even be a few months yet before everything is totally sorted and we can start looking at niceties and wishes. It took us quite a while the first time with debugging our own stuff to get it totally flawless. But it's certainly all coming along slowly but surely, which i guess is actually a huge achievement in it's own right.
Hi Colin,
After watching this thread for a while I am extremelly impressed in your commitment to the product. Congratulations and keep up the outstanding work.
I am looking at purchasing one myself soon and I am reasured that any issues will be dealt with quickly and efficiently. Something that is quite rare these days.
Cheers, Chris
Hiya Chris
Thanks for your comments of appreciation and encouragement.
I have always believed in myself and what i do. I always act as fairly and considerately of others points of view as i possibly can. As such i have no problem in making myself publically open to either compliment or criticism.
That others do not feel or do the same, as you note, speaks volumes.
I am sure you will be delighted with your future purchase choice, and if not, i would truly love to learn any reason as to why.
although i have never Blogged before, i have just started my first one at
http://www.aulro.com/afvb/blogs/bbs+...beginning.html
Which announces todays release of new software upgrades for both the Evolutions and Nanocom ones.
Has anyone had difficulty running the firmware update?Quote:
Originally Posted by BBS Guy
I had it hang/freeze part way through the install. "PROGRAM ERROR!" appears in the dialog box beneath the blue progress bar. It sat for 20 minutes with the progress bar showing that it should have been finished. After disconnecting it it now appears bricked as a 2nd attempt at running the firmware upgrade has also failed.
I'll email BBS now and try and run the 'restore' file after it's plugged back into the vehicle.
Ouch. :(Quote:
Originally Posted by bell1975
Just upgraded Dad's for him tonight. All went through ok.
No dramas with mine uploading.
However I do have an issue with the cooling system over temp flashing up within a minute or so of starting instrument mode for TD5... reset it and it's fine but I haven't checked an actual temp trigger yet.
Using Capitals, the difference between helping your Uncle Jack off a horse or helping your uncle jack off a horse...
Thanks for your replies folks. Mine is still bricked....liaising with Ron from BBS now.
Bit of a worrying mystery so far bell1975.
And of course have been there behind the scenes discussing this with Ron. In fact just before we closed, i sent you an E-mail with some suggestions and a link to a restore file, as since we fixed this in V1.01 you should now be able to use.
Although its a new kernal manager application being distributed with this release, that's only because we tacked a new feature on the end of it that provides the ability to make a back up file. Otherwise all the code that does the updating using the external file is the same as with the v1.01 upgrade which has long since been field trialed.
I have this afternoon run the upgrade a few times on a dozen different PC's of all different speeds, types and different OS's, sometimes having 3 on the go at the same time. I only once had one fail, and after closing the app, i saw a window that Microsoft had updated something and was offering me to reboot now or later :twisted:
I simply clicked later, cycled the USB connection to the EVO, re selecting kernal, re ran the manager app and upgraded the unit again no problem. I even ran the upgrade from a cheap USB stick.
We have had someone else report a not fully installed upgrade a couple of days back, as Ron mentioned, but as i understand he was an EVO 1 owner who we figured was likely putting his unit into upgrade mode using the on screen menu method, rather than the more direct 4 option screen. As this was the only way possible the first time he upgraded. When he wrote in saying his menu was now not there, indicating a main firmware flash content corrupt or missing problem, we wrote back telling him to use the more direct 4 icon screen method and have heard absolutely nothing back since, which sadly and annoyingly is very common when our help, advice and directions sort folks out and they then have no need of you at that time. :angrylock:
But don't worry, i am quite sure you know you are in good and caring hands and we will help sort you out no matter what it takes. ;)
LOVEMYRANGIE,
It sounds like the issue is only that your alert value is currently set below the normal temp value of your vehicle, such that now we have fixed this, in your case you are instantly getting an alert. ;)
Only seems to do it from cold Colin.
It's untouched at 95C but only seems to do it when it's under 25C on the coolant temp readout.
Using Capitals, the difference between helping your Uncle Jack off a horse or helping your uncle jack off a horse...