New Nanocom Evolution News

[Basil135]

Thanks for that. I will give it a try.

I also thought there was a way to have it start by itself. But maybe I mis-read it.

[pohm66]

Hi Colin,

Gave it a try and no success... still draggin'ma ass.:(

dropped you a PM...

Cheers..

[pohm66]

Disconnecting the battery for 45 minutes seems to resolved the issue that the ECU wouldn't rememeber / save the changes.

[LOVEMYRANGIE]

You need to set the heights in the SLABS utility program first. Problem is there is no display for what the actual heights are when you adjust up and down as per the Nano1 :/
You need to keep going back into settings and looking at the heights and then back to utilities again to make any further adjustments.
If the setting is anything under 150, it seems to drop. I settled for 156 on both as I can't seem to get it to balance on anything else bit it feels a bit high when driving...
Mine were reading a difference of 5 to 6 until a bit of stuffing around raising one side and lowering another balanced it out but measuring the actual guard heights produced a flip side of what the inbalance in the readings were so I think there might be some
Issues in the unit here.

Once you have the settings where you want them, go into the SETTINGS menu and check the readings, scroll back and select "Transit mode ENABLED" then scroll forward again and click the save function.
You need to name the file by pressing in the blank section above the .csv extension, enter a file name then save it to an SD card.
Not a bad idea to save the original settings too.

To save the settings to the ECU, select OPEN for the file you just saved click OK then select "write to ECU", unplug the Evo first then switch off ignition and wait at least 60 seconds. Leave the Evo unplugged and then start engine, close all doors and wait for it to level out.
Turning ignition off again should result in everything staying up.

I will say this, the overall operation of the Evo is flaky being as kind as I can to it.
From problems with no screen on boot up, cutting out as low as 35C ambient temp, cutting out for no reason while using instrument mode, a bunch of input and output checks that dont work, boot disk not found, SD card error messages, OBD line test working on 1-4 and failing on line 5 regardless of being plugged in or not, no idea what the pin1 Gnd &open function is for, CANBUS test the same plugged in or not etc etc etc, I personally think it's a bit of a lemon in it's current form.
Sorry Colin but having previously been involved in high level custom electronics production and im talking about processor based output powered control equipment, I do understand the idiosyncrasies of software however in a unit as basic as this which is 25% of the cost of something we produced that's hundreds of times more complicated and powerful, I really don't think anywhere near enough basic beta testing has been done with this unit to enable it to be classed as V1.0, which is never the version you release anyway.
There is a fair amount of work required to correct a large number of hardware, software and functionality issues I have found with this unit and I've only had it a couple of days.
It does have the makings of a very good unit but it's just not up to scratch and in my opinion is less reliable than the Nanocom 1 and does not deliver what is expected of it in a number of different areas.

Colin, I am more than happy to make a list of all the issues I have found, however I would get hold of a D2 and a Fender and actually physically test it in realtime, not simulation setups as is so common in custom electronics production today as a measure of getting it out into the market.

Regards

Andrew


Sent from my backyard TeePee using smoke signals.

[Xtreme]

As the title says, I am requesting urgent help.

I'm leading a one day trip with about 14 vehicles tomorrow and while playing with my recently acquired Nanocom Evo yesterday, I have managed to disable the Defender - ignition lights on, fuel pump running, but absolutely no action from motor.

So, is there anyone out there with a Nanocom Evo and a Td5 Defender who would be willing to go to the AS10 menu and read all the settings from Groups 1 and 2 so that I can compare them to mine and make any changes if they differ in the key areas.

If you are willing to assist in this way then PM me with your phone number and I'll get in contact.

TIA.

[MTB]

Xtreme
Have you tried going into the "Country" setting and picking one of the 3 Australian default setting?
That should then get you back to a functioning state.

[Xtreme]

Xtreme
Have you tried going into the "Country" setting and picking one of the 3 Australian default setting?
That should then get you back to a functioning state.

