Skip to content
HearingTracker
Log in

Noahlink wireless computer connectivity issue

This topic is closed.

43 replies5.2k viewsLast reply

Jump
Link to this topic

Hi, all,

I purchased a Noahlink Wireless box, but it’s giving me trouble. Nothing to this thing, and I’m a computer scientist, so I feel like a bit of a failure here. I got it used from Ebay, and it came without cables, but I have a ton of USB A to B cords around from the days past of USB printers. Unless there’s something special about the cable that comes with it, I don’t think that’s the issue.

When I plug it in, Windows 10 does its usual ding indicating a USB device was plugged in then pops up that “the last device you connected malfunctioned, and Windows does not recognize it.” Heading over to control panel, I see the device with a code 43 and the message:

A request for the USB device descriptor failed.

I’ve tried multiple cables and USB ports. I’ve already got the fitting software installed, and I tried with both the software open and not open. I even went to the Noahlink Wireless download sitea nd downloaded a driver which I shouldn’t have needed to do since it should have been installed with my fitting software. Still no luck.

Anyone run into this before and have any suggestions? It’s entirely possible that the used Noahlink Wireless is deffective, though the seller claims it was tested. They do have a 30-day return policy, but I want to make sure it’s truly the device’s fault before I go down that route.

Thanks for any advice!

13 people in this conversation22 min readJump to latest

So after all that, have you actually tested it through your software? Can you connect to your HAs? That’s all that matters, I don’t know what the windows issue is, but I don’t use the original USB cable on mine ether.

Mine did not work until I updated the software after installing the USB drivers that came with it. While I can’t remember the exact steps, I know the statement that driver with fitting software was all needed was NOT true. Mine was new and hit had installation software on a paper USB drive which I thought was kind of cool, cheap but cool :laughing:

@dkoldman said:

Mine did not work until I updated the software after installing the USB drivers

Well your the first to have this issue like that,but it’s not the Noahlink as such, it was the windows version, the Noahlink wireless is plug and play right out of the box, mine was brand new as well and I just used an existing USB cable, the original USB cable is still in the box, I’ve plugged the Noahlink into 5 different PC/ laptops and not once did I need the installation disc.

Edited

The fitting software normally has the NoahLink drivers with it and installs them automatically. So what you are supposed to do is install the fitting software then after that connect the NoahLink Wireless, which uses the correct driver that is now installed.

You may need to uninstall the NoahLink Wireless to get it to give up being associated with the wrong driver. Then start again with fitting software first (or at least the NoahLink Wireless drivers first). You can download the NoahLink drivers from the HIMSA website.

The original cable has a couple of ferrite slugs on it, one at each end, to keep the interference between the PC and the NoahLink Wireless at a minimum.

image

I did this the other way around. I connected it to my computer and found the HIMSA device in Device Manager (not under USB devices). Then I installed the fitting software and did the check for the device in there after installation. I didn’t install any drivers. It just did it on its own.

Could well be one of the above. Another possibility is another attached USB device messing things up.

In reply to @tenkan

I am not the first to be the first; nor do I expect to be the last to be the first :rofl:

I have Windows 10. and Target 7.2.1 was preinstalled. It did NOT work. I was just giving the poster another option as the instructions were clear and plug and play is foolproof; but mine did not work. As you might imagine there is no real help available, so I ventured into the USB drive that came with the Noahlink. Presumably it was just for the Owners Manual in a million languages, but it did have install utility and I ran it; went back to Target and it has worked every since. FWIW I used the USB cable that came in the box. Thus far I find the Noahlink Wireless to be incredibly efficient. I am looking to learn more about Target because thus far I have already resolved 3 problems that were previously back and forth with Phonak and finger pointing.

Thanks, all, for your suggestions. I wish it was as simple as selecting the device in the control panel and updating the driver. As I mentioned, when I connect the device, it never shows up in the control panel as a HIMSA Noahlink Wireless. All I see is an unknown USB device, andwhen I click on the device, under the general tab it shows a code 43 and that “device descriptor request failed”. So, I don’t really have any device I could uninstall other than the unknown device.

I tried downloading the drivers from HIMSA and installing them with the same result. I presume these are the same as the ones that come on the USB drive that several of you mentioned.

I’ve tried multiple USB ports and cables. I even tried a different computer that had no other USB devices connected. Same result.

I’ll pursue a replacement device at this point unless anyone else has ideas. Thanks for your suggestions.

So just to be sure, did you try installing the Noahlink on another PC/laptop to see what happens?

