I came across a bug which will most likely put my efforts for a windows p3
application on hold: It concerns the markers. I first found this in my
program itself, but I can reproduce it with RealTerm which is an async
terminal program.
Basically, when it works it goes like this: (I alternate the frequencies
manually to show an effect)
I enable the marker: #MKA1;
The correct marker frequency shows up on both the SVGA and P3.
I then issue a #MFA+0001810; (for an example)
This shows up on both displays
I then issue a #QSY1; which is supposed to put the K3 at the marker
frequency.
I then issue a #MKA0; and the markers turn off
This works 3 maybe 4 sometimes 8 times then the following happens:
I enable the marker: #MKA1;
The correct marker frequency shows up on both the SVGA and P3.
I then issue a #MFA+0001810; (for an example)
This shows up on both displays
I then issue a #QSY1 and now things change drastically.
The SVGA screen shows the marker frequency as the original frequency before
the #MFA+0001810
The P3 Screen shows MRK A: 0 (not the frequency)
and the frequency does not change.
When the #MKA0 is issued, the P3 marker is gone, but the " MKA Frequency"
text on the P3 remains.
At this point, it seems to never get better, unless I fiddle with the
controls on the P3 itself.
Any ideas of a work around? It's really too bad, I'm almost set to go.
Thanks for any help.
Tom VA2FSQ
--
View this message in context:
http://elecraft.365791.n2.nabble.com/P3-SVGA-Programming-bug-tp7488122p7488122.html
Sent from the Elecraft mailing list archive at Nabble.com.
__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
