I can't get RS3 or SmartyManager 2 to see my SC HD. I updated to Windows 10 about a month ago and don't know if this is the problem. My software and firmware is up to data. Any help would be appreciated.

 

Not having any issues with RS2/3 and SM2 on Windows 10 with SC HD.

While connected to PC and RS3 running, have you power cycled the SC HD?

Have you tried reinstalling RS3/SM2 after upgrading to W10?

Can you read the microSIM outside of the SC HD on your PC?

Jerry Austin is a good FL source to chat with on this.

 

Kein - thank you for the response. I've power cycled both the SC HD and the PC several times. I haven't tried reinstalling RS3/SM2 since installing Windows 10 and I can read the microSim on the PC. When I plug the PC into the SC HD I hear a chime so it knows something is attached. That leads me to think it's a software problem. I know Jerry well and will talk with him.

Rich Barbieri

 

Just to add to the diagnostics, I attached the SC HD to my laptop which is running Windows 7 and it was immediately recognized. On the laptop I'm running RS 3.03.17 and on the PC 3.08.10.

 

I'm not at my computer to tell you exactly where to look, but go into the control panel and then to the devices page. You will probably see a problem at the USB drivers. Click on it and tell it to look for drivers. That should fix it.

 

Matt - no problems showing in Device Manager. it says that all USB drivers are up to date.


Rich

 

If it's not showing a driver problem and it shows connected, I'm not sure where the problem is. I would suggest calling into AiM and seeing what they say. They field the most calls with problems like this.

 

Call Roanoke or the 800 number and ask for Robbie or Chad.

Although the fact that it works fine on your Win7 computer and not on your new Win10 indicates it's a computer-specific issue...

 

Will do. Thanks for the advice.

 

I agree, if it were me I would uninstall RS3 and reinstall on the Win10 machine and go from there..

 

This might be a bit of a reach but just in case...

I have a device in my car that has USB hookup that apparently refuses to talk to Win10 even though I hear the chime for the "connect". In the end the way I fixed it was to plug a USB2 (_not_ USB3) hub into the PC and then plugged the device into the hub -- voila...no problem. Turns out the Win10 machine in question has no USB2 port (Surface Pro actually).

If the port you are using right now on the Win10 PC is USB3 you might try the older hub trick.

 

Mark, I think you're on the money! I have a Surface Pro 3 and my port doesn't have enough juice, maybe?

 

USB3.0 has more power than USB2.0 http://arstechnica.com/gadgets/2011/...-be-a-reality/

USB3.0 is supposed to be be backwards compatible, but maybe that is the problem. I would be interesting if the hub made it work.

 

USB3.0 is spec'd to allow for more power, that doesn't mean the device running the port always delivers full spec If this 2.0/3.0 thing is the issue though my guess is it won't be down to power.

Yes, 3.0 ports are supposed to be compatible with 2.0 (or earlier) devices. It's hard to mess up the initial device recognition (so, you hear the chime for a connection from the OS) but once the device's specific driver(s) get loaded...well at that point, there are things one can do in USB 2.0 device code that will not work properly on USB 3.0 ports with 2.0 devices. For cases where this happens the only known fixes are: 1) use an older hub interposed; or 2) get the device manufacturer to spin their code for 3.0 compatibility. Obviously the latter is harder to get done...

 

That's the issue James Colburn, Roger and I have had on our SP3's...