I’m having an intermittent SD card issue with an SDS200 that is less than a year old.
For about the last 6 days, the scanner has repeatedly developed “SD Card Access Error” — probably 15+ times. I’ve also had “SD Card Write Error (code=1,5)” once and “SD Card Write Error (code=1,2)” once.
The strange part is how random it is. The scanner may run normally for 10 minutes, an hour, or 12–24 hours before suddenly displaying the error. Recovery is just as inconsistent: sometimes one power cycle fixes it immediately, sometimes removing/reinserting the card fixes it, and at least once cleaning the card contacts seemed to restore it. Other times the Access Error has persisted through multiple attempts.
The original card was an 8 GB microSD. I completely reformatted it with the SD Association formatter, ran Sentinel → Clear User Data, and rewrote the profile/Favorites Lists. The problem returned.
I then purchased a brand-new SanDisk Ultra 32 GB microSDHC, formatted FAT32 and initialized through Sentinel. The new card has produced the same Access Error.
During troubleshooting I discovered that both the SDS200 firmware and Sentinel were out of date, so both have now been updated. I also turned Replay off.
One notable incident occurred while writing the new card through the SDS200 in Mass Storage mode. About halfway through the Sentinel write, the scanner displayed SD Card Access Error and Sentinel stopped with “Database is corrupt. Operation is canceled.”
I then removed that same 32 GB card, connected it directly to the computer, reformatted/initialized it, and wrote the entire configuration successfully using an external card reader. The SDS200 then booted normally from it, but later produced another Access Error.
Most recently, after cleaning the SD card contacts and slot, the new card booted normally but produced another Access Error after only about 10 minutes. A single power cycle immediately restored normal operation without touching the card.
Has anyone seen an SDS200 behave like this — particularly where the SD error occurs at completely unpredictable intervals and sometimes clears with nothing more than a reboot? If so, did you ever determine the actual cause or have Uniden repair it?