Re: ARRL 160m
Tabbing back to the callsign field to ESM my call (S) or resend their exchange info (run) seems fine to me. Enter in the exchange field logging it and all even before exchange is sent and confirmed (S) is a bit optimistic maybe, but in S, not a big penalty to delete that logged entry if the band dropped out or QRM or something meant the QSO didn't get completed. Don't need to do that most of the time. Drew n7da On Sun, Dec 8, 2019 at 5:48 PM Nate Bargmann wrote: > > * On 2019 08 Dec 10:07 -0600, Drew Arnett wrote: > > I played for a couple of hours with the 160m contest as well from a > > very noisy location, so not very many QSOs. Worked a big gun east of > > the Mississippi, but no KG4 for me. :-) Didn't consult with Nate for > > rules or config file. Just grabbed the distributed arrl160m_usa rules > > and merged a bit from my own files from the last contest. > > Like I noted, this KG4 was a 2x1 in VA so no GITMO for me either. > > > I worked a couple of stations during auto CQ, and the rest in S > > Messages and ESM both worked great. I guest operated at another > > station for a bit during CQ WW. They weren't using ESM. Wasn't bad > > using the function keys, but I missed ESM as someone how can touch > > type. > > For me, using ESM in S is a bit disconcerting as when Enter is pressed > after receiving the running stations exchange, the QSO is logged before > my exchange is even sent, let alone confirmed. This is why I did a bit > of work so that in CT mode the Enter key only logs the QSO when both > fields have something it them. > > My S sequence was as follows: > > :CFG and uncomment CTCOMPATIBLE in logcfg.dat, Tlf reloads and resets > the configuration. > > Type in the running station's call. > > Press F6 to send my call. > > Type in his exchange, if DX only a signal report is sent so type a space > character in the exchange field, otherwise ARRL section is typed. > > Press Alt-1 which is set to "TU +5NN- KS" (I left F3 set to "@ +5NN- KS". > > Press Enter once he sends TU or CFM or whatever. > > > > Out of that sequence, what I would consider changing would be if the > exchange field is empty that Enter sends mycall (F6), similar to ESM. > > I would also consider changing Insert to send the S_TU_MSG macro > instead of F3. To go along with this would be enabling a notion of CQ > and S in CT mode so the messages sent would be mostly the same as ESM, > but with different keystrokes and with Enter logging when there are > characters in each field. > > Also, in S, having the + key send "TU" then log was awkward as > convention seems to prefer the S station to send "TU exchange" these > days. > > > I've noticed that clear the call field behavior of the ESC key as > > well. If there is an alternate behavior that makes sense and doesn't > > make ESM worse, I'd love to consider it. It is slightly annoying, but > > I didn't fret over it too much, as I figured it was good practice for > > short term callsign memory. If getting a fill is taking time, it > > might push the limits of my short term memory, though. > > My short term memory is working hard enough being two to three > characters behind his sending! Losing the callsign just because he > decided to start sending his call again a few milliseconds after I fired > the exchange macro and wanting to stop it to get back in sync with him > is annoying. > > I could imagine ESC working like this: > > If the callsign and exchange fields have characters in them, ESC works > just as now but stopping the TX and successively clearing the fields on > additional presses. > > If the callsign field has characters and the exchange field is empty > with the cursor in either, then ESC stops TX. The second press would > clear the callsign and make sure the cursor is in the callsign field. > > The tricky part is, what if there is no TX, I think the current behavior > is to clear the fields immediately, exchange then callsign on successive > presses. > > Since this would be new behavior, it's likely that it should be disabled > by default and enabled with a keyword command as many are probably used > to the current behavior. > > 73, Nate > > -- > > "The optimist proclaims that we live in the best of all > possible worlds. The pessimist fears this is true." > > Web: https://www.n0nb.us > Projects: https://github.com/N0NB > GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 >
Re: ARRL 160m
* On 2019 08 Dec 10:07 -0600, Drew Arnett wrote: > I played for a couple of hours with the 160m contest as well from a > very noisy location, so not very many QSOs. Worked a big gun east of > the Mississippi, but no KG4 for me. :-) Didn't consult with Nate for > rules or config file. Just grabbed the distributed arrl160m_usa rules > and merged a bit from my own files from the last contest. Like I noted, this KG4 was a 2x1 in VA so no GITMO for me either. > I worked a couple of stations during auto CQ, and the rest in S > Messages and ESM both worked great. I guest operated at another > station for a bit during CQ WW. They weren't using ESM. Wasn't bad > using the function keys, but I missed ESM as someone how can touch > type. For me, using ESM in S is a bit disconcerting as when Enter is pressed after receiving the running stations exchange, the QSO is logged before my exchange is even sent, let alone confirmed. This is why I did a bit of work so that in CT mode the Enter key only logs the QSO when both fields have something it them. My S sequence was as follows: :CFG and uncomment CTCOMPATIBLE in logcfg.dat, Tlf reloads and resets the configuration. Type in the running station's call. Press F6 to send my call. Type in his exchange, if DX only a signal report is sent so type a space character in the exchange field, otherwise ARRL section is typed. Press Alt-1 which is set to "TU +5NN- KS" (I left F3 set to "@ +5NN- KS". Press Enter once he sends TU or CFM or whatever. Out of that sequence, what I would consider changing would be if the exchange field is empty that Enter sends mycall (F6), similar to ESM. I would also consider changing Insert to send the S_TU_MSG macro instead of F3. To go along with this would be enabling a notion of CQ and S in CT mode so the messages sent would be mostly the same as ESM, but with different keystrokes and with Enter logging when there are characters in each field. Also, in S, having the + key send "TU" then log was awkward as convention seems to prefer the S station to send "TU exchange" these days. > I've noticed that clear the call field behavior of the ESC key as > well. If there is an alternate behavior that makes sense and doesn't > make ESM worse, I'd love to consider it. It is slightly annoying, but > I didn't fret over it too much, as I figured it was good practice for > short term callsign memory. If getting a fill is taking time, it > might push the limits of my short term memory, though. My short term memory is working hard enough being two to three characters behind his sending! Losing the callsign just because he decided to start sending his call again a few milliseconds after I fired the exchange macro and wanting to stop it to get back in sync with him is annoying. I could imagine ESC working like this: If the callsign and exchange fields have characters in them, ESC works just as now but stopping the TX and successively clearing the fields on additional presses. If the callsign field has characters and the exchange field is empty with the cursor in either, then ESC stops TX. The second press would clear the callsign and make sure the cursor is in the callsign field. The tricky part is, what if there is no TX, I think the current behavior is to clear the fields immediately, exchange then callsign on successive presses. Since this would be new behavior, it's likely that it should be disabled by default and enabled with a keyword command as many are probably used to the current behavior. 73, Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 signature.asc Description: PGP signature
Re: ARRL 160m
I played for a couple of hours with the 160m contest as well from a very noisy location, so not very many QSOs. Worked a big gun east of the Mississippi, but no KG4 for me. :-) Didn't consult with Nate for rules or config file. Just grabbed the distributed arrl160m_usa rules and merged a bit from my own files from the last contest. I worked a couple of stations during auto CQ, and the rest in S Messages and ESM both worked great. I guest operated at another station for a bit during CQ WW. They weren't using ESM. Wasn't bad using the function keys, but I missed ESM as someone how can touch type. I've noticed that clear the call field behavior of the ESC key as well. If there is an alternate behavior that makes sense and doesn't make ESM worse, I'd love to consider it. It is slightly annoying, but I didn't fret over it too much, as I figured it was good practice for short term callsign memory. If getting a fill is taking time, it might push the limits of my short term memory, though. Best regards, Drew n7da On Sun, Dec 8, 2019 at 3:35 PM Nate Bargmann wrote: > > Well, first off, the use of cwdaemon and Tlf via Hamlib on the same > serial port (real motherboard port) worked perfectly without a problem > throughout my operating time. I missed Saturday evening due to having > aggravated my hip yesterday and had to lay down. I was up around 0830z > this AM and worked a bit over an hour and had to lay down for a while > and then again from about 1140z to 1420z or thereabouts. The hip is > feeling batter! > > My CT changes didn't get used much as I saw I had Alt-1 set for the > exchange I wanted to send in S mode so that I didn't have to edit the > F3 message all the time. Making sure that Enter didn't log an > incomplete contact did prove useful in the wee hours... > > ESM mode for running worked perfectly. > > Combining Escape to halt the CW message and clearing the input fields is > a double edged sword. When there is text in the call and exchange > fields and the cursor is in the exchange field and a CW message is in > progress, the first ESC stops the TX and the second clears the exchange > field and the third clears the call field. This is fine so far as it > goes. When the call field has characters in it and the cursor is in the > call field and the exchange field is empty, a single ESC stops the TX > AND clears the call field! That led to several ARGH! moments. I think > that a better algorithm could be worked out. > > Scoring is completely wrong but ARRL 160 is difficult to score. Tlf > several times counted an incorrect multiplier. For one I worked a KG4 > in VA and Tlf scored it as the KG4 mult when it should have determined > that the VA meant it was conus. Another time or two I fat fingered an > exchange and removed the text from the mult column but even a :RES > command had no apparent effect. Also, it seemed as though coming back > from an :EDI command resulted in Tlf forgetting any previous dupes even > though they're marked as zero points. > > In the end, the main thing is that the Cabrillo file is correct and ARRL > will take care of the scoring. > > Overall, I enjoyed using Tlf again. > > 73, Nate > > -- > > "The optimist proclaims that we live in the best of all > possible worlds. The pessimist fears this is true." > > Web: https://www.n0nb.us > Projects: https://github.com/N0NB > GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 >
