Thanks Paul
Tryed to reboot but only get 5 second error message then screen blank emailed surport team yesterday still waiting
Printable View
Thanks Paul
Tryed to reboot but only get 5 second error message then screen blank emailed surport team yesterday still waiting
Griff
you can download all the system files from the Nanocom website, in the restricted area.
Ditto here re unable to read SD card in brand new Evo.
XP, WIn7 and Vista all refuse acceptance of the device, left alone being able to read the cards (Verbation SD 2Gb & Sandisk 1Mb SD)
All three OS' say "unable to recognise the device".
Interstingly, I was able to write a TXT file while the Sandisk SD was in the Evo and connected to the 90 (before trying PC connection). After writing it, the EVO flicked off and I had to fiddle unplugging the Evo from the OBD port, wait, touch screen for 8 seconds etc etc (yawn...) until eventually the Evo decided to restart.
One of my own card readers shows the TXT file but cannot read it: "either the file or the directory is corrupted".
Tried multiple plug in/out but still no go.
I feel bound to say that A$450 for a device which can't (in this era) connect to any recently made PC in mass storage mode simply, is very upsetting.
Interesting but not helpful.
SD card not plugged into Evo.
Hook up USB;
PC says "USB malfunction not able to connect to device or similar (Vista and XP)"
Evo bleeps and shows lovely USB plug and hard drive icons plus:
"MSD USB connection
Firmware memory connected to USB"
Plug in SD card - no change.
was worth a try.
Have now mailed nanocom.it for guidance.
have $ 450 paper weight.
have message that files are missing email support they sent files to load but still will not work.
I was asked if i made backup file before I messed it up
bloody could not format sd card before i could do so.
seem so cheaply made
will see the out come buy the end of the week before I go to war
Are you inserting the SD card before plugging the Evo into your PC's USB port ?Quote:
Originally Posted by brookvale
I know it is a suck eggs question but it has to be asked. I don't think the Evo's SD interfacing module is smart enough to detect hot plugging of an SD device. (Happy to be wrong, but I am not risking my hardware to test this out :( )
I am using a SANDISK 2GB MicroSD card with a SANDISK MicroSD / SD adapter as supplied by Mattia. There is no obvious part number so I can't help any further than that.
From memory, Mattia mentioned the the card needs to be formatted as FAT16 but I can't recall what document stated this. Running a CHKDSK on my functioning SD card shows it to be FAT16. Well to be precise, it shows up as FAT. But not FAT32, so I am assuming it to be FAT16.
Does the card read and format from within Windows ? Is there somebody nearby with a known good SD card you can test your Evo with? As the old saying goes, one test is worth a thousand opinions. :)
Until you boot your unit up with a known good SD card, it is pretty hard to point fingers at exactly where the fault may be. It is possible there may be a fault with the SD socket though I find that very unlikely. Much higher probability of either a fault with the SD card or a compatibility issue between the Evo firmware and the SD card. As others have mentioned the SD protocols _should_ be industry standard but Mattia made a point of offering a known working model of SD card with every Evo purchase so there must have been issues with compatibility.
What firmware revisions are you running, in particular the Kernel, FILEMAN and MAINEXEC ? I doubt it is a firmware issue since the SD module would have been pretty well sorted out very early on in the development. Again, this is an assumption since I have no connection with Mattia or BBS and I do not have access to the source code.
Hey Colin, do you need somebody in Adelaide to provide Evo tech support ?? :cool:
I can certainly appreciate any irritation or disappointment Evo owners may be feeling due to the patchy SD card support. Please be aware when programming microcontroller based hardware most resources are scarce including memory. This can mean code modules are maybe not as robust in their error handling or timings as a modern desktop PC. I know it _shouldn't_ be like that but when you consider the Evo has been basically a hobby project of one man, it is astounding the Evo exists at all. Especially when you consider the build quality and the original price point.
BBS have only just got their hands on the hardware and code so give the boys a chance to get their heads around some quite complex code that they did not write.
Please keep us informed on how your tech support query is handled. It will be useful to give other BBS-Evo owners a good idea on how well the BBS support team function.
Regards,
Pete
G'day Griff,Quote:
Originally Posted by GRIFF
Which files are missing / corrupt ?
Does the Firmware drive appear in windows when you connect the Evo with a USB cable and no card in the SD slot ?
There is (or used to be) a procedure to re-flash the kernel that would still work even if the current Kernel is missing or corrupt. THis procedure requires opening the case and playing with jumpers, so we really need to see what files are causing the problem first.
Regards,
Pete
I was more than careful to read the installation and operating instructions (minimal!). The instructions say "insert card into slot then plug in cable to PC". I tried that and it failed.Quote:
Originally Posted by peter5111
Where in the instructions/website does it mention that the Evo will ONLY work with XYZ make/model of SD card?Quote:
Originally Posted by peter5111
Where in the instructions does it say "WARNING!" this unit has little memory and the software hasn't been coded to be robust"?
All my cards work in every SD reader/camera/PC/car stereo I have with no problems whatsoever. I was able to write a TXT file to card when the Evo was on the OBD port with engine running. After writing it, the Evo flicked into hyperspace and I had to fiddle/re-boot to get it back working again.
That TXT file shows on on my PC with a normal card reader but it cannot be read.
I was not offered a 'known' SD card for purchase with the Evo.
Does the SD card have to be plugged into the Evo before booting it up?
Instructions do not mention if this is a caveat.
>>What firmware revisions are you running, in particular the Kernel, FILEMAN and MAINEXEC<<
I have only just bought the darned thing... it should have the latest (best?) ones.
>>... but when you consider the Evo has been basically a hobby project of one man, it is astounding the Evo exists at all. Especially when you consider the build quality and the original price point. <<
Sorry, but this is not good enough. If the sales blurb said "WARNING! you are buying a machine which needs care when plugging in/using SD cards" I would know what I was buying.
There were no such warnings so we punters expect to be able to plug in SD cards without hassles. (and the 'Country' problems already reported...)
Sorry for the bleat here - it would be better placed with Nano.
I'll keep posting as and when Nano reply.
And thanks to all here who are offering support and guidance in the face of upset users.
Neil
Blackbox emailed me to say they will not deal with me and send to place of purchase.
I emailed them how angry the way I was treated as a dumb person
They said I messed it up and after they sent a link to reload file.
This did not work, I was told it worked with others and it should work end of story
Now they will not give me support as i was rude with them.
Great service
Any one want to buy a little blackbox
Despite the SD card originally working, the Nanocom will now not recognise it.Quote:
Originally Posted by Basil135
I will try formatting it on another pc, but am not holding my breath...
Damn, I don't need another paperweight....:mad: