Welcome Guest! To enable all features please Login or Register.



Rig and rotor interface troubleshooting
#1 Posted : Thursday, June 9, 2011 6:28:57 AM(UTC)

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,080
Location: Auburn, GA

Thanks: 988 times
Was thanked: 492 time(s) in 407 post(s)

Common Problems with Rig and Rotor Interfaces

  • Wrong baud rate. Make sure the baud rate of the rig and LOGic match. LOGic's default baud rate is set for the most common factory setting, but to be sure, set the baud rate in both the rig and in your software. Note that some rigs have an AUTO baud rate setting. Do not use this. It will not work in LOGic, and probably other software as well.

    The baud rate and other settings accessible in the device manager have no effect. They are overridden by your software.

  • Wrong serial port specified. The serial ports on the back of your computer are often not labeled. If you are not sure that you are specifying the proper Com port, try all port settings. LOGic and TRX-Manager show only Com ports that actually exist in the Com port selection. Some software shows all possible Com ports whether they are installed or not.

    If you are using USB => RS232 adapters, you may determine the proper COM port unplugging and replugging the device while observing the Windows device manager.

  • Wrong stop bit setting. We use 2-bit almost exclusively--it puts more space between the asynchronous characters and is less prone to RFI etc. Either setting should work. However, we have had reports on 1 stop bit working and 2 stop bits not working. We had one case where a Yaesu FT-767 would consistently return the wrong value on certain frequencies only when set to 2 stop bits, but worked fine with 1 stop bit.

  • Non-functional serial port. First, make sure that the Com port shows up in the Windows device manager. If it does not show up there, software will not be able to access it. Test your port by doing a loopback test. Also, test the port with other Windows software. The LOGic and TRX-manager demo is readily available. LOGic automatically performs diagnostics on the port and rig interface, and easily provides valuable information to aid in troubleshooting.

    Note that just because a port shows up as OK in the device manager doesn't mean that it is actually working.

    Note that Prolific-based USB=>RS232 adapters are not reliable. We recommend one with an FTDI chipset like the one we sell.

  • Interface or cable bad. Test your interface or cable by doing a loopback test.

  • Cable is of improper type. We get a lot of calls about this, especially on rigs that have a built-in interface and do not require a level converter. Quite often the rig requires a straight-thru cable, and the customer believes this is what he has based on what a salesman at the computer store told him. But in fact, he has a null-modem cable. Check your cable out with an ohmmeter to make sure you have the right thing. Info on which cables are required for various rigs is available on our interface hardware ordering page.

  • The rig is not plugged into a serial port. A serial port on a computer is usually a 9-pin male connector. Older computers may have a 25-pin male connector. A 25-pin female connector is a parallel port. You cannot operate a rig from a parallel port. If you do not have an unused serial port, contact PDA to purchase a USB to RS-232 adapter.

  • Wrong radio driver specified. Try different radio driver options.

  • Rig is defective. This is rare, but it does happen.

  • Rig not turned on or not connected (we get calls about this!)

  • Wrong CI/V address (Icom and some Ten-Tecs only).

  • Transceive matrix (also called CI/V Transceive) not turned on in the rig (Icom and some Ten-Tecs only). Transceive Matrix causes the radio to automatically send out status info whenever the rig is manipulated--changing the frequency or mode for example. If this is not turned on, LOGic's rig control panel display will not update, but it will log the mode and frequency when adding a QSO, and will control the rig.


LOGic can give three basic error messages related to the rig interface:

  1. Timeout or something to that effect. LOGic requested info from the rig and did not receive anything back. This will happen if the rig is not turned on or connected, or if the port or interface or cabling is bad or improper.

  2. Port in use. Check to see if some other program or another serial device in LOGic is using the same port. You CANNOT put, for example, a TNC and radio on the same port. Icom and Ten-Tec-compatible rigs can share the same port. Otherwise, you cannot put two rigs on the same port.

  3. Port not found. You specified a port in setup that does not exist, or that Windows does not see. LOGic only displays available ports on its setup menus, but it is possible to hack the .INI file (or transfer an imporper .INI file from another computer, ). You'll get this error if you set up for a port, then remove that port or the port goes bad.

There are two other messages that you can get from Icom and compatible radios:

  1. Interface OK, but no response from rig. Icom interfaces echo everything sent to them back to the computer, regardless of whether the rig is connected or even exists. LOGic can detect this. If you get this message, you know that you have the right port and the interface is working. If this happens, check baud rate and the rig.

  2. If you get a message about a bad address, LOGic will instruct you to switch modes on the rig. This causes the radio to send a packet so that LOGic can detect the address

Troubleshooting procedures -- substitution

