Usb Audio Codec Not Working
Click to expand.When my 990 is connected via USB to my computer, I do see the 'Silicon Labs CP210x USB to UART Bridge' showing up under device manager. When I right click on the computer volume control in the task bar (or go into Sound under Control Panel) and click on 'recording devices' I see '4-USB Audio CODEC' for the microphone. THIS is where I 'lost' the audio codec once when it went 'hidden' for some reason. I had to click on 'show all devices' or some such (and not even sure where that option is - I don't currently see it but maybe because none are hidden) for the audio codec to show back up.Bob. When my 990 is connected via USB to my computer, I do see the 'Silicon Labs CP210x USB to UART Bridge' showing up under device manager. When I right click on the computer volume control in the task bar (or go into Sound under Control Panel) and click on 'recording devices' I see '4-USB Audio CODEC' for the microphone.
Turbo dismount custom levels download. I see 'USB Audio Device', but not 'USB Audio Codec' when using the SignaLink USB - Is this correct? Windows ME and 2000 may display the SignaLink USB as 'USB Audio Device' instead of 'USB Audio Codec'. If this is the case on your system, then you simply need to select 'USB Audio Device' instead of 'USB Audio Codec' as the sound card. A few Mac users that update to Mac OS X discover their sound and audio output has ceased to work, leading to a completely mute Mac that does not respond to the volume keys. Fortunately, the mysterious missing sound output issue is incredibly simple to fix, and there is nothing actually wrong with.
THIS is where I 'lost' the audio codec once when it went 'hidden' for some reason. I had to click on 'show all devices' or some such (and not even sure where that option is - I don't currently see it but maybe because none are hidden) for the audio codec to show back up.Bob.
Click to expand.I know that they are different in some windows versions. But I seem to recall that there was such a thing there under Sound, Video and game controllers.(Un)fortunately I am running Win 7 and Win 8.1. Both are giving me the same result. Sorry, no Win XP to test.msinfo32:Under Software Environment/System Drivers/ I see the USB Audio Codec. So it is installed, but it isn't running, even so the TS-990 is hooked up to the computer and turned on. That means I will not see the USB Audio Codec in Control Panel/Sound.
That is what I figured. Silabser isn't running either. Silabenm is running.That points to a hardware problem. If all else fails, delete the existing drivers from Device Manager (use Show All) and then reinstall them or reconnect your radio to force Windows to scan for new hardware and download the drivers from scratch.But, of course, if you have not already, first power off both Windows (with a proper shutdown or restart, not hibernation) and your radio, then reboot the PC and then turn your radio back on after the PC finishes rebooting. Sometimes the issue is as simple as a reboot if things were previously working fine, in which case a reboot is the best first diagnostic step.Also note that when it comes to USB devices, Windows can sometimes associate certain drivers with a specific USB port, in which case plugging the USB cable for that device into a different port can break your software and/or driver configuration. In that case the solution is to reconnect to the USB port that was originally used to configure and operate the device.Be aware that the virtual serial port drivers used for radio control are entirely separate from those that handle the virtual soundcard interface, they just happen to share the same USB connection inside the radio.
As such it is perfectly reasonable that one set of drivers may work fine (such as for the virtual serial port) while the other does not (such as for the virtual soundcard). This fault can either be the result of a driver issue on the PC or a fault in the radio's chipset that is responsible for implementing the virtual soundcard-to-USB interface - the best way to figure out which is to try setting up a different PC, or laptop, with the necessary drivers and basic software to see if things work.
If all is well on the new testPC then you know it is a software or configuration issue with the original PC, if not then there is greater reason to suspect (but without perfect certainty) an issue with the radio itself (such as the chipset, firmware, or a relevant menu setting).If there is a fault in the chipset, then there are other options such as the SignaLink USB and Yaesu SCU-17 (which is not brand specific) that can take over the audio encoding and decoding, so there are some options out there. However, damage to the chipset is only very likely if there has been an event that caused excessive RF or a ground loop over the USB cable - but I would hope the radio manufacturer used an isolated a USB port for maximum safety to protect the port, PC and operator from damaging ground loops and backfed RF over the USB cable (which can damage either the radio or PC).Whatever the cause, I wish you all the very best in resolving the issue!
If all else fails, delete the existing drivers from Device Manager (use Show All) and then reinstall them or reconnect your radio to force Windows to scan for new hardware and download the drivers from scratch.But, of course, if you have not already, first power off both Windows (with a proper shutdown or restart, not hibernation) and your radio, then reboot the PC and then turn your radio back on after the PC finishes rebooting. Sometimes the issue is as simple as a reboot if things were previously working fine, in which case a reboot is the best first diagnostic step.Also note that when it comes to USB devices, Windows can sometimes associate certain drivers with a specific USB port, in which case plugging the USB cable for that device into a different port can break your software and/or driver configuration.
In that case the solution is to reconnect to the USB port that was originally used to configure and operate the device.Be aware that the virtual serial port drivers used for radio control are entirely separate from those that handle the virtual soundcard interface, they just happen to share the same USB connection inside the radio. As such it is perfectly reasonable that one set of drivers may work fine (such as for the virtual serial port) while the other does not (such as for the virtual soundcard). This fault can either be the result of a driver issue on the PC or a fault in the radio's chipset that is responsible for implementing the virtual soundcard-to-USB interface - the best way to figure out which is to try setting up a different PC, or laptop, with the necessary drivers and basic software to see if things work. If all is well on the new testPC then you know it is a software or configuration issue with the original PC, if not then there is greater reason to suspect (but without perfect certainty) an issue with the radio itself (such as the chipset, firmware, or a relevant menu setting).If there is a fault in the chipset, then there are other options such as the SignaLink USB and Yaesu SCU-17 (which is not brand specific) that can take over the audio encoding and decoding, so there are some options out there. However, damage to the chipset is only very likely if there has been an event that caused excessive RF or a ground loop over the USB cable - but I would hope the radio manufacturer used an isolated a USB port for maximum safety to protect the port, PC and operator from damaging ground loops and backfed RF over the USB cable (which can damage either the radio or PC).Whatever the cause, I wish you all the very best in resolving the issue! Click to expand.No it isn't a Windows issue. I have tried different versions of windows on 2 different computers already.
I can certainly try the same thing on a 3rd computer, but I doubt very much to see any different results at this point. Your later point (damaged chipset) that is where I put my money on. Certainly after I figured out what my computer and the radio is and is not doing and after seeing that there is a different revision digital board for it. I just better hope the new revision board is better than the old one! Following the schematic, there is a protection diode, a 3 port USB Hub Controller IC and then the Audio codec IC.The actual USB Audio Codec is a PCM2903 IC703 made by TI.
There isn't anything the firmware can upload anything to it. However one can maybe program a Vendor ID into it, and that's about it. No it isn't a Windows issue. I have tried different versions of windows on 2 different computers already. I can certainly try the same thing on a 3rd computer, but I doubt very much to see any different results at this point. Your later point (damaged chipset) that is where I put my money on. Certainly after I figured out what my computer and the radio is and is not doing and after seeing that there is a different revision digital board for it.
I just better hope the new revision board is better than the old one! Following the schematic, there is a protection diode, a 3 port USB Hub Controller IC and then the Audio codec IC.The actual USB Audio Codec is a PCM2903 IC703 made by TI. There isn't anything the firmware can upload anything to it. However one can maybe program a Vendor ID into it, and that's about it. Click to expand.Thanks for the additional followup. If your hunch that the chipset, or any internal component for that matter, has, in fact, been damaged then you will want to look into inserting a galvanic isolator (frequently optical) between the PC's USB port and that of the radio's to ensure a similar event is unlikely to repeat itself in the future.
Here it goes: I had used FLDIGI with the TS-990S for my digital needs and connected the TRX to my computer via the USB - B jack on the back of the radio. That worked fine as kind until lately. I am not sure if it has something to do with the latest firmware, the use driver or physically something wrong with the audio codec IC. When I turn on my radio the computer knows that there is my Kenwood and makes the proper USB connected sound. I can use Kenwoods ARCP.
1.03 on the radio firmware v. So that part works. However if I want to choose FLDIGI or ARUA-10 v 3.0, there is no dice, as the USB audio codec is missing on the audio settings, so I can't set the software up to listen or transmit there. I made sure that's I have latest firmware, software and drivers installed. Got another computer out, installed the Virtual com port driver and same thing there too.Looking at the block diagram, the audio codec ic is before the hub controller. Logic would say, if something would have damaged the codec ic, it should have taken the hub controller too.
So maybe someone can check their TS-990S or has some other ideas, besides some menu settings, that I've never changed. Radio is already a year out of warranty. I have had something like this happen before as well. I'm also running a 990, but that was not the problem. I can't remember exactly the issue, but somewhere in Windows where one selects the various audio codecs was a setting that once clicked on, showed ALL the codecs including those that were not being used. Once I clicked that I was able to use the correct audio codec and all was well. Not sure exactly if this is your problem but until I found that 'setting,' the codec didn't even show up AT ALL.Yea, not a lot to work on but good luck!.Bob.
I have had something like this happen before as well. I'm also running a 990, but that was not the problem. I can't remember exactly the issue, but somewhere in Windows where one selects the various audio codecs was a setting that once clicked on, showed ALL the codecs including those that were not being used. Once I clicked that I was able to use the correct audio codec and all was well. Not sure exactly if this is your problem but until I found that 'setting,' the codec didn't even show up AT ALL.Yea, not a lot to work on but good luck!.Bob. Tried that, no dice.Maybe you could look into your device manager in windows and see if you see the USB audio codec installed and listed?
Mine isn't there. Thinking a bit harder about the problem, I am having more and more the impression that the little digital board that has the USB b controller and the USB audio codec ic is bad. I don't think that a firmware can do anything to the USB hub directly nor on the USB audio ic itself. All that stuff is hard coded into the ic itself. If I could figure out that the board is at least 75% chance of being broken, I would order one and put it in myself no problem. Guess I will be calling Kenwood in Ontario tomorrow and see what they have to say about it.You can't turn the USB off in the firmware, so that's not the problem. Audio over USB is enabled.
I see the USB to UART Bridge in the device manager, but the USB audio codec is not there.So I checked the block diagram and the schematic for the digital unit. Found there is a protection diode, the USB hub controller and the audio codec.
Went to east coast parts and checked for parts. Apparently the original digital board is not available anymore and there is a revised unit for US$351.
Dell Usb Audio Not Working
Usb Audio Device Not Working
No single parts. So if it is a hardware failure (that's what it looks like to me) I guess I have to order a new board. I am going to call Kenwood tomorrow.In the mean time I still would like to know if someone else is seeing the USB Audio Codec in the device manager, as mine is not present. Thanks for the tip running the msinfo32.exe and I will look at that later this evening.