Yes, I did. I tried it on a different computer that had no other USB devices connected. Think I mentioned this in my last reply. That computer also didn’t have the driver installed, but I’d have expected a different error if the driver wasn’t installed. The error was the same as on the first PC: Windows reported that the device malfunctioned, and digging into details in Device Manager reported that the request for the USB device descriptor failed. Unless I’m mistaken, if Windows can’t get a device descriptor from the device, it’s not even to the point of trying to find the right driver. I don’t think any driver monkeying could fix that. If others believe that’s not true, please let me know. Otherwise, I’ll pursue a replacement or refund from the Ebay seller.

Thanks, everyone, for the suggestions. Super glad I’ve found this community. Since the only other hearing aid wearer I know is my mother, and she’s not known for her technical advice, it’s great to have found some fellow DIYers and people to troubleshoot with.

Yeah looks like a return could be your best bet, so what software have you installed, is it target or another brand?

In reply to @keith

From what you describe, returning is your best bet. No way it is even that hard. I had trouble as you did as my did not recognize. I knew it was suppose to but it didn’t, I did try to tinker with anything in control panel because directions were clear. But my unit came with software on a USB drive. I suspect you didn’t have that because yours was used. With Used anything could have happened? My fix was five minutes. I put the paper USB drive that came with my new unit to read the manual and I saw the install program that was no were mentioned in the instruction. I ran it (took about a minute) and restarted Target 7.2.1 and presto it saw it and life has been good. For the money that Noahlink Wireless is a really great buy, it is worth what ever it cost to get a brand new one. I think most buy them for the end game convenience. The Phonak experience is greatly amplified if the hearing aids work, I am 100% convinced that without a Noahlink Wireless it is impossible to get satisfactory experience

Thanks, @dkoldman. Would you or anyone else who received the paper USB drive be willing to share a copy of the driver installer with me that was on it? Perhaps just send it to me through Dropbox or whatever suits your fancy? I suspect it’s the same one that I downloaded from this page: Noahlink Wireless Downloads – HIMSA26
I’ve tried installing that with no change. Like I said, the fact that the device fails to respond with a device descriptor sounds like the end of the line for this device to me, but I’d love to be proven wrong on that.
I’ve emailed the Ebay seller to see if they have another unit and would be willing to do an exchange with me. I don’t expect a response until Monday. If I don’t hear back by later next week, I’ll just pursue a return and look to buy another. And yes, you’re right; probably best to spend a little more to get a new one. For $50 more, I could. Just figured this was worth a try since I didn’t think I needed a driver disk, and heaven knows I didn’t need another USB A to B cable.

I pulled my Paper USB which is actually in a fancy little package that is nice touch by HIMSA. It is version Driver_NLW_V.1.1.0.0 I then compared what you downloaded and it is the exact same thing. So you have dun good :+1:

It also reminded me that I had the exact same issue with not only my Desktop but my laptop. I had written my self notes on the packaging for the paper USB drive s here is repeat of my exact steps.

Desktop & Laptop

  1. Install 7.2.1
  2. Would NOT recognize the Noahlink Wireless, when plugged into the USB ports
  3. Ran the application Driver_NLW_V.1.1.0.0 off the paper USB drive
  4. Went into Target 7.2.1 an updated Firmware within Phonak Software
  5. Plug USB cable in a Presto !!!

I repeat I had to so on both machines :confounded:, so I am not buying so much those that say no issues. I agree that it should be simple, but I don’t see how you install it wrong based on the instructions, so there MUST be some issues when it don’t work. The fact that I got the EXACT same results on two different machines is telling. It is also worth noting that the Manual nor the instructions with the paper USB packaging ever said to run the Install Application off the USB drive :thinking:

If you get bored while waiting to replace you may try uninstalling everything and reinstalling in order I had to… But given your expertise, I would still consider to return and buy new elsewhere; because when you do get it working, you will love it. In my mind it is dirt cheap for what it does and has already paid for itself within 1 week.

One other thing, it looks like a very high end & high quality USB cable? It has not one; but two of the conductor shields on both end about 4 inches from the connector.

In reply to @keith

Ok so this is so simple, when you plug the Noahlink into the USB port, do the green led light up and flash? The fact that 99% of us don’t have an issue getting it up and running is telling, the most common issue is incompatibility with the version of windows you happen to be using, but in your case could well be the Noahlink, but you’ll find out soon enough when you get your replacement.
Do follow the advice given about how to install and remember to actually check within the software (not windows, don’t worry about what it tells you) always use the software to confirm whether in fact the Noahlink is working correctly or not.
Again nothing wrong with following what @dkoldman suggested if you get bored ; ) have fun.

