Noahlink wireless computer connectivity issue

Hearing Aid Self-Fitting and Adjusting [DIY]
#18

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.

#19

@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

#20

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?

#21

You are 100% correct.

[Keith] If I understand correctly, you didn’t get an error from Windows when you plugged in the device; Target just didn’t find it. [dkoldman] Yes, I saw no Window’s issue and Yes Target could not find it.

[Keith] And the Noahlink firmware update utility did find it. Is that correct? [dkoldman] Yes and later after the firmware installed Target 7.2.1. found it too.

The version of Target I have is [PhonakTarget7.2.1.63245.exe]

I have a Dell OptiPlex 390 Desktop and a Dell Latitude 7480

#22

The green lights only stay on when the device is actually talking to your hearing aids and so the lights coming on briefly when you plug it into the PC USB port is correct behaviour.

#23

You may want to consider how you perform Firmware Updates for Noahlink Wireless (Automatic or Manual): Personally, I prefer Manual.

Automatic Noahlink Wireless Firmware Updates by the Fitting Software

As of the beginning of the year 2022; HIMSA says that it is not necessary to update the firmware in your Noahlink Wireless until the fitting software requires it. At that time the fitting software may prompt for the Noahlink Wireless firmware to be updated, or the company will notify you it is time to upgrade. Well DIYers don’t have a company. So, there’s that! Also, how does the fitting software make the call that your Noahlink Wireless requires a firmware upgrade? Does it do so gracefully, or does it give you an error like this Phonak Target error that says;
aa

Perhaps nothing graceful happens and you will get the above error, or a similar error. If you encounter this type of error, then shutdown your fitting software and follow the advice to re-install your Noahlink Driver using the (Noahlink Wireless Driver Installer from HIMSA). After installation of the Noahlink Wireless driver, and upon restarting your fitting software you will likely be prompted to perform a Firmware Update on your Noahlink Wireless device. Sorry to say, this automatic Noahlink Wireless firmware update procedure doesn’t seem very automatic at this point in time??

Manual Noahlink Wireless Firmware Updates

On the other hand!!, if you want to manually keep your hearing aid programming device updated without the ungraceful errors, HIMSA also says that you can upgrade to the latest Noahlink Wireless firmware before the upgrade is available in the fitting software. It is safe to do so because Noahlink Wireless firmware is always backwards compatible with previous firmware versions, meaning that you can safely upgrade your Noahlink Wireless firmware without worrying about losing the connection with your fitting software.

You can manually bring your Noahlink Wireless firmware up-to-date by scrolling down to the very-bottom of HIMSA and download the Noahlink Wireless Firmware Upgrader. As an additional bonus you can view the latest available Firmware version number before downloading, for example (v2.17 June 2017, v2.18 July 2018, v2.23 Jan 2022). I upgraded from v2.17 to v2.23.

Tip: Use your fitting software to display your current Noahlink firmware version and serial number information. Tip: Close your fitting software before running the Noahlink Wireless Firmware Upgrader to avoid conflict.

3 Likes
Confirming Widex Moment programming requirements
#24

You can use a linux live cd and run lsusb at the cli. You might have to install it depending on the cd you download. Here is what I see on my ubuntu mate 21.10 laptop.
Bus 002 Device 021: ID 16f0:0003 GN Hearing A/S Airlink Wireless Programming Interface

I will try again to run target with wine the next time the os upgrades. Then I can dump windows once and forever. LOL

Good luck

#25

Hi, all,

Following others’ advice, I returned the previous device that was giving me the USB device malfunctioning errors and ordered a new one. This one is new (thanks to those who suggested I skip the used route). It came from overseas and took a couple weeks to get here. But it arrived this afternoon. I plugged it in, and it shows up in Device Manager correctly! I plan to start tinkering this weekend.

Thanks to everyone here for the support and encouragement on this little project of mine.

2 Likes
#26

well, i have this stupid error as shown in your picture every time i restart my computer. i updated the firmware, used the latest HIMAS driver from their homepage (which is used by the device as i can see), but still: it will appear as “Unknown USB device” within Windows after a computer restart.

my “solution” is to unplug the Noahlink and plug it in again. after that it is fully recognized and can be used with Target 8.

when i have some more time i will dig a little bit deeper into this topic, but for the moment it’s good enough for me.

#27

That was the long version for using the link provided by HIMSA in case the link gets updated in the future. Here’s the short version;

  1. Download the Noahlink Wireless Firmware Upgrader → https://himsafiles.com/NoahlinkWireless/NLWUpgrader2.24.exe
  2. Run the downloaded file (NLWUpgrader2.24.exe)
#28

i did all that…doesn’t work for the issue i have :wink:

1 Like
#29

HMm; There is one more common driver problem that is described in DIY School PDF file named (Noahlink Wireless - DIY User Guide). But you should already be beyond this because you already fixed the driver problem and your problem just comes back after a restart? Thus I don’t know if this applies??

The root of that problem was that Noahlink Wireless was assigned to “Other devices” instead of being assigned to “HIMSA” and this Noahlink Wireless driver install fixed it → https://himsafiles.com/NoahlinkWireless/Driver_NLW_V.1.1.0.0.exe

Perhaps it may help to look at where (Himsa or other device) Noahlink Wireless is assigned before you fix it? Tip: The assignment takes place on my computer when I plug in my Noahlink Wireless. I don’t leave it plugged in all the time.

c1
c1897×508 90.7 KB

c2

#30

no, my problem seems to be different.

if everything is fine it will show up as HIMSA/Noahlink Wireless as shown in your second picture.
after a computer restart it shows up as USB Controller/Unknown device, and not as “Other devices” as in your first picture. then i have to un- und replug it and it will appear as HIMSA/Noahlink wireless immediately without any further action.

not to worry…maybe i have to use a different USB port on my computer or sth else is causing the trouble here (maybe i have to update the mainboard driver). as long as i can use it it’s not a big problem for me. :slight_smile:

#31

Having same issue myself, except that i purchased mine back in 2017, been using it on and off and finally it seems to have stopped working today.

One thing i noticed is that mine looks a little different to others, it has four silver connectors/pins at the back and the USB-B end includes a small rubber piece inside. I’m pretty sure i accidentaly bent the pins on the left side, i might just try and open it up and see if i can get better access to the pins and bend them back.

IMG_0129
IMG_01291920×1440 85.1 KB

IMG_0130
IMG_01301920×1440 75.2 KB

#32

In what way did it “stop working” did it just suddenly die while using or something else, as for the pins, are you unable to plug your cable in anymore?

#33

In the same way as the original poster, getting the exact same error, it was working a few days ago and then today it stopped, it no longer shows up as “Noahlink Wireless” anywhere on my PC or in the device manager. Regarding the cable, yes it still plugs in as before.

#34

I see, very unusual, well try the driver update, what windows version 11?

https://www.himsa.com/himsa_download/noahlink-wireless-downloads/

#35

Already tried the driver update and also the firmware updater, i also tried a few things mentioned in this thread like trying on a different PC etc, no luck, i doubt it’s the cable but i guess i could try my printer cable to see if that works, i’m on Windows 10.

#36

This are pictures from my Noahlink concector / cable

Noahlink1
Noahlink11346×459 123 KB

On your pictures it looks like that your connector is broken and the black rectangle part stuck in your cable connector.

Try to pull the black part out of your cable end, Then try to re-bend the connector pins inside the Noahlink. It must be 4 seperate distinct pins

2 Likes
#37

Yeah he did mention that connecter, well it’s gotta be it.