Troubleshooting Class Compliant USB Computer Peripherals

?Most USB audio and MIDI computer peripherals are Class Compliant USB devices. This means that to communicate with the computer, they use drivers that are built right into the host computer’s operating system. These drivers are written by Microsoft (or Apple for Macintoshes), and come pre-installed on all computers.

The advantage of Class Compliant USB devices is that they work on all modern computers, and all modern operating systems, and will work with the next generation of Microsoft or Apple operating systems the very same day they are released. There are no special drivers to install, update, or configure.

USB RS-232 Single Port Serial Adapter works with Windows 10 USB to RS232 Adapter for Serial Communication. Synchronize your PDA, Digital Camera, Cell Phone or other device currently using a serial port with this USB RS-232 Serial Adapter. Connect your serial devices to the newer computer equipment needing a serial connection that supports USB. Download the latest driver for UST Pro II Device, fix the missing driver with UST Pro II Device. Remember to Logout - It is important to Logout or close all your web browser windows when you finish using services that require authentication. Cumulative and current firmware and drivers for the Surface Pro 2. This firmware and driver package contains drivers for all of the components in the Surface Pro 2, as well as updates to the system firmware that have been released via Windows Update. These drivers and firmware are compatible with Windows 8.1 and Windows 10, including Enterprise. Our database contains 1 drivers for Logitech WingMan Formula Force GP USB. For uploading the necessary driver, select it from the list and click on ‘Download’ button. Please, assure yourself in the compatibility of the selected driver with your current OS just to guarantee its correct and efficient work. Kawai USB MIDI Driver Package for Windows (v2.1) Required for the VPC Editor and software instruments to be used simultaneously. Designed to comply with USB2.0.

With these products, we commonly receive inquiries with the following symptoms reported:

• Doesn’t connect to computer.
• No Firmware installed … controller dead.
• Doesn’t light up.
• DOA

Based on our experience, 95% of similar inquiries can be quickly resolved and the user gotten up and running. For the most part, similar symptom descriptions indicate incomplete software setup, rather than a true malfunction or defect.

This means that in the vast majority of cases, a preference, setting, or option in the host software (i.e. Ableton, Cubase, GarageBand, Pro Tools) is misconfigured. These software programs don't configure themselves, and the user will not get any audible or visual response from the computer or peripheral until the software is properly configured.

This guide will help determine whether difficullty is due to software settings, a hardware defect, or other factors that can cause similar symptoms.

What does 'class compliant' mean?

A class compliant device is one that doesn't require extra drivers to connect your Windows or Macintosh computer, or to your iPad. Class compliant devices use drivers which are built into the host (i.e. the computer or the iPad) operating system.

To find out if your USB audio or MIDI device is class compliant, check the manufacturer's web page. If it connects automatically to any computer without requiring you to install drivers from a website or a disk, it is probably class compliant.

Class Compliant USB Audio and MIDI Devices

Most USB audio and MIDI computer peripherals are Class Compliant USB devices. This means that to communicate with the computer, they use drivers that are built into the host computer’s operating system. These drivers are written by Microsoft (or Apple for Macintoshes), and come pre-installed on all computers.

The advantage of Class Compliant USB devices is that they work on all modern computers, and all modern operating systems, and will work with the next generation of Microsoft or Apple operating systems the very same day they are released. There are no special drivers to install, update, or configure.

With these products, we commonly receive inquiries with the following symptoms reported:

• Doesn’t connect to computer.
• No Firmware installed … controller dead.
• Doesn’t light up.
• DOA

Based on our experience, over 95% of similar inquiries can be resolved and the user gotten up and running. For the most part, similar symptom descriptions indicate incomplete software setup, rather than a true malfunction or defect.

This means that in the vast majority of cases, a preference, setting, or option in the host software (i.e. Ableton, Cubase, GarageBand, Pro Tools) is misconfigured. These software programs don't configure themselves, and the user will not get any audible or visual response from the computer or peripheral until the software is properly configured.

The guide below will help determine whether difficulty is due to software settings, a hardware defect, or other factors that can cause similar symptoms.

Quick test - Windows

When you're frustrated with not being able to get up and running, or if you thinking you might have a defective product, this 10-second is-it-broken test can restore the confidence necessary to continue working with the product and to complete any needed software setup or authorization process.