In reply to @dkoldman

Thanks, all, for continuing tohelp me with this. A few more clues which, I think, point to a defective device.

The firmware updater available from the HIMSA downloads site reports:

No Noahlink Wireless device found. Please check that it is connected.

The Target software tells me it couldn’t find a Noahlink wireless. I tried both of these in hopes that the suggestion from @tenkan of ignoring what Windows says and just try to use it would pay off.

And to answer the question about the lights, they both turn green when I plug it in, but as soon as Windows reports the error about the device malfunctioning, the lights go off and stay off until I unplug it and plug it back in. They’re on for roughly a second. If I recall the manual correctly, they’re supposed to stay lit. Is that correct?

When you all say Windows incompatibilities, I’m running the latest stable build of Windows 10 64-bit. I can’t imagine an OS incompatibility issue, especially given that I’ve used a wide range of other USB devices with the computer with no issue. And it’s pretty standard hardware, too: a Microsoft Surface Pro 5 connected to a Microsoft Surface dock. The other computer I tried it on, a Surface Pro 3, was not connected to a dock and had no other USB devices connected, and it gave me the exact same error…

@dkoldman, when you said in your steps above “2. Would NOT recognize the Noahlink Wireless, when plugged into the USB ports”, what did you mean by that? Did it show up in Device Manager at all? Did it ding when you connected it? Did it give you an error? I’m wondering if it’s what I’m seeing with the Unknown USB device listed and the “Request for device descriptor failed” message, or if it was something different.

Thanks again, all, You are a great bunch to connect with! I’m working on getting a new one, but the next best deal is from China and looks like it’ll take a few weeks to get here. I’ll hold on to this one for another week or so before returning it in case you all have any other suggestions. From what I understand, though, this is not supposed to be this hard. So, I’m still suspecting a faulty device. I’m very interested to hear what the Ebay seller has to say when they respond in the next couple days.

@keith,

Error I got is attached. The Target software simply said no connection. I did not go into Control panel or Device Manager to troubleshoot. Instead I went to my laptop and got the exact same error. I tried to get help, but like my previous issues with Phonak I got nothing but try another Audiologist :rage: Maybe you and I are the only ones that downloaded the exact specific version of 7.2.1 that did not work because across us both we have confirmed 4 machine that did not work out the box per instructions. :thinking:

So to troubleshoot on my own, I started with wanting to read the manual that came on the paper USB drive, in doing so; I saw the firmware installer, so I ran it. when finished, I went back into Target and it immediately noticed that I needed a firmware upgrade when I
tried to connect, so I ran that upgrade from the Target software and problem solved. I then did my laptop and it did the exact same thing as it worked without issues. I wrote down my notes should I ever need to repeat.

In part of why I say do a complete uninstall, because what I do agree with; it should be easy and should NOT require anything from anyone. In my book my install was successful too, it just that I had to run the Firmware Installer that came on my paper USB drive and then have Target run a internal update. I wouldn’t do anything within Control Panel or with the driver itself.

error

Thanks, @dkoldman. Looks like my mileage varies slightly. Sounds like you didn’t get an error from Windows when you plugged in the device initially; it just didn’t recognize it. For me, I get the “The last device you connected to this computer malfunctioned, and Windows didn’t recognize it” message popping up. Only other time I’ve gotten that was when plugging in old USB thumb drives that were broken or extremely old, and that’s been very rare.

So, trying the next step just in case the installation of Target had installed some funky driver, I removed Target, rebooted, then plugged in the device and opened the Noahlink Wireless firmware update utility. When I plugged in the Noahlink wireless, I got the same error from Windows popping up. And when I opened the Firmware update utility, I was told that no Noahlink wireless devices were found.

If I understand correctly, you didn’t get an error from Windows when you plugged in the device; Target just didn’t find it. And the Noahlink firmware update utility did find it. Is that correct?

Only other thing I could do is install an older version of Target; I still have the installer for 7.1, as well. But I’m fairly convinced at this point that won’t get me anywhere different from where I am now.

FWIW, I’ve tried the device on both USB 2.0 and 3.0 ports; the Surface dock has some of each. No difference either way. Nothing that I’ve read said this is a USB 3.0 device, and it should work with either version of the USB ports. True?

Related discussions