Yep. Tried all three of them and I still have a red light (flashing when door is closed) in the top half of the speedo and still no action at the motor.

Just tried the NO EKA option with a few changes suggested by Paul from Hard Range Aust. but still no go.

I've now disconnected the battery and will leave off for an hour and see what that does to the system.

Thanks for the suggestion and concern.

[Mellow Yellow]

As the title says, I am requesting urgent help.

So, is there anyone out there with a Nanocom Evo and a Td5 Defender who would be willing to go to the AS10 menu and read all the settings from Groups 1 and 2 so that I can compare them to mine and make any changes if they differ in the key areas.

If you are willing to assist in this way then PM me with your phone number and I'll get in contact.

TIA.

Happy to help. I'll send you a PM.

[Nova]

Mine arrived last friday, just need some time to play around with it now (slightly concerned about disabling the car though...) when I get some time.

Cheers,
Nova

[Xtreme]

Problem Solved, thanks to PaulP38a, BBS Guy, and especially Rimmer and Mellow Yellow the latter two who were able to read the SETTINGS from their Td5 Defenders so that I could correct the Australian ones that are embedded in the Nanocom Evo.

Of the 28 items in the two SETTINGS GROUPS for Australia, 9 of them had to be changed. The key one appears to be Arm on Lock which I needed to change (for a 2003 Td5 Defender) from ENABLE to DISABLE.

So don't use any of the SET COUNTRY options from your Evo - they are incorrect and will create many headaches for you.

So now I'll get back to packing a bit of gear so I can get out and enjoy the bush and company of like minded friends tomorrow.

Once again the assistance received from the members of this forum has been outstanding and is much appreciated.

[GRIFF]

just pick up my nanocom.

any tips looking at other posts will wait untill I have worked it out.

so far so good looking forward to pointers

[brookvale]

Hi Paul - unit arrived Friday am - after having to pay the dreaded GST to the Revenue Men on Wednesday...
I was away down country off-roading so only just now (Monday 08:45) sent off the ID code. Guess will have to wait for time zone working day before unlock arrives.
Thanks for all your efforts. Neil

[brookvale]

