I performed some unscientific testing on my own on when these scanners seem to reboot while using the recording feature. I've used 32gb, 8 gb High Endurance SD cards as well as 4gb, 16gb, 32 gb Scan Disk SD cards and results seem to be very similar.
On my (2) 536hp scanners, the Memory used on the Scan Disk card was highest coming in at 87% with the 4Gb SD card. The 16Gb card it made it to 56%, while the 32 GB card it came in at 11%.
The rebooting started when the record files reached 500 (5,000+) files of saved recording on all SD cards.
On my SDS100, the Memory used on the High Endurance 8 GB card was at 58% while the 32Gb High Endurance card was at 26%.
The rebooting started when the record files reached 700 (7,000) files of saved recordings. I performed tests twice on each card.
I have submitted my programming and debug files to Uniden for analysis so this isn't a complaint, but more of passing along information for any current or future users. The first time it happens I used to assume it was an issue with a possible electric current. I have posted on this in other threads, but this time was my unscientific approach.
It's not about Memory usage, but saved recordings appear to be the culprit. I suspect it's related to CPU overload and the record feature. While it's easily resolvable by deleting recordings, it can be easily overlooked my those who are new owners and panic mode might set in.
On my (2) 536hp scanners, the Memory used on the Scan Disk card was highest coming in at 87% with the 4Gb SD card. The 16Gb card it made it to 56%, while the 32 GB card it came in at 11%.
The rebooting started when the record files reached 500 (5,000+) files of saved recording on all SD cards.
On my SDS100, the Memory used on the High Endurance 8 GB card was at 58% while the 32Gb High Endurance card was at 26%.
The rebooting started when the record files reached 700 (7,000) files of saved recordings. I performed tests twice on each card.
I have submitted my programming and debug files to Uniden for analysis so this isn't a complaint, but more of passing along information for any current or future users. The first time it happens I used to assume it was an issue with a possible electric current. I have posted on this in other threads, but this time was my unscientific approach.
It's not about Memory usage, but saved recordings appear to be the culprit. I suspect it's related to CPU overload and the record feature. While it's easily resolvable by deleting recordings, it can be easily overlooked my those who are new owners and panic mode might set in.