To verify that the device is working, and is being seen by the computer…

1. On Windows 8, 7, Vista, or XP, open the Device Manager.
2. Disconnect the controller from the computer, count to 5, then reconnect the controller
   Does the list of devices at all change, refresh, or flash? If yes…Good, the product is recognized by the computer.

If the product does pass the test above, it is not defective, and the difficulty is caused by misconfigured software settings or options. Carefully follow the setup instructions for the software you are using, or contact Technical Support for assistance.

If the product does NOT pass the test above, it could be defective, or it could be that other factors are causing the symptoms. Refer to the section below to rule out a defect or potential other factors. This will help determine whether your symptoms are caused by something on your computer, or by a defective product.

Quick Test - Macintosh

When you're frustrated with not being able to get up and running, or if you thinking you might have a defective product, this 10-second is-it-broken test can restore the confidence necessary to continue working with the product and to complete any needed software setup or authorization process.

To verify that the device is working, and is being seen by the computer…

1. Disconnect the USB interface or controller from the computer, count to 5, then reconnect the device.
   
2. In the upper-left of the screen, click the Apple Menu, and select About This Mac.
   
3. In the window that opens, click More Info.
   
4. On the next screen, click System Report.
   
5. A System Report window will be displayed. On the left-hand side of the window, under Hardware, select USB.
   
6. Your connected USB devices will be displayed on the right (minus the device you're testing since it is disconnected at this point in the test).
   Now, connect the USB interface or controller device you are testing.
   
7. Once your USB device is connected, select File > Refresh Information to update the list of connected devices.
   
8. You should see a new device listed once you have refreshed the list. Disconnect the device and repeat steps 6 and 7 above if you need to confirm.

If the product does pass the test above, it is not defective, and the difficulty is caused by misconfigured software settings or options. Carefully follow the setup instructions for the software you are using, or contact Technical Support for assistance.

If the product does NOT pass the test above, it could be defective, or it could be that other factors are causing the symptoms. Refer to the section below to rule out a defect or potential other factors. This will help determine whether your symptoms are caused by something on your computer, or by a defective product.

Other factors

Note that these factors affect all USB MIDI and Audio Devices the same regardless of the manufacturer, and can be resolved through Technical Support:

• Poor USB communication – bad port, or the use of USB Hub or USB extension cables. This is actually quite a common issue. Perform the quick test above using a USB different port, or on a different computer.
• Bad USB cable - try a different USB cable.
• Logitech Camera Driver Conflict – if you’ve ever connected one of these web-cams to your Windows PC you’ll have trouble using USB audio or MIDI devices. This does not affect Mac users. See below.
• Missing or corrupted Windows or Mac OSX files – these class-compliant product use drivers built in to the Windows and Mac OS. If these files are missing or corrupted, the product won’t function as expected. We can help diagnose and repair this symptom. Of the potential causes for difficulty descriped in this article, this is the least likely. All other potential causes should be ruled out first. See below.
• Ruling out software setup errors versus hardware failure can be difficult. See the Computer Peripheral Testing guide linked below. This archive includes resources and instructions that can be used to test any class-compliant USB Audio or MIDI computer peripheral in about 2 minutes. The guide linked below was developed to shorten evaluation time for repair depots, service centers, and is not intended as a self-support tool for general public. If you need asssitance with your software settings, contact Technical Support.

Technical Support

The suggestions above should help quickly determine whether a product is functional, and to overcome common setup obstacles such as poor USB communication. If you require further assistance with product setup, contact Technical Support. We've included contact links for several manufacturers below:

Prescription Resources

The three resources below are described above. These should be considered prescription medicine.. only to be used to remedy a specific symptom. These are not general maintenance tools. It is not recommended that you use these resources unless you are confident you are affected by the specific scenarios that cover them above. Use these files at your own risk. If you are uncertain whether or how you should use the resources below, contact Technical Support.

NOTE: For non-technical questions, please see our SignaLink USB FAQ.

Please read this brief note before troubleshooting or calling for assistance!

Virtually all of the Technical Support calls that we receive for the SignaLink USB are due to simple configuration issues. This is true for both new installations, and for those that have been using their SignaLink for some time without any trouble but now find that it has stopped working. Every SignaLink and radio cable is 100% tested before shipping, and the SignaLink has proven itself to be very reliable since its release several years ago. Unless you have experienced a nearby lightening strike, power supply failure, or some other catastrophic event, whatever issue you are having with your SignaLink USB is most likely due to incorrect setup of the SignaLink, software volume controls, sound card communication program, or radio, and can be resolved by carefully following the tips below. Please take some time to look through ALL of the information below and you should be able to resolve the problem without having to call Tech Support. Thank you.

Click here if you are experiencing a 'Sound Card Error' after a Windows 10 update

Common Problems

These are the most common problems reported to our Technical Support Staff.If you are unable to resolve your problem, or if you do not find your problem listed here, then please contact our Technical Support Staff for assistance.

Ust Pro Ii Port Devices Driver

1. Radio transmits, but there is no power output or it is too low.

2. My transmit signal is wide and distorted.

3. I can't seem to receive.

4. Why can't I receive some stations.

Technical Questions / Operating Tips

Windows Issues

My SignaLink USB was working perfectly but now will no longer Transmit- This is the most common problem we hear about and it is virtually **always** due to the software volume controls being reset by Windows. This can happen if you unplug the USB cable, change the default sound card in Windows, or accidentally mute the SignaLink's output. Other things can cause this to happen as well, so please check your Windows software volume controls carefully. Note that they will most likely be reset exactly opposite of how they should be set, so they can look correct at a glance. As outlined in the SignaLink Installation Manual and on our web site, the 'Speaker' control should be at 100% (max) and the 'Application' control should be at 50% (note that in Windows XP, this is the 'Wave' control). Be sure that your volume control panel shows 'USB Audio Codec' or you will be adjusting the volume for the wrong sound card. If you are not sure how to adjust the software volume controls, then please refer to the SignaLink Manual for details.

Radio won't transmit (SignaLink USB's Red PTT indicator is OFF) -

