Upcoming changes to LOGPlus! v3
===============================

During the past couple of months, I've been extremely busy "TRYING" 
to locate that ultimate QTH.  My major requirement in searching out 
this QTH is to break the East Coast Curtain, unfortunately; these 
QTH's are very difficult to find, if not impossible!

When I find time (which is very limited at this point), I've been 
thinking of new and exciting changes I'd like to make to LOGPlus!. 
I'd like to take a moment and share a few of the changes which have 
been implemented in the new major release, which is currently in 
beta testing at my QTH.

The PacketCluster monitoring system in both the Dumb Terminal Program 
and logging modules are the center of my attention at this point.  
Coming back to the U.S.A. and noticing the drastic differences between 
the U.S. clusters and Japan, I see major areas in which information can
be extracted and alerting provided.

Significant changes have been made to this section alone.  I'm 
considering offering a program called LOGPlus! TERM as a separate 
package for those who use a second computer for monitoring the 
PacketCluster spots.  This program will offer complete PacketCluster 
tracking as does the DTP.  Comments?

1.  Country, Zone (CQ/ITU) and Continent information is now displayed 
on the screen.  The new top three lines of the DTP and Lw/P will look like:

      Date: 08/23/93  Time: 1414Z   DX: DL3NY         Freq:  7003.3
Country: DL - Germany                                Zone: 14/24    Cont: Eu
Modes Needed: CW SSB RTY MIX  Bands Needed: 160 80 40 30 20 17 15 12 10  6 SAT

2.  6 Meters and Satellite (145MHz) spots are now checked.  I'm looking at 
adding 2 meter DXCC reporting also.  If I can "SLIP" it in, it'll be there.

SPECIAL NOTE FOR 6 METER GRID and IOTA HUNTERS
----------------------------------------------
In an effort to provide as much "HANDS OFF" record keeping as possible, 
I am looking at providing a means in which the DUMB TERMINAL PROGRAM and
LOGGING w/PacketCluster will automatically provide you with the current 
status of the reported GRID/IOTA.  Unfortunately, we suffer from a lack
of uniformity throughout the world on how this data should be reported.

If the search/reporting feature of LOGPlus! is to become a success, your 
support is essential.  We must make every effort to "EDUCATE" the users 
on our PacketClusters to report the information uniformly.

I would like to suggest the following format be "SUGGESTED" on all local 
clusters for reporting GRID/IOTA information:

DX de KD7P:  50110.0   W1NG          CN99 Ken good signal.     1414Z

DX de KD7P:  14086.7   VE7IU         NA033 Rees on XYZ Isl.    1414Z
or
DX de KD7P:  14086.7   VE7IU         IOTA NA033 Rees XYZ Isl.  1414Z

Basically, the GRID/IOTA combination must be the first set of characters 
sent in the comment field.  We must also try to discourage the use of "-" 
or spaces within the combination. (i.e. NA-033 or NA 033).

If we can establish this basic format, LOGPlus! will be extremely successful
in providing up to the second information.

3.  IOTA - To support the ever popular IOTA system, I have provided a 
means in which the IOTA database (IOTA.DBF) will automatically be checked
if an IOTA REFNO (EU001) is reported in the comment field.  With the many
methods in which data is reported in the comment field, I can not provided
any assurances this system will work 100% of the time.  The following will
work:

 a. If the first 6 characters of the comment field are either  EU001  
 eu-001   EU 001 the program will extract the data and alerting provided.
 ( Basically, any upper/lower case combination ).

 b. If the word IOTA is found within the comment field, the next 6 
 characters of the comment field are extracted.  As long as the format 
 above is followed, the program will extract the data and alerting provided.

Notification will be given in the upper left hand corner next to the date 
field in flashing GREEN. See below for example.

         REFNO       STATUS BLOCK OF IOTA.DBF
         =====================================
         EU001(N)    >> Not found in database -- Needed
         EU001(A)    >> Found -- Approved
         EU001(S)    >> Found -- Submitted
         EU001(C)    >> Found -- Confirmed
         EU001(W)    >> Found -- Worked

