locatornax.blogg.se - Echolink ham radio issue with window update

Added Recent QSOs folder to Explorer View.

Fixed bug with mislabeled audio devices on Audio tab.

Better sizing/rendering on Windows “large font” and/or high DPI settings.

This is a significant change to the audio chain that should result in noticeably better SNR and audio quality.

Migrated to 16-bit audio, to match all modern sound cards.

New “ Call CQ” feature (also to be rolled out on Mobile app editions), including DTMF code to activate.

Updated main window look, with dockable menu bar and selectable visual styles.

You should now be on your way to digital radio communications.After a 14-year hiatus, we are pleased to announce that EchoLink for Windows version 2.1 is now available. The very NEXT thing you should do is program your ID code into the general data page and give the radio a name (preferably, your callsign). I suggest you first read the radio in so that the radio data can be received. You should now be able to talk to your radio using the v 1.36 CPS. It should say that it is working properly. You should be able to click on it and verify the status of the driver. Your device will now appear under the USB Hub listings in Device Manager. The installer should find the appropriate driver under that folder tree and install it. Vii) Locate the folder where you installed your CPS and there should be a USB sub-folder there. Vi) Right-click on device and select "Update Driver." DO NOT ALLOW IT TO SEARCH THE WINDOWS DRIVER DATABASE - IT WON'T FIND IT THERE. It should first appear under "Other Devices." V) The Devices list in Manager should update with your device with a yellow marker (flag-like highlite). Iv) Connect USB cable to any USB port (hopefully on the front or side of your computer laptop or desktop). Iii) Attach USB cable to radio and power the radio on. Alternately, open Control Panel and locate Device Manager icon click on it. Ii) Right-click on "My Computer" or "My PC" (the upper-left icon on the desktop). I) Power up PC allow Windows to finish booting. The fix is, included with the v 1.36 CPS is the USB driver(s) that addresses this. It requires a separate driver that no version of Windows (I'll call it the Windows Driver Cloud) supplies. I discovered the following:Ī) The cable supplied with the radio is NOT a USB to serial cable. It works perfectly.Ģ) I also initially had USB problems.

Solution: Find an updated software higher than rev 1.30. It works.ġ) The supplied CPS (computer programming software) reported the radio as the "wrong model" when I initially tried to write to it or read in from it. I was initially successful with programming an analog channel just to verify data transfer.

I just finished interfacing my MD-390 to Windows 7.