• Verify that the SignaLink USB’s PWR LED is ON. If it is not, then make sure that the SignaLink USB's PWR switch is pressed in and the USB cable is securely connected to the computer and the SignaLink. If the PWR indicator still won't turn ON, then try changing USB cables, USB ports, or using a different computer. If none of these make any difference, then you may have a problem with your SignaLink and you should contact Tech Support by telephone for assistance.
  

• Verify that your communication program is configured to use the SignaLink USB’s built-in sound card. The program should have “USB Audio CODEC” selected as the sound card for both Transmit and Receive.
  

• If your communication program has a built-in transmit level control (WSJT-X, etc.), then this will need to be turned up. If you are using an older version of HRD/DM-780 with the 'Output Attenuator' feature, then this should be set to '0 db'.
  

• Verify that the PLAYBACK software volume controls for the SignaLink USB are set according to the procedure in the SignaLink manual. If these controls are set too low or muted, then the SignaLink USB's PTT LED will NOT turn ON. Incorrect software volume control settings are the number one cause of transmit problems, so please check this carefully.
  

• If the SignaLink is plugged into a USB hub, please remove it from the hub and plug it directly into the computer's USB jack until the problem is resolved. Un-powered hubs and some powered hubs cannot supply enough power for the SignaLink to operate properly, so Receive will usually work, but Transmit may not. See our SignaLink FAQ for more details on this.
  

• Usb webcam software. TIP - Incorrect jumper settings, radio setup, and/or the position of the SignaLink's TX, RX and DLY knobs will NOT affect the operation of the SignaLink's PTT LED. Do not worry about these things until you have checked the items above and have the PTT LED turning ON when your communication program is transmitting.

Radio won't transmit (SignaLink USB's PTT indicator is ON) -

• If the SignaLink USB's PTT LED turns ON but the radio doesn't switch to transmit, then you have most likely installed the 'PTT' and/or 'G' (Ground) jumpers incorrectly on the SignaLink's JP1 jumper socket. The jumper may be installed in the wrong location and/or it may not be pressed in all the way. If the SignaLink is connected to your radio's Mic jack, then be sure you have installed the SPKR jumper wire *ONLY* if your radio has Speaker Audio on the Mic jack, or PTT may not work properly (check your radio manual!). Please go back and double-check ALL jumpers carefully making sure that you are using the correct settings for your cable. Most radios have a couple different cable options with different jumper settings, so be sure you've selected the correct one! If you are using a Plug & Play Jumper Module, then double-check that you have the correct module installed and that it is properly inserted in the jumper socket - see our Plug & Play Jumper Modules page for instructions.
  