We have already mentioned loopback testing to test cables, interfaces, and ports. However, substituting known good components for questionable ones is the easiest and most reliable way to troubleshoot--if you have access to the additional components. A friend who has successfully interfaced his rig to a computer can be a friend indeed! His radio need not be the same model as yours. One that uses a similar level converter or cable will do. Click here for info on the interface hardware shared by various rigs.

Take your interface or cable and rig to your friend's shack. Verify his rig is working. Substitute your interface or cable for his. At this point you will know whether or not your cable or interface is good or not.

Assuming the cable or interface is good, substitute your rig for your friend's rig. Ideally, your friends' radio would be identical to yours. Simply make sure the settings such as baud rate, and address for Icoms, is identical. Your rig should then work with without making any changes to your friend's software.

Even if your rigs are not identical, most models of Kenwoods and most models of Icoms will work with the same software settings. Just make sure that the baud rate and Icom address in your rig is set identically to your friends'. If you have Yaesus or other makes of rigs, a different software driver setting will usually be required.

LOGic 9 supports a new radio interface platform that supports the new port sharing feature, and is generally faster and has more features. The old LOGic 8 interfaces are available also. They are marked "(legacy)" in the dropdown list. When selecting the proper rig in LOGic's setup, try both the new interface and old legacy interface if available.

More software-specific troubleshooting info

LOGic radio interfacing FAQ

TRX-Manager support page
Note: We receive a commission from Amazon when you purchase via this link. It does not affect your cost. Thank you!
#2 Posted : Friday, June 10, 2011 6:14:31 PM(UTC)

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,080
Location: Auburn, GA

Thanks: 988 times
Was thanked: 492 time(s) in 407 post(s)

Model-specific Rig Interface Issues

Here is some model-specific information that we have collected.

Elecraft K2 & K3

Use the Kenwood 850 driver. The K3 does not support setting the current VFO to B.

Kenwood TS-2000

This rig has a different default baud rate than the rest of the Kenwood line. Set both the rig and LOGic to 9600 baud, 1 stop bit. In LOGic 5 or later, use the TS-850 driver. We have also had reports that this rig is fixed at 57,600 baud.

Apparently the Auto Information mode of this rig does not work, at least not like the rest of the Kenwood line. The latest update to LOGic 6 includes a new driver that polls the rig. Without this driver, the interface still works--the proper frequency is always logged. The frequency display in LOGic just does not update in real-time.

Kenwood TS-850S

The optional DSP-100 unit for this rig plugs into the connector where the level converter normally goes. To use the level converter with and the DSP simultaneously, plug the DSP into the rig, and the level converter into the CONT OUT jack on the DSP unit.

Icom and Icom-compatible Ten-Tec

If your rig is not listed in LOGic's Driver dropdown, start with ICOM. It covers most rigs. If Split does not work, try other drivers. Some older rigs do not support setting of Split. For these rigs, use the ICOM BASIC driver.

Consult the manual for the default baud rate and CI/V address and set LOGic accordingly. If If the desired address is not in the dropdown list, merely type it in.

The CI/V address and baud rate are changeable on most Icom rigs, so if the default does not work, check the settings of the rig. Most rigs have menus accessible from the front panel. Consult your manual.

Some Icoms have a AUTO baud rate setting. Do not use this setting. It will not work. Choose an actual baud rate (9600 baud is good), and of course set the software to match.

Some Icoms permit setting of split frequency with a computer. If your rig supports this, use the ICOM driver in LOGic to give you this capability. (If in doubt, try and find out).

Most Icoms do not support reading the split status. The Icom driver in LOGic remembers the last split state set from within LOGic, and uses that to determine split status when logging. In other words, LOGic will properly log split frequency only if you control the split status only with LOGic. If you change the split status from the rig's front panel, LOGic has no way of detecting this.

Icom and Ten-Tec rigs have a feature that causes it to automatically send any changes made to the rig via the front panel to the computer. This feature is called by various names--"Transceive Matrix", or ."CI-V Transcieve". The Omni-6 calls this feature "Continuous Data Echo".

This feature should be on in order for LOGic to update its display of the rig's frequency and mode as you tune the rig with the front panel. (If this feature is off, LOGic will still log the proper frequency, since it always requests the frequency, mode, split status, etc. whenever it needs it. However the real-time display will not update).

LOGic has an option to poll Icom rigs. We have seen one case where the CI/V Transceive was reportedly turned on, yet it was not sending data. The customer used the Poll Icoms option instead.

Sometimes, when running multiple Icoms on the same port (using the Icom CI/V networking bus), the radios will interfere with each other--tuning one rig will cause the others to QSY also. Make sure that each rig is set to a different address. If the interaction still occurs, turn off the CI/V Transceive in the rigs, and turn on the Poll option in LOGic.

In LOGic 9 and later, you may assign multiple Icom rigs to the same port, each to a different port, or have one group of Icoms on one port and another on a second port -- you have total flexibility in sharing the CI/V bus.

