I'd like to hear from anyone successfully using WSPR with the
combination of K3/Dell Inspiron 1525 Laptop/Vista Basic.
I'm just operating in 'receive' mode at this time and sometimes it works
and sometimes it doesn't. When it works it seems to work well and
properly; when it doesn't work I
FLDIGI does not require HAMLIB for rig support.
A new version of WSPR requires the use of hamlib for rig support.
The K3 support is broken in hamlib. Since the question was
specifically about problems with fldigi using hamlib and the K3,
the response was appropriate (and accurate).
I know
On Wed, Jan 5, 2011 at 2:27 PM, Joe Subich, W4TV li...@subich.com wrote:
A new version of WSPR requires the use of hamlib for rig support
Ouch! So I guess we shouldn't get any new versions of WSPR until this
changes - if it ever does.
Tony KT0NY
Well since hamblib is 100% free and open source software ANYONE who
wishes to improve the hamlib support for the k3 is completely free to do
so I would expect any shortcomings with K3 support under hamlib to get
fixed in fairly short order
In addition to this WSPR can use com port signal line
The K3 support is (and has been) broken in HAMLIB on the Windows
platform. Fldigi, WSPR and other software that requires HAMLIB
for rig support will not work reliably with the K3.
It's up to the maintainer of the Windows port of HAMLIB to fix the
issue.
73,
... Joe, W4TV
On 1/3/2011
The K3.XML file available from the FLDIGI site works completely,
reliably, and correctly inside FLDIGI (with the K3 in RigCAT and WIN XP
or WIN 7). I would be glad to supply settings if requested (however,
that is not what the gentleman asked for). FLDIGI does not require
HAMLIB for rig
John Ragle wrote:
The K3.XML file available from the FLDIGI site works completely,
reliably, and correctly inside FLDIGI (with the K3 in RigCAT and WIN XP
or WIN 7). I would be glad to supply settings if requested (however,
that is not what the gentleman asked for). FLDIGI does not
* On 2011 05 Jan 13:38 -0600, Joe Subich, W4TV wrote:
The K3 support is (and has been) broken in HAMLIB on the Windows
platform. Fldigi, WSPR and other software that requires HAMLIB
for rig support will not work reliably with the K3.
Sadly, this is true, and until I bought my K3, no one
The Prolific chipset works fine in Delphi using a freeware serial component.
73, Mike NF4L
On 1/5/2011 3:25 PM, Julian, G4ILO wrote:
John Ragle wrote:
The K3.XML file available from the FLDIGI site works completely,
reliably, and correctly inside FLDIGI (with the K3 in RigCAT and WIN XP
I started experimenting with WSPR over the weekend using my MacBook
Pro 13 in with the Intel processor running Windows XP using Parallels
virtual machine. I have the audio connected through an iMic external
USB sound-card and the K3 is connected to the Mac with a generic USB
to Serial card
Phil,
There are reported issues with use of Prolific-based USB/Serial
adapters with Visual Basic applications. Perhaps the WSPR software
you're using is another case of this. The usual suggestion is to get a
USB/Serial adapter that uses the FTDI chip instead...
~Iain / N6ML
On Mon, Jan 3,
Phil, the parameters I use with WSPR are: port COM1 (of course, this depends
on your port assignment; use Device Manager, Properties to set it); Rig
Number 229 Elecraft K3; Serial rate 4800; Data bits 8; Stop bits 1;
handshake None. Click Enable CAT, use PTT DTR (not PTT CAT). WSPR does not
use
wspr is a very low power beconing mode ... see k1jt .. it is a
derivitive of wsjt ..
I wonder if it is conceiveable that the k3 could incoporate wspr
decoding in its firmware ...
I should not imaging becon transmitting would be a problem ..
rational .. wspr beacons may become very common given
stephen pearce wrote:
wspr is a very low power beconing mode ... see k1jt .. it is a
derivitive of wsjt ..
I wonder if it is conceiveable that the k3 could incoporate wspr
decoding in its firmware ...
I should not imaging becon transmitting would be a problem ..
rational .. wspr
14 matches
Mail list logo