While I'm here. 2004 Td5 90. Seller made no mention of chipping or re-map. However it goes (or went...) like stink. Beat the pants off other Td5s in the club. Recent woes meant Autologic check-up. Man said no sign of obvious re-map. Haven't looked inside ECU to see if anyone has tinkered inside.
Both Autologic and Memory Tester (sp?) units could not clear some minor auxiliary fault codes (Air Con, Cruise etc).
Engine runs sweetly for an hour or so - full power, smooth etc. Then suddenly it drops in power and vibrations (not bad).
Second Autologic check - no engine faults logged and still could not clear low-grade auxy fault codes.
Swapped for second-hand unit known to work. Engine runs, no odd vibration but dull as dishwater. No engine fault codes logged. Couple of auxy faults (cruise, air con temp something, which could all be cleared instantly.
Autologic details show 'standard' (?) LR mapping details according to the man.

(What are they?)

Will Nano reveal more about my mapping or chippery?

Can't wait to have it operational and see what faults it shows on the road when my ECU goes wonky!

Noted re saving all details to SD card before any tinkering...
Neil
Auckland NZ

[brookvale]

Sorry - should have posted the above elsewhere - can someone move it to the right forum for me?

[Disco W.A]

Paul,
thanks mine has srrived

Roger

[PaulP38a]

Hi Paul - unit arrived Friday am - after having to pay the dreaded GST to the Revenue Men on Wednesday...
I was away down country off-roading so only just now (Monday 08:45) sent off the ID code. Guess will have to wait for time zone working day before unlock arrives.
Thanks for all your efforts. Neil

Hi Neil - thanks for letting me know it arrived. Out of curiosity, what is the import value threshold before duties and GST apply in NZ?

Cheers, Paul.

[Xtreme]

As reported recently - see posts 255 to 260 this thread, especially the warning in post #260 - I inadvertantly placed my Td5 Defender into a 'no start' situation by using the 'SET COUNTRY' function on my newly acquired Nanocom Evo.

For those who are interested I've attached a spreadsheet file showing the differences between the settings obtained from the Evo and those obtained from two helpful members of this forum - 'Rimmer' and 'Mellow Yellow'.

[brookvale]

Officially NZ$60 but some people get things through with much higher values.
I imported some Borgeson steering parts for my 100" special at US$280 at same time as Evo and no GST claim made... maybe it's random.
Neil

[brookvale]

Paul - you may have seen my problems on the SD card threads. :(
Also found that Evo shows I'm in Low Range when I am actually in High :)
Ditto for Brake light - shows on when off and vice versa.

Another query for you or anyone else.
One code shows my ECI status as "Non Robust".
I am having ECU issues which I hope to monitor with Evo - is this is a clue?
What robustness might it be measuring?
Neil

[pohm66]

Hi all.... looks like that Evos may not be patched with the latest upgrades.

Download the latest software from Nanocom and check against your individual module version settings.

[LOVEMYRANGIE]

Hi all.... looks like that Evos may not be patched with the latest upgrades.

Download the latest software from Nanocom and check against your individual module version settings.

What are the latest? I can't see what mine are as the screen won't initialise....


Sent from my backyard TeePee using smoke signals.

[PaulP38a]

Dunno if this is a good time to bring this up... I have worked out the costs and refunds due (rounded off to the dollar).

Most people purchased an Evo with a pair of unlock codes and sent me $450 which included Express Postage. Actual cost was $438, so you are entitled to a $12 refund.

A few people had their Evos hand-delivered by me, so they save a further $10.... = $22 refund.

A couple had additional unlock codes allocated (you know who you are) inc Express Postage... $20 refund.

PM or e-mail to let me know how you would like your refunds and if you would like me to create a new Tax Invoice.

Cheers, Paul.

[BBS Guy]

All Nanocom Evolutions were upgraded to the latest software version for it just prior to dispatch and will currently therefore require no upgrading.

[IceFyre]

I had two files on my Nanocom that had older dates and different file sizes to the ones in the update package from nanocom.it

Thus mine was not up to date.


All Nanocom Evolutions were upgraded to the latest software version for it just prior to dispatch and will currently therefore require no upgrading.

[brookvale]

I'd love to check/update mine but without any SD card/PC connectivity I am a trifle stuffed... :mad: Neil

[hiline]

A few people had their Evos hand-delivered by me, so they save a further $10.... = $22 refund.


give mine back to the site,i'm sure uncle Dave can use it :D

[Rimmer]

give mine back to the site,i'm sure uncle Dave can use it :D
x 2

Or have a couple sherberts for your efforts.;)

Cheers,
Tod.

[pohm66]

x 3 to Dave

and FYI my Evo needed upgrading. :mellow:

[disco_thrasher]

I had two files on my Nanocom that had older dates and different file sizes to the ones in the update package from nanocom.it

Thus mine was not up to date.


x 3 to Dave

and FYI my Evo needed upgrading. :mellow:

can you guys contact me regarding your td5inside stage 2 remaps

[IceFyre]

Throw my refund Daves' way as well. :D

Kelvin, will give you a ring.

[PaulP38a]

9 of 23 overpayment refund responses recieved:


5 to Dave's fighting fund (AULRO Donation)
3 to the Hard Range red wine appreciation trust ;)
1 refund to member

14 responses to go. Please let me know your wishes asap lest the funds get eaten by bank charges in the meantime ;)

Cheers, Paul.

[BBS Guy]

Did you guys check the revision numbers of the .App modules on your unit using the provided function against the version file in the downloadable update as i understand that the production process puts them on in a different way that may well give them different file sizes and dates although they are the same.