4.  GRIDS - Each time a 6 Meter spot is reported, the first 4 characters 
of the comment field will be checked against the 6 Meter database (VUCC50).
Notification will be given in the upper right hand corner next to the 
frequency field in flashing GREEN.  See below for example.

         GRID       STATUS BLOCK IN VUCC50.DBF
         =====================================
         CN89(N)    >> Not found in database -- Needed
         CN89(A)    >> Found -- Approved
         CN89(S)    >> Found -- Submitted
         CN89(C)    >> Found -- Confirmed
         CN89(W)    >> Found -- Worked


EU001(N) Date: 08/23/93  Time: 1414Z   DX: DL3NY       Freq:  7003.3 CN89(C)
Country: DL - Germany                               Zone: 14/24    Cont: Eu
Modes Needed: CW SSB RTY MIX  Bands Needed: 160 80 40 30 20 17 15 12 10  6 SAT

5.  A Call/Prefix Alert Filter system has been provided to allow a 
particular call or DXCC country to sound the alarm.  Regardless what band 
or mode the station is heard on, the alarm system will activate.  Let say
you're one of those guys who needs to work 3Y/p for a new one or perhaps 
the last one.  With this feature, you could enter 3Y/P (must match the
DXCC database),  or the call 3Y0AK ( no this is not the call of the 
upcoming DXPedition!  This was my 3Y/P call), whenever 3Y/P or 3Y0AK 
is reported, the system will alarm.

6.  A new Band & Mode Alert Filter system has been provided.  Individual 
bands, modes or both, can be turned on/off.  Frequency ranges can been 
set for your particular operating areas.  If your a CW operator only, 
turn on only the CW bands, then sit back.

7.  When in a NON-CONNECTED state, LOGPlus! will still log and track DX 
SPOTS. (YES, THIS IS AN EXCELLENT WAY OF """CHEATING""" IN A CONTEST. 
HOWEVER, I HOPE WE ARE ALL GENTLEMEN/LADIES AND OPERATE FOR THE THRILL
NOT THE END RESULTS).  Multiply spots will be checked and only one
logged to the SPOT database. (NOTE:  I'm looking at REMOVING the SPOT
and WWV databases.  This information can be obtained from the CLUSTER)
COMMENTS?

8.  The ALT-K Hot Keys have been extended to provided up to 70 characters
of data.  This won't be a direct benefit to PacketCluster uses, but RTTY,
ASCII etc.. users will love this addition.  In addition a new system has
been added which will allow 4 unique files to be sent.  These files are:

      BRAG.DTP    >>  Station information
      RYRY.DTP    >>  General RY test tape
      CQCQ.DTP    >>  Long CQ tape which is longer than the one liner
                      provided by a standard ALT-K Hot Key.
      TEST.DTP    >>  Contest exchange or anything else you'd like

(Remember:  These are only suggestions of what can be put in these files.  
However, the file names CAN NOT CHANGE!)

   a.  Establish a ALT-K Hot Key.  Example F1:   

         Here is my station information^//BRAG

         Here is my station information ( ^ is converted to a carriage 
         return, line feed combination and transmitted ) will be transmitted 
         on one line.  Next, the program will extract //BRAG and send the 
         TEXT file BRAG.DTP from the  \PLUSVx directory.  ALL files listed
         above MUST be created with a generic text editor NOT A WORD 
         PROCESSOR.  They must also reside in the \PLUSVx directory. 
         The file can be any length; however, I'd recommend keeping 
         them short so not to overload the TNC buffers.

NOTE:  The "JERKING" motion you'll see when sending out files is 
required to allow your TNC time to digest the information. The delay 
is only 50 milliseconds but sufficient to be noticed.

