[Logic] "CW" vs "CWN" solved
Mel
[email protected]
Sun, 18 Jan 2004 21:17:45 -0500
Actually, I have suggested to Dennis that he round to the nearest KHz in
ADIF exports and such...
There should be a Round function in Foxpro... It's probably something
like : ROUND(Variable,precision)
Perhaps someone with a Foxpro manual can enlighten us.
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Bill VanAlstyne
> Sent: January 18, 2004 17:52
> To: [email protected]
> Subject: Re: [Logic] "CW" vs "CWN" solved
>
>
> Bill VanAlstyne wrote:
>
> > That's how my Modes table was set up already. The report
> I'm using to
> > print cards doesn't work that way. However, I should be
> able to change
> > it so that it does. Thanks for the idea. :-)
>
> What I actually ended up doing was replacing the simple term
> "mode" in the report layout with the expression:
>
>
> iif(mode="CW","CW","")+iif(mode="USB","SSB","")+iif(mode=='LSB
> ',"SSB","")
>
> (Since both "CW" and "CWN" start with CW, the first term of
> the expression picks up both cases, based on the way the
> expression parser apparently works.)
>
> While I was at it, I changed all the expressions in the
> report layout from left-justified to centered so
> variable-width data like "59" and "599" would both be in the
> center of the field, and added a couple conditional black-out
> bars (based on the state of "qsl_rcvd") for PSE and TNX on
> the card. I also installed the "HAM" slashed-zero font, and
> the W0 calls (and other numerals) now look great! I've
> finally got this QSL report printer working the way I want it to....
>
> EXCEPT... I want the frequency to round off to the nearest
> kHz -- e.g., if the freq variable reported by the radio is
> 50.13983, I want the report printer to print 50.140. Right
> now it just truncates, and prints 50.139. I know, I know,
> we're really getting down to NITS here, but... Any ideas? Do
> I have to write a SQL script or something?
>
> Bill / W5WVO
>
>
>
> >
> > Bill / W5WVO
> >
> >
> >
> >> instead of:
> >> CW CW
> >> CWN CWN
> >> This solved the problem for me when printing cards.
> >>
> >>>> From Bill VanAlstyne:
> >>>
> >>>
> >>>> I have a Yaesu FT-897 that reports its mode as "CW" when
> the 2300
> >>>> Hz filter is engaged in CW mode, and as "CWN" when the 500 Hz
> >>>> filter is engaged in CW mode. This "CWN" thing is
> propagating all
> >>>> the way to my QSL printing report, and I want it to go away. I
> >>>> tried deleting it from the Modes list, but the mode then
> just shows
> >>>> up blank. I don't know how to get the rig to report just "CW"
> >>>> without referencing what receive filter is being used. (Who on
> >>>> earth cares???) Is there anything I can do to make LOGic
> interpret
> >>>> CWN as just plain old CW? I think I know how to construct an
> >>>> expression in the QSL printing report that will print "CW" when
> >>>> either mode=CWN or mode=CW, but I'm wondering if there
> is a way to
> >>>> prevent this CWN thing fromn showing up anywhere in LOGic.
> >>>
> >>>
> >>>> Same thing would apply to "USB" and "LSB" instead of
> just plain old
> >>>> SSB, which I would greatly prefer -- but that doesn't
> irritate me
> >>>> as much as "CWN". USB and LSB actually mean something,
> as opposed
> >>>> to CWN.
> >>>
> >>>
> >>> Hi Bill,
> >>>
> >>> Look in the help file under "radio interfacing." I think
> there is a
> >>> way to restrict the list of possible modes for a
> particular radio in
> >>> the modes box listed in the radio ifc window. Here's a
> snippet from
> >>> the help file:
> >>>
> >>> When logging information from the radio, LOGic compares
> the mode you
> >>> are currently operating with this list. If the current
> mode is not
> >>> found, it ignores the mode returned by the radio and logs
> the mode
> >>> from the last QSO. This allows you to log modes such as
> PKT or TOR
> >>> that do not appear on your rig's Mode switch. For
> example, suppose
> >>> you are operating TOR. Your rig's VFO is set to LSB. LOGic will
> >>> automatically log LSB. Manually change the mode to TOR.
> LOGic will
> >>> continue to log TOR for subsequent contacts. Now, suppose
> that you
> >>> start operating CW. LOGic will continue to log TOR for the mode.
> >>> Manually change it to CW. Since CW is supported by your
> rig, it will
> >>> now resume reading the mode from the radio on subsequent
> QSOs. The
> >>> list of supported modes is hard-coded in the rig driver
> program, so
> >>> normally you do not have to enter anything for Modes.
> However, some
> >>> drivers may serve more than one rig model which do not
> all support
> >>> the same modes. In that case, you may enter a list of modes here.
> >>> Separate each mode with a comma. For example:
> >>> AM,FM,SSB,LSB,CW,CWN,RTTY
> >>>
> >>> Does this work?
> >>>
> >>> 73, Art AB4RL
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> LOGic mailing list
> >>> [email protected]
> http://mailman.qth.net/mailman/listinfo/logic
> >>>
> >>
> >>
> >>
> >>
> _______________________________________________
> >> LOGic mailing list
> >> [email protected] http://mailman.qth.net/mailman/listinfo/logic
> >
> > _______________________________________________
> > LOGic mailing list
> > [email protected] http://mailman.qth.net/mailman/listinfo/logic
>
> _______________________________________________
> LOGic mailing list
> [email protected] http://mailman.qth.net/mailman/listinfo/logic
>