[one_iota]

Paul,

Please donate my refund to AULRO. :)

[MTB]

Paul,

Please donate my refund to AULRO. :)
Paul

Likewise, please donate to AULRO.

[greg-g]

Paul
Please donate mine to Dave's fighting fund (AULRO Donation)
Thanks
Greg

[Mellow Yellow]

My refund has gone into Paul's red wine fund. He's done a great job!

Unfortunately I'm having issues with my Evo.

Not with the SD card as I formatted mine in a card reader after failing with it in the Evo. I run Windows 7 64bit and it can be fussy. So maybe the initial failure was not the Evo's fault.

But when connected to the ECU (engine running) the Input Fuelling application fails after initially working and so does the TD5Inst application after initially working. Neither application runs for more than about 30 seconds before putting up an error message. Unplugging the Evo and trying again after a few minutes makes no difference.

The error messages are :-

Input Fuelling ERROR Unable to perform the function.
TD5Inst ERROR ECU communication error.

With the TD5Inst error, the evo turns itself off after displaying the error message for a few seconds.

I'll e-mail the BBS boys tonight and hopefully there's a simple fix.

[peter5111]

Are you connecting to a Defender or Disco? It won't make any difference to your problem, just handy to know what other computer modules are there.

Have you tried to communicate to another module apart from the engine ECU ?

Where is Input Fueling buried in the menu's ?

I know my Evo is setup to boot directly to the engine instruments page and it auto shuts off on loss of communication after 20(?) seconds or so (Ignition off)

Your Evo may be getting power through the OBDII shaped port but it is possible the data wire is not making a good connection.

Can you try the unit in another vehicle ?

Regards,
Pete

[Basil135]

Just to be difficult, split mine between Hard Range RWC (Red Wine Club) and Daves Interesting Things. :D

I appreciate the effort you put in Paul, and without this site, none of it would have happened.

[Disco W.A]

Paul,
plase pass mine onto Dave.
thanks Roger

[Disco_ute84]

Pass mine on to Dave, he does a great job with this site.

[Nova]

Fighting fund for me too, sites like these are brilliant.

Cheers,
Nova

[Mellow Yellow]

My e-mail to BBS got an almost immediate reply. They asked that I
"run the Restore file which will overwrite the original files if the TD5Inst has in anyway become corrupted."

As I had created a Restore File when I formatted the SD card this wasn't a problem and the Evo is working properly again. Yes!!

The Nanocom Quick Reference Guide (downloadable from the Nanocom website) sets out how to do all of the above. If I have a problem with the Evo in the future this will be my first port of call and then, if necessary, BBS.

Answers to peter5111's questions in an earlier post :-

I'm connecting to a Defender.

Both the Evo applications access the ECU.

To find Input Fueling, start with Defender TD5 and go to TD5 Engine.

If necessary I probably could have tried the unit in another vehicle next week.

[peter5111]

MY, great news to hear it was just a software glitch that was easily repairable.

Thanks for the pointer to the Input Fueling. It is the same software module as the Disco one. I have figured out why I didn't recognize it though - I have configured my Evo to automatically boot up into TD5Inst.app . This way I automatically get useful instruments on powerup that are also in bigger font size than the Input Fueling screen.

The TD5Inst.app also does an orderly shut down of the Evo automatically when it looses communication with the ECU, say when you turn the ignition off ;) . This way you don't need to remember the turn off the Evo and as a bonus the orderly shutdown reduces the risk of file corruption.

Regards,
Pete

[brookvale]

Paul, donate any refund to your own red wine fund - for all your hard work.
Neil - NZ

My Evo should be on its way back to BBS tomorrow via DHL under an RMA thingy at cost NZ$180...
I'll keep all posted with results of their damage assessment. If they say it's 'my fault' I think I'll leave it with them as a paperweight - hardly worth the expense of repair and more DHL cost for return. If it's a defect then they should refund the freight and send me the repaired one free - here's hoping!
Neil