• If the SignaLink is attached to your radio’s Data or Accy Port, then your radio might not be configured properly to use that port. Most newer radios must be in a 'digital' mode in order to Transmit properly. Most ICOM radios in the IC-746/756 series require you to use 'USB-D' or 'LSB-D', and a number of Yaesu's require that you select and configure a digital mode such as 'User-U', 'PSK31-U', etc. It should be noted that the 'RTTY' mode is virtually *never* correct for any radio as it is virtually always for FSK only. Please consult your radio manual and verify that your radio is in the correct mode. If you're not sure which mode to use, try checking an on-line forum for your radio, or contact your radio manufacturer's Tech Support department.
  

• If the SignaLink is attached to your radio's 6-pin mini-DIN Data Port and your radio supports 9600 baud Packet operation, then you need to check your radio's '9600 Mode', 'Packet Rate', or similarly worded menu setting and insure that it's set to '1200', or 'OFF'. The exact wording of this menu setting varies widely, but you will find only two choices if you are looking at the correct menu item in your radio. If you see other baud rates besides 1200 and 9600 listed, or if you see other options, then you are looking at the wrong menu item.
  

• If your SignaLink is plugged into a USB hub, then we strongly suggest that you remove the hub for troubleshooting purposes. Non-powered hubs will NEVER work reliably, and many powered USB hubs cannot supply enough power for the SignaLink to operate properly (Receive will work, but Transmit may not). See our SignaLink FAQ for more details on this.
  

• TIP - Be sure to check your radio carefully to confirm that it's actually stuck in Receive. If the radio is switching to Transmit but just doesn't have any power output, then you'll want to check the items under 'Common Problem #4' as well.
  

• TIP - Be sure that the SignaLink's radio cable is plugged into the correct jack on the radio, and that it is plugged in securely and positioned correctly. 13-pin DIN plugs found on Icom and Kenwood radios can be plugged in exactly upside-down even though they are keyed, so be sure to look at the jack on the radio and position the plug accordingly (do NOT go by any arrow or other markings on the cable - You MUST look at the socket on the radio!).

Radio transmits but there is no power output, or it is too low – The SignaLink USB can provide more than enough Transmit Audio to drive virtually any radio to full power. If you have followed the Audio Level setting procedure in the SignaLink USB manual and still cannot get enough power, then check the following:

• If the radio is in Transmit but you have no power output at all, then the 'MIC' jumper wire may be installed incorrectly on the SignaLink's JP1 jumper socket. The jumper may be installed in the wrong location and/or it may not be pressed in all the way. You may also have the Ground ('G') jumper installed incorrectly. Please go back and double-check ALL jumpers carefully making sure that you are using the correct settings for your cable. Most radios have a couple different cable options with different jumper settings, so be sure you've selected the correct one! If you are using a Plug & Play Jumper Module, then double-check that you have the correct module installed and that it is properly inserted in the jumper socket - see our Plug & Play Jumper Modules page for instructions.
  

• If you are using a CAT/CIV interface to control your radio, then you *must* disable 'PTT through that interface, so that the SignaLink can key the radio or you'll have no power output. This is necessary because most radio's will only look for Transmit Audio on the Mic jack if the radio is switched into Transmit by the CAT interface. Note that this is a design issue with the **radio** and has absolutely nothing to do with the SignaLink. The disabling of PTT via CAT/CIV control is done in the communication program by selecting a PTT option that does not key through a CAT interface or CAT/CIV jack. This is often referred to as 'External/Vox' or something similar. See our Communication Program Setup information for details on this.
  

• Verify that your radio’s “Forward Power” (sometimes called “RF Power” or “Carrier Power”) control is set to maximum. On newer radios with menu settings, this is normally a menu item (not a knob). Note that you do NOT want to run full power as measured on your radio, or external watt/power meter. You should normally set this control to max and then adjust the power to the desired level using the SignaLink USB's TX control. This is normally no more than 25-35 watts for PSK31 and 50 watts for most other 100% duty cycle modes, but you should check your radio manual to insure that these power levels are OK for your radio. Continued transmissions at power levels higher than those recommended by your radio manufacturer can damage your radio, so please check your radio manual.
  

