HP-2: HP-2 Mass Storage not connecting properly

[wilbeer]

New Homepatrol 2 unit

• operating as expected (pretty much a terrific scanner)
• sentinel installed and working as expected

Problem

• Plugged in USB (uniden cord) only supplies power. No communication with device to sentinel (PC not mac)
• Randomly allows Mass Storage window to operate with a different USB cord. Different cord allows power always no problem, but infrequent with Mass Storage window.
• updated my drivers, no change in connection
• checked USB port with other devices and it works fine

Any help would be greatly appreciated.

 

[mc48]

Try some contact cleaner or Isopropyl alcohol on contacts of cord and HP2, remember some contact cleaners will melt plastic.

 

[wilbeer]

Seems like an easy enough attempt. I'll give it a shot. The cord was brand new out of the box though. It would seem things should have gone smoothly on the first couple connections. Even with using a different cord I get the same results. Power supply works great. PC comms not so great.

Try some contact cleaner or Isopropyl alcohol on contacts of cord and HP2, remember some contact cleaners will melt plastic.

Thanks for the input

Should have mentioned earlier I'm using Windows 10 if that's relevant.

 

[mc48]

Windows 10 is what I'm running, are you using the correct version of Sentinel? The HP series is the orange shield version.

 

[wilbeer]

Yep, orange sheild, update 12/26/2021.
Sentinel works fine on it's own.
When I do get Mass Storage to connect (rare) both sentinel and scanner function properly
Trouble seems to be between the two conneting
Looking at drivers now to see if that is the source.

Windows 10 is what I'm running, are you using the correct version of Sentinel? The HP series is the orange shield version.

Thanks any help right now is appreciated

 

[phask]

Watch device manager when you plug it in and see what it does if anything.

 

[wilbeer]

Watch device manager when you plug it in and see what it does if anything.

Thanks for the tip

 

[wilbeer]

Just a follow up
May have found the solution
Drivers and USB native(?) ports
All systems fully operational at the moment