January 2015 - AMSAT-BB - mailman.amsat.org

TYT TH-9000 70cm rig on SO50
by John Geiger 10 Jan '15

10 Jan '15

The TYT TH-9000 is a nice priced, 45 watt UHF rig. Has anyone tried using them on SO50 yet? It would be nice to have them for the local repeaters as well. I would be using it with a yagi on 70cm. 73 John AF5CC

1 0

test
by Ted 10 Jan '15

10 Jan '15

test

1 0

email blocked
by wa4hfn＠comcast.net 10 Jan '15

10 Jan '15

I have been unable to receive any email from the amsat bb. I found this Delivery to the following recipient failed permanently: amsat-bb(a)amsat.com Technical details of permanent failure: Google tried to deliver your message, but it was rejected by the server for the recipient domain amsat.com by mx2.daemonmail.net. [216.104.161.5]. The error that the other server returned was: 554 5.7.1 <amsat-bb(a)amsat.com>: Relay access denied Why has amsat blocked me? I have done nothing to cause this . This is the second time this has happened, is it a glich or is someone doing it WA4HFN Damon em55 www.starcommgroup.org

2 1

test email
by wa4hfn＠comcast.net 10 Jan '15

10 Jan '15

this email sent from wa4hfn(a)comcast.net to amsat-bb(a)amsat.org still not seeing any emails from anyone on the amsat bb email

2 1

test email
by damon runion 10 Jan '15

10 Jan '15

test only

1 0

Re: [amsat-bb] Fwd: Delivery Status Notification (Failure)
by Vince Fiscus, KB7ADL 10 Jan '15

10 Jan '15

At 02:43 PM 1/10/2015 +0000, you wrote: >I am not receiving any email from the amsat bb again.I have checked all the >other locations email could go. If I have been blocked or dropped WHY? >Damon WA4HFN em55 >www.starcommgroup.org I'm seeing all the messages you sent. Not sure why it's telling you they're not going through. KB7ADL

1 0

Fwd: Delivery Status Notification (Failure)
by wa4hfn＠comcast.net 10 Jan '15

10 Jan '15

----- Forwarded Message ----- From: "damon runion" <damonwa4hfn(a)gmail.com> To: "Damon Runion" <wa4hfn(a)comcast.net> Sent: Saturday, January 10, 2015 8:41:03 AM Subject: Fwd: Delivery Status Notification (Failure) ---------- Forwarded message ---------- From: damon runion <damonwa4hfn(a)gmail.com> Date: Sat, Jan 10, 2015 at 8:31 AM Subject: Fwd: Delivery Status Notification (Failure) To: wa4nvm(a)comcast.net ---------- Forwarded message ---------- From: Mail Delivery Subsystem <mailer-daemon(a)googlemail.com> Date: Sat, Jan 10, 2015 at 8:28 AM Subject: Delivery Status Notification (Failure) To: damonwa4hfn(a)gmail.com Delivery to the following recipient failed permanently: amsat-bb(a)amsat.com Technical details of permanent failure: Google tried to deliver your message, but it was rejected by the server for the recipient domain amsat.com by mx2.daemonmail.net. [216.104.161.5]. The error that the other server returned was: 554 5.7.1 <amsat-bb(a)amsat.com>: Relay access denied ----- Original message ----- DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=odcizdBh3Eq/OR/s5L6lPJ9FaIpZwMcnO0/eJeqln4g=; b=ffYWFAlYRcMVyJnnyrOqPysaD6tVP9/qLPP/dlmAY8v9aWsO3001kBgpMH9/A38gqz kBp2hbKVdYDPeJdu+EAkqC5AIXj1lwXJAG4RzdhSStUqrxmqtY3jg3oEszNaUJXngX7K 3/ieAkgR87vznw8TYQ42BaxNYSdWTvXhHRfYNVoDh7xLZcgbnWJezSBzxRMjOmKC/3n/ ielICoJw2m06XBos/18FITtjlA81x2CbWtYIkfSOF2Yos9w+TZamgl+1DtvU+gw+vmkx p/aXNH8hxnCvn32XrEvk1906iwtJT8FxarYhzK23ALH6O75K9u+8wR77CDPLLlYr17pG Zc/g== MIME-Version: 1.0 X-Received: by 10.152.1.2 with SMTP id 2mr27255257lai.89.1420900104131; Sat, 10 Jan 2015 06:28:24 -0800 (PST) Received: by 10.25.30.82 with HTTP; Sat, 10 Jan 2015 06:28:24 -0800 (PST) Date: Sat, 10 Jan 2015 08:28:24 -0600 Message-ID: <CACNBj2p= 37S6hhQsr8XohbZG11FjzyQL4AmCiyo6RydNftc0cg(a)mail.gmail.com> Subject: email From: damon runion <damonwa4hfn(a)gmail.com> To: amsat-bb <amsat-bb(a)amsat.com> Content-Type: multipart/alternative; boundary=089e013c6672f7d868050c4d152a I am not receiving any email from the amsat bb again.I have checked all the other locations email could go. If I have been blocked or dropped WHY? Damon WA4HFN em55 www.starcommgroup.org

1 0

logging software
by ted 09 Jan '15

09 Jan '15

I use Bob Furzer's Logger 32. It handles all of my logging needs including satellite QSOs from home, and from over 40 portable grids, many on gridlines. The program allows you to use different operators and to keep track of each within the main log. For example; aa5ck, aa5ck/5, aa5ck/6mtr, aa5ck/EM06, aa5ck/DM71/DM72, etc. Freeware that has evolved over the years from it's early DOS days to what it is today due to the efforts of many great volunteers who recognized it's potential. Almost instant help from the Hamlogger Yahoo Group if needed. The latest version of Logger32 features automatic updates. 73......ted....aa5ck --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com

