Polski Związek Krótkofalowców

 

Polski Klub Radiovideografii

Navigation:  Program HAM SECRETARY and its purpose > Configuration program for work >

Configure the pattern FRM Cabrillo format

Print this Topic Previous page come-back to begin of chapter Next page
Expand all elements   Callapse all elements

In order to create log format. cbr Cabrillo for the contest in the program was created tools to design template fot the  concrete contest.  Files templates have extension  .FRM and are stored in directory CABRILLO_FORM .  . The directory is already provided with the FRM pattern for certain contests - though presented the following tools allow you to completely design a new form or from any template other contest  design the  new FRM for contest. Program  HAM_SECRETARY.EXE can create forms in standard cabrillo 2.0 or  3.0 .  Standard 3.0 is not yet used by all programs - robots contest.  Contests ARRL's and IARU's need at the moment (22.08.2009) standard 3.0. .Others may require a standard of 2.0.

In order to call tools to create a form template select Configuration - Configuration FORM for Cabrillo.

Window what will appears if  design form FRM type Cabrillo

Designing a form type cabriilo FRM for contest

 

The forms that are present have three bands:

Band header
Band Pattern line data
Band footer - END-OF-LOG:

 

Header Band

Header band is mostly populated reported in the section Configuration of personal data is personal data.These data are inserted at the time of the creation of a file type Cabrillo after selecting menu Translate file This band is to choose the field Standard Cabillo 2.0 or 3.0 .. Depending on the choiced standard  cabrillo header fields may contain

for  standard 2.0

 

for  standard 3.0

 

Only some of the lines should be given when creating the form. These include:

For standard 2.0
Line Contest . It should be contest name for the form which is designed
Line  category. If you usually starts in the same category can be given appropriate names already such as SINGLE-OP ALL LOW - Single operator - All Bands - Low Power .. This field can be filled well before the direct shipment already in the file  of text if you not often change the category.

Other fields will be filled either automatically from the personal data fields, or should be entered manually before the shipment in any text editor. With this, and not all fields must be filled. It depends what is this contest.

For standard 3.0
Line  Contest . It should be contest name for which is designed form. It is the only field for which the value we give in the form design. Other fields will be filled either automatically from the personal data fields, or should be entered manually before the shipment in any text editor

 

Apart from the above in this band  there is a field  contest name we want to give up editing or on which you will create another contest

 

 

After selecting this contest ARRL_DX.FRM. Form FRM will look

FRM Form for Cabrillo for contest ARRL-DX-Contest

At any time you can change the header format 3.0 to 2.0 and vice versa - saving it under the same filename - but with a suffix, eg. V3_0.

 

Band Pattern of Line

It is the most critical bandwidth (not amateur band)  which will be printed in the resulting file. The data given here are applicable to every record QSOs taken from a file of source in any format, ie. adi. csv or. txt. Individual boxes and lines have the following meanings::

ADIF names check box. Field1ADIF to Fileld12ADIF. You can use the 12-fields in the resulting file of Cabrillo. In a each box to the right  is present  a button to press to expand the vertically names containing  standard field names according to standard ADIF ADIF 2.2.  In addition, added the names of non- standard fields to be applied in Logger32. Should choose the items needed for the ADIF field. If you select a different name than the other exists for the position then in this coresponding place in the line nr.0 will be inserted new ADIF field name.

 

Some programs loggers use non-standard ADIF fields (except as described above) to the there insert  data from QSO . In this case, the name of this should be added as an additional name in the file Non_standardADIF_addition_field_for_cabrillo.txt. Then these names will be added to the standard names given the opportunity to choose this field as if it were a standard fields. . For example in this file were added custom names:

APP_N1MM_EXCHANGE1
APP_N1MM_MISCTEXT
Line no. 0 - Variable names  -  begins with character double brackets [[and ends mark]]. Example of the line::

[[   FREQ MODE QSO_DATE TIME_ON OPERATOR  RST_SENT TX_PWR CALL    RST_RCVD SRX ]]

As you can see there are standard ADIF field names  - and if such a non-standard was added to the previously described file Non_standardADIF_addition_field_for_cabrillo.txt) to be printed in one line file .cbr for a single record  QSO

 

Line no. 1- Pattern print . Example pattern contains the print pattern in the form of a string # for a single field. Sample pattern for print

QSO: ##### ## ########## #### ############# ### ###### ############# ### ###### 0

Subtitles QSO: will be printed in each row, while in place of a string ##### is inserted data from record QSO - it will be aligment to the left side field

Line no.2 - Information .Absolutely does not affect the character or stored data. Here is an example of the appearance of one line stored in the file. Cbr

QSO: 14085 RY 2008-01-05 1807 SP9AUV        59  100    RA3BB         59  0003

Line no.3 i 4 information . Here are the pattern with numbering position  for  columns

000000000111111111122222222223333333333444444444455555555556666666666777777777788888888889999999999

123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789

Line no.5 information -commentary . You inform what will be included in the next line no.6

//Input format for frequency, QSO_DATE and TIME_ON

Line no.6 - indicating about the data formats in a source file :ie the format frequency input in the file (MHz or kHz), the date format and time format for start QSO

       MHZ     yyyymmdd   hhmm

Here, this provision means that the frequency in a souce file will be given in MHZ, QSO date format will be included in the format as YYYYMMDD eg, 20090128 and the time as hhmm eg QSOs 1903

Line no.7 - information-commentary which will include the next line which will include the next line here inform that it will be the format for the date of QSOs in the output file of Cabrillo. Cbr and how they will look like next field

//Output format for QSO_DATE and rest field  from http://www.kkn.net/~trey/cabrillo/qso-template.html

Line no.8  containing the output format of the date of QSOs and other fields   Line is copied from http://www.kkn.net/~trey/cabrillo/qso-template.html

QSO: ***** ** yyyy-mm-dd nnnn ************* nnn ****** ************* nnn ****** n

Line no.9 i 10 information-commentary .. It is also copied from a specified web page

QSO: freq  mo date       time call          rst exch   call          rst exch   t is transmiter id 0 or 1-there put 0

QSO: 21303 PH 1999-03-06 0000 HC8N          59  700    K9NS          59  IL     1

 

Footer band

Contains only one line END-OF-LOG: required in the file cabrillo.

Final field pattern template

Enter here the field:

Name for file pattern  for writing.. This is a text field. To this field is copied the name of previously selected in the field Choice Contest .  If you only edit the form it does not change the name in this field.  However, here we take as the basis for another form - edit it  and save under a new name contest

Button  Save the form contest . When he pressed on the screen, nothing happens, but we can choose at the top of another contest and edit it.
Button. Exit. - Causes loss of window FRM and return to the main menu.
Button Help - - to call help context