- This topic has 7 replies, 4 voices, and was last updated 2 weeks, 5 days ago by
.
-
Posts
-
I have been running this OS for a long long time. All of a sudden I could not access it, so i went and checked it and saw the 0x2D Error. I restarted it, came inside and looked the error up on the forum. Searching the forum i see it is likely an SD Card issue.
When it happened a zone was watering. I had it up in a browser and even though the zone had physically stopped, it showed the zone still running hours later.
But if it is an SD card failure, why would it boot up and be running ok after recycling the power?
I guess if i see it again, i will swap out the SD card.
0x2D means SD card issue. This error is shown when the controller reboots and couldn’t detect the SD card, or detect an error in the SD card.
Look, I think some of the issues you are seeing may be inter-related. I’ve already mentioned in another thread that perhaps try to reduce the number of zones. In fact, why not perform a factory reset, and keep it in that state (do not import configurations) and monitor it for a while. If the symptoms are gone, that gives us some knowledge about what could have gone wrong (as I said, possibly a data buffer corruption issue due to large data transfer). If you don’t test it in the factory reset state, that won’t help isolate the problem and the result is a bunch of problems stacking together and we don’t know the root cause.
Sorry to resurrect an old thread, but I’ve also recently started to experience 0x2d crashes, after 9 solid years of operation.
I recently upgraded from 2.1.5 to 2.2.0 (2). About a week later I got the 0x2d crash. I saw that it’s SDCard related, and since it’s the original SD card, and it’s 9 years old, I replaced the 128MB card with a 4GB card that I had around yesterday. This morning the Opensprinkler crashed again with the 0x2d error.
It seems odd that I’d get this on a new-ish card, so looking for any other suggestions or advice.
Make sure the SD card is formatted to FAT32 and not other format. You can always reformat the SD card and try again.
As the attached file shows OS 2.3-AC and it’s been showing this error 0x2D frequently. The ethernet lights are 1. Green 2. flashing yellow but I lose connection to my router. A power recycle quickly fixes everything. Should I assume the SDcard is failing and change it out? Recommended size please?
The controller has been inplace for many years without needing any repairs. I’m guessing it came with a SDcard installed? I sure don’t remember opening the unit up but as I say it’s been a long time since I had to do anything to it, other than firmware updates.Thanks, Ron
Attachments:
Error 0x2D is due to SD card issues. It has nothing to do with wired Ethernet. Yes, try to change the microSD card — it’s located close to the top edge of the circuit board. Any size is fine, probably 4GB and 8GB is the most common, you almost can’t find anything smaller, and larger is more expensive.
Also, I would highly recommend you to upgrade your firmware to 2.2.1(0). Your current firmware 2.1.9 is outdated and has known issues with the current UI/app. Upgrading to the latest firmware will solve this problem.
https://openthings.freshdesk.com/support/solutions/articles/5000381694Just a follow up for those who may stumble on this tread.
Opened up the case and found the SD card (128mb!!) Put in a 4gig card to replace it. Expelled the spider living inside the case and it’s cobwebs. Closed everything back up. Updated the firmware to 2.2.1(0). A few hick ups getting that sorted. The help file needs a tiny amount of updating for those of us who are not very savvy with this stuff. The unit is again rock solid, thank you Ray!
- You must be logged in to reply to this topic.