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

Notification

Icon
Error
Radio Interfacing Issue
Options View
Previous Topic Next Topic
K8ZT
#1 Posted : Saturday, January 21, 2012 11:11:57 AM(UTC)
aluscre

Rank: Advanced Member

Groups: Registered
Posts: 46
Location: Stow, OH

Thanks: 1 times
Was thanked: 8 time(s) in 8 post(s)
I have not been able to get Radio interface working to Elecraft K3.

I had it working with LOGic8.

K3 Interfacing issue
Back to top
WWW
1 user thanked K8ZT for this useful post.
EI7BA on 1/23/2012(UTC)
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 : Saturday, January 21, 2012 11:48:56 AM(UTC)
kchavis

Rank: Advanced Member

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

Thanks: 36 times
Was thanked: 224 time(s) in 193 post(s)
Scroll down and select the legacy Kenwood 850 driver the K3 driver does not work.
Back to top
EI7BA
#3 Posted : Saturday, January 21, 2012 11:57:52 AM(UTC)
Rank: Member

Groups: Beta Testers, Registered
Posts: 28
Location: Cork

Thanks: 3 times
Hi Folks!
I have a similar problem with my FT5000.. Similar screens and messages to K8ZT, except it's "FT5000.INIT"

Also, my Spots window refuses to open, giving "variable AWARDMODE not found", followed by "unknown member SPOTLOGREF"
If I try to reopen the Spots window, the program crashes.
I'm running Win 7 64bit.
Vy 73
John EI7BA
Back to top
WWW
N5XZ
#4 Posted : Saturday, January 21, 2012 1:58:09 PM(UTC)
Rank: Advanced Member

Groups: Registered, Beta Testers
Posts: 409
Location: Richmond, TX

Thanks: 35 times
Was thanked: 57 time(s) in 54 post(s)
Same exact problem here as K8ZT with my K3, same baud rate, etc. I didn't try different baud rates, though.
73, Allen N5XZ
Back to top
W3KL
#5 Posted : Saturday, January 21, 2012 2:43:25 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 36

Was thanked: 2 time(s) in 2 post(s)
My problem is that it won't open the "Misc ham setup..." window.

Running XP.
Back to top
WN4AZY
#6 Posted : Saturday, January 21, 2012 7:54:58 PM(UTC)
admin

Rank: Administration

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

Thanks: 997 times
Was thanked: 496 time(s) in 411 post(s)
Ok, sorry. Someone reported that the new 850 driver works minus the VFO B button, but turns out he was in fact using the 850 legacy driver unknowingly. So I will get the new Kenwood driver working, then a special K3 driver will follow shortly.

So use the legacy driver for now. There is also OmniRig. However, the only thing I have confirmed wrong with the 850 driver is that the VFO B button needs to be removed (not supported by the rig), and A=B not working. Not sure if OmniRig supports A=B or not....

Thanks for the screen shots. They will help immensely.

EI7BA: Sorry, please download again. Fe emailed you. Our mistake.

W3KL: Sorry, have not run into this one. What version of Windows? I will see if I get any other reports, and will call you.

Tnx & 73,

Dennis WN4AZY
Back to top
WWW
 |  Edit by user
1 user thanked WN4AZY for this useful post.
K8ZT on 1/22/2012(UTC)
W3KL
#7 Posted : Saturday, January 21, 2012 9:35:41 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 36

Was thanked: 2 time(s) in 2 post(s)
Originally Posted by: WN4AZY Go to Quoted Post
Ok, sorry. Someone reported that the new 850 driver works minus the VFO B button, but turns out he was in fact using the 850 legacy driver unknowingly. So I will get the new Kenwood driver working, then a special K3 driver will follow shortly.

So use the legacy driver for now. There is also OmniRig. However, the only thing I have confirmed wrong with the 850 driver is that the VFO B button needs to be removed (not supported by the rig), and A=B not working. Not sure if OmniRig supports A=B or not....

Thanks for the screen shots. They will help immensely.

EI7BA: Sorry, please download again. Fe emailed you. Our mistake.

W3KL: Sorry, have not run into this one. What version of Windows? I will see if I get any other reports, and will call you.

Tnx & 73,

Dennis WN4AZY


Dennis XP, SP3 (was mistaken in an earlier post...I do have SP3)
Back to top
EI7BA
#8 Posted : Sunday, January 22, 2012 7:46:26 AM(UTC)
Rank: Member

Groups: Beta Testers, Registered
Posts: 28
Location: Cork

Thanks: 3 times
Thanks for the new download Fe/Dennis.. Spotlog now fine.
I still have the problem with rig control...BUT! I found a workaround.
I had the same problem as K8ZT, with the same errors.
Before, when I went to select my rig, the correct rig description was already showing in the selection window by default.
This time, I tried different rigs from the drop down, and selected the correct one (FT5K)
When I returned to LOGic, the errors disappeared, but it said the rig was not available.
I tried the reset command a few times with no success.
However! When I closed, and re-statred LOGic9, the rig control was working.
When I went back into Setup/rig interface, and came back out, I had the same problem.
Again, by exiting, and restarting LOGic, it was working again.
I run Win 7 64 bit, and my com port is a virtual port, running rig control from a Microham MicroKeyer II.
Vy 73
John EI7BA
Back to top
WWW
WN4AZY
#9 Posted : Sunday, January 22, 2012 12:36:16 PM(UTC)
admin

