Re: [digitalradio] Re: MFTTY 3.0.143 is out
I understand, Norbert, now. Hthe information I read leads me to believe (and it's stated as such) that the greater frequency of Pilot tones provides an aid to tuning. IMHO, it seems to me that the pause time that you stated is a bit too long to provide benefit. I don't know where I'd pause for an equivalent of 20 characters. Right now, I am seeing a Pilot tone only at the beginning of the CQ in which I included my callsign, City/State and Locator. I think it could be inserted by the operator at the end of each line of CQ for tuning. I also noticed that without looking at the screen, I instantly recognized the signal by WB4MWD by virtue of the inclusion of the Pilot tones. First time I've been able to identify an exotic mode by ear per se, so the tones have an additional value. I think we just need to adopt a reasonable protocol for the tone use and also allow for manual insertion as needed. Howard W6IDS Richmond, IN - Original Message - From: Norbert Pieper polar_elect...@yahoo.com To: digitalradio@yahoogroups.com Sent: Tuesday, January 13, 2009 4:55 AM Subject: [digitalradio] Re: MFTTY 3.0.143 is out Hello Howard and all, In fact the V3.0143 !!DOES!!- send out pilot tone by SEND button or Send By Enter Key The thing is that the pilot is sent out ONLY if there was a reasonable pause between the transmissions. I did set the pause time to a value that is equivalent to the transmission time of 4 Words (20 characters) This was done to avoid an un-needed flood of bothering pilots. My question to the group is: In Pratice: Is that pause time and the effective number of pilots sufficent or is there higher or lower occurrence of pilots needed?
Re: [digitalradio] Re: MFTTY 3.0.143 is out
I think we just need to adopt a reasonable protocol for the tone use and also allow for manual insertion as needed. Howard W6IDS Richmond, IN Howard, for manual Pilot insertion, just configure a macro as only Pilot and click that to insert a Pilot whenever you want. What I think FMTTY needs more than anything is the ability to double-click on a callsign and use it for the macros, such as CALL (for the other station's callsign). I cannot seem to get the TxMacro boxes to work. When I configure a macro with Box1 and put a callsign in for Box 1, I still get Box1 transmitting instead of the callsign. The macros also need to be linked to function keys for ease of keyboarding use. There really is not enough time to fill in the TxMacro box for every QSO. You have to capture a callsign as quickly as possible in order to keep from losing a contact. A double-click has proven to be the fastest way to do that. For example, the significant default DigiPan macros which many are familiar with are: F2 CQ F3 Call 3 (transmit, 3x3, 3x3, 3x3, receive) F4 Call (transmit, 1x1) F5 BTU (1x1, receive) F6 Signoff (73, 1x1, SK, receive) This way, the new user only has to press F2 to call CQ, F3 to answer a CQ, and then just alternate between F4 and F5 for the QSO. When finished, he just goes to the next function key in line to signoff. Of course preferences of others may vary! 73, Skip KH6TY
Re: [digitalradio] Re: MFTTY 3.0.143 is out
the macro-name for box1 is Name ... for box2 it is Call that should solve the problem greetz dg9bfc - Original Message - From: kh6ty To: digitalradio@yahoogroups.com Sent: Tuesday, January 13, 2009 5:05 PM Subject: Re: [digitalradio] Re: MFTTY 3.0.143 is out I think we just need to adopt a reasonable protocol for the tone use and also allow for manual insertion as needed. Howard W6IDS Richmond, IN Howard, for manual Pilot insertion, just configure a macro as only Pilot and click that to insert a Pilot whenever you want. What I think FMTTY needs more than anything is the ability to double-click on a callsign and use it for the macros, such as CALL (for the other station's callsign). I cannot seem to get the TxMacro boxes to work. When I configure a macro with Box1 and put a callsign in for Box 1, I still get Box1 transmitting instead of the callsign. The macros also need to be linked to function keys for ease of keyboarding use. There really is not enough time to fill in the TxMacro box for every QSO. You have to capture a callsign as quickly as possible in order to keep from losing a contact. A double-click has proven to be the fastest way to do that. For example, the significant default DigiPan macros which many are familiar with are: F2 CQ F3 Call 3 (transmit, 3x3, 3x3, 3x3, receive) F4 Call (transmit, 1x1) F5 BTU (1x1, receive) F6 Signoff (73, 1x1, SK, receive) This way, the new user only has to press F2 to call CQ, F3 to answer a CQ, and then just alternate between F4 and F5 for the QSO. When finished, he just goes to the next function key in line to signoff. Of course preferences of others may vary! 73, Skip KH6TY
Re: [digitalradio] Re: MFTTY 3.0.143 is out
Hey, Skip! Long time no. Yes, I think you're touching on some things that could go well toward enhancing the operation. I, too, am having a little difficulty with the TX Macro box as well. However, I suspect that if we keep the cards 'n letters coming in, there'll be some attention given to the ideas for sure. HI had not thought about using a marco for the Pilot thingie. DUH! I've been trying it by manually typing it in. I wasn't thinking macro in that instance. Trying to capture the callsign, QTH, etc does take time and causes dead time too, not to mention creating a cumbersome process. But, then again, this is new as we are awareand interesting. So far, I'm one up on the receiver side. Still working to get my first transmit check out moment. Regards, Howard W6IDS Richmond, IN - Original Message - From: kh6ty kh...@comcast.net To: digitalradio@yahoogroups.com Sent: Tuesday, January 13, 2009 11:05 AM Subject: Re: [digitalradio] Re: MFTTY 3.0.143 is out I think we just need to adopt a reasonable protocol for the tone use and also allow for manual insertion as needed. Howard W6IDS Richmond, IN Howard, for manual Pilot insertion, just configure a macro as only Pilot and click that to insert a Pilot whenever you want. What I think FMTTY needs more than anything is the ability to double-click on a callsign and use it for the macros, such as CALL (for the other station's callsign). I cannot seem to get the TxMacro boxes to work. When I configure a macro with Box1 and put a callsign in for Box 1, I still get Box1 transmitting instead of the callsign. The macros also need to be linked to function keys for ease of keyboarding use. There really is not enough time to fill in the TxMacro box for every QSO. You have to capture a callsign as quickly as possible in order to keep from losing a contact. A double-click has proven to be the fastest way to do that. For example, the significant default DigiPan macros which many are familiar with are: F2 CQ F3 Call 3 (transmit, 3x3, 3x3, 3x3, receive) F4 Call (transmit, 1x1) F5 BTU (1x1, receive) F6 Signoff (73, 1x1, SK, receive) This way, the new user only has to press F2 to call CQ, F3 to answer a CQ, and then just alternate between F4 and F5 for the QSO. When finished, he just goes to the next function key in line to signoff. Of course preferences of others may vary! 73, Skip KH6TY Announce your digital presence via our Interactive Sked Page at http://www.obriensweb.com/sked Yahoo! Groups Links
Re: [digitalradio] Re: MFTTY 3.0.143 is out
Thanks Seigfried! That works now. I could not find where that was in the Help. Now, if Norbert can only code a double-click to enter the call in Box2, that would be great. I know that it is possible under VB6 as I always code it that way in my own VB PSK31 programs. For example, I code according to the following double-click rules (double-clicking in Windows usually automatically selects a word, as I remember.): 1. If the word contains three consecutive numbers, it goes into the RST field. 2. If the word contains one or two numbers, it goes into the callsign field. 3. If the word has no numbers, it goes into the operator name field. 4. For QTH, I select all the words and use a right-click context menu to enter the text into the QTH field. I do not attempt to distinguish between something like PSK31 and a callsign, but rely on the human brain to make the distinction by where the operator makes the double-click selection. 73, Skip KH6TY - Original Message - From: Siegfried Jackstien siegfried.jackst...@freenet.de To: digitalradio@yahoogroups.com Sent: Tuesday, January 13, 2009 12:07 PM Subject: Re: [digitalradio] Re: MFTTY 3.0.143 is out the macro-name for box1 is Name ... for box2 it is Call that should solve the problem greetz dg9bfc - Original Message - From: kh6ty To: digitalradio@yahoogroups.com Sent: Tuesday, January 13, 2009 5:05 PM Subject: Re: [digitalradio] Re: MFTTY 3.0.143 is out I think we just need to adopt a reasonable protocol for the tone use and also allow for manual insertion as needed. Howard W6IDS Richmond, IN Howard, for manual Pilot insertion, just configure a macro as only Pilot and click that to insert a Pilot whenever you want. What I think FMTTY needs more than anything is the ability to double-click on a callsign and use it for the macros, such as CALL (for the other station's callsign). I cannot seem to get the TxMacro boxes to work. When I configure a macro with Box1 and put a callsign in for Box 1, I still get Box1 transmitting instead of the callsign. The macros also need to be linked to function keys for ease of keyboarding use. There really is not enough time to fill in the TxMacro box for every QSO. You have to capture a callsign as quickly as possible in order to keep from losing a contact. A double-click has proven to be the fastest way to do that. For example, the significant default DigiPan macros which many are familiar with are: F2 CQ F3 Call 3 (transmit, 3x3, 3x3, 3x3, receive) F4 Call (transmit, 1x1) F5 BTU (1x1, receive) F6 Signoff (73, 1x1, SK, receive) This way, the new user only has to press F2 to call CQ, F3 to answer a CQ, and then just alternate between F4 and F5 for the QSO. When finished, he just goes to the next function key in line to signoff. Of course preferences of others may vary! 73, Skip KH6TY Internal Virus Database is out of date. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.9.2/1785 - Release Date: 11/13/2008 9:12 AM
Re: [digitalradio] Re: MFTTY 3.0.143 is out
that was easy to find out how this thing works just right click on the button makro ther you find a predefined text that contains the maros use by the programm glad that i could help dg9bfc siegfried or in short form ... sigi - Original Message - From: kh6ty To: digitalradio@yahoogroups.com Cc: d...@polar-electric.com Sent: Tuesday, January 13, 2009 7:53 PM Subject: Re: [digitalradio] Re: MFTTY 3.0.143 is out Thanks Seigfried! That works now. I could not find where that was in the Help. Now, if Norbert can only code a double-click to enter the call in Box2, that would be great. I know that it is possible under VB6 as I always code it that way in my own VB PSK31 programs. For example, I code according to the following double-click rules (double-clicking in Windows usually automatically selects a word, as I remember.): 1. If the word contains three consecutive numbers, it goes into the RST field. 2. If the word contains one or two numbers, it goes into the callsign field. 3. If the word has no numbers, it goes into the operator name field. 4. For QTH, I select all the words and use a right-click context menu to enter the text into the QTH field. I do not attempt to distinguish between something like PSK31 and a callsign, but rely on the human brain to make the distinction by where the operator makes the double-click selection. 73, Skip KH6TY - Original Message - From: Siegfried Jackstien siegfried.jackst...@freenet.de To: digitalradio@yahoogroups.com Sent: Tuesday, January 13, 2009 12:07 PM Subject: Re: [digitalradio] Re: MFTTY 3.0.143 is out the macro-name for box1 is Name ... for box2 it is Call that should solve the problem greetz dg9bfc - Original Message - From: kh6ty To: digitalradio@yahoogroups.com Sent: Tuesday, January 13, 2009 5:05 PM Subject: Re: [digitalradio] Re: MFTTY 3.0.143 is out I think we just need to adopt a reasonable protocol for the tone use and also allow for manual insertion as needed. Howard W6IDS Richmond, IN Howard, for manual Pilot insertion, just configure a macro as only Pilot and click that to insert a Pilot whenever you want. What I think FMTTY needs more than anything is the ability to double-click on a callsign and use it for the macros, such as CALL (for the other station's callsign). I cannot seem to get the TxMacro boxes to work. When I configure a macro with Box1 and put a callsign in for Box 1, I still get Box1 transmitting instead of the callsign. The macros also need to be linked to function keys for ease of keyboarding use. There really is not enough time to fill in the TxMacro box for every QSO. You have to capture a callsign as quickly as possible in order to keep from losing a contact. A double-click has proven to be the fastest way to do that. For example, the significant default DigiPan macros which many are familiar with are: F2 CQ F3 Call 3 (transmit, 3x3, 3x3, 3x3, receive) F4 Call (transmit, 1x1) F5 BTU (1x1, receive) F6 Signoff (73, 1x1, SK, receive) This way, the new user only has to press F2 to call CQ, F3 to answer a CQ, and then just alternate between F4 and F5 for the QSO. When finished, he just goes to the next function key in line to signoff. Of course preferences of others may vary! 73, Skip KH6TY Internal Virus Database is out of date. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.9.2/1785 - Release Date: 11/13/2008 9:12 AM
