Yes i have the same problem an Bob said this issue was fixed and will be in the next release of Proscan
Here’s a little more info about my web server issues. I can only guess that it started from some other recent non-ProScan Windows 10 System or application update, because I can’t recall it happening for some time after I installed 17.8.0 some months ago. My issue seems to be around a lagging in Control and Super User modes, where I may have to refresh my browser to “maybe” regain control of scanner. Tried different browsers and “push” and “pull” updating to no effect. I think I might be seeing it happening on downgraded 17.0 too, so that’s why I think it is some update outside of ProScan, in my situation. I’m not having any problems just listening and monitoring, and no eventual lockups or crashes. Just a lagging or non-responsive “Control” and/or “Super User” modes on button presses.
It would help if you told us what model scanner you're talking about, but as far as getting audio through the serial/USB connection, the answer is no regardless of model.
Because, There will always be only four numbers, after the decimal point('.') in Proscan. Regardless of whether you see three or five #'s after the decimal point in the RRDB. If you only see three(851.750), a '0' gets added. If you see five numbers(769.90625), the '5' gets chopped off and becomes 769.9063. Because a 5 gets rounded up to the next 'fourth' number. If it were 769.90875, that would become 769.9088. Do you see the pattern?
Fixed my (not ProScan Web Server after all) issue, and it makes sense. Posting here to reiterate what Bob has said time and time again. Using an older RS232 cable (DB9 to DB9), I needed to reduce my scanner rear port, PC com port (Windows Device Manager), and ProScan configured baud rate down to 9600, as this older RS232 cable was from those days. And that explains why ProScan was sometimes showing broken scanner display and occasional non-response to browser web page management of my BCT15.
I always advise to use the highest baud rate that the scanner supports. The baud rate setting in the Win Device Manager has no effect. Just change it in the scanner and ProScan.
Yes. To clarify my earlier statement of “reiterate what Bob has said time and time again” was meant to remind us all that most issues users have with ProScan are related to incorrect or mismatched baud rate settings.
And it works so much better at 19,200 Baud using a USB to RS232 adapter.
Please disregard. Firewall issue. If anyone uses NordVPN and has this issue please open the app and allow the firewall to access local network.
You're very welcome! Thanks.