Rank: Administration

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

Thanks: 997 times
Was thanked: 496 time(s) in 411 post(s)
I researched this last nite and today, and discovered the code that is causing an error is common to ALL of the new non-legacy driver interfaces. It is the line of code that opens the COM port, and the actual error is coming from inside the .NET DLL I wrote or perhaps from inside the .NET framework itself. So the good news here is that there may in fact be no problem with the new Kenwood driver interfaces per se.

But for the people getting this error, none of the new interfaces will work.

I thought it might be not shipping a DLL or something, but that is not the case. I can use the new Kenwood driver on two new machines with no error. Ok, not USE them actually since I don't have a Kenwood, but the port does open without error, and I get a timeout as expected.

Please try changing the stop bit setting. Also, do not use 0 (default baud rate). Select the actual baud rate. I tried leaving the baud rate 0 an no error here however.

I am now researching that "OUT OF PRESENT RANGE" error.

EI7BA: Ok, this is the new non-legacy interface? Does everyone else having this problem have a Microham? Try unplugging the Microham and using a real COM port or FTDI-based USB=>RS232 adapter.

Let me know.

Tnx & 73,

Dennis WN4AZY
Back to top
WWW
 |  Edit by user
EI7BA
#10 Posted : Monday, January 23, 2012 10:09:02 AM(UTC)
Rank: Member

Groups: Beta Testers, Registered
Posts: 28
Location: Cork

Thanks: 3 times
Hi Fe/Dennis..
I've done as you suggested, and it looks like there are two issues here..
The first definitely concerns LOGic.
As you suggested, I ran LOGic9 rig control from the native COM1 on the motherboard, having first unloaded any virtual ports, followed by a re-boot, so that the only port that LOGic could use, was COM1.. I configured my rig on com1, and ran it. I kept going in and out of the rig setup menu, and found that I kept getting an error (see attached .JPG). I could more or less, get rid of the error by selecting "Turn off rig and rotor interfaces" before going into the "misc ham setup". Some times I got the same error when coming out of the setup menu. Once rig control was set up, it worked fine, and problems only arose when trying to change the rig/rotor setup.

When doing the same thing with virtual ports loaded, there are serious issues. Again, the problems occur when trying to change the rig/rotor setup, but this time you don't get the luxury of a fault report. Usually, the whole machine hangs, and you must power off and re-boot. Again, by doing "turn off radio/rotor interfaces", you'll eventually get safely to the rig/rotor setup menu. Sometimes the PC will hang when exiting from this setup menu. Having exited safely, sometimes LOGic can't "see" the rig. This can be corrected by re-starting LOGic.
The crazy thing is, that once you get the rig control working, on either an RS232, or virtual port, it works OK.
There appears to be a question mark over some of the Win 7 virtual port drivers. There has been some discussion on the Microham reflector about this.. A quote from W4TV on the issue..

"Please read the prior messages about this subject - specifically
message 12328:
http://groups.yahoo.com/.../microHAM/message/12328

microHAM's programmers discovered serious bugs in the USB drivers
released by FTDI - the makers of the USB chipset used in all microHAM
interfaces after Router 8.0.7 was released. Those drivers are WHQL
Certified and have been installed through Windoes Update since April
2011!

Work is ongoing on a temporary fix (beta software with older, stable
drivers) but a permanent fix will not be possible until FTDI release
properly functioning, certified drivers.

73,

... Joe Subich, W4TV
microHAM America[/i][/i][/i]

I hope this helps Dennis.
Vy 73
John EI7BA


PS..I can't figure out how to attach a pic to this, so I've sent it via email.
Back to top
WWW
WN4AZY
#11 Posted : Monday, January 23, 2012 2:40:49 PM(UTC)
admin

Rank: Administration

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

Thanks: 997 times
Was thanked: 496 time(s) in 411 post(s)
Ok, I found the problem -- it doesn't work with baud rates of 38400 or higher.

Here is a fix for this. Try this and let me know.
http://hosenose.com/Foru...his-update.aspx#post481

Note that the new Kenwood drivers now load, but have not been tested. If someone can try it and let me know. For the K3 use the kenwood non-legaxy 850 driver.


Tnx & 73,

Dennis WN4AZY
Back to top
WWW
 |  Edit by user
EI7BA
#12 Posted : Monday, January 23, 2012 2:50:56 PM(UTC)
Rank: Member

Groups: Beta Testers, Registered
Posts: 28
Location: Cork

Thanks: 3 times
Thanks Dennis!
I just loaded it, and it seems stable. I'll let you know if any glitches appear.
Vy 73
John EI7BA
Back to top
WWW
Users browsing this topic
Guest (5)
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.074 seconds.