Jeff,
DigiRite v1.1.23 with latest Writelog generated a no-hassle, direct copy and
paste into the WW-Digi log robot. No massaging of any kind required.
I observed essentially all the same issues with DigiRite that you did and maybe
a few others this old fart brain can’t recall.
I really liked the seamless integration with Writelog, especially the
multiplier and dupe checking.
The list of multipliers was great but needs to be in some sort of organized
display - perhaps simply alphabetical order for easy scanning. The yellow color
for 20M Grids worked was very difficult to see; something with more contrast
would help.
On the whole, I was VERY pleased with Wayne’s DigiRite and I applaud him for
his outstanding program and free add-on to Writelog. Thank you Wayne!
73,
Ron N6EE
Sent from my iPhone
> On Sep 1, 2019, at 4:41 PM, Ken K6MR <k6mr@outlook.com> wrote:
>
> I don’t normally use WriteLog, but Wayne’s implementation is definitely
> better than the others out there.
>
>
>
> I have never been able to use a mouse for anything in a contest, so I wrote a
> AutoHotKey script to use F keys to control the various check boxes and
> clicks. Generally pleased with the operation of DigiRite, though still a few
> rough edges.
>
>
>
> Now if I could figure out why so many stations would never respond to me I’d
> be a bit happier. When I could not work AA3B on 80m I figured something was
> not working. I’m not sure I’m enamored enough with WSJT whatever to try and
> fix it. It just does not seem like real radio. Maybe I’m just too old.
>
>
>
> Ken K6MR
>
>
>
> ________________________________
> From: WriteLog <writelog-bounces@contesting.com> on behalf of Jeff Stai
> <wk6i.jeff@gmail.com>
> Sent: Sunday, September 1, 2019 1:23:55 PM
> To: Writelog Reflector <writelog@contesting.com>; Wayne <support@writelog.com>
> Subject: [WriteLog] digirite issues during the WW
>
> Observations and suggestions. Overall a heck of a nice piece of code and I
> very much preferred it over using WSJT-x.
>
> 1. Check boxes unchecking. At various times - when re-sending - the check
> boxes for the QSOs in progress, Calculated next, and/or the Automatically
> Transmit Next would simply uncheck. One example would be answering a CQ,
> then not seeing a CQ for a couple cycles, then seeing the CQ but whoops the
> box is not checked so I don't get my answer sent in the next cycle.
>
> Another case was I was calling CQ and saw a multiplier pop up in the CQ
> window. I quickly clicked on the call and Automatically Transmit Next was
> unchecked and I missed responding. And more than once I saw the call get
> unchecked in QSOs in progress after just one or two resends.
>
> In none of these cases and others was I anywhere close to the 5 minute
> inactivity timeout. Maybe 2 or 3 minutes at the most.
>
> 2. Scrolling in the CQ windows needs to be more "RTTYrite-like" and not
> jumping around while populating. Trying to click on a moving target
> resulted in some erroneous calls and lost Qs. Ditto the Messages to me
> window (I operated with Auto respond unchecked.) I gather some sort of
> prioritization is going on? But I prefer to choose who to contact next.
>
> 3. Calculated next - often was blank but the right next message was chosen
> and sent anyway.
>
> 4. Sometimes I would see the expected message in the conversation window
> but a repeat was sent as if the message hadn't been recognized.
>
> 5. "Starting a QSO by answering a CQ message is the only way that DigiRite
> puts its QSO's transmit frequency on the other station's RX frequency."
> Someone needs to explain why this is desirable.
>
> Over in the WSJT groups I see that it is considered poor practice to
> transmit on the RX frequency - which I can see because someone could
> already be using the other cycle. Usually I have gone to the trouble of
> finding a clear place and I'd like to stay there. And if I am CQing and I
> see a multiplier appear I want to be able to snag it and keep in my clear
> spot.
>
> I'd prefer to see a "Hold TX" like on WSJT-x so I keep my place no matter
> what, or maybe let's just not do this?
>
> 6. I was amazed at seeing so many strong signals in the Transceive window
> but seeing so few decodes as a result. Not sure what to make of that...
>
> 7. I'll echo the request I saw elsewhere for being able to do the longer
> sequence with signal report when the other op expects it. I found I was
> able to click and choose the alt message if I was quick but I had to be
> right there after seeing the decode in the conversation window. I see this
> as analogous to a RTTY op getting conversational on you in a contest. It's
> just polite practice, even if you'd rather not... :)
>
> 8. I wish I had taken a screen shot of this, but last night I was noticing
> some weirdness in the number of points per QSO. Stuff like an N5 being 5
> points while a CE is 3 points. Also my score was like 4000 something. I
> made a mental note the check on it later.
>
> This morning after I made my Cabrillo I went to do my 3830 post. That's
> when I noticed my score was now 2000 something and my points now appeared
> correct. I don't know when this change happened and I'm reasonably certain
> I wasn't on drugs.
>
> Thanks! jeff wk6i
>
> --
> Jeff Stai ~ WK6I ~ wk6i.jeff@gmail.com
> RTTY op at W7RN
> Twisted Oak Winery ~ http://www.twistedoak.com/
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web: http://www.writelog.com/
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|