I'm using a Dell Optiplex 3020 Micro that I got off eBay. Got that and my scanner, modem, and router connected to a UPS.
ProScan: Official Software Thread
I'm using a Dell Optiplex 3020 Micro that I got off eBay. Got that and my scanner, modem, and router connected to a UPS.
Problem with recording audio.
I have my audio set up so it can be recorded off my scanner but the recording is queing up a second too late. My recording is just not caputuring the first second of a transmission. Is there anyway to fix this?
I have my audio set up so it can be recorded off my scanner but the recording is queing up a second too late. My recording is just not caputuring the first second of a transmission. Is there anyway to fix this?
Set the Prepend Buffer option to 1 second. Located in the Options -> Recording tab.
Doesn't seem to be working. No matter what I set it to.
I'll look at it before the next release.
Error codes are more for my use. Most of them means that the connection broke between the server and client. The TCP protocol doesn't provide where the connection broke so therefore it's unable to indicate if the problem is on the server or client side.
If it's only one client that abnormally disconnects, that would indicate the client side.
If all clients then that would indicate the server side.
RSOIP requires a solid connection. Problem could be router ports, cables, NIC cards, etc.
Don't use AVG anti-virus software as that is known to interrupt TCP connections.
nwradiorick
Member
I have my SDS100 connected to proscan & it runs great.a problem occurs if I reboot my computer (win10 HP) and start up proscan (ver14.3) my SDS will not connect to proscan again until I disconnect and reconnect the USB cable. After reboot I looked in the device manager and it still shows the sds100 on comport 8. Proscan shows comport in use, I never had that problem with 436 or 536 scanners but iknow those have seperate serial ports, maybe thats why?
Has anyone else experienced this.
Thanks
Has anyone else experienced this.
Thanks
jasonhouk
Member
Are you rebooting while ProScan is still actively receiving data via the port?
Sent from my Moto G (4) using Tapatalk
Sent from my Moto G (4) using Tapatalk
nwradiorick
Member
Im closing proscan first then rebooting. im goin to try another pc tommorow and see if same problem occurs
Thanks
Thanks
Yes, but with two 536's on a high-end Dell PC running Win10. I think it has more to do with the USB drive and not ProScan.
I am running 4 536's (wifi) 4 996p2's 9 pin serial 4 15X's 9 pin serial and 1 785D 9 pin serial all on a Dell optiplex 990 I5 CPU 8GB Ram all at the same time. That is 13 total scanners on 1 PC.
I meant to say USB port, not drive. The PC has dual 8-core processors and 32GB of RAM.
Same here with the same amount of radio's. Mostly hardware serial ports via 4 and 8 port boards though but also have eight FTDI based serial adapters. Never experience any issues with ProScan on this machine using any mix or quantity of USB or standard serial ports. I did not downgrade to Win 10 though, I stayed at Win7 64 bit.
I am running 10 64 bit PRO
I have a difficult enough time with two. It seems windows 10 likes to drop drivers and mix things up at times, especially when you introduce USB audio devices. How do you keep them all locked in place?
nwradiorick
Member
Thanks for the input
I tried another PC Win7 64 and same thing. I also have combo of 8 536 and 436 scanners with no problem on same PC. I tried changing the Comport to NONE restarting and still nothing, only happens to the SDS100 scanner. It would be nice if i could use the other USB serial port on the SDS100.
I tried another PC Win7 64 and same thing. I also have combo of 8 536 and 436 scanners with no problem on same PC. I tried changing the Comport to NONE restarting and still nothing, only happens to the SDS100 scanner. It would be nice if i could use the other USB serial port on the SDS100.
jasonhouk
Member
Verified the same reboot issues tying up com port and submitted a bug report to the beta group.
Houk
Houk
You may want to include the BCD996P2 and BCD325P2. Same driver and same symptom
