Loading ...
Sorry, an error occurred while loading the content.

RE: [BPQ32] Running ARESDATA with BBPQ32

Expand Messages
  • John Wiseman
    If you are already using BPQ32 for anything else, load those programs first, then start ARESDATA in a dos box/cmd window. I d recommend running BPQTerminal as
    Message 1 of 19 , Nov 1, 2011
    • 0 Attachment
      If you are already using BPQ32 for anything else, load those programs first, then start ARESDATA in a dos box/cmd window. I'd recommend running BPQTerminal as a minimum, so you can connect to ARESDATA to test.
       
      You can just start ARESDATA in a dos box. BPQ32 will be loaded as ARESDATA initialises.
       
      I should have made clear before that this all applies to Windows 2000 and later.
       
      73,
      John
       


      From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of Tyler Griffiths
      Sent: 31 October 2011 23:40
      To: BPQ32@yahoogroups.com
      Subject: Re: [BPQ32] Running ARESDATA with BBPQ32

       

      So you run BPQ32 in windows first then ARESDATA. Is this correct?


      Tyler N7UWX

      On Mon, Oct 31, 2011 at 9:31 AM, John Wiseman <john.wiseman@...> wrote:
       

      Hi.
       
      I've made a couple of changes to the bpq1632 files to make them easier to use with ARESDATA.
       
      Download the bpq1632.zip from this YAHOO group.
       
      Copy bpq1632.dll to your Windows\system32 folder.
       
      Copy bpq1632.exe and dedhost.com to your ARESDATA folder.
       
      Edit ARESDATA.CFG to use BPQ (uncomment the relevant attach line).
       
      I edited the AREASDATA.BAT  to contain:
       
      rem ARESDATA.BAT.
      rem This loads the BPQ32 Interface
      BPQ1632
      rem This loads the terminate and stay resident program that makes the
      rem BPQ switch speak DED host mode, using software interrupt hex FE (254)
      rem with 9 connects available, start with stream 1, use application 3
      rem    (ARES/Data), and 40 K available for buffering DED packets.
      DEDHOST 9 1 4 40 254 N
      aresda16
       
      This is set to use BPQ APPL 3 - change the 3rd Param of DEDHOST to suit.
       
      It is best to create a shortcut to AREASDATA.BAT, and set "Run In Separate Memory space" in the advanced properties. Then the bpq interface will be unloaded when the program exits.
       
      It works as far as I can see, though I don't know what the program is supposed to do, so I can't be sure!
       
       
      73,
      John
       
       

       




      --
      Tyler Griffiths
      N7UWX

      See where I am:
      http://map.findu.com/n7uwx-12

    • John Wiseman
      I intalled ARESDATA into it s own folder, but you could install into your BPQ32 folder. You d need to edit ARESDATA.CFG to suit. John _____ From:
      Message 2 of 19 , Nov 1, 2011
      • 0 Attachment
        I intalled ARESDATA into it's own folder, but you could install into your BPQ32 folder. You'd need to edit ARESDATA.CFG to suit.
         
         
        John


        From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of D R Mynatt
        Sent: 01 November 2011 01:09
        To: BPQ32@yahoogroups.com
        Subject: RE: [BPQ32] Running ARESDATA with BBPQ32

         

        Great stuff for sure.  If I understand correctly, we should just copy the exe into the BPQ subdir and execute. Right?
         
        Dave
        KA0SWT


        From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of WS7I
        Sent: Monday, October 31, 2011 7:02 PM
        To: BPQ32@yahoogroups.com
        Subject: Re: [BPQ32] Running ARESDATA with BBPQ32

        Maybe this would help.  From my working files  this stuff runs fine on old bpq under Win98 which is where I had/have it.  But we don't use it around here any longer.  Ran a lot of users up to 10 plus under DRSI and BPQ.
         
         
         
        Revised and reprinted from Proceedings of the Seventh ARRL Computer Networking
        Conference (ARRL, Newington, CT, 1988), pp. 141-144, by permission of the
        authors.


                                         ARES/Data:
                    A PACKET RADIO DATABASE FOR EMERGENCY COMMUNICATIONS

                                     W. E. Moerner, WN6I
                                      1003 Belder Drive
                                 San Jose, California  95120
                                        WN6I @ KB6OWT

                                      David Palmer, N6KL
                                       248 Omira Drive
                                 San Jose, California  95123
                                N6KL @ KB6OWT, CIS: 73357,3157


                                         INTRODUCTION

        ARES/Data is a multiple connect, specialized bulletin board system tailored to
        store and retrieve basic information about people, places, or things during an
        emergency.  The program is a generalized form of the FINDER program (Family
        Information Database for Emergency Responders), written by David Palmer, N6KL
        and W.  E.  Moerner, WN6I [See FINDER:  The Family Information Database for
        Emergency Responders, Proceedings of the Sixth ARRL Computer Networking
        Conference, 1987, by W.  E.  Moerner, Sharon Moerner, and David Palmer].
        Although ARES/Data allows access to the database via packet radio, the program
        can also operate stand-alone without the need for packet radio hardware.  The
        actual operating mode is chosen by the system operator when the ARES/Data
        program is started.

        ARES/Data is a system designed for management of information during a
        widespread emergency that overloads normal communications channels.  The
        program is designed to be flexible, so that it can be used without change for
        both small and large disasters to organize information about victims, evacuees,
        or even ham radio operators.  Examples of situations in which ARES/Data could
        be used are:

         -  registration of individuals at Red Cross shelters
         -  patient/victim tracking in a multiple casualty incident
         -  maintaining staffing information about hams assigned to an emergency
         -  listings of road closures or damage reports
         -  logging reports from SKYWARN observers during periods of severe weather

        With alternate power sources and their own frequencies, Amateur Radio Emergency
        Service (ARES) operators can provide the ARES/Data service without tying up
        critical communications channels or relying on commercial power.


                                  ARES/Data SYSTEM OVERVIEW

        There are three major elements to the ARES/Data system:

         -  ARES/Data software and database
         -  Data Concentrators (remotely connected packet operators)
         -  Voice operators

        The central element of the ARES/Data system is the computer on which the
        ARES/Data program is running.  The ARES/Data program collects and collates
        current information about people or items in the system, according to the needs
        of the incident.  The program establishes and maintains the actual database on
        floppy disk or hard disk at this central computer.  In general, the operator at
        the computer keyboard can add new records to the database, delete incorrect
        records, perform searches for specific information, and generate database
        summaries.  The ARES/Data program will run on any IBM Personal Computer or
        IBM-compatible system running IBM DOS or MS/DOS with at least one floppy disk,
        although a hard disk increases the allowable size of the database and improves
        performance.  [IBM is a registered trademark of International Business Machines
        Corporation.]

        If remote access to the database is desired, addition of a serial port, TNC,
        and radio allows the central database computer to become the hub of a packet
        radio network in which up to eight remotely connected stations can
        simultaneously access the information in the ARES/Data database.  These packet
        radio stations, called "Data Concentrators," can update or query the shared
        database.  This data access occurs by exchanging updates or queries in a
        simple, precise, and well-defined format.

        Data Concentrators extend the coverage of the ARES/Data system.  They are the
        input/output ports of the ARES/Data database when remote access is needed.  The
        Data Concentrators can also act as local net controls for any participating
        voice operators within their range.  If voice operators are not needed, the
        packet operators interact with the public and/or disaster officials directly.

        The Voice Operators enter the ARES/Data system when the points of contact with
        those needing information are numerous and/or spread over a wide area.  These
        amateurs are also the public face of the ARES/Data system.  They can be the
        'reporters' live at the scene, sending status updates and requests to the Data
        Concentrators.  They also ensure delivery of responses to the persons making
        status requests.

        Emergency responders, their families, evacuees located at a particular shelter,
        and responsible agency officials access the ARES/Data system by contacting a
        participating amateur radio operator.


                   DESCRIPTION and OPERATION of the ARES/Data SYSTEM V. 0.1

                                    The ARES/Data Program

        The ARES/Data software was written by W. E. Moerner, WN6I, and David Palmer,
        N6KL.  It may be run in either of two modes:  stand-alone with no TNC support
        and no remote access, or by changing the configuration file, the program will
        control a TNC that allows multiple (simultaneous) remote connections.  If TNC
        support is chosen, the program requires a TNC with WA8DED firmware, because
        WA8DED host mode is used for communication between the computer and the TNC.
        WA8DED firmware is currently available for the TAPR TNC-1 and TNC-2 as well as
        the AEA PK-87.  We emphasize that NO REQUIREMENT IS PLACED ON THE OTHER TNC'S
        CONNECTED TO THE ARES/Data DATABASE MACHINE, except that they use AX.25
        link-layer protocol.  The ARES/Data program is written in Turbo Pascal Version
        4, and uses Turbo Database Toolbox for management and indexing of its B-plus
        structured tree.  [Turbo Pascal and Turbo Database Toolbox are trademarks of
        Borland International, Inc.] Briefly, ARES/Data may be regarded as a
        specialized multiple connect BBS with a specific command set tailored to the
        handling of STATUS INPUT information and SEARCH REQUESTS.

        The ARES/Data database is simply a collection of records.  Each record consists
        of four main items or "fields" plus a message item.  The information in the
        four main fields can be sorted or searched as required.  The rest of this
        section provides examples and a condensed user manual for the ARES/Data system.


                General Rules for Current Information Input / Search Requests

        All basic commands can be entered either at the main ARES/Data keyboard or at
        any one of the remotely connected packet stations.  In addition, the operator
        at the main ARES/Data keyboard (the "sysop") has an additional set of commands
        that allow direct communication with the TNC, the printing of a log, backups,
        and disk report files.


                            Syntax for Current Information Input:

        To add a record to the database, the operator simply enters the four fields and
        any message, in order, with separators between the fields.  The only valid
        separator is the comma.  Within a field, leading and trailing blanks are
        ignored, but imbedded blanks ARE significant.  If no value is desired for a
        particular field, just skip the field by adding an extra comma.  The database
        will fill that field with ten blank characters.  For example,

            field1,field2,field3,field4,message<cr>

            (<cr> means carriage return)

        Fields 1 through 4

        The four fields are very general.  Each can have up to 20 characters, with
        imbedded blanks.  The meaning of each field is defined at the beginning of the
        event by the ARES officials, depending upon the nature of the event and what
        type of information needs to be tracked.  The sysop can issue a "labels"
        command that will give specific names to each of the four fields to help the
        operators remember the purpose of each field for a particular event.

        Message

        MESSAGE is an optional, free-form field that can be up to 80 characters in
        length.  It could contain a message, a phone number, an address, or other
        information deemed useful for the incident.

        Examples of Data Input with Sample Responses from ARES/Data

            85553195,joe,12,sj34<cr>
         response->   1040: data input accepted, #234.

            Johnson,Mary,93445,sj13, home 2333 Alsace Ln SJ 617-555-2368<cr>
         response->   2134: data input accepted, #114.

        All of the input information is stored in the database as a record of the
        status and location of a particular person at a particular time and date.  The
        time and date are added automatically by ARES/Data.  The number at the end of
        the response is the actual "record number" associated with the input
        information assigned by ARES/Data.  Further data input packets for the same
        person will also be saved in the database under a new record number.  The time
        and date identifies which information is most recent.


                                  Syntax for Search Requests

        The search commands instruct the database to look for ALL entries with the same
        value for field 1, 2, 3, or 4.  For example:

            /1,value<cr>                  Searches for "value" in field 1
            /2,value<cr>                  Searches for "value" in field 2
            /3,value<cr>                  Searches for "value" in field 3
            /4,value<cr>                  Searches for "value" in field 4

        (For convenience in typing, the character question mark "?" may be used instead
        of the diagonal bar "/"--both are treated identically).  A status report
        listing all information for each match in the field specified is sent back to
        the requesting packet station.  The first line gives the search value and the
        field number.  VALUE must exactly match what was originally typed in for the
        selected field, with leading and trailing blanks removed, and without regard
        for case.  At the end of the report, the line

            ARES/Data Search done at HHMM, nn hits.

        is sent, which signifies no more information coming, and that "nn" matches (or
        hits) were found in the database at time "HHMM".

        Examples of Search Requests:

            /1,5553195<cr>
            /2,w1aw<cr>
            /3,mercyhosp<cr>
            /4,85563<cr>

        Example Response from ARES/Data for the last case:

            Search for value "85563" in Field4
             Recno DT/Time: Field1,Field2,Field3,Field4,Msg
             29    13/1225: JOHNSON JOE,M35,SHELTER 1,85563, MISSING DOG AND CAT
             59    13/1257: DOE JANE,F23,SH05,85563, 2 CHILDREN
            ARES/Data search done at 1259, 2 hits.


                                 Syntax for Summary Requests

        A Summary command is provided that prints a breakdown of the number of
        like-named items for any particular field.  For example, if ARES/Data were
        being used to maintain a list of evacuees, and field 3 was designated for
        "shelter location", then the command "$3" would print a list of all distinct
        shelter names in use, and adjacent to each, the number of records (people) in
        the database at each shelter would be printed.

             $1<cr>                       Produces a summary on field 1
             $2<cr>                       Produces a summary on field 2
             $3<cr>                       Produces a summary on field 3
             $4<cr>                       Produces a summary on field 4

        Sample Output from a Summary Request:

             Database summary for Field3 at 1455 on 23
                OAK GROVE            3
                PIONEERHS            20
                EASTVIEW             66
                SHLTR5               37
             ARES/Data done at 1456, found 4 distinct values, entire DB has 153 records.


                      Listing Specific Entries (Records) in the Database

        Each record is automatically assigned a unique record number for identification
        purposes.

             l nnnnn<cr>                  lists record nnnnn


                    Deleting Specific Entries (Records) from the Database

        This function is always enabled at the sysop keyboard.  Its use by remotely
        connected packet stations is controlled initially by the configuration file
        during program startup.  Thereafter, the sysop can disable or enable this
        function as necessary.  Be extremely careful in using this command!  Always
        list the record first before deleting to be sure you have the right one.

             d nnnnn<cr>                  deletes record nnnnn


                                Conference Bridge (Roundtable)

        This feature allows any connected station to send messages to other connected
        stations or to the sysop.  The conference bridge illustrates how the ARES/Data
        system operates as a hub-oriented network, with all transactions passing
        through the central database station.

        Users Command

        The users command in the form "users<cr>" or "u<cr>" returns a list of the
        callsigns of packet stations currently connected to ARES/Data.  The response is
        of the form:

             At WN6I-1:  N6KL  W6BB-3  AJ6T

        Tell Command

        The Tell command allows connected packet stations to use ARES/Data as a
        conference bridge, or roundtable.  The general format is:

             tell callsign message<cr>      or      t callsign message<cr>

        For example:

             tell w6bb-3 We have lots of people here at SJ12<cr>

        The message "We have lots of people here at SJ12" is sent to the connected
        station W6BB-3 prefaced by a time stamp and the call of the station originating
        the tell command.  In this case, if the tell command was sent by AJ6T, W6BB-3
        sees:

             1230  AJ6T> We have lots of people here at SJ12

        The special callsign "*" or "all" is used to send a message to all connected
        stations.  The special callsign "sysop" sends the message to the sysop at the
        ARES/Data database station.  It is not necessary to enter the entire callsign--
        just the suffix or some other substring will do.  In this case, the message is
        sent to any connected station whose callsign contains this substring.  This
        feature can be used to create multiple roundtables.  For example, packet
        stations located at, say, hospitals could adopt subªstation identifiers (SSIDs)
        of "-1", while those located at shelters could use SSIDs of "-2".  This way,
        broadcast messages of interest to either group can be easily sent without
        disrupting the other group.  For example:

             tell -1  Mercy Hospital has 12 beds available.<cr>

        This message would be sent to all stations that were part of the hospital net.


               EXAMPLES OF HOW TO USE ARES/Data IN SPECIFIC DISASTER SCENARIOS

        -  In an evacuation of residents in a local area, the Red Cross often maintains
        health and welfare status information about evacuees.  In this case, the four
        fields and the comment field might be defined to be:

             Last Name - First Name, Shelter, Number in Family, Last phone, Next of kin

        -  In a multiple-casualty event where victim transportation needs to be
        tracked:

             Name, Sex/Age, Ambulance#, Hospital, Injuries

        -  In a ham radio staffing situation:

             Call, Name, Location, Shift, phone number for cancellation

        -  In a disaster situation where damage assessment and damage reports are
        needed:

             Coded type of damage, Location, Number of injuries, Callsign, comment

        There are many more possibilities, of course.  This is why the exact
        definitions of the various fields are not defined in advance.  In any given
        situation, more information than will fit into four fields and a comment field
        might be needed.  However, on today's 1200 baud packet radio networks, not much
        more information per record can be accommodated without restricting the total
        number of records that can be handled in a reasonable time.


                      HOW TO OBTAIN YOUR COPY OF THE ARES/Data PROGRAM

        The ARES/Data program, a relative of and successor to the FINDER program, is in
        the public domain.  The current version is 0.1, which operates as described in
        this paper.  A copy of the program along with the documentation is available
        for non-commercial, non-profit use from WN6I or N6KL by sending a blank,
        formatted 5 1/4" (360 kB) or 3 1/2" (720 kB) floppy in a mailer with return
        postage stamps.  The cost to you is the cost of the diskette and postage.  No
        other compensation can or will be accepted - please do not send money.  We have
        included a configuration file facility so that you can tailor many parameters
        to your specific system.


                                      FUTURE DIRECTIONS

        The ARES/Data program is continuously being updated to add additional function
        and flexibility.  For example, multiple TNC operation at the main database is
        being added to the program to allow more data concentrators on multiple
        frequencies.  Database enhancements include substring searches and the ability
        to update a specific field for a specific record.  We encourage your comments
        and suggestions, and will strive to incorporate them in future releases.


                                  

      • Tyler Griffiths
        John, Could you possibly send along your .cfg files for both ARESDATA and BPQ32? Is there a cfg. file for BPQ1632? I m struggling. Thanx, Tyler N7WX ... --
        Message 3 of 19 , Nov 12, 2011
        • 0 Attachment
          John,
          Could you possibly send along your .cfg files for both ARESDATA and BPQ32?
          Is there a cfg. file for BPQ1632? I'm struggling.

          Thanx,
          Tyler N7WX

          On Tue, Nov 1, 2011 at 3:17 AM, John Wiseman <john.wiseman@...> wrote:
           

          I intalled ARESDATA into it's own folder, but you could install into your BPQ32 folder. You'd need to edit ARESDATA.CFG to suit.
           
           
          John


          From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of D R Mynatt
          Sent: 01 November 2011 01:09
          To: BPQ32@yahoogroups.com
          Subject: RE: [BPQ32] Running ARESDATA with BBPQ32

           

          Great stuff for sure.  If I understand correctly, we should just copy the exe into the BPQ subdir and execute. Right?
           
          Dave
          KA0SWT


          From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of WS7I
          Sent: Monday, October 31, 2011 7:02 PM
          To: BPQ32@yahoogroups.com
          Subject: Re: [BPQ32] Running ARESDATA with BBPQ32

          Maybe this would help.  From my working files  this stuff runs fine on old bpq under Win98 which is where I had/have it.  But we don't use it around here any longer.  Ran a lot of users up to 10 plus under DRSI and BPQ.
           
           
           
          Revised and reprinted from Proceedings of the Seventh ARRL Computer Networking
          Conference (ARRL, Newington, CT, 1988), pp. 141-144, by permission of the
          authors.


                                           ARES/Data:
                      A PACKET RADIO DATABASE FOR EMERGENCY COMMUNICATIONS

                                       W. E. Moerner, WN6I
                                        1003 Belder Drive
                                   San Jose, California  95120
                                          WN6I @ KB6OWT

                                        David Palmer, N6KL
                                         248 Omira Drive
                                   San Jose, California  95123
                                  N6KL @ KB6OWT, CIS: 73357,3157


                                           INTRODUCTION

          ARES/Data is a multiple connect, specialized bulletin board system tailored to
          store and retrieve basic information about people, places, or things during an
          emergency.  The program is a generalized form of the FINDER program (Family
          Information Database for Emergency Responders), written by David Palmer, N6KL
          and W.  E.  Moerner, WN6I [See FINDER:  The Family Information Database for
          Emergency Responders, Proceedings of the Sixth ARRL Computer Networking
          Conference, 1987, by W.  E.  Moerner, Sharon Moerner, and David Palmer].
          Although ARES/Data allows access to the database via packet radio, the program
          can also operate stand-alone without the need for packet radio hardware.  The
          actual operating mode is chosen by the system operator when the ARES/Data
          program is started.

          ARES/Data is a system designed for management of information during a
          widespread emergency that overloads normal communications channels.  The
          program is designed to be flexible, so that it can be used without change for
          both small and large disasters to organize information about victims, evacuees,
          or even ham radio operators.  Examples of situations in which ARES/Data could
          be used are:

           -  registration of individuals at Red Cross shelters
           -  patient/victim tracking in a multiple casualty incident
           -  maintaining staffing information about hams assigned to an emergency
           -  listings of road closures or damage reports
           -  logging reports from SKYWARN observers during periods of severe weather

          With alternate power sources and their own frequencies, Amateur Radio Emergency
          Service (ARES) operators can provide the ARES/Data service without tying up
          critical communications channels or relying on commercial power.


                                    ARES/Data SYSTEM OVERVIEW

          There are three major elements to the ARES/Data system:

           -  ARES/Data software and database
           -  Data Concentrators (remotely connected packet operators)
           -  Voice operators

          The central element of the ARES/Data system is the computer on which the
          ARES/Data program is running.  The ARES/Data program collects and collates
          current information about people or items in the system, according to the needs
          of the incident.  The program establishes and maintains the actual database on
          floppy disk or hard disk at this central computer.  In general, the operator at
          the computer keyboard can add new records to the database, delete incorrect
          records, perform searches for specific information, and generate database
          summaries.  The ARES/Data program will run on any IBM Personal Computer or
          IBM-compatible system running IBM DOS or MS/DOS with at least one floppy disk,
          although a hard disk increases the allowable size of the database and improves
          performance.  [IBM is a registered trademark of International Business Machines
          Corporation.]

          If remote access to the database is desired, addition of a serial port, TNC,
          and radio allows the central database computer to become the hub of a packet
          radio network in which up to eight remotely connected stations can
          simultaneously access the information in the ARES/Data database.  These packet
          radio stations, called "Data Concentrators," can update or query the shared
          database.  This data access occurs by exchanging updates or queries in a
          simple, precise, and well-defined format.

          Data Concentrators extend the coverage of the ARES/Data system.  They are the
          input/output ports of the ARES/Data database when remote access is needed.  The
          Data Concentrators can also act as local net controls for any participating
          voice operators within their range.  If voice operators are not needed, the
          packet operators interact with the public and/or disaster officials directly.

          The Voice Operators enter the ARES/Data system when the points of contact with
          those needing information are numerous and/or spread over a wide area.  These
          amateurs are also the public face of the ARES/Data system.  They can be the
          'reporters' live at the scene, sending status updates and requests to the Data
          Concentrators.  They also ensure delivery of responses to the persons making
          status requests.

          Emergency responders, their families, evacuees located at a particular shelter,
          and responsible agency officials access the ARES/Data system by contacting a
          participating amateur radio operator.


                     DESCRIPTION and OPERATION of the ARES/Data SYSTEM V. 0.1

                                      The ARES/Data Program

          The ARES/Data software was written by W. E. Moerner, WN6I, and David Palmer,
          N6KL.  It may be run in either of two modes:  stand-alone with no TNC support
          and no remote access, or by changing the configuration file, the program will
          control a TNC that allows multiple (simultaneous) remote connections.  If TNC
          support is chosen, the program requires a TNC with WA8DED firmware, because
          WA8DED host mode is used for communication between the computer and the TNC.
          WA8DED firmware is currently available for the TAPR TNC-1 and TNC-2 as well as
          the AEA PK-87.  We emphasize that NO REQUIREMENT IS PLACED ON THE OTHER TNC'S
          CONNECTED TO THE ARES/Data DATABASE MACHINE, except that they use AX.25
          link-layer protocol.  The ARES/Data program is written in Turbo Pascal Version
          4, and uses Turbo Database Toolbox for management and indexing of its B-plus
          structured tree.  [Turbo Pascal and Turbo Database Toolbox are trademarks of
          Borland International, Inc.] Briefly, ARES/Data may be regarded as a
          specialized multiple connect BBS with a specific command set tailored to the
          handling of STATUS INPUT information and SEARCH REQUESTS.

          The ARES/Data database is simply a collection of records.  Each record consists
          of four main items or "fields" plus a message item.  The information in the
          four main fields can be sorted or searched as required.  The rest of this
          section provides examples and a condensed user manual for the ARES/Data system.


                  General Rules for Current Information Input / Search Requests

          All basic commands can be entered either at the main ARES/Data keyboard or at
          any one of the remotely connected packet stations.  In addition, the operator
          at the main ARES/Data keyboard (the "sysop") has an additional set of commands
          that allow direct communication with the TNC, the printing of a log, backups,
          and disk report files.


                              Syntax for Current Information Input:

          To add a record to the database, the operator simply enters the four fields and
          any message, in order, with separators between the fields.  The only valid
          separator is the comma.  Within a field, leading and trailing blanks are
          ignored, but imbedded blanks ARE significant.  If no value is desired for a
          particular field, just skip the field by adding an extra comma.  The database
          will fill that field with ten blank characters.  For example,

              field1,field2,field3,field4,message<cr>

              (<cr> means carriage return)

          Fields 1 through 4

          The four fields are very general.  Each can have up to 20 characters, with
          imbedded blanks.  The meaning of each field is defined at the beginning of the
          event by the ARES officials, depending upon the nature of the event and what
          type of information needs to be tracked.  The sysop can issue a "labels"
          command that will give specific names to each of the four fields to help the
          operators remember the purpose of each field for a particular event.

          Message

          MESSAGE is an optional, free-form field that can be up to 80 characters in
          length.  It could contain a message, a phone number, an address, or other
          information deemed useful for the incident.

          Examples of Data Input with Sample Responses from ARES/Data

              85553195,joe,12,sj34<cr>
           response->   1040: data input accepted, #234.

              Johnson,Mary,93445,sj13, home 2333 Alsace Ln SJ 617-555-2368<cr>
           response->   2134: data input accepted, #114.

          All of the input information is stored in the database as a record of the
          status and location of a particular person at a particular time and date.  The
          time and date are added automatically by ARES/Data.  The number at the end of
          the response is the actual "record number" associated with the input
          information assigned by ARES/Data.  Further data input packets for the same
          person will also be saved in the database under a new record number.  The time
          and date identifies which information is most recent.


                                    Syntax for Search Requests

          The search commands instruct the database to look for ALL entries with the same
          value for field 1, 2, 3, or 4.  For example:

              /1,value<cr>                  Searches for "value" in field 1
              /2,value<cr>                  Searches for "value" in field 2
              /3,value<cr>                  Searches for "value" in field 3
              /4,value<cr>                  Searches for "value" in field 4

          (For convenience in typing, the character question mark "?" may be used instead
          of the diagonal bar "/"--both are treated identically).  A status report
          listing all information for each match in the field specified is sent back to
          the requesting packet station.  The first line gives the search value and the
          field number.  VALUE must exactly match what was originally typed in for the
          selected field, with leading and trailing blanks removed, and without regard
          for case.  At the end of the report, the line

              ARES/Data Search done at HHMM, nn hits.

          is sent, which signifies no more information coming, and that "nn" matches (or
          hits) were found in the database at time "HHMM".

          Examples of Search Requests:

              /1,5553195<cr>
              /2,w1aw<cr>
              /3,mercyhosp<cr>
              /4,85563<cr>

          Example Response from ARES/Data for the last case:

              Search for value "85563" in Field4
               Recno DT/Time: Field1,Field2,Field3,Field4,Msg
               29    13/1225: JOHNSON JOE,M35,SHELTER 1,85563, MISSING DOG AND CAT
               59    13/1257: DOE JANE,F23,SH05,85563, 2 CHILDREN
              ARES/Data search done at 1259, 2 hits.


                                   Syntax for Summary Requests

          A Summary command is provided that prints a breakdown of the number of
          like-named items for any particular field.  For example, if ARES/Data were
          being used to maintain a list of evacuees, and field 3 was designated for
          "shelter location", then the command "$3" would print a list of all distinct
          shelter names in use, and adjacent to each, the number of records (people) in
          the database at each shelter would be printed.

               $1<cr>                       Produces a summary on field 1
               $2<cr>                       Produces a summary on field 2
               $3<cr>                       Produces a summary on field 3
               $4<cr>                       Produces a summary on field 4

          Sample Output from a Summary Request:

               Database summary for Field3 at 1455 on 23
                  OAK GROVE            3
                  PIONEERHS            20
                  EASTVIEW             66
                  SHLTR5               37
               ARES/Data done at 1456, found 4 distinct values, entire DB has 153 records.


                        Listing Specific Entries (Records) in the Database

          Each record is automatically assigned a unique record number for identification
          purposes.

               l nnnnn<cr>                  lists record nnnnn


                      Deleting Specific Entries (Records) from the Database

          This function is always enabled at the sysop keyboard.  Its use by remotely
          connected packet stations is controlled initially by the configuration file
          during program startup.  Thereafter, the sysop can disable or enable this
          function as necessary.  Be extremely careful in using this command!  Always
          list the record first before deleting to be sure you have the right one.

               d nnnnn<cr>                  deletes record nnnnn


                                  Conference Bridge (Roundtable)

          This feature allows any connected station to send messages to other connected
          stations or to the sysop.  The conference bridge illustrates how the ARES/Data
          system operates as a hub-oriented network, with all transactions passing
          through the central database station.

          Users Command

          The users command in the form "users<cr>" or "u<cr>" returns a list of the
          callsigns of packet stations currently connected to ARES/Data.  The response is
          of the form:

               At WN6I-1:  N6KL  W6BB-3  AJ6T

          Tell Command

          The Tell command allows connected packet stations to use ARES/Data as a
          conference bridge, or roundtable.  The general format is:

               tell callsign message<cr>      or      t callsign message<cr>

          For example:

               tell w6bb-3 We have lots of people here at SJ12<cr>

          The message "We have lots of people here at SJ12" is sent to the connected
          station W6BB-3 prefaced by a time stamp and the call of the station originating
          the tell command.  In this case, if the tell command was sent by AJ6T, W6BB-3
          sees:

               1230  AJ6T> We have lots of people here at SJ12

          The special callsign "*" or "all" is used to send a message to all connected
          stations.  The special callsign "sysop" sends the message to the sysop at the
          ARES/Data database station.  It is not necessary to enter the entire callsign--
          just the suffix or some other substring will do.  In this case, the message is
          sent to any connected station whose callsign contains this substring.  This
          feature can be used to create multiple roundtables.  For example, packet
          stations located at, say, hospitals could adopt subªstation identifiers (SSIDs)
          of "-1", while those located at shelters could use SSIDs of "-2".  This way,
          broadcast messages of interest to either group can be easily sent without
          disrupting the other group.  For example:

               tell -1  Mercy Hospital has 12 beds available.<cr>

          This message would be sent to all stations that were part of the hospital net.


                 EXAMPLES OF HOW TO USE ARES/Data IN SPECIFIC DISASTER SCENARIOS

          -  In an evacuation of residents in a local area, the Red Cross often maintains
          health and welfare status information about evacuees.  In this case, the four
          fields and the comment field might be defined to be:

               Last Name - First Name, Shelter, Number in Family, Last phone, Next of kin

          -  In a multiple-casualty event where victim transportation needs to be
          tracked:

               Name, Sex/Age, Ambulance#, Hospital, Injuries

          -  In a ham radio staffing situation:

               Call, Name, Location, Shift, phone number for cancellation

          -  In a disaster situation where damage assessment and damage reports are
          needed:

               Coded type of damage, Location, Number of injuries, Callsign, comment

          There are many more possibilities, of course.  This is why the exact
          definitions of the various fields are not defined in advance.  In any given
          situation, more information than will fit into four fields and a comment field
          might be needed.  However, on today's 1200 baud packet radio networks, not much
          more information per record can be accommodated without restricting the total
          number of records that can be handled in a reasonable time.


                        HOW TO OBTAIN YOUR COPY OF THE ARES/Data PROGRAM

          The ARES/Data program, a relative of and successor to the FINDER program, is in
          the public domain.  The current version is 0.1, which operates as described in
          this paper.  A copy of the program along with the documentation is available
          for non-commercial, non-profit use from WN6I or N6KL by sending a blank,
          formatted 5 1/4" (360 kB) or 3 1/2" (720 kB) floppy in a mailer with return
          postage stamps.  The cost to you is the cost of the diskette and postage.  No
          other compensation can or will be accepted - please do not send money.  We have
          included a configuration file facility so that you can tailor many parameters
          to your specific system.


                                        FUTURE DIRECTIONS

          The ARES/Data program is continuously being updated to add additional function
          and flexibility.  For example, multiple TNC operation at the main database is
          being added to the program to allow more data concentrators on multiple
          frequencies.  Database enhancements include substring searches and the ability
          to update a specific field for a specific record.  We encourage your comments
          and suggestions, and will strive to incorporate them in future releases.


                                    




          --
          Tyler Griffiths
          N7UWX

          See where I am:
          http://map.findu.com/n7uwx-12
        • John Wiseman
          Tyler, I’ve uploaded a zipped copy of my ARESDATA installation to “ARES Configured for BPQ32.zip” in the files section this group.. I had it installed in
          Message 4 of 19 , Nov 12, 2011
          • 0 Attachment

            Tyler,

             

            I’ve uploaded a zipped copy of my ARESDATA installation to “ARES Configured for BPQ32.zip” in the files section this group.. I had it installed in the root of the C: drive, but it is configured with relative paths, so you should be able to unzip it anywhere. Just make sure you preserve the directory structure.

             

            There isn’t any configuration for bpq1632 – just make sure you copy the bpq1632.dll from the bpq1632.zip in the files section of this group to your SYSTEM32 folder. The version in the current release is out of date.

             

            Start ARESDATA using the “Start ARESDATA” shortcut.

             

            There is no special configuration needed for bpq32 – just add an APPLICATION line for ARES to your bpq32.cfg. Something like:

             

            APPLICATION 1,ARES,,MYCALL-1,ARES,0

             

            73,

            John

             

             


            From: BPQ32@yahoogroups.com [mailto: BPQ32@yahoogroups.com ] On Behalf Of Tyler Griffiths
            Sent: 12 November 2011 20:01
            To: BPQ32@yahoogroups.com
            Subject: Re: [BPQ32] Running ARESDATA with BBPQ32

             

             

            John,

            Could you possibly send along your .cfg files for both ARESDATA and BPQ32?

            Is there a cfg. file for BPQ1632? I'm struggling.

             

            Thanx,

            Tyler N7WX

            On Tue, Nov 1, 2011 at 3:17 AM, John Wiseman <john.wiseman@...> wrote:

             

            I intalled ARESDATA into it's own folder, but you could install into your BPQ32 folder. You'd need to edit ARESDATA.CFG to suit.

             

             

            John

             


            From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of D R Mynatt
            Sent: 01 November 2011 01:09
            To: BPQ32@yahoogroups.com
            Subject: RE: [BPQ32] Running ARESDATA with BBPQ32

             

            Great stuff for sure.  If I understand correctly, we should just copy the exe into the BPQ subdir and execute. Right?

             

            Dave

            KA0SWT

             


            From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of WS7I
            Sent: Monday, October 31, 2011 7:02 PM
            To: BPQ32@yahoogroups.com
            Subject: Re: [BPQ32] Running ARESDATA with BBPQ32

            Maybe this would help.  From my working files  this stuff runs fine on old bpq under Win98 which is where I had/have it.  But we don't use it around here any longer.  Ran a lot of users up to 10 plus under DRSI and BPQ.

             

             

             

            Revised and reprinted from Proceedings of the Seventh ARRL Computer Networking
            Conference (ARRL, Newington, CT, 1988), pp. 141-144, by permission of the
            authors.


                                             ARES/Data:
                        A PACKET RADIO DATABASE FOR EMERGENCY COMMUNICATIONS

                                         W. E. Moerner, WN6I
                                          1003 Belder Drive
                                     San Jose , California   95120
                                            WN6I @ KB6OWT

                                          David Palmer, N6KL
                                           248 Omira Drive
                                     San Jose , California   95123
                                    N6KL @ KB6OWT, CIS: 73357,3157


                                             INTRODUCTION

            ARES/Data is a multiple connect, specialized bulletin board system tailored to
            store and retrieve basic information about people, places, or things during an
            emergency.  The program is a generalized form of the FINDER program (Family
            Information Database for Emergency Responders), written by David Palmer, N6KL
            and W.  E.  Moerner, WN6I [See FINDER:  The Family Information Database for
            Emergency Responders, Proceedings of the Sixth ARRL Computer Networking
            Conference, 1987, by W.  E.  Moerner, Sharon Moerner, and David Palmer].
            Although ARES/Data allows access to the database via packet radio, the program
            can also operate stand-alone without the need for packet radio hardware.  The
            actual operating mode is chosen by the system operator when the ARES/Data
            program is started.

            ARES/Data is a system designed for management of information during a
            widespread emergency that overloads normal communications channels.  The
            program is designed to be flexible, so that it can be used without change for
            both small and large disasters to organize information about victims, evacuees,
            or even ham radio operators.  Examples of situations in which ARES/Data could
            be used are:

             -  registration of individuals at Red Cross shelters
             -  patient/victim tracking in a multiple casualty incident
             -  maintaining staffing information about hams assigned to an emergency
             -  listings of road closures or damage reports
             -  logging reports from SKYWARN observers during periods of severe weather

            With alternate power sources and their own frequencies, Amateur Radio Emergency
            Service (ARES) operators can provide the ARES/Data service without tying up
            critical communications channels or relying on commercial power.


                                      ARES/Data SYSTEM OVERVIEW

            There are three major elements to the ARES/Data system:

             -  ARES/Data software and database
             -  Data Concentrators (remotely connected packet operators)
             -  Voice operators

            The central element of the ARES/Data system is the computer on which the
            ARES/Data program is running.  The ARES/Data program collects and collates
            current information about people or items in the system, according to the needs
            of the incident.  The program establishes and maintains the actual database on
            floppy disk or hard disk at this central computer.  In general, the operator at
            the computer keyboard can add new records to the database, delete incorrect
            records, perform searches for specific information, and generate database
            summaries.  The ARES/Data program will run on any IBM Personal Computer or
            IBM-compatible system running IBM DOS or MS/DOS with at least one floppy disk,
            although a hard disk increases the allowable size of the database and improves
            performance.  [IBM is a registered trademark of International Business Machines
            Corporation.]

            If remote access to the database is desired, addition of a serial port, TNC,
            and radio allows the central database computer to become the hub of a packet
            radio network in which up to eight remotely connected stations can
            simultaneously access the information in the ARES/Data database.  These packet
            radio stations, called "Data Concentrators," can update or query the shared
            database.  This data access occurs by exchanging updates or queries in a
            simple, precise, and well-defined format.

            Data Concentrators extend the coverage of the ARES/Data system.  They are the
            input/output ports of the ARES/Data database when remote access is needed.  The
            Data Concentrators can also act as local net controls for any participating
            voice operators within their range.  If voice operators are not needed, the
            packet operators interact with the public and/or disaster officials directly.

            The Voice Operators enter the ARES/Data system when the points of contact with
            those needing information are numerous and/or spread over a wide area.  These
            amateurs are also the public face of the ARES/Data system.  They can be the
            'reporters' live at the scene, sending status updates and requests to the Data
            Concentrators.  They also ensure delivery of responses to the persons making
            status requests.

            Emergency responders, their families, evacuees located at a particular shelter,
            and responsible agency officials access the ARES/Data system by contacting a
            participating amateur radio operator.


                       DESCRIPTION and OPERATION of the ARES/Data SYSTEM V. 0.1

                                        The ARES/Data Program

            The ARES/Data software was written by W. E. Moerner, WN6I, and David Palmer,
            N6KL.  It may be run in either of two modes:  stand-alone with no TNC support
            and no remote access, or by changing the configuration file, the program will
            control a TNC that allows multiple (simultaneous) remote connections.  If TNC
            support is chosen, the program requires a TNC with WA8DED firmware, because
            WA8DED host mode is used for communication between the computer and the TNC.
            WA8DED firmware is currently available for the TAPR TNC-1 and TNC-2 as well as
            the AEA PK-87.  We emphasize that NO REQUIREMENT IS PLACED ON THE OTHER TNC'S
            CONNECTED TO THE ARES/Data DATABASE MACHINE, except that they use AX.25
            link-layer protocol.  The ARES/Data program is written in Turbo Pascal Version
            4, and uses Turbo Database Toolbox for management and indexing of its B-plus
            structured tree.  [Turbo Pascal and Turbo Database Toolbox are trademarks of
            Borland International, Inc.] Briefly, ARES/Data may be regarded as a
            specialized multiple connect BBS with a specific command set tailored to the
            handling of STATUS INPUT information and SEARCH REQUESTS.

            The ARES/Data database is simply a collection of records.  Each record consists
            of four main items or "fields" plus a message item.  The information in the
            four main fields can be sorted or searched as required.  The rest of this
            section provides examples and a condensed user manual for the ARES/Data system.


                    General Rules for Current Information Input / Search Requests

            All basic commands can be entered either at the main ARES/Data keyboard or at
            any one of the remotely connected packet stations.  In addition, the operator
            at the main ARES/Data keyboard (the "sysop") has an additional set of commands
            that allow direct communication with the TNC, the printing of a log, backups,
            and disk report files.


                                Syntax for Current Information Input:

            To add a record to the database, the operator simply enters the four fields and
            any message, in order, with separators between the fields.  The only valid
            separator is the comma.  Within a field, leading and trailing blanks are
            ignored, but imbedded blanks ARE significant.  If no value is desired for a
            particular field, just skip the field by adding an extra comma.  The database
            will fill that field with ten blank characters.  For example,

                field1,field2,field3,field4,message<cr>

                (<cr> means carriage return)

            Fields 1 through 4

            The four fields are very general.  Each can have up to 20 characters, with
            imbedded blanks.  The meaning of each field is defined at the beginning of the
            event by the ARES officials, depending upon the nature of the event and what
            type of information needs to be tracked.  The sysop can issue a "labels"
            command that will give specific names to each of the four fields to help the
            operators remember the purpose of each field for a particular event.

            Message

            MESSAGE is an optional, free-form field that can be up to 80 characters in
            length.  It could contain a message, a phone number, an address, or other
            information deemed useful for the incident.

            Examples of Data Input with Sample Responses from ARES/Data

                85553195,joe,12,sj34<cr>
             response->   1040: data input accepted, #234.

                Johnson,Mary,93445,sj13, home 2333 Alsace Ln SJ 617-555-2368<cr>
             response->   2134: data input accepted, #114.

            All of the input information is stored in the database as a record of the
            status and location of a particular person at a particular time and date.  The
            time and date are added automatically by ARES/Data.  The number at the end of
            the response is the actual "record number" associated with the input
            information assigned by ARES/Data.  Further data input packets for the same
            person will also be saved in the database under a new record number.  The time
            and date identifies which information is most recent.


                                      Syntax for Search Requests

            The search commands instruct the database to look for ALL entries with the same
            value for field 1, 2, 3, or 4.  For example:

                /1,value<cr>                  Searches for "value" in field 1
                /2,value<cr>                  Searches for "value" in field 2
                /3,value<cr>                  Searches for "value" in field 3
                /4,value<cr>                  Searches for "value" in field 4

            (For convenience in typing, the character question mark "?" may be used instead
            of the diagonal bar "/"--both are treated identically).  A status report
            listing all information for each match in the field specified is sent back to
            the requesting packet station.  The first line gives the search value and the
            field number.  VALUE must exactly match what was originally typed in for the
            selected field, with leading and trailing blanks removed, and without regard
            for case.  At the end of the report, the line

                ARES/Data Search done at HHMM, nn hits.

            is sent, which signifies no more information coming, and that "nn" matches (or
            hits) were found in the database at time "HHMM".

            Examples of Search Requests:

                /1,5553195<cr>
                /2,w1aw<cr>
                /3,mercyhosp<cr>
                /4,85563<cr>

            Example Response from ARES/Data for the last case:

                Search for value "85563" in Field4
                 Recno DT/Time: Field1,Field2,Field3,Field4,Msg
                 29    13/1225: JOHNSON JOE,M35,SHELTER 1,85563, MISSING DOG AND CAT
                 59    13/1257: DOE JANE,F23,SH05,85563, 2 CHILDREN
                ARES/Data search done at 1259, 2 hits.


                                     Syntax for Summary Requests

            A Summary command is provided that prints a breakdown of the number of
            like-named items for any particular field.  For example, if ARES/Data were
            being used to maintain a list of evacuees, and field 3 was designated for
            "shelter location", then the command "$3" would print a list of all distinct
            shelter names in use, and adjacent to each, the number of records (people) in
            the database at each shelter would be printed.

                 $1<cr>                       Produces a summary on field 1
                 $2<cr>                       Produces a summary on field 2
                 $3<cr>                       Produces a summary on field 3
                 $4<cr>                       Produces a summary on field 4

            Sample Output from a Summary Request:

                 Database summary for Field3 at 1455 on 23
                    OAK GROVE            3
                    PIONEERHS            20
                    EASTVIEW             66
                    SHLTR5               37
                 ARES/Data done at 1456, found 4 distinct values, entire DB has 153 records.


                          Listing Specific Entries (Records) in the Database

            Each record is automatically assigned a unique record number for identification
            purposes.

                 l nnnnn<cr>                  lists record nnnnn


                        Deleting Specific Entries (Records) from the Database

            This function is always enabled at the sysop keyboard.  Its use by remotely
            connected packet stations is controlled initially by the configuration file
            during program startup.  Thereafter, the sysop can disable or enable this
            function as necessary.  Be extremely careful in using this command!  Always
            list the record first before deleting to be sure you have the right one.

                 d nnnnn<cr>                  deletes record nnnnn


                                    Conference Bridge (Roundtable)

            This feature allows any connected station to send messages to other connected
            stations or to the sysop.  The conference bridge illustrates how the ARES/Data
            system operates as a hub-oriented network, with all transactions passing
            through the central database station.

            Users Command

            The users command in the form "users<cr>" or "u<cr>" returns a list of the
            callsigns of packet stations currently connected to ARES/Data.  The response is
            of the form:

                 At WN6I-1:  N6KL  W6BB-3  AJ6T

            Tell Command

            The Tell command allows connected packet stations to use ARES/Data as a
            conference bridge, or roundtable.  The general format is:

                 tell callsign message<cr>      or      t callsign message<cr>

            For example:

                 tell w6bb-3 We have lots of people here at SJ12<cr>

            The message "We have lots of people here at SJ12" is sent to the connected
            station W6BB-3 prefaced by a time stamp and the call of the station originating
            the tell command.  In this case, if the tell command was sent by AJ6T, W6BB-3
            sees:

                 1230  AJ6T> We have lots of people here at SJ12

            The special callsign "*" or "all" is used to send a message to all connected
            stations.  The special callsign "sysop" sends the message to the sysop at the
            ARES/Data database station.  It is not necessary to enter the entire callsign--
            just the suffix or some other substring will do.  In this case, the message is
            sent to any connected station whose callsign contains this substring.  This
            feature can be used to create multiple roundtables.  For example, packet
            stations located at, say, hospitals could adopt subªstation identifiers (SSIDs)
            of "-1", while those located at shelters could use SSIDs of "-2".  This way,
            broadcast messages of interest to either group can be easily sent without
            disrupting the other group.  For example:

                 tell -1  Mercy Hospital has 12 beds available.<cr>

            This message would be sent to all stations that were part of the hospital net.


                   EXAMPLES OF HOW TO USE ARES/Data IN SPECIFIC DISASTER SCENARIOS

            -  In an evacuation of residents in a local area, the Red Cross often maintains
            health and welfare status information about evacuees.  In this case, the four
            fields and the comment field might be defined to be:

                 Last Name - First Name, Shelter, Number in Family, Last phone, Next of kin

            -  In a multiple-casualty event where victim transportation needs to be
            tracked:

                 Name, Sex/Age, Ambulance#, Hospital, Injuries

            -  In a ham radio staffing situation:

                 Call, Name, Location, Shift, phone number for cancellation

            -  In a disaster situation where damage assessment and damage reports are
            needed:

                 Coded type of damage, Location, Number of injuries, Callsign, comment

            There are many more possibilities, of course.  This is why the exact
            definitions of the various fields are not defined in advance.  In any given
            situation, more information than will fit into four fields and a comment field
            might be needed.  However, on today's 1200 baud packet radio networks, not much
            more information per record can be accommodated without restricting the total
            number of records that can be handled in a reasonable time.


                          HOW TO OBTAIN YOUR COPY OF THE ARES/Data PROGRAM

            The ARES/Data program, a relative of and successor to the FINDER program, is in
            the public domain.  The current version is 0.1, which operates as described in
            this paper.  A copy of the program along with the documentation is available
            for non-commercial, non-profit use from WN6I or N6KL by sending a blank,
            formatted 5 1/4" (360 kB) or 3 1/2" (720 kB) floppy in a mailer with return
            postage stamps.  The cost to you is the cost of the diskette and postage.  No
            other compensation can or will be accepted - please do not send money.  We have
            included a configuration file facility so that you can tailor many parameters
            to your specific system.


                                          FUTURE DIRECTIONS

            The ARES/Data program is continuously being updated to add additional function
            and flexibility.  For example, multiple TNC operation at the main database is
            being added to the program to allow more data concentrators on multiple
            frequencies.  Database enhancements include substring searches and the ability
            to update a specific field for a specific record.  We encourage your comments
            and suggestions, and will strive to incorporate them in future releases.


                                      



             

            --
            Tyler Griffiths
            N7UWX

            See where I am:
            http://map.findu.com/n7uwx-12

          • Tyler Griffiths
            Works great except it is not connecting to the TNC. TNC is a KPC-3 running on comm 2. Thanx! Tyler ... -- Tyler Griffiths N7UWX See where I am:
            Message 5 of 19 , Nov 12, 2011
            • 0 Attachment
              Works great except it is not connecting to the TNC. TNC is a KPC-3 running on comm 2.

              Thanx!
              Tyler

              On Sat, Nov 12, 2011 at 3:00 PM, John Wiseman <john.wiseman@...> wrote:
               

              Tyler,

               

              I’ve uploaded a zipped copy of my ARESDATA installation to “ARES Configured for BPQ32.zip” in the files section this group.. I had it installed in the root of the C: drive, but it is configured with relative paths, so you should be able to unzip it anywhere. Just make sure you preserve the directory structure.

               

              There isn’t any configuration for bpq1632 – just make sure you copy the bpq1632.dll from the bpq1632.zip in the files section of this group to your SYSTEM32 folder. The version in the current release is out of date.

               

              Start ARESDATA using the “Start ARESDATA” shortcut.

               

              There is no special configuration needed for bpq32 – just add an APPLICATION line for ARES to your bpq32.cfg. Something like:

               

              APPLICATION 1,ARES,,MYCALL-1,ARES,0

               

              73,

              John

               

               


              From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of Tyler Griffiths
              Sent: 12 November 2011 20:01


              To: BPQ32@yahoogroups.com
              Subject: Re: [BPQ32] Running ARESDATA with BBPQ32

               

               

              John,

              Could you possibly send along your .cfg files for both ARESDATA and BPQ32?

              Is there a cfg. file for BPQ1632? I'm struggling.

               

              Thanx,

              Tyler N7WX

              On Tue, Nov 1, 2011 at 3:17 AM, John Wiseman <john.wiseman@...> wrote:

               

              I intalled ARESDATA into it's own folder, but you could install into your BPQ32 folder. You'd need to edit ARESDATA.CFG to suit.

               

               

              John

               


              From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of D R Mynatt
              Sent: 01 November 2011 01:09
              To: BPQ32@yahoogroups.com
              Subject: RE: [BPQ32] Running ARESDATA with BBPQ32

               

              Great stuff for sure.  If I understand correctly, we should just copy the exe into the BPQ subdir and execute. Right?

               

              Dave

              KA0SWT

               


              From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of WS7I
              Sent: Monday, October 31, 2011 7:02 PM
              To: BPQ32@yahoogroups.com
              Subject: Re: [BPQ32] Running ARESDATA with BBPQ32

              Maybe this would help.  From my working files  this stuff runs fine on old bpq under Win98 which is where I had/have it.  But we don't use it around here any longer.  Ran a lot of users up to 10 plus under DRSI and BPQ.

               

               

               

              Revised and reprinted from Proceedings of the Seventh ARRL Computer Networking
              Conference (ARRL, Newington, CT, 1988), pp. 141-144, by permission of the
              authors.


                                               ARES/Data:
                          A PACKET RADIO DATABASE FOR EMERGENCY COMMUNICATIONS

                                           W. E. Moerner, WN6I
                                            1003 Belder Drive
                                       San Jose, California  95120
                                              WN6I @ KB6OWT

                                            David Palmer, N6KL
                                             248 Omira Drive
                                       San Jose, California  95123
                                      N6KL @ KB6OWT, CIS: 73357,3157


                                               INTRODUCTION

              ARES/Data is a multiple connect, specialized bulletin board system tailored to
              store and retrieve basic information about people, places, or things during an
              emergency.  The program is a generalized form of the FINDER program (Family
              Information Database for Emergency Responders), written by David Palmer, N6KL
              and W.  E.  Moerner, WN6I [See FINDER:  The Family Information Database for
              Emergency Responders, Proceedings of the Sixth ARRL Computer Networking
              Conference, 1987, by W.  E.  Moerner, Sharon Moerner, and David Palmer].
              Although ARES/Data allows access to the database via packet radio, the program
              can also operate stand-alone without the need for packet radio hardware.  The
              actual operating mode is chosen by the system operator when the ARES/Data
              program is started.

              ARES/Data is a system designed for management of information during a
              widespread emergency that overloads normal communications channels.  The
              program is designed to be flexible, so that it can be used without change for
              both small and large disasters to organize information about victims, evacuees,
              or even ham radio operators.  Examples of situations in which ARES/Data could
              be used are:

               -  registration of individuals at Red Cross shelters
               -  patient/victim tracking in a multiple casualty incident
               -  maintaining staffing information about hams assigned to an emergency
               -  listings of road closures or damage reports
               -  logging reports from SKYWARN observers during periods of severe weather

              With alternate power sources and their own frequencies, Amateur Radio Emergency
              Service (ARES) operators can provide the ARES/Data service without tying up
              critical communications channels or relying on commercial power.


                                        ARES/Data SYSTEM OVERVIEW

              There are three major elements to the ARES/Data system:

               -  ARES/Data software and database
               -  Data Concentrators (remotely connected packet operators)
               -  Voice operators

              The central element of the ARES/Data system is the computer on which the
              ARES/Data program is running.  The ARES/Data program collects and collates
              current information about people or items in the system, according to the needs
              of the incident.  The program establishes and maintains the actual database on
              floppy disk or hard disk at this central computer.  In general, the operator at
              the computer keyboard can add new records to the database, delete incorrect
              records, perform searches for specific information, and generate database
              summaries.  The ARES/Data program will run on any IBM Personal Computer or
              IBM-compatible system running IBM DOS or MS/DOS with at least one floppy disk,
              although a hard disk increases the allowable size of the database and improves
              performance.  [IBM is a registered trademark of International Business Machines
              Corporation.]

              If remote access to the database is desired, addition of a serial port, TNC,
              and radio allows the central database computer to become the hub of a packet
              radio network in which up to eight remotely connected stations can
              simultaneously access the information in the ARES/Data database.  These packet
              radio stations, called "Data Concentrators," can update or query the shared
              database.  This data access occurs by exchanging updates or queries in a
              simple, precise, and well-defined format.

              Data Concentrators extend the coverage of the ARES/Data system.  They are the
              input/output ports of the ARES/Data database when remote access is needed.  The
              Data Concentrators can also act as local net controls for any participating
              voice operators within their range.  If voice operators are not needed, the
              packet operators interact with the public and/or disaster officials directly.

              The Voice Operators enter the ARES/Data system when the points of contact with
              those needing information are numerous and/or spread over a wide area.  These
              amateurs are also the public face of the ARES/Data system.  They can be the
              'reporters' live at the scene, sending status updates and requests to the Data
              Concentrators.  They also ensure delivery of responses to the persons making
              status requests.

              Emergency responders, their families, evacuees located at a particular shelter,
              and responsible agency officials access the ARES/Data system by contacting a
              participating amateur radio operator.


                         DESCRIPTION and OPERATION of the ARES/Data SYSTEM V. 0.1

                                          The ARES/Data Program

              The ARES/Data software was written by W. E. Moerner, WN6I, and David Palmer,
              N6KL.  It may be run in either of two modes:  stand-alone with no TNC support
              and no remote access, or by changing the configuration file, the program will
              control a TNC that allows multiple (simultaneous) remote connections.  If TNC
              support is chosen, the program requires a TNC with WA8DED firmware, because
              WA8DED host mode is used for communication between the computer and the TNC.
              WA8DED firmware is currently available for the TAPR TNC-1 and TNC-2 as well as
              the AEA PK-87.  We emphasize that NO REQUIREMENT IS PLACED ON THE OTHER TNC'S
              CONNECTED TO THE ARES/Data DATABASE MACHINE, except that they use AX.25
              link-layer protocol.  The ARES/Data program is written in Turbo Pascal Version
              4, and uses Turbo Database Toolbox for management and indexing of its B-plus
              structured tree.  [Turbo Pascal and Turbo Database Toolbox are trademarks of
              Borland International, Inc.] Briefly, ARES/Data may be regarded as a
              specialized multiple connect BBS with a specific command set tailored to the
              handling of STATUS INPUT information and SEARCH REQUESTS.

              The ARES/Data database is simply a collection of records.  Each record consists
              of four main items or "fields" plus a message item.  The information in the
              four main fields can be sorted or searched as required.  The rest of this
              section provides examples and a condensed user manual for the ARES/Data system.


                      General Rules for Current Information Input / Search Requests

              All basic commands can be entered either at the main ARES/Data keyboard or at
              any one of the remotely connected packet stations.  In addition, the operator
              at the main ARES/Data keyboard (the "sysop") has an additional set of commands
              that allow direct communication with the TNC, the printing of a log, backups,
              and disk report files.


                                  Syntax for Current Information Input:

              To add a record to the database, the operator simply enters the four fields and
              any message, in order, with separators between the fields.  The only valid
              separator is the comma.  Within a field, leading and trailing blanks are
              ignored, but imbedded blanks ARE significant.  If no value is desired for a
              particular field, just skip the field by adding an extra comma.  The database
              will fill that field with ten blank characters.  For example,

                  field1,field2,field3,field4,message<cr>

                  (<cr> means carriage return)

              Fields 1 through 4

              The four fields are very general.  Each can have up to 20 characters, with
              imbedded blanks.  The meaning of each field is defined at the beginning of the
              event by the ARES officials, depending upon the nature of the event and what
              type of information needs to be tracked.  The sysop can issue a "labels"
              command that will give specific names to each of the four fields to help the
              operators remember the purpose of each field for a particular event.

              Message

              MESSAGE is an optional, free-form field that can be up to 80 characters in
              length.  It could contain a message, a phone number, an address, or other
              information deemed useful for the incident.

              Examples of Data Input with Sample Responses from ARES/Data

                  85553195,joe,12,sj34<cr>
               response->   1040: data input accepted, #234.

                  Johnson,Mary,93445,sj13, home 2333 Alsace Ln SJ 617-555-2368<cr>
               response->   2134: data input accepted, #114.

              All of the input information is stored in the database as a record of the
              status and location of a particular person at a particular time and date.  The
              time and date are added automatically by ARES/Data.  The number at the end of
              the response is the actual "record number" associated with the input
              information assigned by ARES/Data.  Further data input packets for the same
              person will also be saved in the database under a new record number.  The time
              and date identifies which information is most recent.


                                        Syntax for Search Requests

              The search commands instruct the database to look for ALL entries with the same
              value for field 1, 2, 3, or 4.  For example:

                  /1,value<cr>                  Searches for "value" in field 1
                  /2,value<cr>                  Searches for "value" in field 2
                  /3,value<cr>                  Searches for "value" in field 3
                  /4,value<cr>                  Searches for "value" in field 4

              (For convenience in typing, the character question mark "?" may be used instead
              of the diagonal bar "/"--both are treated identically).  A status report
              listing all information for each match in the field specified is sent back to
              the requesting packet station.  The first line gives the search value and the
              field number.  VALUE must exactly match what was originally typed in for the
              selected field, with leading and trailing blanks removed, and without regard
              for case.  At the end of the report, the line

                  ARES/Data Search done at HHMM, nn hits.

              is sent, which signifies no more information coming, and that "nn" matches (or
              hits) were found in the database at time "HHMM".

              Examples of Search Requests:

                  /1,5553195<cr>
                  /2,w1aw<cr>
                  /3,mercyhosp<cr>
                  /4,85563<cr>

              Example Response from ARES/Data for the last case:

                  Search for value "85563" in Field4
                   Recno DT/Time: Field1,Field2,Field3,Field4,Msg
                   29    13/1225: JOHNSON JOE,M35,SHELTER 1,85563, MISSING DOG AND CAT
                   59    13/1257: DOE JANE,F23,SH05,85563, 2 CHILDREN
                  ARES/Data search done at 1259, 2 hits.


                                       Syntax for Summary Requests

              A Summary command is provided that prints a breakdown of the number of
              like-named items for any particular field.  For example, if ARES/Data were
              being used to maintain a list of evacuees, and field 3 was designated for
              "shelter location", then the command "$3" would print a list of all distinct
              shelter names in use, and adjacent to each, the number of records (people) in
              the database at each shelter would be printed.

                   $1<cr>                       Produces a summary on field 1
                   $2<cr>                       Produces a summary on field 2
                   $3<cr>                       Produces a summary on field 3
                   $4<cr>                       Produces a summary on field 4

              Sample Output from a Summary Request:

                   Database summary for Field3 at 1455 on 23
                      OAK GROVE            3
                      PIONEERHS            20
                      EASTVIEW             66
                      SHLTR5               37
                   ARES/Data done at 1456, found 4 distinct values, entire DB has 153 records.


                            Listing Specific Entries (Records) in the Database

              Each record is automatically assigned a unique record number for identification
              purposes.

                   l nnnnn<cr>                  lists record nnnnn


                          Deleting Specific Entries (Records) from the Database

              This function is always enabled at the sysop keyboard.  Its use by remotely
              connected packet stations is controlled initially by the configuration file
              during program startup.  Thereafter, the sysop can disable or enable this
              function as necessary.  Be extremely careful in using this command!  Always
              list the record first before deleting to be sure you have the right one.

                   d nnnnn<cr>                  deletes record nnnnn


                                      Conference Bridge (Roundtable)

              This feature allows any connected station to send messages to other connected
              stations or to the sysop.  The conference bridge illustrates how the ARES/Data
              system operates as a hub-oriented network, with all transactions passing
              through the central database station.

              Users Command

              The users command in the form "users<cr>" or "u<cr>" returns a list of the
              callsigns of packet stations currently connected to ARES/Data.  The response is
              of the form:

                   At WN6I-1:  N6KL  W6BB-3  AJ6T

              Tell Command

              The Tell command allows connected packet stations to use ARES/Data as a
              conference bridge, or roundtable.  The general format is:

                   tell callsign message<cr>      or      t callsign message<cr>

              For example:

                   tell w6bb-3 We have lots of people here at SJ12<cr>

              The message "We have lots of people here at SJ12" is sent to the connected
              station W6BB-3 prefaced by a time stamp and the call of the station originating
              the tell command.  In this case, if the tell command was sent by AJ6T, W6BB-3
              sees:

                   1230  AJ6T> We have lots of people here at SJ12

              The special callsign "*" or "all" is used to send a message to all connected
              stations.  The special callsign "sysop" sends the message to the sysop at the
              ARES/Data database station.  It is not necessary to enter the entire callsign--
              just the suffix or some other substring will do.  In this case, the message is
              sent to any connected station whose callsign contains this substring.  This
              feature can be used to create multiple roundtables.  For example, packet
              stations located at, say, hospitals could adopt subªstation identifiers (SSIDs)
              of "-1", while those located at shelters could use SSIDs of "-2".  This way,
              broadcast messages of interest to either group can be easily sent without
              disrupting the other group.  For example:

                   tell -1  Mercy Hospital has 12 beds available.<cr>

              This message would be sent to all stations that were part of the hospital net.


                     EXAMPLES OF HOW TO USE ARES/Data IN SPECIFIC DISASTER SCENARIOS

              -  In an evacuation of residents in a local area, the Red Cross often maintains
              health and welfare status information about evacuees.  In this case, the four
              fields and the comment field might be defined to be:

                   Last Name - First Name, Shelter, Number in Family, Last phone, Next of kin

              -  In a multiple-casualty event where victim transportation needs to be
              tracked:

                   Name, Sex/Age, Ambulance#, Hospital, Injuries

              -  In a ham radio staffing situation:

                   Call, Name, Location, Shift, phone number for cancellation

              -  In a disaster situation where damage assessment and damage reports are
              needed:

                   Coded type of damage, Location, Number of injuries, Callsign, comment

              There are many more possibilities, of course.  This is why the exact
              definitions of the various fields are not defined in advance.  In any given
              situation, more information than will fit into four fields and a comment field
              might be needed.  However, on today's 1200 baud packet radio networks, not much
              more information per record can be accommodated without restricting the total
              number of records that can be handled in a reasonable time.


                            HOW TO OBTAIN YOUR COPY OF THE ARES/Data PROGRAM

              The ARES/Data program, a relative of and successor to the FINDER program, is in
              the public domain.  The current version is 0.1, which operates as described in
              this paper.  A copy of the program along with the documentation is available
              for non-commercial, non-profit use from WN6I or N6KL by sending a blank,
              formatted 5 1/4" (360 kB) or 3 1/2" (720 kB) floppy in a mailer with return
              postage stamps.  The cost to you is the cost of the diskette and postage.  No
              other compensation can or will be accepted - please do not send money.  We have
              included a configuration file facility so that you can tailor many parameters
              to your specific system.


                                            FUTURE DIRECTIONS

              The ARES/Data program is continuously being updated to add additional function
              and flexibility.  For example, multiple TNC operation at the main database is
              being added to the program to allow more data concentrators on multiple
              frequencies.  Database enhancements include substring searches and the ability
              to update a specific field for a specific record.  We encourage your comments
              and suggestions, and will strive to incorporate them in future releases.


                                        



               

              --

              Tyler Griffiths
              N7UWX

              See where I am:
              http://map.findu.com/n7uwx-12




              --
              Tyler Griffiths
              N7UWX

              See where I am:
              http://map.findu.com/n7uwx-12
            • John Wiseman
              Tyler, The TNC must be placed into KISS mode before starting bpq32. If that isn’t the problem, send me your bpq32.cfg off list and I’ll check it. 73, John
              Message 6 of 19 , Nov 13, 2011
              • 0 Attachment

                Tyler,

                 

                The TNC must be placed into KISS mode before starting bpq32. If that isn’t the problem, send me your bpq32.cfg off list and I’ll check it.

                 

                73,

                John

                 

                 


                From: BPQ32@yahoogroups.com [mailto: BPQ32@yahoogroups.com ] On Behalf Of Tyler Griffiths
                Sent: 13 November 2011 02:30
                To: BPQ32@yahoogroups.com
                Subject: Re: [BPQ32] Running ARESDATA with BBPQ32

                 

                 

                Works great except it is not connecting to the TNC. TNC is a KPC-3 running on comm 2.

                 

                Thanx!

                Tyler

                On Sat, Nov 12, 2011 at 3:00 PM, John Wiseman <john.wiseman@...> wrote:

                 

                Tyler,

                 

                I’ve uploaded a zipped copy of my ARESDATA installation to “ARES Configured for BPQ32.zip” in the files section this group.. I had it installed in the root of the C: drive, but it is configured with relative paths, so you should be able to unzip it anywhere. Just make sure you preserve the directory structure.

                 

                There isn’t any configuration for bpq1632 – just make sure you copy the bpq1632.dll from the bpq1632.zip in the files section of this group to your SYSTEM32 folder. The version in the current release is out of date.

                 

                Start ARESDATA using the “Start ARESDATA” shortcut.

                 

                There is no special configuration needed for bpq32 – just add an APPLICATION line for ARES to your bpq32.cfg. Something like:

                 

                APPLICATION 1,ARES,,MYCALL-1,ARES,0

                 

                73,

                John

                 

                 


                From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of Tyler Griffiths
                Sent: 12 November 2011 20:01


                To: BPQ32@yahoogroups.com
                Subject: Re: [BPQ32] Running ARESDATA with BBPQ32

                 

                 

                John,

                Could you possibly send along your .cfg files for both ARESDATA and BPQ32?

                Is there a cfg. file for BPQ1632? I'm struggling.

                 

                Thanx,

                Tyler N7WX

                On Tue, Nov 1, 2011 at 3:17 AM, John Wiseman <john.wiseman@...> wrote:

                 

                I intalled ARESDATA into it's own folder, but you could install into your BPQ32 folder. You'd need to edit ARESDATA.CFG to suit.

                 

                 

                John

                 


                From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of D R Mynatt
                Sent: 01 November 2011 01:09
                To: BPQ32@yahoogroups.com
                Subject: RE: [BPQ32] Running ARESDATA with BBPQ32

                 

                Great stuff for sure.  If I understand correctly, we should just copy the exe into the BPQ subdir and execute. Right?

                 

                Dave

                KA0SWT

                 


                From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of WS7I
                Sent: Monday, October 31, 2011 7:02 PM
                To: BPQ32@yahoogroups.com
                Subject: Re: [BPQ32] Running ARESDATA with BBPQ32

                Maybe this would help.  From my working files  this stuff runs fine on old bpq under Win98 which is where I had/have it.  But we don't use it around here any longer.  Ran a lot of users up to 10 plus under DRSI and BPQ.

                 

                 

                 

                Revised and reprinted from Proceedings of the Seventh ARRL Computer Networking
                Conference (ARRL, Newington, CT, 1988), pp. 141-144, by permission of the
                authors.


                                                 ARES/Data:
                            A PACKET RADIO DATABASE FOR EMERGENCY COMMUNICATIONS

                                             W. E. Moerner, WN6I
                                              1003 Belder Drive
                                         San Jose , California   95120
                                                WN6I @ KB6OWT

                                              David Palmer, N6KL
                                               248 Omira Drive
                                         San Jose , California   95123
                                        N6KL @ KB6OWT, CIS: 73357,3157


                                                 INTRODUCTION

                ARES/Data is a multiple connect, specialized bulletin board system tailored to
                store and retrieve basic information about people, places, or things during an
                emergency.  The program is a generalized form of the FINDER program (Family
                Information Database for Emergency Responders), written by David Palmer, N6KL
                and W.  E.  Moerner, WN6I [See FINDER:  The Family Information Database for
                Emergency Responders, Proceedings of the Sixth ARRL Computer Networking
                Conference, 1987, by W.  E.  Moerner, Sharon Moerner, and David Palmer].
                Although ARES/Data allows access to the database via packet radio, the program
                can also operate stand-alone without the need for packet radio hardware.  The
                actual operating mode is chosen by the system operator when the ARES/Data
                program is started.

                ARES/Data is a system designed for management of information during a
                widespread emergency that overloads normal communications channels.  The
                program is designed to be flexible, so that it can be used without change for
                both small and large disasters to organize information about victims, evacuees,
                or even ham radio operators.  Examples of situations in which ARES/Data could
                be used are:

                 -  registration of individuals at Red Cross shelters
                 -  patient/victim tracking in a multiple casualty incident
                 -  maintaining staffing information about hams assigned to an emergency
                 -  listings of road closures or damage reports
                 -  logging reports from SKYWARN observers during periods of severe weather

                With alternate power sources and their own frequencies, Amateur Radio Emergency
                Service (ARES) operators can provide the ARES/Data service without tying up
                critical communications channels or relying on commercial power.


                                          ARES/Data SYSTEM OVERVIEW

                There are three major elements to the ARES/Data system:

                 -  ARES/Data software and database
                 -  Data Concentrators (remotely connected packet operators)
                 -  Voice operators

                The central element of the ARES/Data system is the computer on which the
                ARES/Data program is running.  The ARES/Data program collects and collates
                current information about people or items in the system, according to the needs
                of the incident.  The program establishes and maintains the actual database on
                floppy disk or hard disk at this central computer.  In general, the operator at
                the computer keyboard can add new records to the database, delete incorrect
                records, perform searches for specific information, and generate database
                summaries.  The ARES/Data program will run on any IBM Personal Computer or
                IBM-compatible system running IBM DOS or MS/DOS with at least one floppy disk,
                although a hard disk increases the allowable size of the database and improves
                performance.  [IBM is a registered trademark of International Business Machines
                Corporation.]

                If remote access to the database is desired, addition of a serial port, TNC,
                and radio allows the central database computer to become the hub of a packet
                radio network in which up to eight remotely connected stations can
                simultaneously access the information in the ARES/Data database.  These packet
                radio stations, called "Data Concentrators," can update or query the shared
                database.  This data access occurs by exchanging updates or queries in a
                simple, precise, and well-defined format.

                Data Concentrators extend the coverage of the ARES/Data system.  They are the
                input/output ports of the ARES/Data database when remote access is needed.  The
                Data Concentrators can also act as local net controls for any participating
                voice operators within their range.  If voice operators are not needed, the
                packet operators interact with the public and/or disaster officials directly.

                The Voice Operators enter the ARES/Data system when the points of contact with
                those needing information are numerous and/or spread over a wide area.  These
                amateurs are also the public face of the ARES/Data system.  They can be the
                'reporters' live at the scene, sending status updates and requests to the Data
                Concentrators.  They also ensure delivery of responses to the persons making
                status requests.

                Emergency responders, their families, evacuees located at a particular shelter,
                and responsible agency officials access the ARES/Data system by contacting a
                participating amateur radio operator.


                           DESCRIPTION and OPERATION of the ARES/Data SYSTEM V. 0.1

                                            The ARES/Data Program

                The ARES/Data software was written by W. E. Moerner, WN6I, and David Palmer,
                N6KL.  It may be run in either of two modes:  stand-alone with no TNC support
                and no remote access, or by changing the configuration file, the program will
                control a TNC that allows multiple (simultaneous) remote connections.  If TNC
                support is chosen, the program requires a TNC with WA8DED firmware, because
                WA8DED host mode is used for communication between the computer and the TNC.
                WA8DED firmware is currently available for the TAPR TNC-1 and TNC-2 as well as
                the AEA PK-87.  We emphasize that NO REQUIREMENT IS PLACED ON THE OTHER TNC'S
                CONNECTED TO THE ARES/Data DATABASE MACHINE, except that they use AX.25
                link-layer protocol.  The ARES/Data program is written in Turbo Pascal Version
                4, and uses Turbo Database Toolbox for management and indexing of its B-plus
                structured tree.  [Turbo Pascal and Turbo Database Toolbox are trademarks of
                Borland International, Inc.] Briefly, ARES/Data may be regarded as a
                specialized multiple connect BBS with a specific command set tailored to the
                handling of STATUS INPUT information and SEARCH REQUESTS.

                The ARES/Data database is simply a collection of records.  Each record consists
                of four main items or "fields" plus a message item.  The information in the
                four main fields can be sorted or searched as required.  The rest of this
                section provides examples and a condensed user manual for the ARES/Data system.


                        General Rules for Current Information Input / Search Requests

                All basic commands can be entered either at the main ARES/Data keyboard or at
                any one of the remotely connected packet stations.  In addition, the operator
                at the main ARES/Data keyboard (the "sysop") has an additional set of commands
                that allow direct communication with the TNC, the printing of a log, backups,
                and disk report files.


                                    Syntax for Current Information Input:

                To add a record to the database, the operator simply enters the four fields and
                any message, in order, with separators between the fields.  The only valid
                separator is the comma.  Within a field, leading and trailing blanks are
                ignored, but imbedded blanks ARE significant.  If no value is desired for a
                particular field, just skip the field by adding an extra comma.  The database
                will fill that field with ten blank characters.  For example,

                    field1,field2,field3,field4,message<cr>

                    (<cr> means carriage return)

                Fields 1 through 4

                The four fields are very general.  Each can have up to 20 characters, with
                imbedded blanks.  The meaning of each field is defined at the beginning of the
                event by the ARES officials, depending upon the nature of the event and what
                type of information needs to be tracked.  The sysop can issue a "labels"
                command that will give specific names to each of the four fields to help the
                operators remember the purpose of each field for a particular event.

                Message

                MESSAGE is an optional, free-form field that can be up to 80 characters in
                length.  It could contain a message, a phone number, an address, or other
                information deemed useful for the incident.

                Examples of Data Input with Sample Responses from ARES/Data

                    85553195,joe,12,sj34<cr>
                 response->   1040: data input accepted, #234.

                    Johnson,Mary,93445,sj13, home 2333 Alsace Ln SJ 617-555-2368<cr>
                 response->   2134: data input accepted, #114.

                All of the input information is stored in the database as a record of the
                status and location of a particular person at a particular time and date.  The
                time and date are added automatically by ARES/Data.  The number at the end of
                the response is the actual "record number" associated with the input
                information assigned by ARES/Data.  Further data input packets for the same
                person will also be saved in the database under a new record number.  The time
                and date identifies which information is most recent.


                                          Syntax for Search Requests

                The search commands instruct the database to look for ALL entries with the same
                value for field 1, 2, 3, or 4.  For example:

                    /1,value<cr>                  Searches for "value" in field 1
                    /2,value<cr>                  Searches for "value" in field 2
                    /3,value<cr>                  Searches for "value" in field 3
                    /4,value<cr>                  Searches for "value" in field 4

                (For convenience in typing, the character question mark "?" may be used instead
                of the diagonal bar "/"--both are treated identically).  A status report
                listing all information for each match in the field specified is sent back to
                the requesting packet station.  The first line gives the search value and the
                field number.  VALUE must exactly match what was originally typed in for the
                selected field, with leading and trailing blanks removed, and without regard
                for case.  At the end of the report, the line

                    ARES/Data Search done at HHMM, nn hits.

                is sent, which signifies no more information coming, and that "nn" matches (or
                hits) were found in the database at time "HHMM".

                Examples of Search Requests:

                    /1,5553195<cr>
                    /2,w1aw<cr>
                    /3,mercyhosp<cr>
                    /4,85563<cr>

                Example Response from ARES/Data for the last case:

                    Search for value "85563" in Field4
                     Recno DT/Time: Field1,Field2,Field3,Field4,Msg
                     29    13/1225: JOHNSON JOE,M35,SHELTER 1,85563, MISSING DOG AND CAT
                     59    13/1257: DOE JANE,F23,SH05,85563, 2 CHILDREN
                    ARES/Data search done at 1259, 2 hits.


                                         Syntax for Summary Requests

                A Summary command is provided that prints a breakdown of the number of
                like-named items for any particular field.  For example, if ARES/Data were
                being used to maintain a list of evacuees, and field 3 was designated for
                "shelter location", then the command "$3" would print a list of all distinct
                shelter names in use, and adjacent to each, the number of records (people) in
                the database at each shelter would be printed.

                     $1<cr>                       Produces a summary on field 1
                     $2<cr>                       Produces a summary on field 2
                     $3<cr>                       Produces a summary on field 3
                     $4<cr>                       Produces a summary on field 4

                Sample Output from a Summary Request:

                     Database summary for Field3 at 1455 on 23
                        OAK GROVE            3
                        PIONEERHS            20
                        EASTVIEW             66
                        SHLTR5               37
                     ARES/Data done at 1456, found 4 distinct values, entire DB has 153 records.


                              Listing Specific Entries (Records) in the Database

                Each record is automatically assigned a unique record number for identification
                purposes.

                     l nnnnn<cr>                  lists record nnnnn


                            Deleting Specific Entries (Records) from the Database

                This function is always enabled at the sysop keyboard.  Its use by remotely
                connected packet stations is controlled initially by the configuration file
                during program startup.  Thereafter, the sysop can disable or enable this
                function as necessary.  Be extremely careful in using this command!  Always
                list the record first before deleting to be sure you have the right one.

                     d nnnnn<cr>                  deletes record nnnnn


                                        Conference Bridge (Roundtable)

                This feature allows any connected station to send messages to other connected
                stations or to the sysop.  The conference bridge illustrates how the ARES/Data
                system operates as a hub-oriented network, with all transactions passing
                through the central database station.

                Users Command

                The users command in the form "users<cr>" or "u<cr>" returns a list of the
                callsigns of packet stations currently connected to ARES/Data.  The response is
                of the form:

                     At WN6I-1:  N6KL  W6BB-3  AJ6T

                Tell Command

                The Tell command allows connected packet stations to use ARES/Data as a
                conference bridge, or roundtable.  The general format is:

                     tell callsign message<cr>      or      t callsign message<cr>

                For example:

                     tell w6bb-3 We have lots of people here at SJ12<cr>

                The message "We have lots of people here at SJ12" is sent to the connected
                station W6BB-3 prefaced by a time stamp and the call of the station originating
                the tell command.  In this case, if the tell command was sent by AJ6T, W6BB-3
                sees:

                     1230  AJ6T> We have lots of people here at SJ12

                The special callsign "*" or "all" is used to send a message to all connected
                stations.  The special callsign "sysop" sends the message to the sysop at the
                ARES/Data database station.  It is not necessary to enter the entire callsign--
                just the suffix or some other substring will do.  In this case, the message is
                sent to any connected station whose callsign contains this substring.  This
                feature can be used to create multiple roundtables.  For example, packet
                stations located at, say, hospitals could adopt subªstation identifiers (SSIDs)
                of "-1", while those located at shelters could use SSIDs of "-2".  This way,
                broadcast messages of interest to either group can be easily sent without
                disrupting the other group.  For example:

                     tell -1  Mercy Hospital has 12 beds available.<cr>

                This message would be sent to all stations that were part of the hospital net.


                       EXAMPLES OF HOW TO USE ARES/Data IN SPECIFIC DISASTER SCENARIOS

                -  In an evacuation of residents in a local area, the Red Cross often maintains
                health and welfare status information about evacuees.  In this case, the four
                fields and the comment field might be defined to be:

                     Last Name - First Name, Shelter, Number in Family, Last phone, Next of kin

                -  In a multiple-casualty event where victim transportation needs to be
                tracked:

                     Name, Sex/Age, Ambulance#, Hospital, Injuries

                -  In a ham radio staffing situation:

                     Call, Name, Location, Shift, phone number for cancellation

                -  In a disaster situation where damage assessment and damage reports are
                needed:

                     Coded type of damage, Location, Number of injuries, Callsign, comment

                There are many more possibilities, of course.  This is why the exact
                definitions of the various fields are not defined in advance.  In any given
                situation, more information than will fit into four fields and a comment field
                might be needed.  However, on today's 1200 baud packet radio networks, not much
                more information per record can be accommodated without restricting the total
                number of records that can be handled in a reasonable time.


                              HOW TO OBTAIN YOUR COPY OF THE ARES/Data PROGRAM

                The ARES/Data program, a relative of and successor to the FINDER program, is in
                the public domain.  The current version is 0.1, which operates as described in
                this paper.  A copy of the program along with the documentation is available
                for non-commercial, non-profit use from WN6I or N6KL by sending a blank,
                formatted 5 1/4" (360 kB) or 3 1/2" (720 kB) floppy in a mailer with return
                postage stamps.  The cost to you is the cost of the diskette and postage.  No
                other compensation can or will be accepted - please do not send money.  We have
                included a configuration file facility so that you can tailor many parameters
                to your specific system.


                                              FUTURE DIRECTIONS

                The ARES/Data program is continuously being updated to add additional function
                and flexibility.  For example, multiple TNC operation at the main database is
                being added to the program to allow more data concentrators on multiple
                frequencies.  Database enhancements include substring searches and the ability
                to update a specific field for a specific record.  We encourage your comments
                and suggestions, and will strive to incorporate them in future releases.


                                          



                 

                --

                Tyler Griffiths
                N7UWX

                See where I am:
                http://map.findu.com/n7uwx-12



                 

                --
                Tyler Griffiths
                N7UWX

                See where I am:
                http://map.findu.com/n7uwx-12

              • Kirk
                Tyler, I m a little late joining this thread but just got caught up this morning. I m in Salt Lake City and have done what you seem to be attempting. In the
                Message 7 of 19 , Nov 14, 2011
                • 0 Attachment
                  Tyler,
                  I'm a little late joining this thread but just got caught up this morning. I'm in Salt Lake City and have done what you seem to be attempting. In the mid-1990's, in putting together a packet system to track the runners in the Wasatch 100 mile endurance run, I started with ARESDATA and BPQ and we made a workable system. I was able to get the source code for ARESDATA from one of the authors and made significant changes to the DOS version to make it more suitable for tracking runners. The original ARESDATA was written in Borland Turbo Pascal and used a Turbo Pascal add in module for database management.

                  To condense the story, the system has significantly evolved and we are now running a Windows version of the database program, highly customized for the Wasatch 100 race, written in Delphi 4, using BPQ32 very successfully. The database is in dBase IV format and is accessed using the Borland Database Engine. The last race was September 11-12, 2011 and we tracked around 250 runners through 15 remote checkpoints all using packet radio through BPQ32.

                  I moved out of my house last year and a lot of stuff didn't make the move with me, but I have found the last version of the DOS software. I've also got the source for all the Windows 32 bit versions, which I'll be happy to share with you.

                  Kirk Boman, KD0J



                  --- In BPQ32@yahoogroups.com, "John Wiseman" <john.wiseman@...> wrote:
                  >
                  > If you are already using BPQ32 for anything else, load those programs first,
                  > then start ARESDATA in a dos box/cmd window. I'd recommend running
                  > BPQTerminal as a minimum, so you can connect to ARESDATA to test.
                  >
                  > You can just start ARESDATA in a dos box. BPQ32 will be loaded as ARESDATA
                  > initialises.
                  >
                  > I should have made clear before that this all applies to Windows 2000 and
                  > later.
                  >
                  > 73,
                  > John
                  >
                  >
                  > _____
                  >
                  > From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of
                  > Tyler Griffiths
                  > Sent: 31 October 2011 23:40
                  > To: BPQ32@yahoogroups.com
                  > Subject: Re: [BPQ32] Running ARESDATA with BBPQ32
                  >
                  >
                  >
                  >
                  > So you run BPQ32 in windows first then ARESDATA. Is this correct?
                  >
                  >
                  > Tyler N7UWX
                  >
                  >
                  > On Mon, Oct 31, 2011 at 9:31 AM, John Wiseman <john.wiseman@...>
                  > wrote:
                  >
                  >
                  >
                  >
                  >
                  >
                  >
                  > Hi.
                  >
                  > I've made a couple of changes to the bpq1632 files to make them easier to
                  > use with ARESDATA.
                  >
                  > Download the bpq1632.zip from this YAHOO group.
                  >
                  > Copy bpq1632.dll to your Windows\system32 folder.
                  >
                  > Copy bpq1632.exe and dedhost.com to your ARESDATA folder.
                  >
                  > Edit ARESDATA.CFG to use BPQ (uncomment the relevant attach line).
                  >
                  > I edited the AREASDATA.BAT to contain:
                  >
                  > rem ARESDATA.BAT.
                  > rem This loads the BPQ32 Interface
                  > BPQ1632
                  > rem This loads the terminate and stay resident program that makes the
                  > rem BPQ switch speak DED host mode, using software interrupt hex FE (254)
                  > rem with 9 connects available, start with stream 1, use application 3
                  > rem (ARES/Data), and 40 K available for buffering DED packets.
                  > DEDHOST 9 1 4 40 254 N
                  > aresda16
                  >
                  > This is set to use BPQ APPL 3 - change the 3rd Param of DEDHOST to suit.
                  >
                  > It is best to create a shortcut to AREASDATA.BAT, and set "Run In Separate
                  > Memory space" in the advanced properties. Then the bpq interface will be
                  > unloaded when the program exits.
                  >
                  > It works as far as I can see, though I don't know what the program is
                  > supposed to do, so I can't be sure!
                  >
                  >
                  > 73,
                  > John
                  >
                  >
                  >
                  >
                  >
                  >
                  >
                  >
                  >
                  >
                  > --
                  > Tyler Griffiths
                  > N7UWX
                  >
                  > See where I am:
                  > http://map.findu.com/n7uwx-12
                  >
                • Tyler Griffiths
                  Kirk, I would love to get a copy of your windows version! I do have a copy of ARESDATA 1.6. Looking at your stuff on the Wasatch 100 website was what got me
                  Message 8 of 19 , Nov 14, 2011
                  • 0 Attachment
                    Kirk,
                    I would love to get a copy of your windows version! I do have a copy of ARESDATA 1.6.
                    Looking at your stuff on the Wasatch 100 website was what got me interested in making ARESDATA working for the BEAR 100.
                     
                    Thanks,
                    Tyler

                    On Mon, Nov 14, 2011 at 1:46 PM, Kirk <ksboman@...> wrote:
                     

                    Tyler,
                    I'm a little late joining this thread but just got caught up this morning. I'm in Salt Lake City and have done what you seem to be attempting. In the mid-1990's, in putting together a packet system to track the runners in the Wasatch 100 mile endurance run, I started with ARESDATA and BPQ and we made a workable system. I was able to get the source code for ARESDATA from one of the authors and made significant changes to the DOS version to make it more suitable for tracking runners. The original ARESDATA was written in Borland Turbo Pascal and used a Turbo Pascal add in module for database management.

                    To condense the story, the system has significantly evolved and we are now running a Windows version of the database program, highly customized for the Wasatch 100 race, written in Delphi 4, using BPQ32 very successfully. The database is in dBase IV format and is accessed using the Borland Database Engine. The last race was September 11-12, 2011 and we tracked around 250 runners through 15 remote checkpoints all using packet radio through BPQ32.

                    I moved out of my house last year and a lot of stuff didn't make the move with me, but I have found the last version of the DOS software. I've also got the source for all the Windows 32 bit versions, which I'll be happy to share with you.

                    Kirk Boman, KD0J



                    --- In BPQ32@yahoogroups.com, "John Wiseman" <john.wiseman@...> wrote:
                    >
                    > If you are already using BPQ32 for anything else, load those programs first,
                    > then start ARESDATA in a dos box/cmd window. I'd recommend running
                    > BPQTerminal as a minimum, so you can connect to ARESDATA to test.
                    >
                    > You can just start ARESDATA in a dos box. BPQ32 will be loaded as ARESDATA
                    > initialises.
                    >
                    > I should have made clear before that this all applies to Windows 2000 and
                    > later.
                    >
                    > 73,
                    > John
                    >
                    >
                    > _____
                    >
                    > From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of
                    > Tyler Griffiths
                    > Sent: 31 October 2011 23:40
                    > To: BPQ32@yahoogroups.com
                    > Subject: Re: [BPQ32] Running ARESDATA with BBPQ32
                    >
                    >
                    >
                    >
                    > So you run BPQ32 in windows first then ARESDATA. Is this correct?
                    >
                    >
                    > Tyler N7UWX
                    >
                    >
                    > On Mon, Oct 31, 2011 at 9:31 AM, John Wiseman <john.wiseman@...>

                    > wrote:
                    >
                    >
                    >
                    >
                    >
                    >
                    >
                    > Hi.
                    >
                    > I've made a couple of changes to the bpq1632 files to make them easier to
                    > use with ARESDATA.
                    >
                    > Download the bpq1632.zip from this YAHOO group.
                    >
                    > Copy bpq1632.dll to your Windows\system32 folder.
                    >
                    > Copy bpq1632.exe and dedhost.com to your ARESDATA folder.
                    >
                    > Edit ARESDATA.CFG to use BPQ (uncomment the relevant attach line).
                    >
                    > I edited the AREASDATA.BAT to contain:
                    >
                    > rem ARESDATA.BAT.
                    > rem This loads the BPQ32 Interface
                    > BPQ1632
                    > rem This loads the terminate and stay resident program that makes the
                    > rem BPQ switch speak DED host mode, using software interrupt hex FE (254)
                    > rem with 9 connects available, start with stream 1, use application 3
                    > rem (ARES/Data), and 40 K available for buffering DED packets.
                    > DEDHOST 9 1 4 40 254 N
                    > aresda16
                    >
                    > This is set to use BPQ APPL 3 - change the 3rd Param of DEDHOST to suit.
                    >
                    > It is best to create a shortcut to AREASDATA.BAT, and set "Run In Separate
                    > Memory space" in the advanced properties. Then the bpq interface will be
                    > unloaded when the program exits.
                    >
                    > It works as far as I can see, though I don't know what the program is
                    > supposed to do, so I can't be sure!
                    >
                    >
                    > 73,
                    > John
                    >
                    >
                    >
                    >
                    >
                    >
                    >
                    >
                    >
                    >
                    > --
                    > Tyler Griffiths
                    > N7UWX
                    >
                    > See where I am:
                    > http://map.findu.com/n7uwx-12
                    >




                    --
                    Tyler Griffiths
                    N7UWX

                    See where I am:
                    http://map.findu.com/n7uwx-12
                  Your message has been successfully submitted and would be delivered to recipients shortly.