[Elecraft] KAT500 Utility 1.14.4.10 beta test version available on our FTP site

[Stan Gibbs, KR7C]

Yes, I was typing the commands on the Command Tester tab.

I notice from my P3's 28.004 oscillator signal that the oscillator is
enabled immediately when the Firmware or Operate tabs are selected. 
However, the oscillator runs continuously while the Operate tab is selected
and turns off after a delay in the case of the Firmware tab.  Is there a
reason for this difference?  Sending firmware to the KAT500 with idle sleep
enabled seems to work reliably now, even waiting for the oscillator to
time-out first.

The Configuration and Command Tester tabs don't enable the oscillator until
the user either clicks a configuration button or sends a macro command.  In
both cases the oscillator stops after a few seconds of idleness, like the
Firmware tab.

Why not simply enable the oscillator (disable the sleep) after the utility
has established communications with the KAT500 on startup, and restore the
user's Idle Sleep setting on exit?  If users are fiddling with their KAT500
configuration, it doesn't seem like they should be that concerned about the
28.004 signal being present.  If they are using the Operate tab to monitor
station operation, then the oscillator signal will be present regardless of
the Idle Sleep setting.

However, this begs the question of other apps accessing the KAT500.  IMHO,
requiring all of them to send junk commands until they get a reasonable
response does not seem like a very reliable strategy.

Is there a hardware mod that could be made that would shift the oscillator
out of the 10m band?  That would eliminate the problem altogether, allow the
firmware to be simplified and greatly improve the communications
reliability.




-----
73, Stan - KR7C
--
View this message in context: http://elecraft.365791.n2.nabble.com/KAT500-Utility-1-14-4-10-beta-test-version-available-on-our-FTP-site-tp7586987p7587017.html
Sent from the Elecraft mailing list archive at Nabble.com.