[DXLog.net - Support] ESM mode

[9A5K]

You're right Jose. Didn't add this to release notes.

It's in closed task at flyspray:
http://flyspray.dxlog.net/index.php?do=details&task_id=33&string=&project=1&type[0]=&sev[0]=&pri[0]=&due[0]=2&reported[0]=&cat[0]=&status[0]=closed&percent[0]=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=

73,
Chris - 9A5K


On Thu, Oct 3, 2013 at 12:22 PM, Jose Orellana <ea7bj at hotmail.com> wrote:

> Already solved the problem of ESM contest mode ... thanksI don't see this
> improvement in release notes..
> 73, EA7BJ, Jose.
>
> Date: Sun, 29 Sep 2013 11:37:30 +0200
> Subject: Re: [DXLog.net - Support] ESM mode
> From: 9a5k at 9a5k.com
> To: ea7bj at hotmail.com
> CC: n6tv at arrl.net; support at dxlog.net
>
> Hi Jose & Bob..
> $RSTEXCHSENT and $SETEXCHSENT are not yet implemented in DXLog.net..
> Regarding ESM, you're right. Focus shouldn't be moved until $LOGGEDCALL
> wasn't sent.
> I will correct this in next release.
> Also, I will check this behavior in DXpedition mode. Currently DXLog.net
> in ESM mode works on the waythat it checks content of the fields, which
> makes a problem in case of DXpedition mode, but also in the case
> you have Exchange guessing set to Automatically.
> I think that this should be changed to check which of the fields has entry
> focus, so, if you're in callsign field,either callsign or CQ should be sent
> (if callsign field is empty).
> Of course, when RCVD fields has focus, if RCVD field isn't mandatory (for
> example DXPedition mode), and CALLSIGNfield is properly field, TU message
> should be sent and QSO will be logged...
>
> I'll fix this for 2.0.17..
> Thanks.
> 73,Chris - 9A5K
>
>
>
>
>
>
>
> On Sat, Sep 28, 2013 at 11:58 PM, Jose Orellana <ea7bj at hotmail.com> wrote:
>
> Really, does not work like WINTEST or N1MM.This I have detected in
> DXpedition mode, have not tried contest mode ...In DXpedition mode, no need
> to fill in any field, the only fields to fill (599/599) are generated
> automatically by dxlog.
>
>
> 73, EA7BJ, Jose.
>
>
>
>
>
>
>
>
>
> > From: n6tv at arrl.net
>
> > Date: Sat, 28 Sep 2013 14:37:39 -0700
>
> > To: support at dxlog.net
>
> > Subject: Re: [DXLog.net - Support] ESM mode
>
> >
>
> > After pressing [Enter] to call a station, you have to fill in the
> received
>
> > exchange before it will send the PLUS message to log the QSO.  You can't
>
> > leave the exchange fields blank.
>
> >
>
> > But I have questions:
>
> >
>
> > Did you type RUNSP [Enter] to enable RUN/S&P switching?
>
> >
>
> > Are you in RUN MODE or S&P mode (visible in Clock window).  Did you
> program
>
> > your RUN messages different than your S&P messages?
>
> >
>
> > There does seem to be one bug, though.  In S&P mode, type a call (for
> dupe
>
> > checking), then press [Enter].  It should send the S&P F1 message, but
>
> > instead it sends the INSERT message.  It should only do that if the
>
> > received exchange field is filled in when in S&P mode.
>
> >
>
> > I'm not sure if Win-Tests $RSTEXCHSENT and $SETEXCHSENT macros are
>
> > recognized, but they may be needed for ESM to work like Win-Test.
>
> >
>
> > It looks like $ESM is programmed to automatically issue a $SPACEBAR (a
>
> > Win-Test macro not yet externalized by DXLog.net), but that means you
> must
>
> > always type the *complete* callsign before you press [Enter], which
> wastes
>
> > some time in RUN mode.  I think the cursor shouldn't move until after the
>
> > $LOGGEDCALL is sent, to give you more time to finish typing in the call
>
> > after you start sending.
>
> >
>
> > 73,
>
> > Bob, N6TV
>
> >
>
> > On Sat, Sep 28, 2013 at 2:19 PM, Jose Orellana <ea7bj at hotmail.com>
> wrote:
>
> >
>
> > > Hi All...
>
> > > In ESM mode, after pressing enter, dxlog send dxlog "call+599".Again I
> hit
>
> > > enter, and repeats "call+599", always so ... should move to the next
> line
>
> > > for a new QSO, but it does.
>
> > > This is correct ??
>
> > > 73 EA7BJ, Jose.
>
> > >
>
> > >
>
> > > _______________________________________________
>
> > > Support mailing list
>
> > > Support at dxlog.net
>
> > > http://www.dxlog.net/mailman/listinfo/support
>
> > >
>
> > _______________________________________________
>
> > Support mailing list
>
> > Support at dxlog.net
>
> > http://www.dxlog.net/mailman/listinfo/support
>
>
>
> _______________________________________________
>
> Support mailing list
>
> Support at dxlog.net
>
> http://www.dxlog.net/mailman/listinfo/support
>
>
>
> _______________________________________________
> Support mailing list
> Support at dxlog.net
> http://www.dxlog.net/mailman/listinfo/support
>