| |
CX2SA > SATDIG 23.06.14 14:02l 479 Lines 16680 Bytes #999 (0) @ WW
BID : AMSATBB9205
Read: GUEST
Subj: AMSAT-BB-digest V9 205
Path: IZ3LSV<IW0QNL<IR2UBX<IK2XDE<DB0RES<DB0ANF<CX2SA
Sent: 140623/1201Z @:CX2SA.SAL.URY.SA #:7137 [Salto] FBB7.00e $:AMSATBB9205
From: CX2SA@CX2SA.SAL.URY.SA
To : SATDIG@WW
Today's Topics:
1. DIGEST readers (John Becker)
2. Re: DIGEST readers (Glen Zook)
3. Re: CAT control for TX and RX - [SOLVED] (Stu2)
4. Fodtrack Serial rotor controller on HamLib (Greg D)
5. 64 bit tracking software? (=?utf-8?B?dzBodkBzYmNnbG9iYWwubmV0?=)
6. I heard on6/22/14 (Richard Elverum SR.)
7. [Info] FOTOS _ Field Day _ 2014 (ARVM)
8. Re: Fodtrack Serial rotor controller on HamLib (Jim Jerzycke)
9. Re: Fodtrack Serial rotor controller on HamLib (Greg D)
10. Re: Fodtrack Serial rotor controller on HamLib (Gary Mayfield)
----------------------------------------------------------------------
Message: 1
Date: Sun, 22 Jun 2014 10:54:12 -0500
From: John Becker <w0jab@xxxxxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] DIGEST readers
Message-ID: <53A6FC24.2000508@xxxxxxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Please guys edit you digest reply to only what you are replying to.
Those of us that live in the rural area only have 3 ways of getting email
1. dial up - only good to 1 mile or so from the phone company office.
2. satellite - fast but has a daily limit. once that limit is reach either
must pay more or the download speed is slowed way down.
Option 3 is to block offenders. and I have not problem doing so.
Your choice.
John
------------------------------
Message: 2
Date: Sun, 22 Jun 2014 09:21:37 -0700
From: Glen Zook <gzook@xxxxx.xxx>
To: John Becker <w0jab@xxxxxxxxx.xxx>, "amsat-bb@xxxxx.xxxx
<amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] DIGEST readers
Message-ID:
<1403454097.9423.YahooMailNeo@xxxxxxxxx.xxxx.xxx.xxxxx.xxx>
Content-Type: text/plain; charset=iso-8859-1
Unfortunately, a while back, Yahoo changed how multiple messages about the
same subject (even to different reflectors - those are "bundled" into a
single message) are handled and, when a reply to any of those messages is
sent, all of the attached messages cannot be deleted! ?At least I have not
found a way!
The only way all the replies can be "deleted" is to actually retype the
pertinent data into a completely new message and then type the response.
?This takes a LOT of time and, to be blunt, is not worth the effort because
a very few persons have download problems. ?I know that this seems crass.
?However, such is one of the "facts of life" of the "modern" Internet.
?
Glen, K9STH
Website: http://k9sth.com
On Sunday, June 22, 2014 10:55 AM, John Becker <w0jab@xxxxxxxxx.xxx> wrote:
Please guys edit you digest reply to only what you are replying to.
Those of us that live in the rural area only have 3 ways of getting email
1. dial up - only good to 1 mile or so from the phone company office.
2. satellite - fast but has a daily limit. once that limit is reach either
must pay more or the download speed is slowed way down.
Option 3 is to block offenders. and I have not problem doing so.
Your choice.
John
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 3
Date: Sun, 22 Jun 2014 12:45:02 -0400
From: Stu2 <stu@xxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] CAT control for TX and RX - [SOLVED]
Message-ID: <53A7080E.8010502@xxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1
I installed SatPC32 and was able to make things work with the DVB dongle
(RX) and TS-2K (TX). I configured the HDSDR as 'radio1' and the TS2K as
'radio2'. However, SatPC32 tries to put the TS-2K into satellite mode
and my rig sends a '?' The frequencies aren't changed to the right
bands. The instructions say to make sure the TS2K is radio 1 and that
radio 2 is set to 'none', but this is for using the TS2K in satellite
mode, not as stand alone, single band TX.
To solve the problem, I selected 'Kenwood' and 'TS-790' for both radio 1
and radio 2. Uncheck 'Autom. RX/TX Changed' and 'Satellite mode'. Now,
SatPC32 corrects both the HDSDR instance and TS2K for Doppler. You can
also change the RX frequency (Tune) in HDSDR and have the TS2K follow.
Barring any overload/interference issues, this looks like a really good
set up for FD. Not only is it operational effective, but there are lots
of visuals for visitors. I've always had the computer controlled rotor
wow factor, but the SDR waterfall is really cool.
Thanks for the help and hope to work you during Field Day.
73's
Stu2
W7IY
(W4IY Field Day -9A VA)
------------------------------
Message: 4
Date: Sun, 22 Jun 2014 11:08:53 -0700
From: Greg D <ko6th.greg@xxxxx.xxx>
To: Amsat BB <AMSAT-BB@xxxxx.xxx>
Subject: [amsat-bb] Fodtrack Serial rotor controller on HamLib
Message-ID: <53A71BB5.3050101@xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi folks,
So all this talk about Gpredict got me to look at updating my own setup,
which pre-dated the modern Gpredict capabilites. But being so archaic,
I need some help connecting the dots...
I have Gpredict / Hamlib talking to my Yaesu FT-736R radio for Doppler
tracking just fine, but the rotor is a problem. My controller is
home-brewed, and emulates the subset of the "Yaesu serial protocol" as
output from the original DOS version of FODTrack. The syntax is the
letter "W" followed by the Azimuth, a space, the Elevation, and
terminated with a carriage return (hex 0d). Both the Az and El are
whole decimal integers. When I moved to Linux and Predict (the ncurses
version) in 2002, I modified the software to copy that same syntax, and
all was fine.
Tab forward over a decade to my question: What model "Yaesu controller"
was FODTrack thinking it was talking to? I need to find an equivalent
model for Hamlib's rotctl daemon, and none of the choices seem to
match. They all seem to want to talk to a single rotor (Az or El, not
both). Is there an equivalent model, Yaesu or otherwise, that accepts
"Waaa eee\n" for Az + El positioning?
Thanks,
Greg KO6TH
------------------------------
Message: 5
Date: Sun, 22 Jun 2014 12:47:16 -0500
From: "=?utf-8?B?dzBodkBzYmNnbG9iYWwubmV0?=" <w0hv@xxxxxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] 64 bit tracking software?
Message-ID: <566021.81411.bm@xxxxxxx.xxxx.xxx.xxxxx.xxx>
Content-Type: text/plain; charset=utf-8
Getting ready for Field Day, I tried to fire up good, old, reliable Predict
on my nice new laptop with Windows 8.1 with 64 bit processing. I was sad to
see a message saying it wouldn't run because it's a 32 bit program.
I've previously had Satscape, at least until Win7.
So, what freeware software can I look at set up and install quickly, and
without a steep learning curve?
Oh, and please! No rants about Windows and how I should switch to Linux.
Not gonna happen.
Jim Reicher, W0HV
------------------------------
Message: 6
Date: Sun, 22 Jun 2014 12:58:36 -0600
From: Richard Elverum SR. <KB0VBZ@xxxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] I heard on6/22/14
Message-ID: <BLU404-EAS1779EDBCD8A4CC8074CAB9B981C0@xxx.xxx>
Content-Type: text/plain; charset="utf-8"
LU7AA 17:44 utc
437.440
9k6
Kiss format
Over Colorado
USA
?tita
KB0VBZ Richard
------------------------------
Message: 7
Date: Sun, 22 Jun 2014 22:28:42 +0100
From: "ARVM" <arvm@xxxx.xxx>
To: <info@xxxx.xxx>
Subject: [amsat-bb] [Info] FOTOS _ Field Day _ 2014
Message-ID: <000001cf8e60$f0abcfb0$d2036f10$@xxx>
Content-Type: text/plain; charset="utf-8"
<http://www.arvm.org/fd14.html> FOTOS
<http://www.arvm.org/fd14.html> Field Day _ 2014
In:
<http://www.arvm.org/fd14.html> http://www.arvm.org/fd14.html
<mailto:arvm@xxxx.xxx> arvm@xxxx.xxx
A.R.V. M.
---
Este email est? liivre de v?rus e malware porque a prote??o avast! Antivirus
est? ativa.
http://www.avast.com
-------------- next part --------------
_______________________________________________
Esta mensagem est? de acordo com a legisla??o Europeia sobre o envio de
mensagens. Qualquer mensagem dever? estar claramente identificada com os
dados do emissor que dever? proporcionar ao receptor a hip?tese de ser
movido da lista. Para ser removido da nossa lista, basta que nos responda a
esta mensagem colocando a palavra "Remover" no Assunto. (Dir ectiva
2000/31/CE do Parlamento Europeu; Relat?rio A5-0270/2001 do Parlamento
Europeu.
------------------------------
Message: 8
Date: Mon, 23 Jun 2014 00:39:49 +0000
From: Jim Jerzycke <kq6ea@xxxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] Fodtrack Serial rotor controller on HamLib
Message-ID: <53A77755.4020700@xxxxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I would suspect it's using the Yaesu GS-232 protocol.
Jim KQ6EA
On 06/22/2014 06:08 PM, Greg D wrote:
> Hi folks,
>
> So all this talk about Gpredict got me to look at updating my own
> setup, which pre-dated the modern Gpredict capabilites. But being so
> archaic, I need some help connecting the dots...
>
> I have Gpredict / Hamlib talking to my Yaesu FT-736R radio for Doppler
> tracking just fine, but the rotor is a problem. My controller is
> home-brewed, and emulates the subset of the "Yaesu serial protocol" as
> output from the original DOS version of FODTrack. The syntax is the
> letter "W" followed by the Azimuth, a space, the Elevation, and
> terminated with a carriage return (hex 0d). Both the Az and El are
> whole decimal integers. When I moved to Linux and Predict (the
> ncurses version) in 2002, I modified the software to copy that same
> syntax, and all was fine.
>
> Tab forward over a decade to my question: What model "Yaesu
> controller" was FODTrack thinking it was talking to? I need to find
> an equivalent model for Hamlib's rotctl daemon, and none of the
> choices seem to match. They all seem to want to talk to a single
> rotor (Az or El, not both). Is there an equivalent model, Yaesu or
> otherwise, that accepts "Waaa eee\n" for Az + El positioning?
>
> Thanks,
>
> Greg KO6TH
>
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
> Not an AMSAT-NA member? Join now to support the amateur satellite
> program!
> Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
>
------------------------------
Message: 9
Date: Sun, 22 Jun 2014 20:39:06 -0700
From: Greg D <ko6th.greg@xxxxx.xxx>
To: Jim Jerzycke <kq6ea@xxxxxxx.xxx>, amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] Fodtrack Serial rotor controller on HamLib
Message-ID: <53A7A15A.2040707@xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8; format=flowed
Ok, some progress. I went back to my modifications to predict to see
what exactly I had done, and one of the mods was to set the serial port
stop bits to 2. I recall now that the Basic Stamp that drives my
controller logic isn't fast enough to parse the serial stream with only one.
Setting -C stop_bits=2 on the command line brought the rotor to life!
Now the next problem... I notice that Gpredict freezes while tracking
is running. No GUI updates, though the tracking (both rig and rotor)
keeps going. The rest of the system is fine, nowever, and top doesn't
show anything stuck in a spin loop. Disengaging the rotor control
(which takes a long time sometimes) brings things back. Feels like a
timeout is at fault.
I took a capture of the traffic on the serial port, and it appears that
the program is polling the controller for its position (command C2). My
controller doesn't support that command, so that's probably what's
hanging things up. Poking around I find -C timeout=1 Ha! Now we're
looking good...
Final runstring: rotctld -r /dev/ttyS3 -s 9600 -m 603 -C stop_bits=2 -C
timeout=1
Thanks again,
Greg KO6TH
Jim Jerzycke wrote:
> I would suspect it's using the Yaesu GS-232 protocol.
>
> Jim KQ6EA
>
>
> On 06/22/2014 06:08 PM, Greg D wrote:
>> Hi folks,
>>
>> So all this talk about Gpredict got me to look at updating my own
>> setup, which pre-dated the modern Gpredict capabilites. But being so
>> archaic, I need some help connecting the dots...
>>
>> I have Gpredict / Hamlib talking to my Yaesu FT-736R radio for
>> Doppler tracking just fine, but the rotor is a problem. My
>> controller is home-brewed, and emulates the subset of the "Yaesu
>> serial protocol" as output from the original DOS version of
>> FODTrack. The syntax is the letter "W" followed by the Azimuth, a
>> space, the Elevation, and terminated with a carriage return (hex
>> 0d). Both the Az and El are whole decimal integers. When I moved to
>> Linux and Predict (the ncurses version) in 2002, I modified the
>> software to copy that same syntax, and all was fine.
>>
>> Tab forward over a decade to my question: What model "Yaesu
>> controller" was FODTrack thinking it was talking to? I need to find
>> an equivalent model for Hamlib's rotctl daemon, and none of the
>> choices seem to match. They all seem to want to talk to a single
>> rotor (Az or El, not both). Is there an equivalent model, Yaesu or
>> otherwise, that accepts "Waaa eee\n" for Az + El positioning?
>>
>> Thanks,
>>
>> Greg KO6TH
>>
>> _______________________________________________
>> Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
>> Not an AMSAT-NA member? Join now to support the amateur satellite
>> program!
>> Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
>>
>
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
> Not an AMSAT-NA member? Join now to support the amateur satellite
> program!
> Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 10
Date: Sun, 22 Jun 2014 22:59:15 -0500
From: "Gary Mayfield" <kk0sd@xxxxx.xxx>
To: "'Jim Jerzycke'" <kq6ea@xxxxxxx.xxx>, <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] Fodtrack Serial rotor controller on HamLib
Message-ID: <024401cf8e97$80135430$8039fc90$@xxx>
Content-Type: text/plain; charset="us-ascii"
FODTrack was/is a parallel port controller.
73,
Joe kks0d
-----Original Message-----
From: amsat-bb-bounces@xxxxx.xxx [mailto:amsat-bb-bounces@xxxxx.xxxx On
Behalf Of Jim Jerzycke
Sent: Sunday, June 22, 2014 7:40 PM
To: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] Fodtrack Serial rotor controller on HamLib
I would suspect it's using the Yaesu GS-232 protocol.
Jim KQ6EA
On 06/22/2014 06:08 PM, Greg D wrote:
> Hi folks,
>
> So all this talk about Gpredict got me to look at updating my own
> setup, which pre-dated the modern Gpredict capabilites. But being so
> archaic, I need some help connecting the dots...
>
> I have Gpredict / Hamlib talking to my Yaesu FT-736R radio for Doppler
> tracking just fine, but the rotor is a problem. My controller is
> home-brewed, and emulates the subset of the "Yaesu serial protocol" as
> output from the original DOS version of FODTrack. The syntax is the
> letter "W" followed by the Azimuth, a space, the Elevation, and
> terminated with a carriage return (hex 0d). Both the Az and El are
> whole decimal integers. When I moved to Linux and Predict (the
> ncurses version) in 2002, I modified the software to copy that same
> syntax, and all was fine.
>
> Tab forward over a decade to my question: What model "Yaesu
> controller" was FODTrack thinking it was talking to? I need to find
> an equivalent model for Hamlib's rotctl daemon, and none of the
> choices seem to match. They all seem to want to talk to a single
> rotor (Az or El, not both). Is there an equivalent model, Yaesu or
> otherwise, that accepts "Waaa eee\n" for Az + El positioning?
>
> Thanks,
>
> Greg KO6TH
>
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
> Not an AMSAT-NA member? Join now to support the amateur satellite
> program!
> Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
>
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
------------------------------
_______________________________________________
Sent via amsat-bb@xxxxx.xxx. Opinions expressed are those of the author.
Not an AMSAT member? Join now to support the amateur satellite program!
http://amsat.org/mailman/listinfo/amsat-bb
End of AMSAT-BB Digest, Vol 9, Issue 205
****************************************
Read previous mail | Read next mail
| |