[PaulP38a]

I might have stumbled across something useful here that I could not find documented in the manuals or elsewhere...

A member here sent me his Evo to have a play with after he inadvertently formatted the NC_FIRMWARE disk. The symptom was the "ERROR: MAINEXEC.mex file not found" message displayed below
http://hardrange.com/gallery1/d/831-2/IMG-20110321-00030.jpg

First step was to try to restore the system using the RESTORE.BIN file from BBS. I copied the RESTORE.BIN file to the SD card and rebooted the Evo... no good, it complained that "No restore file found".
http://hardrange.com/gallery1/d/843-2/IMG-20110322-00039.jpg

Bugger, so I tried the same thing with 4 other SD cards (2x Sandisk, 1x HP, 1x Pulse) with no joy.

Downloaded the 17-Nov-2010 upgrade pack and manually copied the system files to the NC_FIRMWARE disk. Now it booted to the wallpaper screen (the one with diagonal NANOCOM text) but complained about a missing CFG folder, so I created the CFG folder. Rebooted again and it complained about NANOCOM.cfg file missing... copied the MAINMENU.CFG file from the root, in to the CFG folder and renamed it to NANOCOM.cfg.

Now the unit booted up with the usual menus but I suspected I had missed stuff or screwed up something. To check if the SD card was working, I decided to do a backup... all good, then a restore... all good.

Then it occurred to me when looking at the SD card through the PC... the RESTORE.BIN file is stored in the NCRF folder on the SD card, not in the root :o

So, I copied the "good" RESTORE.BIN file from BBS to the NCRF folder, overwriting the potentially dodgy RESTORE.BIN I had created, deleted the MAINEXEC.mex from the NC_FIRMWARE disk to force a restore on boot, and now I appear to have a functional Evo.
http://hardrange.com/gallery1/d/858-2/IMG-20110322-00054.jpg

Just as well I restored from the BBS image... there are several additional files in the root and CFG folders of NC_FIRMWARE that are not included in the 17-Nov-2010 upgrade pack.

Will return this Evo to the member who will have to re-enter his unlock codes.

Lessons learned:


make a backup of your Evo (after entering the unlock codes) ASAP, preferably to a second SD card that you will keep in a safe place.
if you restore from a known good RESTORE.BIN file make sure it is in a folder called NCRF on the SD card
if you use me instead of BBS to restore your Evo, I accept Jacobs Creek, Wolf Blass or Penfolds Koonunga Hill reds as payment :p... if it has to go back to BBS, you may have to pay more :eek:... Joking, Nanocom/BBS is always your first point of contact for support. They might ask me to check it out before returning to them, but that is their call.

Hope this is some use.

Cheers, Paul.

[brookvale]

Thanks for these tidbits Paul.
Is there a 'correct' folder structure and file content list for the firmware somewhere for us to compare our own systems with?
I'd be trying to do this now but my Evo is sitting here in a courier box waiting to fly to Cyprus.

[999]

Maybe a remote PC session could get the majority of the EVO units that are having issues going again, Like a logmein session with a webcam.

It seems most issues can be user rectified, it's just that it may be a bit complicated for some with little or no basic knowledge of how file systems work.

As for SD cards we should create A list of all working and non working cards,

I list mine tonight. When I ordered my EVO from Mattia I payed the extra 5E (I think for the SD card) And have no issues what so ever.

[Nova]

I have only tried one SD card so far and it worked well. It is an old 128MB Panasonic card from an old camera. It was already formatted to FAT before I tried. I will get around to trying some others soon as having a backup one is a really good idea.

Model - Panasonic 128MB, RP-SD128B

Cheers,
Nova

[greg-g]

I purchased a basic 2GB SanDisk SD Card from Office Works for about $9 and it works fine straight out of the box. It's format is FAT.
I've now backed the EVO up and copied the SD Card to my hard disk.