In previous versions of LOGic, all Icom drivers in LOGic have a counterpart that does not use the common Icom CI/V bus, but permits using a different unshared COM port for each rig.

Some Icom rigs have the ability to set the width of the frequency field in the data returned by the radio. This setting should be set to 5 bytes. (The IC-735 is an exception. It always sends 4 bytes.)

LOGic 9 automatically detects the frequency length. Users of prior versions of LOGic must be careful to select the proper driver. An example of problems experienced by an improper setting of this option is as follows: A customer with a 756 Pro III reported that the rig would return the proper frequency when the rig was polled. However, spinning the VFO knob would not cause a frequency update, even though CI-V Transceive was on, and LOGic's data scope verified that the radio was sending data. The Icom 735 driver would properly display the frequency as the dial was turned.

You can test an Icom to make sure that it is sending a signal with a multimeter. Make sure the Transceive Matrix/CI-V Transeive feature of the rig is on Connect the meter to the output of the rig's data jack. When set to DC, our meter shows about 2 volts, that spasmaticly decreases as you spin the VFO dial. When set to AC, our meter showed almost nothing when the dial was stationary, and about 0.8 volts when spinning the dial.

The meter we used is a Radio Shack 22-178 "Auto Range Sampling Bargraph Digital Multimeter". It is probably manufactured by Fluke, and is probably identical to their low-end model. Both the bar graph and digital display indicate very obvious change as the dial is spun. Your meter may not be responsive enough to detect the data stream.

Kenwood rigs have a feature similar to Icom's Transceive Matrix. They call it Auto Information mode. It must be enabled in software. So, if you are able to control your Kenwood but not read from it, you should be able to test it with a voltmeter as follows. Start LOGic and control the rig to initialize Auto Information. Disconnect the rig from the interface and connect the voltmeter to the rig's data out (see the Loopback Test page for pinouts). Proceed as described for Icom.

We have not been able to get the Auto Information feature to work on the TS-2000.

Omni 6

The Omni 6 + requires a custom-made cable. The rig end needs a DB25 male connector. Here is the information for making your own cable for a 9-pin RS-232 port.
Computer 9 -pin Radio 25-pin
2 --> 2
3 ---> 3
5 ---> 7

On the computer end, jumper:
pins 7 and 8

pins 1, 4, and 6

If you still have a 25-pin serial port on your computer, here is how to make a cable: Pins 2,3,7 are run straight through to the DB25F connector on the computer. On the DB25F on the computer, pins 4,5 are jumpered and pins 6,8,20 are jumpered.

The Omni 6 can send frequency data to the computer in 4-byte or 5-byte format. The configuration that we know works is to set the Omni 6 to 4-byte frequency and set LOGic to use the Icom 735 driver. However, other features may be available by setting the Omni 6 to 5 bytes, and using the Icom Plus driver in LOGic.

Yaesu FT-847

The first release of this rig was incapable of sending mode and frequency data to the computer. FT-736 software works with this ROM.

The vast majority of 847's have the new ROM that provides full two-way communications. If you have the old ROM, contact Yaesu for an upgrade.

Yaesu FT1000D and FT990

These radios have been sold with two substantially different ROMs. The old-style ROMs were somewhat problematic because they would return information about all memories--an enormous amount of data--when requesting mode/freq status. This would tie up the radio for around 3 seconds. The new ROMs, which started shipping in the spring of 1992, overcame this problem by providing new commands that cause the radio to return only a minimal amount of data. Besides increased speed, we have had reports of higher reliability with the new ROMs.

To see if your radio has the new or old chip, turn the radio off. While holding down the 1 and 3 keys on the keypad, turn the radio on. On the FT1000, the new ROM is revision 6.0 or later. On the FT990, the new ROM is revision 1.3 or later.

