[hpsdr] ANAN-100 sometimes no TX after upgrade to 2.9b/3.0 and 3.2.19

[Mike Sch. (IMAP Acct.)]

(Original on 10/30/14 was rejected by moderator, as I had the incorrect 
SUBJECT MATTER; So very sorry.  I'm learning!  -Mike-)

On 10/30/14, 5:34 PM [Oct 30], Mike Sch. (IMAP Acct.) wrote:
> Warren;
>
> As it turned out, when I reverted to 2.7, my on-air reports were 
> COMPLAINTS!  My audio was bad, mushy, bassey, and so on.  Nothing at 
> all to be proud of...  The good part was that my TX was now 
> consistently working, not the sometimes-no-RF, as I had earlier with 
> either 2.9 or m3.0, I cannot remember.
>
> So, I deleted the wisdom file and the database file, restarted the 
> computer, then loaded firmware 2.5, just as Lou, KI6UM had to do. This 
> is running fine.  (!!)  My audio quality and sound is again something 
> to be proud of, and the TX ALWAYS works in SSB!!! (Woo-HOO!)
>
> I am planning to leave it set up with 2.5 and 3.2.19 for the time 
> being.  I do agree with you, though; -It is a possible hit-or-miss on 
> my system, maybe.  So, I might re-visit 2.9, maybe 3.0.
>
> Also, I see that I have TWO of the firmware load apps on my Win-7 
> desktop!!  I seem to recall that there are two, for some sort of 
> reason that I did not understand.  (COP vs. NON-COP, or something 
> similar???)
>
> My ANAN-100 is running as it should.  I still have "skirts of RF" 
> above and below my frequency, though.  As it was this was the only 
> reason that I decided to shift from firmware 2.2 to something a bit 
> more current.
>
> Q1:  Will firmware 2.9 or 3.0 offer a better "RF skirt" output than my 
> present 2.5???
> Q2:  Is 2.9 missing the PTT output to the rear panel DB-25??
>
> 73 for now.  -Mike-  K0JTA
>
>
> On 10/30/14, 4:24 PM [Oct 30], hpsdr-request at lists.openhpsdr.org wrote:
>> Date: Wed, 29 Oct 2014 15:07:18 -0700
>> From: "Warren C. Pratt"<warren at wpratt.com>
>> To:hpsdr at lists.openhpsdr.org
>> Subject: Re: [hpsdr] ANAN-100 sometimes no TX, after upgrade to
>>     2.9b/3.0, and 3.2.19
>> Message-ID:<54516516.3060103 at wpratt.com>
>> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
>>
>> Hi Mike,
>>
>> You are on the right track here.  To get to the correct solution, it's
>> very helpful to isolate this to either hardware, firmware, or software.
>> If you conclude that 2.7 works correctly but 3.0 does not, it appears to
>> be a firmware issue, or at minimum an issue related to the firmware
>> version.  I would switch firmware back and forth a couple times to be
>> sure whether the problem follows the firmware.
>>
>> 73,
>> Warren  NR0V
>