[Xtreme]

x2^

[Basil135]

Well, I am now on my second SD card, as the Kingston that I was using kept coming up with an error.

Paul, could you give a basic run-down on how to do the backup of the files?

This is the sort of information that I expected to read in the comprehensive user manual that came with the unit....:eek:


Even a $40 DVD player comes with a multi page manual....:mad:

[Mellow Yellow]

If you've downloaded the Nanocom Evolution Quick Reference Guide from the Nanocom website it's set out on page 4.

The only thing with Page 4 is that the paragraphs are out of sequence. That is, before creating a restore file you've got to format your SD card but this paragraph is the second of the two relevant paragraphs.

With my SD card, I didn't format it in the Evo, I used a card reader as my PC runs Windows 7 64 bit which can be temperamental when you plug uncommon things into it.

After formatting your SD card, if you go to the "Restoring file creation" paragraph in the Quick Reference Guide and the screens it points you at, you'll find the process quite straightforward.

[PaulP38a]

Thanks for these tidbits Paul.
Is there a 'correct' folder structure and file content list for the firmware somewhere for us to compare our own systems with?
I'd be trying to do this now but my Evo is sitting here in a courier box waiting to fly to Cyprus.

If you remove the SD card and plug the Evo in to your PC via the USB cable, the NC_FIRMWARE flash disk should mount as a new drive and have the following files:
APPMAN.app
AS10.app
DEFABS.app
DISCOACE.app
FILEMAN.app
MAINEXEC.mex
MAINMENU.cfg
NCSET.app
SLABS.app
TD5ENG.app
TD5ENG.BIN
TD5INST.app
TD5MAP.app
TXTEDIT.app
VALBCU.app
VALBCU.bin
PUMAENG.app
PUMAIPC.app
PUMAINST.app

In addition to these files is a folder called CFG containing:
NANOCOM.CFG
TD5INST.CFG
UNLOCK.TXT
PUMAINST.CFG

if you now dimount/eject the NC_FIRMWARE drive (via Windows "safely remove hardware"), disconnect the USB cable, insert the SD card in to the Evo and then reconnect the USB cable, a drive will mount again. This may or may not have a volume name... I called mine EVO-SD.

If you have done a backup there should be a folder on the SD card called NCRF containing a RESTORE.BIN file.

BTW: after restoring the Evo last night, I subsequently found that all of the SD cards I had worked fine.


Paul, could you give a basic run-down on how to do the backup of the files?

This is the sort of information that I expected to read in the comprehensive user manual that came with the unit....:eek:


As Mellow Yellow suggested, the manual is available at http://web.nanocom.it/download/NANOCOME%20VOLUTION%20QUICK%20REFERENCE%20R1.0.pdf
or a copy that may be less confusing to some web browsers at http://hardrange.com/downloads/manual/NanocomEvoQuickRefR1.0.pdf

Basic steps are:


have the SD card inserted in the Evo
boot the Evo
from the main menu select the NANOCOM item
select SETUP
scroll to the last item RESTORING FILE
select CREATE RESTORING FILE
watch the green bar fill left to right. You should get a Restoring file created message when it is done.

Hopefully BBS will fix the English menus (and manual) in a future software update... all credit to Mattia though, his English is much better than my Italian ;)

Cheers, Paul.

[Basil135]

Thanks Paul.

Very much appreciated.

[disco_thrasher]

Gee looks like these evo are causing alot of troubles :(

[LOVEMYRANGIE]

Paul, mine will be coming back to you via mail. Screen still blanks when you power up. Backlight comes on and it beeps but nothing else.

Cheers

Andrew



Sent from my backyard TeePee using smoke signals.

[peter5111]

Gee looks like these evo are causing alot of troubles :(

You could say the same thing about the TD5 engine. ;)

It is just a new tool that folks aren't used to using. I think the biggest factor that makes it look really problematic right now is there are 23 ish brand new Evo's that have all hit the street at exactly the same time.

So there are 23 owners all learning the same things at the same time.

Personally I think it is great to see the issues being aired in public - that is the only way to build up a knowledge base. And in true Landrover owner form we seem tell the story warts and all. :angel:

[999]

Just checked the SD card in mine it's sandisk microSD 2GB with a microSD to SD adapter.:)

[brookvale]

You could say the same thing about the TD5 engine. ;)

