Hi all!
I had an interesting issue with upgrading my BCD325P2 to the latest firmware this evening as the BC_VUP3 Firmware Updater would consistently lockup upon selecting a COM Port and clicking “next.” I felt it was safe to force close the program as (a) nothing indicated active connectivity on the scanner’s screen, and (b) the Windows Task Manager was showing no activity even after waiting for several minutes. So, I took to the web, but the best thing that I could find is a decade-or-so old post advising to ensure that you have a bidirectional sync cable as that will somehow allow a “handshake” that will correct the problem.
The thing is, that post was in fact half-true as the cable did have to communicate back-and-forth to allow the next phase to begin, but the issue was not my cable at all. I had an idea to check the Device Manager settings for the selected COM Port and it immediately stood out to me! The “Flow Control” setting was off, rather it only needing to be changed to “hardware!” Once you apply hardware flow control instead of no flow control at all, you are allowing the hardware to say “hey, I’m here” from one direction to the other, so both pieces are satisfied in knowing that their partner is waiting for a connection to be established! I subsequently verified that ProScan remains to work as expected.
So, if you experience this unusual lockup while attempting to update your scanner to the most current software version, it’s likely a simple tweak that could be resolved with the change of only a single setting! No cable swapping should be required! Hopefully this will save someone some significant time as this was admittedly a bit confusing at first, but fortunately my undergrad was in Comp Sci and I had a hunch as they say!
Good luck!
I had an interesting issue with upgrading my BCD325P2 to the latest firmware this evening as the BC_VUP3 Firmware Updater would consistently lockup upon selecting a COM Port and clicking “next.” I felt it was safe to force close the program as (a) nothing indicated active connectivity on the scanner’s screen, and (b) the Windows Task Manager was showing no activity even after waiting for several minutes. So, I took to the web, but the best thing that I could find is a decade-or-so old post advising to ensure that you have a bidirectional sync cable as that will somehow allow a “handshake” that will correct the problem.
The thing is, that post was in fact half-true as the cable did have to communicate back-and-forth to allow the next phase to begin, but the issue was not my cable at all. I had an idea to check the Device Manager settings for the selected COM Port and it immediately stood out to me! The “Flow Control” setting was off, rather it only needing to be changed to “hardware!” Once you apply hardware flow control instead of no flow control at all, you are allowing the hardware to say “hey, I’m here” from one direction to the other, so both pieces are satisfied in knowing that their partner is waiting for a connection to be established! I subsequently verified that ProScan remains to work as expected.
So, if you experience this unusual lockup while attempting to update your scanner to the most current software version, it’s likely a simple tweak that could be resolved with the change of only a single setting! No cable swapping should be required! Hopefully this will save someone some significant time as this was admittedly a bit confusing at first, but fortunately my undergrad was in Comp Sci and I had a hunch as they say!
Good luck!