• If the SignaLink is attached to your radio’s Data or Accessory Port, then your radio might not be configured properly to use that port. Some radios must be in a 'digital' mode in order to Transmit properly. Most ICOM radios in the IC-746/756 series require you to use 'USB-D' or 'LSB-D', and a number of Yaesu radios require that you select and configure a digital mode such as 'User-U', 'PSK31-U', etc. It should be noted that the 'RTTY' mode is virtually *never* correct for any radio as it is virtually always for FSK only. Your radio may also have a menu based gain control for the Data/Accy Port that needs to be turned up (common on newer Kenwood, Yaesu and Ten-Tec radios), and/or it may have a 'Transmit Audio Source' menu that needs to be set properly (common on Ten-Tec radios). Please consult your radio manual or an online forum for the correct settings to use, or contact your radio manufacturer's Tech Support department.
  

• If the SignaLink is attached to your radio's 6-pin mini-DIN Data Port and your radio supports 9600 baud Packet operation, then you need to check your radio's '9600 Mode', 'Packet Rate', or similarly worded menu setting and insure that it's set to '1200', or 'OFF'. The exact wording of this menu setting varies widely, but you will find only two choices if you are looking at the correct menu item in your radio. If you see other baud rates besides 1200 and 9600 listed, or if you see other options, then you are looking at the wrong menu item.
  

• If your radio has a built-in USB sound card connection, then you'll want to be sure that the 'Modulation Source', 'Transmit Audio Source' or similarly worded menu item is set to 'ACC' (Accessory), or whatever setting connects it to the radio's Accy or Data Port jack, NOT the radio's USB connection.
  

• If the SignaLink is attached to your radio’s Mic jack, then try turning up your radio’s Mic Gain control.
  

• Confirm that your transmit modulation in your communication program is set within the range of 500hz to 2500hz. In PSK31 programs this means that you should be within the range of 500 to 2500 Hz in the waterfall display. If you go outside of these limits then your radio will not be able to pass the modulation and your power will drop significantly.
  

• Set the Windows (PLAYBACK) 'Application' control higher (note that this is the 'Wave' control in Windows XP). Be sure you are adjusting the slider for USB Audio Codec or it will have no affect on the issue!
  

• See the “Special Jumpers” section of this manual and install JP3. This will dramatically increase the SignaLink’s Transmit Audio level. Note that this is NOT needed for most radios, so you really need to be sure that everything else is correct before doing this.
  

• If the SignaLink is attached to a Kenwood 13-pin Accessory Port, then you may have set the PTT jumper incorrectly. Double-check the document that was supplied with your radio cable and/or check our Jumper Settings page to see if your radio requires a standard PTT jumper or the diode module to be installed. If you are using our Plug & Play Jumper Modules then check our Jumper Module page for the correct setting for your radio. Please note that 13-pin DIN plugs found on Icom and Kenwood radios can be plugged in exactly upside-down even though they are keyed, so be sure to look at the jack on the radio and position the plug accordingly (do NOT go by any arrow or other markings on the cable - You MUST look at the socket on the radio!)
  

My transmit signal is wide or distorted - This is generally the result of over-driving your radio. Be sure you are following the guidelines for setting/adjusting your transmit power in the SignaLink manual, and see the common problem listed below if applicable.

The SignaLink USB's TX control is 'touchy', making it difficult to control my RF power - This is most likely because the radio’s Mic, Data or Accy Port gain control is set too high, but before continuing, please be sure that you have NOT installed special jumper JP3 inside the SignaLink. This jumper is rarely needed, and will normally cause the SignaLink to provide too much audio to the radio making adjustment of the TX knob difficult.

If the SignaLink is attached to your radio's Mic jack, then you can resolve this issue by turning the radio’s Mic Gain control down. If the SignaLink is attached to the radio's Data or Accy Port, then your radio likely has a menu setting or trimmer to adjust the gain. This gain adjustment is often called “Packet Input Level” or “Packet Gain”, but may have another name, so check your radio manual carefully. Note that the radio's Mic Gain control on some older radios may also affect the Data/Accy Port (TS-440 for example), so you should check this as well.

