I've been getting the following message all day today:

"A timeout has ocurred while atempting to communicate with a rig.
Make sure rig is turned on and check cabling and setup paramaters.

(get_cur() flags) 0 characters in buffer

I have to go to Tools > Reset Radio & Rotor interface.

The radio is turned on (FT-1000D) and the CAT system is on connected o the radio (I see the flashing CAT System on the radio's screen).

I don' have anything else connected to the radio.

Any ideas what might be causing the radio to lose communication with LOGic ?

Hi Dennis,
I rebooted the pc and checked all the connections. I'm using a serial port with the FIF-232C CAT System interface. The polling interval in LOGic was set to 2.0 (I changed it to 3.0). The STOP BITS is set to 2.0. The error happens no matter if I'm transmitting or just listening. Now that I've changed the polling interval to 3.0, it hasn't happened in a while, but I'll post a message if it happens.

Well, I thought 3 seconds fixed it but the error timeout returned. The PC is running fine (Windows 7). I defragged and ran malware, spyware and it came up clean. I'll put the polling back to 2. I wasn't transmitting at all when it happened. I was going through my log and just listening to 40 CW when it happened again.

Update 12/31/2011: I am logged into a local node using Telnet1 and have been listening to ZS4L on 15 meters for the past hour and the timeout message has appeared a dozen times. I've had to reset the radio each time. The pc has been defragged several times and is running fine, I ran maleware and spyware (nothing found).

The STOP BITS is set to 2 for the FT-1000D and the POLLING INTERVALS is set to 2.0, BAUD RATE is set to Ø (default). All the cables to the radio and CAT interface have been checked and are secured.

I am out of ideas what might be causing the timeout error to appear so many times

Hi Vin:

Make sure LOGic 9 isn't running in compatibility mode. That will make it dreadfully slow when accessing the Prefix table (which it does all the time). Right-click the shortcut you use to start it, and look at the COMPATABILITY tab.

As for the flakiness of the rig, are you using any USB=>RS232 adapters? Anything without a FTDI driver is suspect.

Tnx & 73,

Dennis WN4AZY

Hi--

What are you using for an RS-232 port on your computer to plug the FIF-232C into? If it is a USB=>RS232 adapter, then it has drivers. If it is made by FTDI it will have FTDI drivers. If from some other manufacturer, then it will have their drivers. Only FTDI is known to work.

Other manufacturers may work. Those that do not cause errors, not slowness that I have seen. Still, you could try disabling the rig and seeing if that fixes the slowness.

Call me and I can log in and take a look too -- I might see something.

Tnx/73,

Dennis WN4AZY

Hi Dennis,

LOGic 9.0.71 is still running painfully slow. I sent you an email this evening because I could not import my adif file for the CQWW 160 M SSB contest I just completed this weekend. I also found the following "not responding" messages:

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path: C:\Program Files\LOGic9\logic.exe

Problem signature
Problem Event Name: AppHangB1
Application Name: logic.exe
Application Version: 9.0.71.0
Application Timestamp: 47139f24
Hang Signature: 44b8
Hang Type: 6400
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Hang Signature 1: 44b8acadaba4d3ab1b38506572dd3e54
Additional Hang Signature 2: 3079
Additional Hang Signature 3: 307978a87f1955d2bdb8c7abe0010f60
Additional Hang Signature 4: 44b8
Additional Hang Signature 5: 44b8acadaba4d3ab1b38506572dd3e54
Additional Hang Signature 6: 3079
Additional Hang Signature 7: 307978a87f1955d2bdb8c7abe0010f60

What is causing LOGic 9 to be so slow? LOGic 8 worked just fine.

Thanks,
Vin

Hi Dennis,

That error dump came from Windows 7 Action Center. I had a small flag show up on my taskbar and when I opened it, it listed LOGic9 twice with the same error dump on 2 different days.

Vin, 73
K1VC

You are most welcome. YOU are really the one who figured it out!

For my notes and for anyone else experiencing extreme slowness in LOGic 9:

LOGic was too slow to be useable. It took maybe 2 minutes to load and 2 minutes to exit. Some things worked OK. Prefix lookup, which is known to be super-slow if LOGic is run in Compability Mode, was fine. Going to tools/export took forever. I thought maybe it was the slowness of opening a file selector dialog, but no. Edit a File worked fine.

The solution was to move the install directory from c:\program files\logic9 to c:\logic9. Why this is, I have no idea. The system configuration was a little uncommon: A 64-bit processor running a 32-bit version of Windows 7.

We did not try safe mode or MSCOnfig to clean-boot. Vin had already tried disabling his virus checker. We also did not try the default installation directory of c:\program files\logic. But again, why should the location matter?

I will do some reading on Program Files vs Program Files (x86). Other than the fact that the registry affects default installation folders, as far as I know, they are just folders.

Tnx & 73,

Dennis WN4AZY