<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Good day;<br>
<br>
Please note the UPDATED information! The ANAN-NET was on 14.340 Mhz
on Sundays at 1715Z; -It will now shift to 1815Z, as "Daylight
Savings Time" will have ended early Sunday morning. It will still
meet at 12:15 Central local time, as usual. The shift is due to
"Daylight Savings Time" vs. "Standard Time" for those of us here in
the USA.<br>
<div id="yui_3_15_0_1_1414792417450_997"
class="ygrps-yiv-2078860576ygrps-yiv-1039398856ygroups-quoted">
<div
id="ygrps-yiv-2078860576ygrps-yiv-1039398856ygrps-yiv-673292776">
<div id="yui_3_15_0_1_1414792417450_996"
class="ygrps-yiv-2078860576ygrps-yiv-1039398856ygrps-yiv-673292776ygroups-quoted">
<div
id="ygrps-yiv-2078860576ygrps-yiv-1039398856ygrps-yiv-673292776ygrps-yiv-78608138"><br>
To recap: -The ANAN-NET was, and still will be on 14.340 Mhz
(Sundays at 12:15 PM, central local time) on a permanent
basis. A GMT-time reference will shift by one hour, when
the daylight savings time (DST) makes its twice-yearly
shift.<br>
<br>
Last Sunday, the ANAN-NET was somewhat abbreviated, due to
the CQ-contest, of course.<br>
<br>
Lou (KI6UM) had recapped his move from his previous "latest
and greatest" firmware and HP-PowerSDR versions back to 2.5
and 3.2.10. (If I wrote his PSDR version down
correctly...) His issue was that his RX and TX audio were
"burping," as I had understood him to explain to me.
Dropping back to earlier versions resolved his issues<br>
<br>
Jerry (WB2OZE) in Oklahoma had reported perfect success with
v2.9 and 3.2.19, on his ANAN-100.<br>
<br>
My ANAN-100 was still running the firmware that it arrived
with, version 2.2. I had upgraded my PSDR version to
3.2.17, as my only update.<br>
<br>
I had on-air reports of a too-wide RF signal, and was
advised by someone that I feel is in the know. (A
firmware/software designer of the ANAN products?) The
suggested resolution was to upgrade to 2.9 and 3.2.19.<br>
<br>
After the net, I did the upgrade to 2.9 and 3.2.19. All
seemed to be fine, but I discovered that ten percent of the
time, I had no RF power being produced at PTT! Yet, all
indications were that I was indeed in transmit mode! -Just
no RF power. I could make this error go away, by releasing,
then re-pressing my PTT switch. I'd then have transmit
power. (Again, the on-screen displays were as before, when
no power was being produced!)<br>
<br>
I deleted the wisdom file and database file, used the
control panel's DELETE to delete the PowerSDR, restarted the
computer, as usual, Then, I applied firmware 3.0 and PSDR
3.2.19. OK transmit (no ten percent fail-to-generate RF)
but my audio was very, VERY bad!<br>
<br>
I went through several delete-upgrade steps, and wound up
with 2.5 and 3.2.19. Good audio, no flaws in transmit.<br>
<br>
<span class="ygrps-yiv-2078860576tab">I still have
opposite-sideband bleed! (To recap, this was my only
reason to move from my previous 2.2 and 3.2.17.)<br>
<br>
I believe (??) that I can reduce the bleed issue, if I
decrease the PREAMP GAIN SETTING in the ten-band
equalizer. But, this is at a distinct loss of indicated
AVERAGE power. -The PEAK POWER suffers some, but not a
lot. Before, my MIC, LEVELER, AGC and so on were all at
or below the zero-dB point. As a matter of a fact, ONLY
the LEVELER was bumping into the zero-dB point; -The other
levels were well under, at a max of -5 dB.<br>
<br>
My questions:<br>
- Is the bleed over to the opposite sideband really an
issue?<br>
- Will a FIRMWARE upgrade to 2.9 or 3.0 help?<br>
- Aside from buying and applying the hardware for
PURESIGNAL, is there any possibility to use the PureSignal
as-is, without having to purchase the add-on hardware? (I
heard this mentioned as a possibility in a YouTube video,
but it was also mentioned that this was not QUITE as good
as the directional coupler method.)<br>
</span><br>
Back to the ANAN-NET topic: As usual, I will have my
Livestream video/audio streaming on line for the net
session. I will plan on using LIVESTREAM for anyone that
might have an interest in seeing and hearing what I see and
hear from my ham station, which is South-East Minnesota. My
Livestream link is as follows:<br>
livestream.com/k0jta<br>
<br>
When you first get to the linked Livestream web site, there
is a short commercial that you will have to endure before
the feed (video and audio) is allowed to pass to you. There
is also a several second DELAY in the audio and video feed,
due to the internet and hardware needs.<br>
<br>
73; Mike K0JTA</div>
</div>
</div>
</div>
</body>
</html>
1414792670.0