If the above solutions don't help, then we suggest that you install Special Jumper JP4 inside the SignaLink and LOWER the Windows 'Application' control for the SignaLink's sound card (note that this is the 'Wave' control in Windows XP). The Application control can be lowered to just abovethe point where the SignaLink's PTT LED turns OFF, so as to provide minimal TX Audio to the radio while insuring that the SignaLink's PTT circuit functions correctly. We recommend finding this threshold while transmitting a steady test tone, and with the SignaLink's Delay knob set to minimum.

ATTENTION IC-7000, IC-746PRO and FT-450 Users - Some customers have reported that these radios have unusually sensitive Data Ports, which can make adjustment of the SignaLink's TX knob somewhat difficult. If this is the case with your radio, then you should find that the procedure above where you install jumper JP4 and lower the Wave volume control resolves the issue. However, you may also need to turn the radio's RF Power menu setting down for better control. A power setting of 35 to 45 watts usually works well for 25 to 35 watts of actual RF output as measured on a watt meter, or the radios Power Output meter. For lower power levels, we would suggest setting the radios RF Power setting to 5 to 10 watts above the actual RF power level that you would like to use. For example, for 5 watts of actual RF power on PSK31, set the radio's RF Power setting to 10 or 15 watts, and then adjust the power output using the SignaLink's TX knob until 5 watts is observed on the watt/power meter.

If you are unable to control the power output sufficiently with the SignaLink's TX knob, then please check that you are following our instructions carefully and try again. If you are still unable to resolve the issue and you are confident that you are doing things correctly, then please contact our Technical Support Staff by telephone and they will go through it with you.

I can't seem to receive: It is perfectly normal for some signals not to be copied (see 'Why can't I receive some stations' below). However, even without proper decoding, you should still see audio/noise from the radio appear in your sound card communication program's waterfall, spectrum, or other display. You can check this by turning the radio OFF and ON, or adjusting the SignaLink's RX control from minimum to maximum while watching the program's display. If you do not see a clear change indicating that RX Audio (noise) is reaching the SignaLink, then check the following:

Ust Pro Ii Port Devices Driver Ed

• Be sure that your communication program is configured to use the SignaLink's 'USB Audio Codec' sound card for the 'Input' or 'Receive' sound card. This is one of the most common causes of Receive problems.
• Using the procedure outlined in the SignaLink USB manual, be sure that the Windows Recording control for the SignaLink's USB Audio Codec sound card isn't muted or turned down too low.
  
• Verify that the SignaLink's RX level control is turned up (clockwise). If needed, install special jumper JP2 inside the SignaLink to increase the radio's RX Audio level (check other possible causes first!).
  
• If the SignaLink is attached to your radio's Data./Accy Port (not the Mic jack), then you may need to increase the radios RX Audio output level, which is typically done through a menu setting (check your radio manual).
  
• If the SignaLink is attached to your radio's Mic jack, then try turning up your radio's Volume control. If that doesn't help, then you may not have the RX Audio signal on the Mic jack, and you'll have to connect the supplied audio cable between the SignaLink's 'SPKR' jack and the radio's External Speaker / Headphone output jack. Check your radio manual for the presence of RX Audio on the Mic jack, and review the “Connecting The Radio” section of the SignaLink USB Installation Manual.
  

Why Can't I Receive Some Stations - No matter how good your antenna and radio are, there will always be some stations that you cannot copy (even with strong signals!). While the reason for this may be because of operator error (wrong mode or baud rate, off frequency, etc.), radio wave propagation problems can often prevent you from receiving.Some modes are more susceptible to this than others.For example, even though PSK31 usually works very well with weak signals, sometimes even strong PSK31 signals cannot be copied at all because of multipath and Doppler Shift propagation problems.Other modes like HF Packet and RTTY do not work well with weak signals and are susceptible to multipath and Doppler Shift.

Windows 'System Sounds' Cause The SignaLink USB To Transmit – This will NOT happen if you configure Windows to use your computer’s sound card as the default sound card. See the “Connecting The Computer” section of the SignaLink USB Installation Manual to resolve this problem.