1 0

Re: [amsat-bb] weak signal ISS packet
by Robert Bruninga 09 Jan '15

09 Jan '15

Yes, again, "best packet" all depends on the settings of the transmitting station (and matching it on receive). When the ISS used a kenwood, then another kenwood would always work the best. Because both are built at the factory for optimum performance (to each other) and they use direct modulation and demodulation to the same levels. My kenwoods can decode another kenwood (direct) with only 3 bars. BUT similarly, I can see many signals that appear to have full scale signals and then barely deocde because so many signals on the air were never adjusted properly. AND there are two standards. Do the sending and receiving radios use pre- and de-emphasis (speaker and Mic connections)? Or do they operate flat with direct modulation and demodulation. Is the receiver an FM demodulator or Phase demodulator? BUT on ISS, I believe they are currently using another radio, not a kenwood. SO now you need a receiving system best matched to this radios transmitted waveform. Maybe someone on the AMSAT-BB has captured the existing ISS waveform and we can see what kind of receiver is best. But then again, the captured waveform MUST indicate exactly what kind of receiver (with or without de-emphasis) was used in capturing the waveform! Two manufactured APRS radios work BEST between them because they were factory adjusted for BALANCED tone levels and NO preemphasis or de-emphasis. But other stations may just use the Mic connections and speaker connections and get over 6 dB of performance loss if they are not accounted for. The use of speaker/mic connections(with pre- and de-emphasis) and direct modulation and discriminator demodulation can each have optimum performance. But there are always problems when crossing between the two. BUT, it IS possible to adjust on the transmit side for a compromise between the two and then receivers of each type can decode pretty good. Though maybe 1% of hams go to this trouble. Packet radio is NOT Plug-N-play. The transmitter must be adjusted for optimum waveform! I should be able to tell everyone what the RIGHT way to do it is, but I never trust my memory anymore, and don’t have time today to go do all the research again... But I'm going to recall from memory, that I think the WORST situation of most TNC's is if the LOW tone is higher than the HIGH tone, that decoding always suffers. And suffers FAR WORSE than the other way around. So that is why the compromise is to make the high tone about 3 dB higher (30% on an OO scope) so that it doesn’t get completely lost when it goes through a speaker connected receiver and gets de-emphasized. OR, If I remember wrong and it is the other way around! Good luck. Bob -----Original Message----- I was hoping for some ideas to better my station and am very pleased you have responded. I want to better utilize my station and increase my throughput with the ISS in particular. I have available 10 element crossed Yagi antennas and Yaesu az el rotor and several radios with TNC's built in including Yaesu FTM-350 and FTM-400 and Kenwood TM-D700 and TS-2000. MFJ and Kantronics TNC's as well as products from Byonics and Argent Data are found on my bench. I am currently running a Kenwood TM-D700 to a M2 Eggbeater as a 24/7 ISS station with UISS software and modules to upload to the internet. I want to increase my capabilities with respect to the ISS and APRS. I have found that the Kenwood TM-D700 requires that you get about almost a half scale reading to effect good packet reception. I don't want to use the fully automated station (FT-847) that I have when I'm not home because in the past a failure caused my rotor to jam and I had to lower my tower to remove and repair the az-el rotor. I suspect that the best way might be to use a sound card software and computer to give the best decoding. Thanks for the response Steve KB1CHU

1 0

Re: [amsat-bb] Logging software and multi grid QSO's
by David W0DHB 08 Jan '15

08 Jan '15

Thanks to all who provided feedback, this all came about when I found a bug in Log4OM and the Log4OM folks asked about how other Logging software handled it. Here’s what I discovered. DXKeeper did the best job, it allows up to 4 grids to be entered and tracks VUCC awards correctly N3FJP with some tricks allows up 4 grids to be entered, but I believe it will not track VUCC awards correctly HRD Logger allows 2 grids to be entered and does not track VUCC awards correctly Log4OM allows 2 grids to be entered, does not track VUCC awards correctly and the grid field is overwritten with one grid after LoTW download (trying to get fixed) What I mean does not track VUCC awards correctly is that in most cases the logging software VUCC tracking only uses the first grid in the list of 2 or 4 (ie. DM62,DM63,DM72,DM73) only gives you credit for DM62 Notes about LoTW LoTW basically ignores the stations Grid from your log when it does QSO matching, the grid is only used for determining VUCC. LoTW doesn’t care what grid(s) you give for the station you contacted. The download file from LoTW does include multiple grid information. Still looking into eQSL On January 8, 2015 10:38:18 AM CST, David W0DHB <dave(a)w0dhb.net <mailto:[email protected]> > wrote: I'm currently using Log4OM software and discovered that in the case where a multigrid QSO is logged (Station is on a grid boundary) the software has some issues. - Seems to upload to LoTW ok, but downloads from LoTW only one grid is marked as confirmed. - The internal award tracking only recognizes one Grid. HRD Logger has similar issues. Does anyone have logging software (N3JFP, DXKeeper, etc.) that handles multi-grid QSO's correctly , especially LoTW/eqsl upload download Thanks Dave W0DHB _____ Sent via AMSAT-BB(a)amsat.org <mailto:[email protected]> . AMSAT-NA makes this open forum available to all interested persons worldwide without requiring membership. Opinions expressed are solely those of the author, and do not reflect the official views of AMSAT-NA. Not an AMSAT-NA member? Join now to support the amateur satellite program! Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

1 0