Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+TR\s+RTTY\s+\-\s+can\'t\s+transmit\s+message\s+buffers\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+TR\s+RTTY\s+\-\s+can\'t\s+transmit\s+message\s+buffers\s*$/: 11 ]

Total 11 documents matching your query.

1. [TRLog] TR RTTY - can't transmit message buffers (score: 1): Author: k4ro@k4ro.net (K4RO Kirk Pickering); Date: Thu, 3 Oct 2002 02:47:40 -0500; Thanks for the suggestion Brett. I tried the strings you suggested below. It will now transmit when F1 is pressed, but after sending the text (CQ TEST K4RO) it stays in transmit instead of returning; /archives//html/TRLog/2002-10/msg00003.html (8,653 bytes)
2. [TRLog] TR RTTY - can't transmit message buffers (score: 1): Author: vr2bg@harts.org.hk (VR2BrettGraham); Date: Thu, 03 Oct 2002 23:23:51 +0000; <04> is ^D, which is the default character to put the PK232 into receive when sent at it as part of the text it is transmitting. ^F does the same thing, but with a CW ID sent before going into receiv; /archives//html/TRLog/2002-10/msg00007.html (10,255 bytes)
3. [TRLog] TR RTTY - can't transmit message buffers (score: 1): Author: k4ro@k4ro.net (K4RO Kirk Pickering); Date: Fri, 4 Oct 2002 12:25:37 -0500; That did the trick, thanks George. On the PK-232, the command which sets this is "AWlen 7". It defaults to 8 bit. The TU still works with AWlen 8 until you try to send it some of these special charac; /archives//html/TRLog/2002-10/msg00008.html (9,297 bytes)
4. [TRLog] TR RTTY - can't transmit message buffers (score: 1): Author: vr2bg@harts.org.hk (VR2BrettGraham); Date: Mon, 07 Oct 2002 03:24:21 +0000; That is why it is necessary to set: rtty send string = tc<0D>x<0D> So as to clear the transmit buffer of whatever it is that the PK232 thinks it got from TR after the ^D to put it back into receive.; /archives//html/TRLog/2002-10/msg00021.html (8,868 bytes)
5. [TRLog] TR RTTY - can't transmit message buffers (score: 1): Author: k4ro@k4ro.net (K4RO Kirk Pickering); Date: Tue, 8 Oct 2002 07:28:30 -0500; <^D^D>cmd:** Transmit data remaining whenever I use the F10 key to converse in RTTY. I apparently still don't have something set right Here are my settings: rtty send string = tc<0D>x<0D> rtty receiv; /archives//html/TRLog/2002-10/msg00026.html (8,483 bytes)
6. [TRLog] TR RTTY - can't transmit message buffers (score: 1): Author: vr2bg@harts.org.hk (VR2BrettGraham); Date: Tue, 08 Oct 2002 22:34:36 +0000; Sorry, I guess I didn't make myself clear - that doesn't stop the PK232 from thinking there is something left in its buffer - it just makes sure that what is in the buffer gets cleared before going i; /archives//html/TRLog/2002-10/msg00027.html (9,097 bytes)
7. [TRLog] TR RTTY - can't transmit message buffers (score: 1): Author: k4ro@k4ro.net (K4RO Kirk Pickering); Date: Tue, 8 Oct 2002 23:41:32 -0500; OK, I believe I've got it now. Essentially, I can just ignore the "**Transmit Data Remaining" message, knowing that the buffer is being properly cleared before each transmission. That seems to be the; /archives//html/TRLog/2002-10/msg00028.html (8,515 bytes)
8. [TRLog] TR RTTY - can't transmit message buffers (score: 1): Author: vr2bg@harts.org.hk (VR2BrettGraham); Date: Thu, 10 Oct 2002 02:07:01 +0000; K4RO continued: Yes - there is something in the buffer after you finished transmitting, but by clearing it before the next time you transmit, it isn't a worry. There may be a more elegant way to deal; /archives//html/TRLog/2002-10/msg00029.html (9,822 bytes)
9. [TRLog] TR RTTY - can't transmit message buffers (score: 1): Author: k4ro@k4ro.net (K4RO Kirk Pickering); Date: Sun, 13 Oct 2002 02:00:41 -0500; I've received several requests for these mods, so here they are for the archives: http://www.qsl.net/k0bx/ Many thanks to K0BX for the mods. C U on RTTY -Kirk K4RO; /archives//html/TRLog/2002-10/msg00035.html (8,027 bytes)
10. [TRLog] TR RTTY - can't transmit message buffers (score: 1): Author: k4ro@k4ro.net (K4RO Kirk Pickering); Date: Fri, 27 Sep 2002 18:30:43 -0500; Last minute appeal, 30 minutes before the contest... I've been trying to get TR-Log working on RTTY for the first time, after reading VE3IAY's posts on the subhject. I am able to receive, but I canno; /archives//html/TRLog/2002-09/msg00037.html (7,495 bytes)
11. [TRLog] TR RTTY - can't transmit message buffers (score: 1): Author: vr2bg@harts.org.hk (VR2BrettGraham); Date: Sat, 28 Sep 2002 22:49:09 +0000; K4RO posted: For the PK-232, the critical stuff for logcfg.dat is: rtty PORT = SERIAL 1 PACKET BEEP = FALSE rtty receive string = <04> rtty send string = tc<0D>x<0D> Sorry if this is a dupe, but I'm; /archives//html/TRLog/2002-09/msg00038.html (6,815 bytes)

Current List: 1 - 11
Page: [1]