Radio cycles between Transmit and Receive when the 13-pin radio cable is plugged in - Please check that you have the radio cable plugged in correctly by comparing the position of the plug with the socket on the radio. Do not assume that the cable is plugged in correctly because of the position of the notch on the end of the plug! As unlikely as this may sound, we have seen several 13-pin plugs installed upside down and the results are immediate cycling between Transmit and Receive.

How do I operate 'direct keyed' CW with the SignaLink - This is done by simply connecting the SignaLink's PTT and Ground lines to the 'Key' and 'Ground' lines of your radio's Key jack. One of our un-terminated radio cables can be used to make these connections. You will need to attach the appropriate plug for your radio's Key jack to this cable. Using our SLCABNC cable, we suggest attaching the white/orange wire to the tip of the plug, and the orange wire to the plug's body/sleeve. You will then need to install the SignaLink jumpers as follows; PTT to 1, and G (ground) to 2. Note that direct keyed CW is limited to about 25 WPM on Transmit (there is no limit on Receive), so if you need to transmit faster than this, you'll want to run AFSK CW.

Do I select a serial port when configuring my communications program - Some communications programs will have a COM Port selection for PTT (Push To Talk), and some will also have COM Port selection for radio control ('CAT' control). The SignaLink does NOT use a serial port for PTT control, so your communications program should be set to 'None', 'COM0', 'External VOX', or a similar setting to indicate that a serial port is not used. Some newer programs have a 'SignaLink' setting that should be used if available.

If you have a CAT interface and will be using it for radio control, then the CAT control portion of your communications program should be set to use the COM Port that the CAT interface is plugged into. If you do not have a CAT interface, then this should also be set to 'None' (or similar).

What general settings must I make when configuring my communications program - As explained in the SignaLink Installation Manual, you must configure your communications program to use 'USB Audio Codec' as the sound card for BOTH Transmit and Receive. You may also need to disable serial port PTT control and CAT control as mentioned in the question above. These are typically the only settings required to use the SignaLink USB with most programs, but some programs do have other 'special' program specific settings such as 'use AFSK in place of FSK', or 'send CW as AFSK' that may need to be set. In general, you can configure most programs properly if you remember that you will be operating AFSK (audio tones/modulation) and NOT using a serial port for.

I see 'USB Audio Device', but not 'USB Audio Codec' when using the SignaLink USB - Is this correct? Some computers 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.

I don't see a 'New Hardware Found' (or similar) message when I first plug in the SignaLink USB - This is generally not an indication of a problem. You may not see a 'New Hardware Found' message when plugging in the SignaLink USB for the first time because of a number of reasons, including the speed of your computer, the version/build of Windows you are running, or the way Windows is configured. If you want to confirm that the drivers were properly installed, then (after waiting a minute or two after the initial plug-in) open your communication program (DigiPan, etc.) and confirm that the SignaLink's 'USB Audio Codec' sound card is available in the list of available sound cards. If it is, then the drivers are properly installed. Note that the SignaLink MUST be connected to the computer, or you will not find it listed as an available sound card even if the drivers have been installed.

Windows 98 can't find a file during installation - There is a bug in all versions of Windows 98 that causes the Operating System to sometimes 'forget' what drive the installation CD is in during installation. If you receive a 'Can't Find File..' error message during installation of the SignaLink USB, then you will need to manually enter the location of your Windows CD drive into the dialog box when prompted. For example, if your CD drive is 'D:' then you will type 'D:WIN98'. Note that you may also be able to click the location drop down menu and select the correct CD drive location.

Windows resets the SignaLink USB's software volume controls to incorrect positions - If the SignaLink's USB cable is unplugged or the default sound card in the computer is changed, Windows may reset the SignaLink's software volume controls to incorrect levels. The symptom for this problem is that the SignaLink USB was working perfectly, but now will not transmit. This issue can be resolved by manually setting the 'Speaker' volume control back to maximum, and the 'Application' control to 50%.