It is just a new tool that folks aren't used to using. I think the biggest factor that makes it look really problematic right now is there are 23 ish brand new Evo's that have all hit the street at exactly the same time.

So there are 23 owners all learning the same things at the same time.


Sorry, not so right sir (polite).
The Evo user guide does not say "make sure the SD card is inserted in the unit before powering up or connecting/plugging into the OBD port... "
Almost like the LR book for Td5 vehicles forgot to say "make sure you have oil in the sump before trying to start your engine".

These are fundamentals which, if critical, must be told for users of a device which appears, on the surface to have a standard style USB connection, but has actually has issues when it should/should not have the card plugged in.

I think the Evo software person wrote the user guide themselves rather than having a real user try them out and reporting back - they did not remember that we would treat the Evo as 'card reader' and plug/unplug the card in at anytime we fancy (as it should be)

And it seems peculiar that User A has no problems with an Acme Cheapo SD card but User B with a 'high spec, reliable' Sandisk one, does.

Odds seem to be stacking up that the quality control is lacking somewhere with the hardware or the software's implementation.

One weeks' testing by an ordinary LR owner would have surely picked up these issues before the unit went on the market.
Neil

[peter5111]

Apologies if I came across a little flippant. The comment was intended to be a light hearted observation. I have been using one of Mattia's original batch of Evo's now since September last year and it has been rock solid for me.

Having said that, I have caused SD card issues on my Evo recently but only by doing things that after 20 years of working with computers of all shapes and sizes from mainframes to and micro controllers, are totally unnatural to me and used to be for all computer owners up until ~Windows XP era. (like pulling out an SD card while it is in use). The code needs to be made more robust. Putting a warning in the documents is only a temporary measure.

I DO agree that the Evo has been prematurely released on an unsuspecting user base with an unacceptable lack of Beta testing and woeful documentation.

Hopefully BBS are paying attention and will roll all the good suggestions here into a revision of the manuals and a decent Beta testing program. The Evo has too much potential to ruin it's name by releasing a half baked product.

I have no connection to Mattia or BBS but I do believe in the potential of the Evo. I have put a stack of time into helping new users both in the forum and in private, and I will continue to give whatever help I can.

As I have mentioned previously, we are rapidly building a decent base of knowledge and knowledgeable users. I think we need to start a good-oil thread with links to the important stuff in this and other Evo threads.

Regards,
Pete

[PaulP38a]

As I have mentioned previously, we are rapidly building a decent base of knowledge and knowledgeable users. I think we need to start a good-oil thread with links to the important stuff in this and other Evo threads.


Good idea Pete, I agree that this thread has outlived it's usefulness and we should start another thread to discuss the good, bad and lessons learned from our new toys. Where to put it though? It is a diagnostics-specific discussion so maybe a new thred in this forum, or is the somewhat cluttered "Good Oil" forum a better choice?

Cheers, Paul.

[brookvale]

I'm all for the Evo too - just a trifle pi**ed off at the moment - but I'm getting over it :)
I'll be more than happy to help out with establishing an "Evo Operations" thread - I was planning a graphic menu structure for the thing so others don't have to flounder around wondering why they can't just flip from one mode to another without a re-start. But this will have to wait until mine comes back. ~~ Neil

[LOVEMYRANGIE]

Got my Evo back last night from BBS after it went mucho kooky. All looks good now.

Thanks Paul for looking after it!

Andrew


I am not a moderator, I am a human being!!!