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

Notification

Icon
Error
LOGic 9.87 Icom Interface broken?
Options View
Previous Topic Next Topic
KD5M
#1 Posted : Friday, July 1, 2016 7:06:01 PM(UTC)
Rank: Member

Groups: Registered
Posts: 25
Location: Crestview, FL

Was thanked: 1 time(s) in 1 post(s)
Today I attempted to connect to my Icom Pro III with LOGic 9.87 and get error No Interface Found on COMxx and no frequency displayed or else LOGic crashes and must be Cleaned and reloaded with the Pro III off.
I think this interface was working prior to my update to 9.86.
I verified the port is indeed working with two other logging programs (Writelog and Wintest).
The port is a Microham virtual port to a DigiKeyer II through CI-V to the rig.
Did this interface also get broken along with the Elecraft interface in 9.86??
Happy July 4th to all.
Edd - KD5M
Back to top
Sponsor
Note: We receive a commission from Amazon when you purchase via this link. It does not affect your cost. Thank you!
Back to top  
wa4pgm
#2 Posted : Sunday, July 3, 2016 8:07:10 AM(UTC)
kchavis

Rank: Advanced Member

Groups: Administrators, Registered, Beta Testers
Posts: 387
Man
Location: Farmville, VA

Thanks: 39 times
Was thanked: 235 time(s) in 203 post(s)
I verified that my Pro II and microHAM microKEYER was working with 9.0.86 and then updated to 9.0.87. Everything seems to working fine here with no errors or crashing. Check to make sure you're using the correct driver and address.
Back to top
1 user thanked wa4pgm for this useful post.
WN4AZY on 7/15/2016(UTC)
KD5M
#3 Posted : Sunday, July 3, 2016 11:33:44 AM(UTC)
Rank: Member

Groups: Registered
Posts: 25
Location: Crestview, FL

Was thanked: 1 time(s) in 1 post(s)
Good Morning.
I can watch the port connection with MicroHam Router go from closed to open as LOGic 9.0.87 opens it, yet LOGic gives the error "No Interface Found on COMxx". Occasionally LOGic will connect to the port and show correct data in its rig window, but more often it gives the above error. It may also crash after attempting to open the port before loading all its other windows. Polling doesn't matter (I don't think it should be checked).
Which LOGic driver is the correct one for the Pro III (46-51)?
Edd
Back to top
wa4pgm
#4 Posted : Sunday, July 3, 2016 1:12:26 PM(UTC)
kchavis

Rank: Advanced Member

Groups: Administrators, Registered, Beta Testers
Posts: 387
Man
Location: Farmville, VA

Thanks: 39 times
Was thanked: 235 time(s) in 203 post(s)
Here's my setup:
Driver 20 "Icom 775, 756, 7800 .......... legancy"
with Poll Icoms checked

No errors
Back to top
1 user thanked wa4pgm for this useful post.
WN4AZY on 7/5/2016(UTC)
KD5M
#5 Posted : Sunday, July 3, 2016 1:55:50 PM(UTC)
Rank: Member

Groups: Registered
Posts: 25
Location: Crestview, FL

Was thanked: 1 time(s) in 1 post(s)
Thank you. Those drivers appear separate from the newer Icom drivers in the list - I had forgotten about them.
That seems to be working now - Driver 20 with Poll Icoms checked.
Have a nice July 4th!
Back to top
KD5M
#6 Posted : Sunday, July 3, 2016 2:30:04 PM(UTC)
Rank: Member

Groups: Registered
Posts: 25
Location: Crestview, FL

Was thanked: 1 time(s) in 1 post(s)
Perhaps I spoke too quickly. The driver (Driver 20) reads the frequency into the XCVR box in LOGic, but LOGic does not pick up the frequency/mode data and input it into the LOGic logging software.
Back to top
WN4AZY
#7 Posted : Tuesday, July 5, 2016 3:34:25 PM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,172
Man
Location: Auburn, GA

Thanks: 1070 times
Was thanked: 520 time(s) in 434 post(s)
Try this:

https://www.youtube.com/watch?v=TEaJ9bkM84Q