Every time I open the Window's Volume Control Panel, it has reset back to my computer's sound card - This is perfectly normal. Windows will ALWAYS show the default sound card (which should be your computer's sound card) when opening the Volume Control Panel. The only place you should see the SignaLink USB's sound card 'stick' is in your communication program (DigiPan, etc.).

11025 Hz Sample Rate offset error - Due to a Windows system issue, some Windows ME, 2000 and XP computers may show an abnormal sample rate offset error of around 7000 ppm at the 11025 Hz sample rate (other sample rates are NOT affected). If this offset error occurs on your computer, it can result in your transmit (modulation) frequency being off from your receive frequency. When operating digital modes, this can manifest itself in several different ways. With PSK31, other stations may not respond when you answer their CQ, or they may respond but say that you are off frequency. It can also result in both you and the person that you're talking to 'walking' across the waterfall as each of you corrects your tuning after each transmission.

This issue can be easily resolved in virtually all cases by simply changing the sample rate in your communication program from 11025 Hz to 12000 Hz. It's important to note that changing the sample rate will NOT hurt anything if this problem doesn't exist on your computer, so if you're not sure, we suggest changing it just to avoid the issue. Also, other standard sample rates (8000, 22050, 44.1, etc.) work just fine and do not need to be changed. It should also be noted that Windows 98SE, Vista, Windows 7/8/10 systems never show this offset error.

Sound Card Calibration - Transmit and Receive sample rate errors and sample rate offset errors occur with all sound cards, and can cause you to experience transmit and/or receive problems when operating digital, if the error is large enough. The sample rate error can cause a variety of problems depending on the mode that you are using. With PSK31, other stations may not respond when you answer their CQ, or they may respond but say that you are off frequency. Other stations may respond to your CQ, but be off frequency so that you can't copy them. These errors can also result in both you and the person that you're talking to 'walking' across the waterfall as each of you corrects your tuning after each transmission. On MT63, this problem can result in other stations not being able to copy you at all, or they receive your text in lower or upper case only, or certain characters such as spaces are missing. With SSTV, sample rate errors result in slanted pictures.

If you are using Window ME, 2000, or XP it is important that you see the '11025 Hz Sample Rate offset error' issue above before going any further. This will resolve most sound card calibration issues. If this doesn't completely fix the problem you are experiencing, then sound card calibration might be necessary to remove the remaining error. This can be done with your communication program's built-in calibration routine if available (see your program's documentation), or with the 'Check Sample Rate' utility that comes free with the popular 'Mix-W' program. If you use the Check Sample Rate utility, be sure to select the SignaLink's sound card and let it run for at least 30 minutes. Do not use your computer for anything else during this time, and do not let it go into sleep or suspend mode, or the results will be invalid. After at least 30 minutes of operation, the TX/RX offset error displayed at the bottom of the program window will settle and can entered your communication program to correct for any sample rate error. In DigiPan, for example, you would enter these numbers in the 'Configure - Sample Rate Corrections' menu. Other programs have similar options - See your program's Help documentation for details.

For the most accurate calibration possible, you can calibrate your system using the sound card calibration procedure contained in the MMSSTV program's 'Help' documentation. This procedure uses your transceiver and the WWV time station to obtain sub 1Hz accuracy. While some users might want to do this for the sake of having the most accurate signal possible, it should be noted that this isn't normally necessary. Excellent performance can virtually always be achieved by using one of the procedures listed above.

Starting with Windows 10 update Version 1803 and continuing with the most recent Windows 10 update (2004 as of when this was written), Windows 10 is sometimes shutting off microphone access due an incorrect privacy setting. This results in an error message when starting the communication program (Fldigi, WSJT-X, Digipan, etc.). If you have just updated your Windows 10 OS and are experiencing this error, then follow the steps below to resolve it. If you have experienced a different problem after a Windows 10 update, then we would suggest that you double-check that your sound card settings in Windows and the communication program are correct (these settings can change after a Windows update!).

Ust Pro Ii Port Devices Driver Download

Special thanks to Richard, KE6SHL, for providing us with this information!

1 - Close any communication programs that may be running.

2 - In Windows, go to All settings, then Privacy.
3 - Scroll down to App Permissions, Microphone.
4 - On the right side panel, select/enable 'Allow access to the microphone on this device'.
5 - Microphone access for this device should now be ON. If not, then click Change and switch it to ON.
Note that you can apparently have the switch under 'Allow apps to access your microphone' off and the SignaLink USB will still work.

Ust Pro Ii Port Devices Driver Updater