K3 / FLDIGI problem...

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

K3 / FLDIGI problem...

John Ragle
I am:

Using WIN 7 Ultimate.

Using Elecraft K3/100 set to "Data A" or to "USB." RS232 params set to
19200 + 1 stop.
Using E'craft USB to RS232 adapter, which loads driver and selects
COM13. Device manager shows COM13/19200/1 stop.

Using SignaLink USB with E'craft cable to rear connections.

Using either fldigi 3.12.5 or 3.20.b9...problem is the same with either.
 
Using RigCat with K3.xml, 19200 + 1 stop on Com 13.


Everything appears to be normal...receive OK, transmit OK via SignaLink,
TX power levels correct, waterfall appears normal.

Problem: NO CAT Control...no rig control (frequency) via fldigi. (Should
be coming in on the RS232 line. Disconnecting the RS232 line has no
effect.)

On bringing up fldigi it throws an error    "E: rigCAT_getfreq: Hexout
failed" & in addition the "QSY" button on the bottom toolbar is greyed
out. Both these are clearly related to the failure to communicate across
the RS232 line.

Any suggestions?

John Ragle -- W1ZI


______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Reply | Threaded
Open this post in threaded view
|

Re: K3 / FLDIGI problem...

David Herring-2
John,

Have you tried Hamlib to see if you are able to establish a connection  
to your rig?

If Hamlib worked and RigCat didn't that could narrow down your field  
of possibilities.

Also, does the Elecraft utility communicate with your rig using this  
configuration?

73, Dave. K6DCH

Sent from my iPhone

On Mar 31, 2010, at 12:25 PM, John Ragle <[hidden email]> wrote:

> I am:
>
> Using WIN 7 Ultimate.
>
> Using Elecraft K3/100 set to "Data A" or to "USB." RS232 params set to
> 19200 + 1 stop.
> Using E'craft USB to RS232 adapter, which loads driver and selects
> COM13. Device manager shows COM13/19200/1 stop.
>
> Using SignaLink USB with E'craft cable to rear connections.
>
> Using either fldigi 3.12.5 or 3.20.b9...problem is the same with  
> either.
>
> Using RigCat with K3.xml, 19200 + 1 stop on Com 13.
>
>
> Everything appears to be normal...receive OK, transmit OK via  
> SignaLink,
> TX power levels correct, waterfall appears normal.
>
> Problem: NO CAT Control...no rig control (frequency) via fldigi.  
> (Should
> be coming in on the RS232 line. Disconnecting the RS232 line has no
> effect.)
>
> On bringing up fldigi it throws an error    "E: rigCAT_getfreq: Hexout
> failed" & in addition the "QSY" button on the bottom toolbar is greyed
> out. Both these are clearly related to the failure to communicate  
> across
> the RS232 line.
>
> Any suggestions?
>
> John Ragle -- W1ZI
>
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Reply | Threaded
Open this post in threaded view
|

Re: K3 / FLDIGI problem...

Don Wilhelm-4
In reply to this post by John Ragle
John,

Since your software is operating at 19200 bps, have you set the K3
CONFIG: RS232 menu parameter to 19200 as well.
If the software application is smart enough (K3 Utility is), it can
change the K3 port data rate, but many cannot so you have to do it
manually at the K3 end.

73,
Don W3FPR

John Ragle wrote:

> I am:
>
> Using WIN 7 Ultimate.
>
> Using Elecraft K3/100 set to "Data A" or to "USB." RS232 params set to
> 19200 + 1 stop.
> Using E'craft USB to RS232 adapter, which loads driver and selects
> COM13. Device manager shows COM13/19200/1 stop.
>
> Using SignaLink USB with E'craft cable to rear connections.
>
> Using either fldigi 3.12.5 or 3.20.b9...problem is the same with either.
>  
> Using RigCat with K3.xml, 19200 + 1 stop on Com 13.
>
>  
>
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Reply | Threaded
Open this post in threaded view
|

Re: K3 / FLDIGI problem...

Joe Planisky
In reply to this post by John Ragle
IIRC, I had difficulties getting fldigi to work with the K3.xml file  
from the fldigi site.  I had better luck with the one from G4ILO's  
site ( http://www.g4ilo.com/files/k3.xml ).  Never took the time to  
figure out the difference.

That said, I've been having trouble using RigCAT with the 3.20 betas  
and have had to switch back to Hamlib, which seems to work OK.

So I'd suggest trying to use Hamlib and see if you get better  
results.  If that works and you still want to use RigCAT, try G4ILO's  
xml file.

73
--
Joe KB8AP

On Mar 31, 2010, at 3:25 PM, John Ragle wrote:

> I am:
>
> Using WIN 7 Ultimate.
>
> Using Elecraft K3/100 set to "Data A" or to "USB." RS232 params set to
> 19200 + 1 stop.
> Using E'craft USB to RS232 adapter, which loads driver and selects
> COM13. Device manager shows COM13/19200/1 stop.
>
> Using SignaLink USB with E'craft cable to rear connections.
>
> Using either fldigi 3.12.5 or 3.20.b9...problem is the same with  
> either.
>
> Using RigCat with K3.xml, 19200 + 1 stop on Com 13.
>
>
> Everything appears to be normal...receive OK, transmit OK via  
> SignaLink,
> TX power levels correct, waterfall appears normal.
>
> Problem: NO CAT Control...no rig control (frequency) via fldigi.  
> (Should
> be coming in on the RS232 line. Disconnecting the RS232 line has no
> effect.)
>
> On bringing up fldigi it throws an error    "E: rigCAT_getfreq: Hexout
> failed" & in addition the "QSY" button on the bottom toolbar is greyed
> out. Both these are clearly related to the failure to communicate  
> across
> the RS232 line.
>
> Any suggestions?
>
> John Ragle -- W1ZI
>
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Reply | Threaded
Open this post in threaded view
|

Re: K3 / FLDIGI problem...

Julian, G4ILO
I also had trouble with Fldigi using a Prolific based USB adapter (which the Elecraft adapter also is.) The FTDI based adapter was OK.
Julian, G4ILO. K2 #392  K3 #222 KX3 #110
* G4ILO's Shack - http://www.g4ilo.com
* KComm - http://www.g4ilo.com/kcomm.html
* KTune - http://www.g4ilo.com/ktune.html