alarmdecoder.com

Hi,

I am running Windows 10 Pro build 10586.36 on Intel NUC NUC5i7RYH. The OS is a new install with default settings. I updated the Intel drivers and ran Windows update.

On connection, AD2USB is recognized as a USB Mass Storage Device. I've tried installing drivers using AlarmDecoderApp_windows_2_0_10, and then, following an uninstall, using FTDI's driver package CDM v2.12.10 WHQL Certified. Neither results in a visible, accessible COM port on the system.

I've run the Windows 10 hardware troubleshooter. I've uninstalled all items under USB Controllers in Device Manager and restarted the system. Neither led to discovery of the AD2USB interface. I've also tried two different known-good USB-to-USB mini cables with no success. I've connected the AD2USB to all three of the USB ports on the NUC with no luck. All three ports work with other USB devices (e.g, mouse/keyboard)

AD2USB is connected to my Ademco 20SE per the install instructions and the green heartbeat light is blinking.

It appears AD2USB should work on Windows 10 given FTDI's recent driver update. Given that, I suspect incompatibility with the NUC or faulty hardware in the AD2USB module. Is there any reason to believe I should NOT be able to use AD2USB with Windows 10 or the Intel NUC?

Any advice on how to proceed with troubleshooting will be appreciated.

Cliff

No reason I can think of that it wouldn't work in that configuration, but it is definitely not something we have tested.

Can you try hooking it up to a regular PC, such as a laptop and see if the results are the same?

I connected with a Lenovo X230 running Windows 10 Build 10586.36. The laptop had an Intel serial over LAN port installed prior to installing AlarmDecoderApp_windows_2_0_10. In any case, I connected AD to the laptop and ran the AlarmDecoder Keypad installer.

The installation created no new COM port, so I attempted to use the Intel SOL COM3. I was unable to connect to AD using putty on COM3, 115200/8/N/1. There was no response to key inputs and no output related to input on a separate physical keypad.

The Keypad application, however, shows some level of communication with AD:

Starting AlarmDecoderApp build #2.0.10.40818
1/5/2016 10:13:05 AM Loding modules. To remove modules use the modules tab under the about menu
1/5/2016 10:13:05 AM Example V1.0 initialized
1/5/2016 10:13:05 AM keypad V1.0 initialized ()
1/5/2016 10:13:05 AM MyStuff V1.0b initialized
1/5/2016 10:13:11 AM Waiting for communication to AlarmDecoder to open
1/5/2016 10:13:11 AM Opening com port: 'COM3'
1/5/2016 10:13:11 AM Communicaiton to AlarmDecoder established
1/5/2016 10:13:11 AM Trying to make sure we are not in config mode sending \r\n A Bunch!
1/5/2016 10:13:14 AM Sending '\r\n' to check if in config mode.
1/5/2016 10:13:14 AM The AlarmDecoder not in config mode. Continuing to initialize.
1/5/2016 10:13:15 AM Sending 'V' command to the AlarmDecoder
1/5/2016 10:13:19 AM Timeout waiting for !VER message from the AlarmDecoder
1/5/2016 10:13:20 AM Sending '\r\n' command to the AlarmDecoder

I tried disabling xHCI support in the BIOS to force the USB 3.0 ports to USB 2.0, and different combinations of enabled/auto/smart auto, followed by reinstalling the driver. Nothing helped.

Are there any known problems with AD2USB and Intel chipsets? I've seen some chatter on other boards to that effect, but nothing official.

Cliff

I have not heard of any issues with regard to the ad2usb and intel chipsets.

I am leaning toward a defective device - but do you have any computers that aren't windows 10 to test with? I haven't heard any issues with windows 10, but haven't tested it personally - just want to rule it out.

If you can't, that's fine, email ad2usb@support.nutech.com to setup an RMA.

I should be able to put Win7 on the NUC tomorrow and test it. If it still fails to connect, I'll proceed with the RMA.

Cliff

I put a new drive in the NUC and installed Windows 7 Pro SP1. After installing AD Keypad package with the AD connected to the NUC, there's still no COM port available...looks like a hardware fault, so I'll proceed with an RMA.

Thanks for the troubleshooting assistance, Kevin.

Cliff

Great, just email ad2usb@support.nutech.com and we'll take care of you

Just include a small description of the problem as well as your return address. If you do it in the next hour, I can get it out today, even.

Edit* Confirmed AD2USB does work in Windows 10.