Hi all!
I have a few BCD436HP scanners. Different HW versions manufactured in different years, from 2015 to 2017. Different firmware versions, including latest .31. But problem is the same — in Discovery mode they spontaneously stop discovering and exit in Scan mode. In this case current session Discovery data become empty
Here is what I tried:
- Removing all data from card
- SD card format
- SD card replacement with brand new ones, including SanDisk Class 10 cards
- New and fresh batteries, including Li-Ion
- External USB power connected and disconnected
- Different USB power adapters
- Different USB cords
But no luck! The only difference I noticed – interval from Discovery start to Discovery crash. It varies from 30 minutes to a few hours (maximum). My personal record is 2 hours.
Scan mode works just fine and can run for a few days with no issues.
Asked a friend of mine about it and he said that his BCD536HP is the same.
WTF?
A few questions to UPMan:
1. Is any solution available?
2. Is this bug confirmed and admitted?
3. Are you working on it, or you’re with the head immersed in a new multi-colored scanner?
I have a few BCD436HP scanners. Different HW versions manufactured in different years, from 2015 to 2017. Different firmware versions, including latest .31. But problem is the same — in Discovery mode they spontaneously stop discovering and exit in Scan mode. In this case current session Discovery data become empty
Here is what I tried:
- Removing all data from card
- SD card format
- SD card replacement with brand new ones, including SanDisk Class 10 cards
- New and fresh batteries, including Li-Ion
- External USB power connected and disconnected
- Different USB power adapters
- Different USB cords
But no luck! The only difference I noticed – interval from Discovery start to Discovery crash. It varies from 30 minutes to a few hours (maximum). My personal record is 2 hours.
Scan mode works just fine and can run for a few days with no issues.
Asked a friend of mine about it and he said that his BCD536HP is the same.
WTF?
A few questions to UPMan:
1. Is any solution available?
2. Is this bug confirmed and admitted?
3. Are you working on it, or you’re with the head immersed in a new multi-colored scanner?