Apparently Yaesu no longer provides upgraded ROMs (The FT-1000D new ROM part# was G1093217. The cost was about $10. Yaesu America phone# is 310-404-2700 last we heard. ). However,third party replacements are available. Search the web and eBay.

To the best of our knowledge, the FT-990 ROM is soldered in place, and it is difficult to find a replacement -- your best bet is finding a junked radio and salvaging the board that contains the chip. We do not know if the ROM version is printed on the chip or not.

There is almost no software available to supports these old ROMs. We dropped support for the old ROMs with LOGic 5.0. TRX-Manager still supports them.

Ten-Tec Pegasus and Jupiter

LOGic supports interface to the Pegasus , Jupiter, and Omni 7 radios. This permits simultaneous use of LOGic and the Pegasus control program. LOGic can read and control these radios. The Jupiter is just like the pegasus except that it features a physical front panel. All information on interfacing the Pegasus applies to the Jupiter.

This interface uses an intermediate disk file to pass information between the two programs. This file is buffered, so there is no actual wear and tear on your disk drive as you use the program. No serial port is actually used by LOGic.

Make sure you are running LOGic version 5.2.54 or later. Download the latest Pegasus software from Ten-Tec. Install the software and run it. Insure that the software is communicating with the rig.

Run LOGic. Go to tools/setup/misc ham setup. Select Radio Ifc. Select the "Pegasus with disk file interface" driver. Leave the Port selection blank, and baud rate 0. This interface does not use a serial port. Click OK.

You will be prompted for the inteface disk file name. Select PEGASUS.OUT. It will be located in the same folder as the Pegasus software. LOGic will remember the file location and will not ask for it again. (The file name is stored in Pegasus.INI, which is located in the LOGIC5 folder.)

Note that the Pegasus program does not permit setting or reading of split status. LOGic merely assumes that split mode is on if the TX and RX frequencies are different.

The N4PY software also works with LOGic. Be sure to select the interface disk file that is compatible with Ten-Tec's program. By default it's interface disk file is different than the file made by the Ten-Tec software, and therefore not compatible with LOGic. Consult the N4PY documentation for details.

Updated May/29/16
#3 Posted : Thursday, March 15, 2012 12:43:08 PM(UTC)
Rank: Newbie

Groups: Registered
Posts: 2

Hi love my new logic9, was having trouble with it polling my radio. Have an Icom 746 pro. Changed the bit from 2 to 1 and works great. db
#4 Posted : Thursday, March 15, 2012 8:16:45 PM(UTC)

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,080
Location: Auburn, GA

Thanks: 988 times
Was thanked: 492 time(s) in 407 post(s)
Thanks for the info. Changing stop bits has made a difference on many occasions, althougnh 2 seems to usually be the ticket.

BTW, unless you are using more than one rig in the CI-V bus, I advise not polling Icoms. There is much faster response when you spin the dial, and less load on the computer. LOGic ALWAYS polls when it NEEDS the frequency to log it or whatever -- this is not optional and cannot be turned off -- wanna make sure we have the CORRECT frequency. Maybe that is what you were referring to.
#5 Posted : Friday, April 6, 2012 4:58:02 PM(UTC)
Rank: Newbie

Groups: Registered
Posts: 2
Location: Fort Walton Beach, FL

Thanks: 1 times

I've been trying to get the software to recognize my ICOM Pro III, tried: 19200, N, 1...works sometimes, tried: 19200, N, 2...nothing.
Polling none used.

Great program, I have become frustrated with the interface problem however.

What say you ICOMPROIII users?


John, W4JCM
#6 Posted : Sunday, April 8, 2012 11:01:20 AM(UTC)

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,080
Location: Auburn, GA

Thanks: 988 times
Was thanked: 492 time(s) in 407 post(s)
OK, you are mentioning parity (19200, N, 1) so I guess that you are setting the baud rate etc in Windows? You must set these in LOGic under tools/setup/misc ham setup. The Windows settings are ignored.

I would try lower baud rate -- 9600 is popular. Do not use AUTO baud rate on the rig. Set it to 9600 baud also.

Are you using a USB adapter? If you got it from us or have an FTDI based unit, you should be golden. Anything else is unlikely to work reliably.

Check this out.

Tnx & 73,

Dennis WN4AZY
#7 Posted : Sunday, April 8, 2012 1:35:24 PM(UTC)
Rank: Newbie

Groups: Registered
Posts: 2
Location: Fort Walton Beach, FL

Thanks: 1 times
I am using the US Interface Navigator.
I had it working for awhile with the 19200 baud rate, but it would only last about several frequency changes.

The setting only last for a few minutes and then nothing...so maybe the speed was too high.

#8 Posted : Monday, April 30, 2012 10:52:33 PM(UTC)
Rank: Newbie

Groups: Registered
Posts: 1
Location: W. Bridgewater, MA

Same problem here !!! Same premeters your using.
It used to work fine with Logic 8.

I've been using Logic since ver 3 and never had this kind of problem !!!

Bob, K1VU
#9 Posted : Tuesday, May 1, 2012 1:40:10 PM(UTC)

Rank: Advanced Member

Groups: Registered
Posts: 364
Location: Viterbo, VT - ITALY

Thanks: 57 times
Was thanked: 85 time(s) in 79 post(s)
Hi All,
i'm an ICOM user and i never find problems to interface LogicX with that transceivers.
I working with 7600, 756PROIII, 7000, 910H and all are connected with CT-17 and two RIGblaster Pro at different Logmainforms in Logic9. I'm using the same parameters as 19200,8,1,N, but I changed only the addresses, going into the appropriate menu, in all radio devices.
73's de IKØCHU Mauro
Users browsing this topic
Guest (2)
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.146 seconds.