Thank you to each one who responded, both on and off list. I was particularly surprised to see a message this morning from Wayne (N6KR) himself, indicating that he would try to reproduce the problem on his side.
To hear back directly from the chief engineer who designed your rig, just a few hours after reporting an issue (and on a Sunday morning at that!) . . . well, this is what makes Elecraft a very special company indeed!! One further note: I discovered while "running" later today, that the problem will also occur after using the paddle to send a call sign live, and then pressing a memory to send the rest of the exchange. The significant thing is that the carrier does not drop out between the two. So, the problem is routinely reproducible, either by 'chaining' memories, or by sending with the paddle followed immediately (without drop of carrier) with a memory. I will try to keep the list informed as to what develops on this front. Thanks, 73 John N6JW K1, K2, K3 & P3 N6JW wrote: > > Briefly stated, here is the problem: While in FSK D data mode, > if one is sending a "chained" stored message, upon returning to > receive, the audio frequency is "offset" by (I believe) the selected > Mark pitch frequency (e.g. 915hz or 1275 hz). The 'offset' remains, > but some commands can reset things to normal. > > > -- View this message in context: http://elecraft.365791.n2.nabble.com/K3-FSK-D-Mode-possible-Bug-tp5571721p5573611.html Sent from the [K3] 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:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