9.  When pressing one of the ALT-K Hot Keys, entering a SPOT or TALK, 
there was a 50 millisecond delay to give the TNC time to react.  This
delay was found to be unnecessary and removed.

10.  A new more powerful indexing feature has been added.  It's 
currently under BETA testing and results are extremely favorable. 
You'll immediately notice a 70-90% savings on disk space.  Typically, 
LOGPlus! created numerous .NTX files which on an average took up 2.2MEGS 
of space for 5100 QSOs. The new system will reduce that to 700K! AND 
the indexing will be 200% faster!!  In addition, I've provided a means 
in which you can TURN OFF many of the indexing feature of the LOGBOOK.  
Many of us don't use IOTA and GRID features and hate to waste time 
creating a file which is never going to be used. 

11.  Automatic searching of external databases such as HamBase, SAM 
and possible HAMCALL will also be provide in the Real-Time and Off-Air 
modules.  The operator will have the ability to turn the feature on/off
to reduce any slow down.  Name, State and county fields will 
automatically be updated.

12.  For the COUNTY Hunters, I'm looking at adding a method of
automatically search the logbook, extracting the callsign, cross checking 
the call with the SAM database THEN automatically update the logbook 
with the county information.  I'm also going to provide a ZIPCODE look 
up feature which will ZOOM in on any ZIPCODE, CITY and STATE in the U.S.
( Database courtesy of KY7X and the U.S. Postal Service )
  
13.  I'm also going to add N6TR Contest support. 

14.  Users have expressed a desire to run programs like
GEOCLOCK, MINIMUF, MINIPROP PLUS and other EXTERNAL programs while
running LOGPlus!.  I'm happy to say that v3 WILL provide this
interface.  Three external program of your choicing (basically ANY
program can be run, even WINDOWS 3.1!, but I highly don't recommend
it) can now be set up under the Parameter/Default screen.

15.  Deleted countries seemed to be a sticking point for some
under v2.  With v3, I'm going to provide a much sounder interface
to track deleted countries.  No longer will CW countries prior to
1/1/75 be counted.

16.  A new DXCC Statistics window has been added which will allow
you to quickly view your DXCC Statistics by mode.  In addition, BAND
COUNTRIES (total of all bands) has been added.  Basically, you'll
have a TON of information right at your finger tips!

17. I've also added a "HIT LIST" which basically allows you to enter
calls such as SLIMS, P5RS7, 1Z9A and 1Z9B which are in your log but don't
count for anything to be SKIPPED during DXCC updating.  This way,
your DXCC totals will be exactly what you think they should be.  Once
the call has been accepted, you can remove him from the "HIT LIST"
and update the DXCC statistics accordingly.

18.  At the request of N7AVK/Lew, I've developed a PARTIAL CALLSIGN
SEARCH ROUTINE.  This option can be turned ON/OFF depending on your
needs.  The partial callsign will allow you to enter let say "7AV",
you logbook will be search and EVERY call with 7AV in it will be
displayed.

19.  SPEED and MORE SPEED!!!!  One thing I and most of you hate, is
seating around waiting for your system to finish updating the various
awards.  Because of this, I'm completely rewriting the code with
SPEED in mind.  Currently two modules have been completed with some
very positive results.  Please note that I'm using a 486/66MHz system
so my times will vary from yours.  However, you can be assured you'll
see the same improvements:


                  Updating of 5100 records in logbook
                    All times in minutes and seconds
               ===========================================

                  DXCC Band & Mode Automatic Update
                        v2.2:  4 min 50 secs
                        v3.0:  0 min 33 secs

                   WAZ Band & Mode Automatic Update
                        v2.2: 15 min 13 secs
                        v3.0:  0 min 43 secs

Overall, you'll notice some major changes and additions which will 
greatly enhance the program.  If you feel I've left something out, 
please don't hesitate to make suggestions.  Remember, LOGPlus! is a 
user support software, user input is taken seriously!

Bob/KD7P