Tnx & 73,

Dennis WN4AZY
Back to top
WWW
KD5M
#8 Posted : Tuesday, July 12, 2016 7:48:18 PM(UTC)
Rank: Member

Groups: Registered
Posts: 25
Location: Crestview, FL

Was thanked: 1 time(s) in 1 post(s)
Dennis, the video was helpful - everything was already set as you pointed out but I learned how to change which rig is read by LOGic.
It seems to work using Icom driver 20 but after some time I get an error that LOGic has timed out accessing the rig and it reverts to frequency 00.00 and no longer reads from the rig. Opening and closing tools/setup/misc ham rig .. will reset it and it will read correctly for a while then drop out again.
Any more suggestions or ideas why LOGic loses sync??
Back to top
WN4AZY
#9 Posted : Friday, July 15, 2016 7:52:54 AM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,172
Man
Location: Auburn, GA

Thanks: 1070 times
Was thanked: 520 time(s) in 434 post(s)
Hi--

First of all, does driver #40 just plain not work? The .Net interfaces are a lot cleaner, but .Net is more picky about having a 100%-compatible USB=>RS232 interface.

Does it do it while receiving or just while transmitting? I'm thinking RF....

What happens if you turn polling off in LOGic and turn CI/V transceive on in the rig?

Tnx & 73,

Dennis
Back to top
WWW
KD5M
#10 Posted : Monday, July 25, 2016 10:18:48 AM(UTC)
Rank: Member

Groups: Registered
Posts: 25
Location: Crestview, FL

Was thanked: 1 time(s) in 1 post(s)
Good morning Dennis.
My apologies for my delay in replying.
No, Driver #40 does not work at all - no Frequency or mode/filter control.
Driver #20 will read Fx, change modes and VFOs.
Driver #24, 25 read Fx, changes modes, but not VFOs or filters
Driver #46, 47, 48 do not work - No Fx or mode/VFO/Filter changes
Driver #51 No Fx but will change Mode/Filter
This is all with receiving - no RF involved at all. CI-V is on in the rig.
The interface is a MicroHam DigiKeyer II interface.
Any other ideas??
Edd
Back to top
WN4AZY
#11 Posted : Monday, August 1, 2016 2:41:51 PM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,172
Man
Location: Auburn, GA

Thanks: 1070 times
Was thanked: 520 time(s) in 434 post(s)
Hi Edd:

Sorry, I didn't see your reply until now -- it wasn't marked red or if it was I overlooked it.

Ok, so 40 doesn't work, with or without polling, right? It's unusual that it doesn't work at all -- usually you get OLE errors and stuff like that, but I've never seen it to be totally non-functional.

I KNOW interface 40 is OK -- that's what I use. I run it with polling off and CI/V on in the rig. I use a simple FTDI-based W1GEE Icom interface.

What does Microham say?

Tnx & 73,

Dennis WN4AZY
Back to top
WWW
KD5M
#12 Posted : Monday, August 1, 2016 7:39:18 PM(UTC)
Rank: Member

Groups: Registered
Posts: 25
Location: Crestview, FL

Was thanked: 1 time(s) in 1 post(s)
Good evening Dennis.
No Driver #40 does not work at all.
I haven't asked MicroHam because I don't think it is a MicroHam issue. Both Writelog and WinTest will work without problems using the setup as it is with MicroHam DKII.
LoGic has always worked fine with this interface until recent upgrades (somewhere around 9.87)
Edd
Back to top
WN4AZY
#13 Posted : Tuesday, August 2, 2016 8:18:03 PM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,172
Man
Location: Auburn, GA

Thanks: 1070 times
Was thanked: 520 time(s) in 434 post(s)
Well, call me and I can log in and see if I see anything. We made some changes to the Kenwood/Elecraft interfaces, and some changes to the .Net libraries that affect ALL non-legacy interfaces, but NO changes to the Icom interfaces themselves.

There is always OmniRig.

Tnx & 73,

Dennis WN4AZY
770-307-1496
Back to top
WWW
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 1.9.5.5 | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.086 seconds.