[Elecraft] P3 bug

[Ian White]

OK, Vic: the computer RS232 link is not involved.

I hadn't noticed any hangups while testing with an external keyer using
VOX (semi-breakin) but could easily create hangups using full QSK. That
may be simply because full QSK generates many more TX/RX transitions.
Sometimes even one dot was enough to cause a hangup.

If something is marginal in the communication between the K3 and the P3,
that might explain why the problem varies so much, both in the frequency
of the hangups and in their duration. It might also explain why some
people have never noticed it at all. 

Also, are we correct in believing that the problem only affects SVGA
users? 

It's getting late here, but maybe someone could repeat the test with the
SVGA display disconnected from the P3, in case that might be a source of
disruption to the data communications.


73 from Ian GM3SEK


>-----Original Message-----
>From: Elecraft [mailto:elecraft-bounces at mailman.qth.net] On Behalf Of
Vic
>Rosenthal 4X6GP/K2VCO
>Sent: 29 December 2014 20:51
>To: elecraft at mailman.qth.net
>Subject: Re: [Elecraft] P3 bug
>
>I have just tested it with and without a logging program running. It
>happens either way.
>
>The way I test it it to turn QSK and TX TEST on and send a series of
>groups of V's with the internal keyer at 25 wpm: VVV VVV VVV etc. It
>seems to happen from once every three groups to once in 8 or so.
Usually
>the delays are about 1s. Sometimes they are longer.
>
>On 29 Dec 2014 22:32, Ian White wrote:
>>
>>> On Mon,12/29/2014 7:35 AM, Joe Subich, W4TV wrote:
>>>> I have never seen this but I don't have the SVGA.
>>>
>>> Nor have I. Perhaps an RF issue?
>>>
>>> 73, Jim K9YC
>>
>> I have the same problem and it does occur in TEST mode so it isn't
RF.
>> It is also a problem of long standing, not related to any recent
>> firmware upgrade.
>>
>> The displays (both P3 and SVGA) hang at very irregular intervals, on
>> average about once in maybe 10-20-30 returns to TX. Sometimes the
>> displays freeze for only about a second, but sometimes for as long as
10
>> seconds or even more. I also have the impression that the problem
>> sometimes occurs in 'streaks' when the probability seems much higher.
>>
>> Unfortunately the problem cannot be created on demand, only by
>repeated
>> TX-RX cycling, but it does not seem to happen at all with purely
manual
>> keying.
>>
>> It only happens here when the logging program (N1MM+) is active,
which
>> suggests it is related to traffic on the RS232 link - perhaps some
kind
>> of data collision which is being resolved by timeouts. I have the
>> impression that the displays become more likely to hang when the VFOB
>> knob is rotated while transmitting on VFO A, which will feed a
backlog
>> of data into the RS232 link or its buffers.  (FYI, my RS232 link uses
>> the hardware COM1 port on the PC motherboard and the PC-P3-K3
>chaining
>> is exactly as specified in the manuals; the whole link functions
>> perfectly in every other respect.)
>>
>> Although the problem seems to require that the logging program is
>> running, it does not seem to be directly related to the source of CW
>> and/or PTT. The problem occurs with manual keying and VOX, just as
>often
>> as it does with keying from N1MM+ (DTR=CW, RTS=PTT).
>>
>> The same problem also occurs on RTTY but I'm not sure about SSB.
>>
>>
>> 73 from Ian GM3SEK
>
>--
>73,
>Vic, 4X6GP/K2VCO
>Rehovot, Israel
>http://www.qsl.net/k2vco/
>______________________________________________________________
>Elecraft mailing list
>Home: http://mailman.qth.net/mailman/listinfo/elecraft
>Help: http://mailman.qth.net/mmfaq.htm
>Post: mailto:Elecraft at mailman.qth.net
>
>This list hosted by: http://www.qsl.net
>Please help support this email list: http://www.qsl.net/donate.html
>Message delivered to gm3sek at ifwtech.co.uk