Just fired up an S3+ today which came with the antMiner_S320141126.bin and as prior posts indicate it would stop hashing (~47Gh) after a few hours. I thought it was bad hardware, but I had also upgraded 5 other S3 & S3+ today to the same firmware and they each began doing the same thing.
Uploaded antMiner_S320141024.bin and things are pretty normal.
Try upgrading to the latest antMiner_S320141126.bin firmware and then ssh in and execute this command.
cp /overlay/etc/config/cgminer /tmp/cgminer.tmp && cp /overlay/etc/config/network /tmp/network.tmp && rm -r /overlay/* && mkdir /overlay/etc && mkdir /overlay/etc/config && cp /tmp/cgminer.tmp /overlay/etc/config/cgminer && cp /tmp/network.tmp /overlay/etc/config/network && reboot
This should clear out most bad configs and preserve your network and cgminer configs.
You may also want to execute this to set your voltage
uci set cgminer.default.voltage=0725 && uci commit
and this to set your frequency.
uci set cgminer.default.freq=18:225:0882 && uci commit
These all seemed to fix any low hashing S3+ I had on the newest firmware.
Turns out this didn't completely fix it, the issue is that the pic firmware from this build is very unstable. You can fix this by flashing the pic firmware from the antMiner_S320141013.bin firmware. To retrieve the stable pic firmware first flash the antMiner_S320141013.bin firmware to your miner, do not retrieve from any other firmware version especially antMiner_S320141024.bin(the pic firmware is identical to antMiner_S320141013.bin but very tricky to retrieve due to the filesystems being built incorrectly).
To retrieve the firmware scp it to your computer using the following command. This assumes your miner is still on the default IP of 192.168.1.99 .
scp root@192.168.1.99:/rom/etc/config/miner_pic.hex miner_pic.hex
Next Flash the latest antMiner_S320141126.bin firmware and upload the file back.
scp miner_pic.hex root@192.168.1.99:/etc/config/miner_pic.hex
Finally reboot your miner to apply the stable pic firmware.