I finally got used to that after about 100 QSO's but it surely did
drive me nuts at first. I am also thinking of rearranging the data
entry window to put the call sign first. Having to back tab to get
to the NR field after entering the call sign and then later having
to tab past it was also a pain.
---
73, Rich - W3ZJ
> -----Original Message-----
> From: owner-writelog@contesting.com
> [mailto:owner-writelog@contesting.com]On Behalf Of Bill Axelrod
> Sent: Wednesday, November 08, 2000 2:28 AM
> To: writelog@contesting.com
> Subject: [WriteLog] Re: WriteLog Digest V3 #305
>
>
>
> I concur 100% in the comment regarding an automatic
> move from the check to
> the section field for the Sweepstakes contest. That
> the software
> automatically moved from the check field to the section
> field drove me nuts!
>
> Bill K3WA
> ----- Original Message -----
> From: "WriteLog Digest" <owner-writelog-digest@contesting.com>
> To: <writelog-digest@contesting.com>
> Sent: Tuesday, November 07, 2000 11:50 PM
> Subject: WriteLog Digest V3 #305
>
>
> >
> > WriteLog Digest Tuesday, November 7 2000
> Volume 03 : Number
> 305
> >
> >
> >
> > In this issue:
> >
> > Re: [WriteLog] WriteLog-TS950SDX-FSK almost there but ...
> > Re: [WriteLog] Sweepstakes Field Moves
> > [WriteLog] Init-Sequences to Modem
> > RE: [WriteLog] report field compatibility problem
> during SS
> > [WriteLog] Writelog "out-of-band" enhancement
> > [WriteLog] Simple Writelog "Status" enhancement
> > RE: [WriteLog] Sweepstakes Field Moves
> > Re: [WriteLog] Writelog "out-of-band" enhancement
> > [WriteLog] 10 minute Rule
> > Re: [WriteLog] 10 minute Rule
> > RE: [WriteLog] Writelog "out-of-band" enhancement
> > RE: [WriteLog] Writelog "out-of-band" enhancement
> > [WriteLog] Rotor control
> > RE: [WriteLog] Rotor control
> > [WriteLog] test
> > [WriteLog] "out of band" enhancement
> > Re: [WriteLog] Sweepstakes Field Moves
> >
> > See the end of the digest for information about 3830-digest
> >
> >
> --------------------------------------------------------
> --------------
> >
To: <writelog@contesting.com>
> > Date: Tue, 7 Nov 2000 10:50:56 +0200
> > From: "Igor UA2FZ" <ua2fz@gazinter.net>
> > Subject: Re: [WriteLog] WriteLog-TS950SDX-FSK almost
> there but ...
> >
> > Hi Jon,
> > I'm using TS-950-SDX and WL too. It appeared the same
> thing in the CQWW
> > RTTY. I have PTT and FSK keying circuit on PC port Com2 using
> > pair of 4n25. Reverse mode installed on TS950 menu
> and FSK - rev on TU
> type
> > on WL. All is working OK.
> > 73! Igor UA2FZ
> > ----- Èñõîäíîå ñîîáùåíèå -----
> > Îò: Jon Suehiro <nn5t@attglobal.net>
> > Êîìó: <writelog@contesting.com>
> > Îòïðàâëåíî: November 06, 2000 7:45 PM
> > Òåìà: [WriteLog] WriteLog-TS950SDX-FSK almost there but ...
> >
> >
> > >
> > >
> > > I made FSK keying circuit with a photo coupler
> using com port TXD and
> GND
> > > connection.
> > >
> > > I don't know how TS850 and TS870 are, but
> originally Kenwood FSK keying
> > has
> > > been in backward compare to Yaesu/Icom.
> > >
> > > With Tele-reader, I can individually select
> normal/reverse on TX and RX.
> > >
> > > When I was using KAM, I can reverse the FSK keying
> polarity on one of
> KAM
> > > command (FSK rev: On).
> > >
> > > TS950 FSK reverse on Menu does not work because it
> reverses not only TX
> > but
> > > RX also.
> > >
> > > The TU type on Rittyrite - TNC setup nor
> FSK-Norm/FSK-Rev doesn't work
> > > either by the same reason (I just need to reverse
> the keying polarity on
> > TX
> > > only).
> > >
> > > Let me know if there is any trick to it. Or do I
> need to add another
> > > transistor in the keying circuit to reverse the
> polarity electrically in
> > > hard way ?
> > >
> > > How are you doing, Kenwood RTTY contester with WL ?
> > >
> > > Jon, nn5t@arrl.net
> > >
> > >
> > >
> > > --
> > > WWW: http://www.writelog.com/
> > > Submissions: writelog@contesting.com
> > > Administrative requests: writelog-REQUEST@contesting.com
> > > Problems: owner-writelog@contesting.com
> > >
> >
> > ------------------------------
> >
To: <writelog@contesting.com>
> > Date: Tue, 7 Nov 2000 10:36:00 -0000
> > From: "JOHN KENDRA" <k4jk@home.com>
> > Subject: Re: [WriteLog] Sweepstakes Field Moves
> >
> > I had the same trouble. It took me about half way
> through the contest to
> > almost break me of the habit of spacing after the SECT field.
> >
> > I also have a problem in that items I send to the
> reflector do not get
> > posted.
> >
> > John
> >
> > - ----- Original Message -----
> > From: "Ralph Fedor" <rfedor@cloudnet.com>
> > To: <writelog@contesting.com>
> > Sent: Tuesday, November 07, 2000 2:01 AM
> > Subject: [WriteLog] Sweepstakes Field Moves
> >
> >
> > >
> > > WriteLog worked very well for me in the CQWW Phone
> Contest. I decided
> to
> > > check out CW by making a few contacts in the ARRL
> CW Sweepstakes. It
> > > worked well with one exception --- for me.
> > >
> > > I had difficulty making the move from the Check to
> the Section field.
> > When
> > > moving from each other field to the next field, the
> space bar is used to
> > > toggel you to the next field. However, when moving
> from the Check to
> the
> > > Section field, the cursors advances on its own
> after entering the two
> > digit
> > > check, without the use of the spacebar.
> > >
> > > I found that I instinctively push the spacebar to
> move a next field --
> I'm
> > > programed that way by using it in all previous
> field movements. When I
> do
> > > this to go from Check to Section, the cursor wraps
> around to the Call
> Sign
> > > field and I repeatedly entered the section in front
> of the call sign.
> > >
> > > Did anyone else find this difficult? I'd prefer to
> always use the
> > spacebar
> > > to make a field movement.
> > >
> > > 73 -
> > > Ralph - K0IR
> > >
> > > --
> > > WWW: http://www.writelog.com/
> > > Submissions: writelog@contesting.com
> > > Administrative requests: writelog-REQUEST@contesting.com
> > > Problems: owner-writelog@contesting.com
> > >
> >
> > ------------------------------
> >
To: <writelog@contesting.com>
> > Date: Tue, 07 Nov 2000 12:02:53 +0100
> > From: dl2fag@t-online.de (Karl-Heinz Kuehlborn)
> > Subject: [WriteLog] Init-Sequences to Modem
> >
> > Hello,
> >
> > I want to initialize the Modem (PTC2) via the
> Writelog.ini file.
> > So I implement in th epart (RTTYRITE) the needed parts as:
> >
> > TncInit1=TO 1
> > TncInit2=TR 0
> > TncInit3=BAU
> > TncInit4=Bri 5
> >
> > But it does not work in this way.
> >
> > Does anybody is using the ini-file of Writelog to set a modem?
> >
> > Any help is welcome
> >
> > 73 de Karl-Heinz
> >
> > PS: See you in the WAEDC-Test
> > ===================================
> > Karl-Heinz Kuehlborn
> >
> > - - DL2FAG -
> >
> > ------------------------------
> >
To: <writelog@contesting.com>
> > Date: Tue, 07 Nov 2000 08:33:38 -0500
> > From: Steve Bookout <nj4f@erols.com>
> > Subject: RE: [WriteLog] report field compatibility
> problem during SS
> >
> > Hello Wayne,
> >
> > I think you described what I did pretty well.
> >
> > Normally, in the past, I have always taken one setup
> and moved it on down
> > the network. But, this time, these options got
> enabled as if they were
> one
> > of the other matter-of-fact options, not something
> which, if done in a
> > poorly timed manner, would really mess things up.
> >
> > Normally, being used to this sort of stuff and being
> on 'your side' of the
> > Email, this would have stood out as one of those
> 'don't touch that' type
> of
> > thing.
> >
> > At least I know why now so I can avoid this situation again.
> >
> > 73 de Steve, NR4M
> >
> > At 02:10 AM 11/7/00 +0000, W. Wright, W5XD wrote:
> >
> > >I agree with the posting from VE9WH saying the best
> policy is to set up a
> WL
> > >file before the contest and start all your logs from there.
> > >
> > >But the conflict reported with the "r" field and the
> "Operator" field
> made
> > >me realize there is a problem with WL especially for
> new users--its a
> trap
> > >of sorts. There are two menu entries on the program
> that will add a new
> > >column to the log at any time--including after
> logging QSOs or after
> > >connecting to the network. I think its OK if any one
> networked station
> adds
> > >a single column, but if two do it, and they're not
> the same one, then the
> > >networking software won't reconnect later.
> > >
> > >I'll have to make it impossible to fall into this
> hole. (but I'm still
> > >thinking about how to plug the hole without making
> it impossible to do
> other
> > >useful things like add the Operator column after
> starting the log).
> > >
> > >Wayne
> > >
> > >
> > >--
> > >WWW: http://www.writelog.com/
> > >Submissions: writelog@contesting.com
> > >Administrative requests: writelog-REQUEST@contesting.com
> > >Problems: owner-writelog@contesting.com
> >
> > - ---------------------------------------------
> > - -Steve Bookout, NR4M (ex NJ4F)
> > Rapidan Data Systems
> >
> > 'DX4WIN...The way logging programs should be!'
> > Free demo at http://www.dx4win.com
> >
> > ------------------------------
> >
To: <writelog@contesting.com>
> > Date: Tue, 7 Nov 2000 09:48:00 -0500
> > From: "Skopal, Eugene" <ESkopal@datatec.com>
> > Subject: [WriteLog] Writelog "out-of-band" enhancement
> >
> > Wayne,
> >
> > I, like others, keep getting burned by out-of-band
> spots. I would really
> > like the PC to warn me that I am configured to
> transmit out of band. It
> > would be GREAT if Writelog had a feature that would
> turn the frequency box
> > next to the entry window RED if you were setup to
> transmit outside of the
> > band.
> >
> > Additionally, it would be great of the out-of-band
> spots were color coded
> > (or bordered/boxed in) differently in the band-map.
> >
> > ..Eugene..
> > AE2F
> >
> > ------------------------------
> >
To: <writelog@contesting.com>
> > Date: Tue, 7 Nov 2000 09:50:44 -0500
> > From: "Skopal, Eugene" <ESkopal@datatec.com>
> > Subject: [WriteLog] Simple Writelog "Status" enhancement
> >
> > Wayne,
> >
> > I use Writelog to participate in the CQWW contests.
> I am a systems
> > programmer, and I do some interesting "software"
> things at my station. I
> > would like to ask that you add a simple feature to
> Writelog, that being to
> > record the "status" information into either a file or
> into the registry.
> > This would consist of a timestamp, the RX/TX
> frequency of each radio, the
> > desired beam headings for each radio, and possibly a
> RUN/MULTIPLIER
> > indication. You might think of other good things to
> include that I
> haven't
> > considered.
> >
> > I run Multi/Single and share antennas with the other
> station (Literally, I
> > use a C31XR with 3 feedlines). My entire network is
> Windows 2000 based.
> I
> > use a rotor control "server" program that runs on a
> server that has it's
> COM
> > ports connected to the rotor controllers. A window
> on each operator's PC
> > allows either operator to control either rotor. This
> technique also frees
> > up COM ports in the "operating" PCs.
> >
> > Your new Rotor control feature is great, but it is
> difficult to take
> > advantage of. If you recorded the "desired" beam
> heading in the registry,
> > my "client" program could poll the registry looking
> for updates and
> > translate them into the appropriate control functions.
> >
> > Secondly, I keep getting burned by out-of-band spots.
> As I mentioned in
> an
> > earlier note, it would really like the PC to warn me
> that I am configured
> to
> > transmit out of band. It would be GREAT if Writelog
> had a feature that
> > would turn the frequency box next to the entry window
> RED if you were
> setup
> > to transmit outside of the band.
> >
> > Additionally, it would be great of the out-of-band
> spots were color coded
> > (or bordered/boxed in) differently in the band-map.
> >
> > Lacking that, I can write a program that will poll
> the "status"
> information
> > and flash a warning on the screen that should I
> transmit, I would be
> > out-of-band.
> >
> > Obviously, there are lots of other uses for the
> status information. It is
> > not an elegant, "event" driven interface, but it is
> one many programmers
> > would find very easy to interface to using VB or any
> other language of
> > choice.
> >
> > Thanks for your consideration, and keep up the
> excellent work on your
> > program.
> >
> > ..Eugene..
> > AE2F
> >
> > ------------------------------
> >
To: <writelog@contesting.com>
> > Date: Tue, 7 Nov 2000 15:26:43 -0000
> > From: "Scot Herrick" <sherrick@ameritech.net>
> > Subject: RE: [WriteLog] Sweepstakes Field Moves
> >
> > Hi Ralph (and others),
> >
> > This behavior can be controlled by setting up the
> parameters in the
> Exchange
> > Field. I have mine so that I ALWAYS hit the space bar
> between fields
> > (thousands of QSO's this way, too sleepy, habits die
> hard...). Check out
> how
> > to set the parameters on my web site and go to
> 'WriteLog Windows' and
> > 'Exchange Format.' What you're looking for is how to
> set the 'Tab Only'
> > parameter.
> >
> > Hope this helps.
> >
> > CU...Scot, K9JY
> >
> >
> > See WriteLog's complete user manual at
> > K9JY's WriteLog site http://www.k9jy.com
> >
> > mailto:scot@k9jy.com
> >
> >
> > > -----Original Message-----
> > > From: owner-writelog@contesting.com
> > > [mailto:owner-writelog@contesting.com]On Behalf Of
> Ralph Fedor
> > > Sent: Tuesday, November 07, 2000 02:01
> > > To: writelog@contesting.com
> > > Subject: [WriteLog] Sweepstakes Field Moves
> > >
> > >
> > >
> > > WriteLog worked very well for me in the CQWW Phone
> Contest. I decided
> to
> > > check out CW by making a few contacts in the ARRL
> CW Sweepstakes. It
> > > worked well with one exception --- for me.
> > >
> > > I had difficulty making the move from the Check to
> the Section
> > > field. When
> > > moving from each other field to the next field, the
> space bar is used to
> > > toggel you to the next field. However, when moving
> from the Check to
> the
> > > Section field, the cursors advances on its own
> after entering the
> > > two digit
> > > check, without the use of the spacebar.
> > >
> > > I found that I instinctively push the spacebar to
> move a next
> > > field -- I'm
> > > programed that way by using it in all previous
> field movements.
> > > When I do
> > > this to go from Check to Section, the cursor wraps
> around to the
> > > Call Sign
> > > field and I repeatedly entered the section in front
> of the call sign.
> > >
> > > Did anyone else find this difficult? I'd prefer to
> always use
> > > the spacebar
> > > to make a field movement.
> > >
> > > 73 -
> > > Ralph - K0IR
> > >
> > > --
> > > WWW: http://www.writelog.com/
> > > Submissions: writelog@contesting.com
> > > Administrative requests: writelog-REQUEST@contesting.com
> > > Problems: owner-writelog@contesting.com
> > >
> >
> > ------------------------------
> >
To: <writelog@contesting.com>
> > Date: Tue, 07 Nov 2000 11:12:50 -0500
> > From: "Laurence 'Mike' Hammer" <ldh3@cornell.edu>
> > Subject: Re: [WriteLog] Writelog "out-of-band" enhancement
> >
> > Filtering for out of band spots is a very interesting
> problem from a
> > programmer's perspective. 'Interesting' here means
> it will generate lots
> > of user feedback, both good and bad!
> >
> > From the programmer's perspective, what becomes
> critical is the data
> > coming in to filter. Most spotting programs, data
> entry forms on WWW and
> > so forth either don't force-fill QSX when appropriate
> (radio not connected
> > to computer, program not reading QSX freq when
> creating spot) or don't
> show
> > how to enter a QSX freq when taking manual spots. So
> the data coming into
> > WL over packet isn't 100% reliable by any stretch.
> As a result, WL or any
> > program that would filter spots would have to make a
> whole lot of
> > assumptions that would result in some valid spots
> being filtered out.
> >
> > As one of the mult-chasers for W6XR and a few other
> efforts I'd rather
> > decide for myself whether a spot is a good one or
> not. I think that is
> > part of the operator-skill portion of a contest. I'm
> generally against
> > fully automated contests, think the tools we have
> right now leave just
> > enough to the operator for SSB contests at least.
> What I'd like to see is
> > some more monitoring and some kind of points
> reduction for folks caught
> > transmitting out of band, etc. Then we would all
> remember to check for
> > QSX! As a fairly new ham but old participant in
> other forms of
> competition
> > I'm amazed at how little enforcement there is in
> radio contesting.
> >
> > Mike N2VR
> >
> >
> > At 09:48 AM 11/7/00 -0500, Skopal, Eugene wrote:
> >
> > >Wayne,
> > >
> > >I, like others, keep getting burned by out-of-band
> spots. I would really
> > >like the PC to warn me that I am configured to
> transmit out of band. It
> > >would be GREAT if Writelog had a feature that would
> turn the frequency
> box
> > >next to the entry window RED if you were setup to
> transmit outside of the
> > >band.
> > >
> > >Additionally, it would be great of the out-of-band
> spots were color coded
> > >(or bordered/boxed in) differently in the band-map.
> > >
> > >..Eugene..
> > >AE2F
> > >
> > >--
> > >WWW: http://www.writelog.com/
> > >Submissions: writelog@contesting.com
> > >Administrative requests: writelog-REQUEST@contesting.com
> > >Problems: owner-writelog@contesting.com
> >
> > ------------------------------
> >
To: <writelog@contesting.com>
> > Date: Tue, 07 Nov 2000 12:30:54 -0600
> > From: Ed Gray <w0sd@rapidnet.com>
> > Subject: [WriteLog] 10 minute Rule
> >
> > I suppose this should be on the contest reflector but
> since it is RTTY I
> > will put it here, please reply direct. I am
> confused about the 10 minute
> > rule for single transmitter, multi-op in regards to
> the CQ RTTY contest
> > which I need to get sent in. Please look at the
> following section of my
> > log and tell me if our working 1094 FK8HC is
> breaking the 10 minute rule?
> > When we worked him my rationale was we changed our
> main band from 20 to 40
> > so we could work one multiplier on another band every
> 10 minutes but when
> I
> > looked at the log in retrospect I am wondering if
> since we went to 40 we
> > have to be there 10 minutes before we can work a
> multiplier on another
> > band? Thanks Ed W0SD!
> >
> > 1087 2000-09-24 0210 14093 N2HTL 599 599 5 NY
> > 1 United States K A
> > 1088 2000-09-24 0211 14093 NO2T 599 599 5 NJ
> > 1 United States K A
> > 1089 2000-09-24 0216 14093 K5IID 599 599 5 WV
> > 1 United States K A
> > 1090 2000-09-24 0216 14093 YU7AL 599 599 15
> > 3 Yugoslavia YU A
> > 1091 2000-09-24 0217 14093 UA4LCQ 599 599 16
> > 3 European Russi UA A
> > 1092 2000-09-24 0220 14093 LT0H 599 599 13
> > 3 Argentina LU A
> > 1093 2000-09-24 0225 7082 NW0L 599
> 599 4 MO 1 68
> > 1 United States K A
> > 1094 2000-09-24 0225 21097 FK8HC 599 599
> 32 1
> > 144 3 New Caledonia FK B
> > 1095 2000-09-24 0231 7084 K1RO 599 599 5 CT
> > 1 United States K A
> > 1096 2000-09-24 0234 7085 RW2F 599
> 599 15 1 69
> > 3 Kaliningradsk UA2 A
> > 1097 2000-09-24 0235 7087 W6JOX 599 599 3 CA
> > 1 United States K A
> > 1098 2000-09-24 0236 21091 ZL2AMI 599
> 599 32 1
> > 123 3 New Zealand ZL B
> > 1099 2000-09-24 0236 7087 Z30M 599
> 599 15 1
> 70
> > 3 Macedonia Z3 A
> > 1
> >
> >
> > Ed Gray McCook County Extension
> Educator-Marketing/Farm Management
> > Box 130
> > 130 East Essex
> > Salem, SD 57058-0130
> >
> > Office phone 605 425 2242
> > FAX 605 425 3144
> >
> > ------------------------------
> >
To: <writelog@contesting.com>
> > Date: Tue, 07 Nov 2000 13:51:14 -0500
> > From: "Laurence 'Mike' Hammer" <ldh3@cornell.edu>
> > Subject: Re: [WriteLog] 10 minute Rule
> >
> > At 12:30 PM 11/7/00 -0600, Ed Gray wrote:
> > > 1092 2000-09-24 0220 14093 LT0H 599 599 13
> > > 3 Argentina LU A
> > > 1093 2000-09-24 0225 7082 NW0L 599
> 599 4 MO 1 68
> > > 1 United States K A
> > > 1094 2000-09-24 0225 21097 FK8HC 599
> 599 32 1
> > > 144 3 New Caledonia FK B
> >
> >
> >
> > Here's the rule:
> > C. Multi-Operator (all band operation only):
> > 1. Single Transmitter: Only one transmitter and one
> band permitted during
> > any 10-minute period, defined as starting with the
> first logged QSO on a
> > band. Exception: One-and only one-other band may be
> used during any
> > 10-minute period if-and only if-the station worked is
> a new multiplier.
> > Logs found in violation of the 10-minute rule will be
> automatically
> > reclassified as multi-multi.
> >
> >
> > From how I read this you're clearly OK. Logic: You
> switched to the
> > combination of 40-run and 15-mult after at least 10
> min on 20-run with no
> > mult band in that 10 minute period. Since there was
> no other mult in these
> > 10 mins, you've satisfied the 10 minute rule for any
> previous undisclosed
> mult.
> >
> > Mike N2VR
> >
> > ------------------------------
> >
To: <writelog@contesting.com>
> > Date: Tue, 7 Nov 2000 14:02:58 -0500
> > From: "Skopal, Eugene" <ESkopal@datatec.com>
> > Subject: RE: [WriteLog] Writelog "out-of-band" enhancement
> >
> > Mike,
> >
> > I am not suggesting any sort of filtering! The spots
> still appear.
> >
> > I am only suggesting that if the spot is outside of
> the operator's bands,
> > and doesn't have a QSX frequency that is inside the
> bands, then highlight
> > the SPOT as a warning to the operator. WL already
> highlights spots (as
> > different colors) for worked, not-worked, and
> multiplier. I am suggesting
> > another highlight, a gray border, for out of band.
> >
> > The operator can still select the spot, and determine
> if the station is
> > advertising a QSX frequency. When he works the
> station he can re-spot the
> > station with the correct QSX info (as I frequently do
> in S&P mode).
> >
> > Beyond that, I would like WL to warn me that I have
> tuned beyond the band,
> > or that I don't have the dual-vfo buttons set correctly.
> >
> > It would be cool to color-code the Band-Map with two
> back ground colors,
> one
> > for inband (black as it is now) on one for
> out-of-band (I would suggest
> > gray). Obviously, if you looked at a spot in the
> "gray" part of the band
> > map you would be suspicious -- but if the spot has a
> black border around
> it,
> > then you know that it has a valid QSX frequency
> associated with it!
> > Conversely, if it is gray then you know to be very careful.
> Interestingly,
> > if you see a spot in the black part of the band-map
> with a gray border,
> then
> > you know that it has an invalid QSX frequency
> associated with it (it
> > happens!) and again you know to be careful!
> >
> > By the way, I certainly agree that you don't want to filter!
> >
> > ..Eugene..
> > AE2F
> >
> > - -----Original Message-----
> > From: Laurence 'Mike' Hammer [mailto:ldh3@cornell.edu]
> > Sent: Tuesday, November 07, 2000 11:13 AM
> > To: Skopal, Eugene
> > Cc: writelog@contesting.com
> > Subject: Re: [WriteLog] Writelog "out-of-band" enhancement
> >
> >
> >
> > Filtering for out of band spots is a very interesting
> problem from a
> > programmer's perspective. 'Interesting' here means
> it will generate lots
> > of user feedback, both good and bad!
> >
> > From the programmer's perspective, what becomes
> critical is the data
> > coming in to filter. Most spotting programs, data
> entry forms on WWW and
> > so forth either don't force-fill QSX when appropriate
> (radio not connected
> > to computer, program not reading QSX freq when
> creating spot) or don't
> show
> > how to enter a QSX freq when taking manual spots. So
> the data coming into
> > WL over packet isn't 100% reliable by any stretch.
> As a result, WL or any
> > program that would filter spots would have to make a
> whole lot of
> > assumptions that would result in some valid spots
> being filtered out.
> >
> > As one of the mult-chasers for W6XR and a few other
> efforts I'd rather
> > decide for myself whether a spot is a good one or
> not. I think that is
> > part of the operator-skill portion of a contest. I'm
> generally against
> > fully automated contests, think the tools we have
> right now leave just
> > enough to the operator for SSB contests at least.
> What I'd like to see is
> > some more monitoring and some kind of points
> reduction for folks caught
> > transmitting out of band, etc. Then we would all
> remember to check for
> > QSX! As a fairly new ham but old participant in
> other forms of
> competition
> > I'm amazed at how little enforcement there is in
> radio contesting.
> >
> > Mike N2VR
> >
> >
> > At 09:48 AM 11/7/00 -0500, Skopal, Eugene wrote:
> >
> > >Wayne,
> > >
> > >I, like others, keep getting burned by out-of-band
> spots. I would really
> > >like the PC to warn me that I am configured to
> transmit out of band. It
> > >would be GREAT if Writelog had a feature that would
> turn the frequency
> box
> > >next to the entry window RED if you were setup to
> transmit outside of the
> > >band.
> > >
> > >Additionally, it would be great of the out-of-band
> spots were color coded
> > >(or bordered/boxed in) differently in the band-map.
> > >
> > >..Eugene..
> > >AE2F
> > >
> > >--
> > >WWW: http://www.writelog.com/
> > >Submissions: writelog@contesting.com
> > >Administrative requests: writelog-REQUEST@contesting.com
> > >Problems: owner-writelog@contesting.com
> >
> > ------------------------------
> >
To: <writelog@contesting.com>
> > Date: Tue, 07 Nov 2000 14:28:18 EST
> > From: "Barry N1EU" <n1eu@hotmail.com>
> > Subject: RE: [WriteLog] Writelog "out-of-band" enhancement
> >
> > Just a comment that I'm sure I'm not the only one
> that essentially ignores
> > the Band Map for "gunning". I use the packet window.
> In addition to the
> > fact that the Band Map will only show a segment of
> the band at any given
> > time, the color coding is not updated as you work
> stations/mults. The "M"
> > designator for spots in the Packet Window is
> immediately updated.
> >
> > I would propose adding a designator to the spots in
> the Packet Window: "Q"
> > to indicate an in-band QSX frequency is included with
> the spot and "B" to
> > indicate spot is out-of-band with no QSX frequency
> included with the spot.
> > These are obviously USA-only designators.
> >
> > 73,
> > Barry N1EU
> > website: www.albany.net/~bg
> >
> >
> > >From: "Skopal, Eugene" <ESkopal@datatec.com>
> > >Reply-To: "AE2F (E-mail)" <AE2F@QSL.NET>
> > >To: "Laurence 'Mike' Hammer" <ldh3@cornell.edu>
> > >CC: writelog@contesting.com
> > >Subject: RE: [WriteLog] Writelog "out-of-band" enhancement
To: <writelog@contesting.com>
> > >Date: Tue, 7 Nov 2000 14:02:58 -0500
> > >
> > >
> > >Mike,
> > >
> > >I am not suggesting any sort of filtering! The
> spots still appear.
> > >
> > >I am only suggesting that if the spot is outside of
> the operator's bands,
> > >and doesn't have a QSX frequency that is inside the
> bands, then highlight
> > >the SPOT as a warning to the operator. WL already
> highlights spots (as
> > >different colors) for worked, not-worked, and
> multiplier. I am
> suggesting
> > >another highlight, a gray border, for out of band.
> > >
> > >The operator can still select the spot, and
> determine if the station is
> > >advertising a QSX frequency. When he works the
> station he can re-spot
> the
> > >station with the correct QSX info (as I frequently
> do in S&P mode).
> > >
> > >Beyond that, I would like WL to warn me that I have
> tuned beyond the
> band,
> > >or that I don't have the dual-vfo buttons set correctly.
> > >
> > >It would be cool to color-code the Band-Map with two
> back ground colors,
> > >one
> > >for inband (black as it is now) on one for
> out-of-band (I would suggest
> > >gray). Obviously, if you looked at a spot in the
> "gray" part of the band
> > >map you would be suspicious -- but if the spot has a
> black border around
> > >it,
> > >then you know that it has a valid QSX frequency
> associated with it!
> > >Conversely, if it is gray then you know to be very careful.
> Interestingly,
> > >if you see a spot in the black part of the band-map
> with a gray border,
> > >then
> > >you know that it has an invalid QSX frequency
> associated with it (it
> > >happens!) and again you know to be careful!
> > >
> > >By the way, I certainly agree that you don't want to filter!
> > >
> > >..Eugene..
> > >AE2F
> > >
> > >-----Original Message-----
> > >From: Laurence 'Mike' Hammer [mailto:ldh3@cornell.edu]
> > >Sent: Tuesday, November 07, 2000 11:13 AM
> > >To: Skopal, Eugene
> > >Cc: writelog@contesting.com
> > >Subject: Re: [WriteLog] Writelog "out-of-band" enhancement
> > >
> > >
> > >
> > >Filtering for out of band spots is a very
> interesting problem from a
> > >programmer's perspective. 'Interesting' here means
> it will generate lots
> > >of user feedback, both good and bad!
> > >
> > > From the programmer's perspective, what becomes
> critical is the data
> > >coming in to filter. Most spotting programs, data
> entry forms on WWW and
> > >so forth either don't force-fill QSX when
> appropriate (radio not
> connected
> > >to computer, program not reading QSX freq when
> creating spot) or don't
> show
> > >how to enter a QSX freq when taking manual spots.
> So the data coming
> into
> > >WL over packet isn't 100% reliable by any stretch.
> As a result, WL or
> any
> > >program that would filter spots would have to make a
> whole lot of
> > >assumptions that would result in some valid spots
> being filtered out.
> > >
> > >As one of the mult-chasers for W6XR and a few other
> efforts I'd rather
> > >decide for myself whether a spot is a good one or
> not. I think that is
> > >part of the operator-skill portion of a contest.
> I'm generally against
> > >fully automated contests, think the tools we have
> right now leave just
> > >enough to the operator for SSB contests at least.
> What I'd like to see
> is
> > >some more monitoring and some kind of points
> reduction for folks caught
> > >transmitting out of band, etc. Then we would all
> remember to check for
> > >QSX! As a fairly new ham but old participant in
> other forms of
> competition
> > >I'm amazed at how little enforcement there is in
> radio contesting.
> > >
> > >Mike N2VR
> > >
> > >
> > >At 09:48 AM 11/7/00 -0500, Skopal, Eugene wrote:
> > >
> > > >Wayne,
> > > >
> > > >I, like others, keep getting burned by out-of-band
> spots. I would
> really
> > > >like the PC to warn me that I am configured to
> transmit out of band.
> It
> > > >would be GREAT if Writelog had a feature that
> would turn the frequency
> > >box
> > > >next to the entry window RED if you were setup to
> transmit outside of
> the
> > > >band.
> > > >
> > > >Additionally, it would be great of the out-of-band
> spots were color
> coded
> > > >(or bordered/boxed in) differently in the band-map.
> > > >
> > > >..Eugene..
> > > >AE2F
> > > >
> > > >--
> > > >WWW: http://www.writelog.com/
> > > >Submissions: writelog@contesting.com
> > > >Administrative requests: writelog-REQUEST@contesting.com
> > > >Problems: owner-writelog@contesting.com
> > >
> > >--
> > >WWW: http://www.writelog.com/
> > >Submissions: writelog@contesting.com
> > >Administrative requests: writelog-REQUEST@contesting.com
> > >Problems: owner-writelog@contesting.com
> > >
> >
> >
> ________________________________________________________
> _________________
> > Get Your Private, Free E-mail from MSN Hotmail at
> http://www.hotmail.com.
> >
> > Share information about yourself, create your own
> public profile at
> > http://profiles.msn.com.
> >
> > ------------------------------
> >
To: <writelog@contesting.com>
> > Date: Tue, 07 Nov 2000 17:33:48 -0500
> > From: "Wayne F. King" <wfking@worldnet.att.net>
> > Subject: [WriteLog] Rotor control
> >
> > Please, what is a the DCU1??? I'm not familiar with this term.
> > I have a Big Boy rotor with a DB9 connect for
> computer/remote control.
> > Can I use it with WL?
> > Wayne N2WK
> >
> > ------------------------------
> >
To: <writelog@contesting.com>
> > Date: Tue, 7 Nov 2000 17:52:00 -0500
> > From: "Richard B Drake" <rbdrake@erols.com>
> > Subject: RE: [WriteLog] Rotor control
> >
> > Wayne,
> >
> > DCU1 is the model number of the digital controller for certain
> > Hy-Gain rotors. It can be added to the HAM-IV, is an
> integral part
> > of the HAM-V, and I think it can be used with a
> couple of other
> > models. I just recently ordered a HAM-V.
> Unfortunately it is back
> > ordered at AES :-(
> >
> > - ---
> > 73, Rich - W3ZJ
> >
> > > -----Original Message-----
> > > From: owner-writelog@contesting.com
> > > [mailto:owner-writelog@contesting.com]On Behalf Of
> Wayne F. King
> > > Sent: Tuesday, November 07, 2000 17:34 PM
> > > To: WL Reflector
> > > Subject: [WriteLog] Rotor control
> > >
> > >
> > >
> > > Please, what is a the DCU1??? I'm not familiar with
> this term.
> > > I have a Big Boy rotor with a DB9 connect for
> > > computer/remote control.
> > > Can I use it with WL?
> > > Wayne N2WK
> > >
> > >
> > > --
> > > WWW: http://www.writelog.com/
> > > Submissions: writelog@contesting.com
> > > Administrative requests: writelog-REQUEST@contesting.com
> > > Problems: owner-writelog@contesting.com
> > >
> > >
> >
> > ------------------------------
> >
To: <writelog@contesting.com>
> > Date: Wed, 8 Nov 2000 01:07:23 -0000
> > From: "JOHN KENDRA" <k4jk@home.com>
> > Subject: [WriteLog] test
> >
> > This is a test using text.
> >
> > ------------------------------
> >
To: <writelog@contesting.com>
> > Date: Tue, 7 Nov 2000 21:32:13 -0500
> > From: "Jerry Keller" <dxdog@rcn.com>
> > Subject: [WriteLog] "out of band" enhancement
> >
> > I agree with AE2F.... it would be great if writelog
> could be setup to warn
> > of out-of-band operation, plus distinguishing the
> packet spots. Colors
> would
> > be an excellent way to do it. An overall custom setup
> would be the best,
> so
> > it could be tailored to an individual's license
> priveleges plus band
> > preferences.
> > Jerry K3MGT
> >
> > ------------------------------
> >
To: <writelog@contesting.com>
> > Date: Tue, 7 Nov 2000 21:22:15 EST
> > From: PTSMANTUA@aol.com
> > Subject: Re: [WriteLog] Sweepstakes Field Moves
> >
> > Field Moves and Space no Space.
> >
> > I noticed the same issue.
> >
> > Also, when I worked dialing up the band style, the
> sequence of fields is
> in
> > the wrong order vs, if I was initiating the cq.
> >
> > When dialing up the band, It would be better to get
> the call field first,
> so
> > your automated reply sends it back OK, and then the
> stations sequence,
> power,
> > check and sect.
> >
> > A simple check box for dial the band vs. I am the
> king of this frequency
> > arrangement of fields would be a great enhancement.
> Perhaps a selectable
> > setting of field sequence would be even better.
> >
> > As it was, when I was CQ'ing, the field order was
> great. But when dialing
> up
> > the band, I rotated through the fields twice before
> entering all data, so
> the
> > automated send using F2 would send the full sequence,
> while I typed. This
> was
> > a real chineese fire drill with a couple of the weak
> 30+ WPM folks.
> >
> > BTW, I had a blast, and worked only 40 M using 2Watts
> running Solar
> Battery
> > Power. When ya got 2 Watts, it is tough to hold a
> frequency. So the mod,
> > looking from this angle I think merits consideration.
> >
> > 73's
> >
> > Phil
> > KF8JW
> > 104 contacts-8320 score running 2W, and about 7 hours
> as time permitted.
> >
> > ------------------------------
> >
> > End of WriteLog Digest V3 #305
> > ******************************
> >
> >
> > --
> > WWW: http://www.writelog.com/
> > Submissions: writelog@contesting.com
> > Administrative requests:
> writelog-digest-REQUEST@contesting.com
> > Problems: owner-writelog-digest@contesting.com
>
> _______________________________________________
> Why pay for something you could get for free?
> NetZero provides FREE Internet Access and Email
> http://www.netzero.net/download/index.html
>
> --
> WWW: http://www.writelog.com/
> Submissions: writelog@contesting.com
> Administrative requests: writelog-REQUEST@contesting.com
> Problems: owner-writelog@contesting.com
>
>
--
WWW: http://www.writelog.com/
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|