Is any one familiar with the use of WSJT-X with a RigBlaster interface to a Ten
Tec Omni VII?
I have someone who reports rig_open errors with drivers recommended by
WestMountain Radio.
--- John G4KLA
--
Download BIRT iH
On 24/11/2014 05:48, Alan VK2ZIW wrote:
> Hi all,
Hi Alan,
It helps if you can start a new mail thread for a new subject. Adding
unrelated questions to existing threads can cause your request to be
missed by those of us using thread mail readers.
> O/S: Fedora release 20 (Heisenbug) x86_64
> Har
On 24/11/2014 09:22, John Nelson wrote:
Hi John,
> Is any one familiar with the use of WSJT-X with a RigBlaster interface to a
> Ten Tec Omni VII?
Mike W9MDB reported issues with using a direct hamlib connection to his
Omni VII, I believe he was looking into the cause.
>
> I have someone who repo
I'm working on it right now...hope to have a fixed hamlib omnivii.c today.
It was really in alpha stage and was using wrong commands too.
For some odd reason all commands are returning an extra byte which I haven't
quite figured out yet but I'm removing the dependency on return length and
using ret
On 24/11/2014 14:58, Michael Black wrote:
Hi Mike,
> I'm working on it right now...hope to have a fixed hamlib omnivii.c today.
> It was really in alpha stage and was using wrong commands too.
> For some odd reason all commands are returning an extra byte which I haven't
> quite figured out yet but
well, John,
I have two Rigblaster-interfaces running on my two Kenwood Radios:
The Advantage is connected to my TS440SAT and the Rigblaster Blue is on my
TS950S.
When I first tried to connect the Advantage via the built-in RS-232-port to
the Kenwood via the socalled "poor man´s interface (a resisto
I can confirm the extra byte is bogusI am also running a C# program to
test the commands and don't see any extra bytes via that method.
Once I get the Omni working I'm going to try and track down the extra byte.
-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Hmmm...termio on Winodws seems quite unstable...sounds a bit like it's
related to the Kenwood problem too.I can test all these commands in C#
and they get the expected response so I'm quite confident it's not any
hardware related issue or the radio. I get the same results on Windows 7
64bit an
I tested reducing the expected response on the ?N command from 3 to 2...and
instead of getting back 2 bytes I only got 1.
This behavior doesn't make a lot of sense. So I'm going to ignore the
length on ?N and see how that works.
Mon Nov 24 18:58:12 2014
GMT(C:\JTSDK-QT\src\wsjtx\HamlibTransceiver
The string length logic seems a bit inconsistent on hamlib.
It looks to me like all rigs that use hamlib serial com should be having
problems.
I checked some other rigs and it appears they should have similar problems
with truncated responses.
If you read_string() with a correct expected length f
On 24/11/2014 22:27, Michael Black wrote:
Hi Mike,
> The string length logic seems a bit inconsistent on hamlib.
> It looks to me like all rigs that use hamlib serial com should be having
> problems.
>
> I checked some other rigs and it appears they should have similar problems
> with truncated res
You referred to me to whatever version this is which I assume is the hamlib3
custom one you've referred to for WSJT-X?
git clone git://git.code.sf.net/u/bsomervi/hamlib src
Mike W9MDB
-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Monday, November 24, 2014 4
On 24/11/2014 22:51, Michael Black wrote:
Hi Mike,
> You referred to me to whatever version this is which I assume is the hamlib3
> custom one you've referred to for WSJT-X?
> git clone git://git.code.sf.net/u/bsomervi/hamlib src
OK, some comments below.
> Mike W9MDB
>
> -Original Message-
Yes there are two functions which have no '\r'.
Set Transmit On/Off *T which gives a 1-byte return (that will be PTT via
CAT)
Set CWChar to Transmit *C2K which gives a 1-byte return (this one doesn't
matter for WSJT-X)
The problem I ran into was that the logic in omnivii.c was expecting the
count
On 24/11/2014 23:23, Michael Black wrote:
Hi Mike,
Yes there are two functions which have no '\r'.
Set Transmit On/Off *T which gives a 1-byte return (that will be PTT via
CAT)
Set CWChar to Transmit *C2K which gives a 1-byte return (this one doesn't
matter for WSJT-X)
I'm not sure that's correct
15 matches
Mail list logo
