Technical Information

General Information

N1MM logger is a contest program written in Microsoft Visual Basic which uses a Microsoft Access 2000 database for storing information. Writing and retrieving data to and from the database is done with SQL (Structured Query Language).
Running the program needs no more programs or files than supplied in the installation package and the program update (NewExeVx.x.x).

Do you need all the information given below to use the program? NO

We recommend not to change any data in the database or any other files unless you are very sure what you are doing. It is possible to change the behavior of the program and get erroneous results. If you have changed the contents of the database and the program behaves strange go back to the original (unaltered) version of the database.

No support will be given to users who change the database structure or contents. The same goes for changing other files used by the program.

You are on your own!

Note: Normally there is no need to access the database or ini files. Don't make changes if you are not very sure what you are doing. Second and last warning!

Note: When changing data always make a backup from the database (and preferably the whole N1MM logger directory).

Why is this information given?

Accessing information direct in the database sometimes gives possibilities not directly supported by the program.

Examples:

• You want to have reports which are not standard in the program. With some knowledge of SQL and Access it is possible to generate your own.
• Changing information in the database can sometimes be done much easier this way than within the N1MM logger program.

Note: After changing qso information always do a rescore! N.B. Multiplier information and qso points will be updated after a rescore so these changes made direct in the database will be lost. Change multiplier and qso points in the (Cabrillo) output files. The program updates the database and not the other way around.

N.B. It is not possible to add a contest to the program this way.
Contests and it's rules etc. are in the main program file (N1MM logger.exe) and are not stored in the database or any other files!

Directory structure

The default directory where the program is installed is in the 'Program Files' directory on the first hard disk (C:). Below this directory two directories are (or can be) made to support Digital Voice Keying (DVK).

Where is the program information stored?

There are several places where program information is stored.

• The Access database file
  • After a first install called HAM.MDB
  • You can rename it or add your own databases from within the program.
  • General contest information
    • Contests information
    • Station information
    • QSOs made in the contests
    • Packet spots
    • (Function) key information
    • Country information
    • Etc.
• N1MM logger.ini file
  • Program settings from the configuration screens , these settings overrule the settings in 'Default Settings.ini'
  • Window settings (screen setup)
• Default Settings.txt
  • Default settings file used by the program
• Configuration files
  • Setting up your external TNC
  • MMTTY specific files
• Other files
  • Wav files for CQ etc.
  • Exported Cabrillo, ADIF, generic log and summary sheet files
  • Section files used for specific contests (*.sec)

The Access database

A database has tables with in it the data.

The "N1MM logger.ini" file

Everything in the "N1MM logger.ini" file should be settable through the program's User Interface. Defaults are in the file "Default Settings.txt" . An item will not appear in the "N1MM logger.ini" file if its value is the same as in the 'Default Settings.txt' file. Both files can be found in the program directory.

• The "N1MM logger.ini" file is organized by function (top of file) and windows (bottom of file).
• The function section's attributes can be deleted, and defaults will be used by the program.
• The window section contains position and other window information. Generally these values should not be changed unless a window disappears.
• Try to keep the file in this order, it will make things easier to find during discussions on the user group.
• To comment out a value in the file precede it with a semicolon (;)
• Removing the 'N1MM logger.ini' file will use the defaults in 'Default Settings.txt', the 'N1MM logger.ini' file will be recreated.

Functions section

Possible functions are:

Examples

[Packet]
Packet Tab=1 - Telnet window is selected, if removed the Packet tab is selected.

[Configurer]
Database Name=C:\Program Files\N1MM Logger\PI4GN-Maart-2004.mdb Selected database
Contest Type=VHFREG1Selected contest in the selected database
Contest NR=1 Selected contest number in the selected database
Recent Contest 1=VHFREG1:6-3-2004:C:\Program Files\N1MM Logger\PI4GN-Maart-2004.mdb Most recent opened contest

Window Section

Possible windows are:

Examples

[EntryWindow]
Top=3825
Left=2985
Height=3330
Width=5370

[PacketWindow]
WindowState=0 Window is open (default) or closed (0), the Entry window can not be closed
Top=9000
Left=3270
Height=2550
Width=12105
Telnet Port=K1TTT.NET The selected telnet cluster from the list. Specific for this section.

[BandMap]
CW Wide - 1=*RMF400CW Narrow - 1=*RMF250

[InfoWindow]
WWVMessagesVisible=False WWV messages are not shown in the Info window

Configuration files

After installation the files below are stored in the N1MM logger program directory.

Program files

Never delete these (program) files!

• arrow.bmp - arrow icon used in the bandmaps (non active bandmap)
• ClearRegistry.bat - used to clear the contents of the registry used by the program (obsolete per version 4, can be deleted from the directory).
• cty.dat - the default country file name used when the menu item 'Tools /Import country list from downloaded file' is selected.
• CW IF.exe - this is the Active X component which generates the CW.
• cyanarrow.bmp - arrow icon used in the bandmaps (active bandmap).
• Default Settings.txt - the default settings for the program, differences are in N1MM Logger.ini.
• dirswap.BAT - rename wav file directory (example).
• empty.wav - file used to stop sending a wav file.
• led_Red.bmp - icon used when a message is shown which needs attention.
• master.dta - file used by the Check window with calls from many contesters.
• N1MMLoggerHelp.chm - windows help file (shown when pressing Alt+H).
• N1MM Logger.exe - the N1MM logger contest program.
• N1MM loger.ini - configuration file for functions and windows. Be careful when editing.
• N1MM loger.ini.init - configuration file from the NewExe file. Will be renamed to N1MM Logger.ini if not found.
• N1MMlogger.pdf - the manual which is shown when selecting 'Help / Manual'.
• N1mmWave.ocx - ocx used for recording and playing wav files.
• reddot.gif - icon used when a warning message is shown in the Entry window pane.
• RevisionHistory.htm - N1MM Logger Revision History overview.
• *.sec - text files used for different contest (example: SAC.sec, REF.sec etc).
• style.css - style sheet ued in the file 'RevisionHistory.htm'.
• ST6UNST.LOG - file used by Windows when removing this program from your hard disk.
• Suncalcs.dll - dll used by the program.
• Update Log.wri - overview from the last program changes and updates. (obsolete, can be deleted from the directory).
• Upgrade.bat - file to register CW IF.exe to Windows (normally automatically done by the program).
• *.init - files used during installing which can be deleted but we recommend to leave them in.
• Nice to have a clean ham.mdb at your disposal (ham.mdb.init) or a clean 'N1MM loffer.ini' settings file.

Database files

• ham.mdb - default database file (don't delete).
• new.mdb - default database file used when a new database is created by the user (don't delete).
• *. MDB - database files made when selecting 'File / New Database'.
  Deleting this file means loosing all the contest QSOs in it. It's good practice to make a new file every (major) contest and name it after the contest. Example: PACC2002.MDB

Files created on your command:

• <YOURCALL>.ADI - ADIF file made by the program when selecting 'File / Export / Export ADIF to file...'
• <YOURCALL>.LOG - Cabrillo file made by the program when selecting 'File / Export / Export Cabrillo to file...'
• <YOURCALL>.SUM - Summary Sheet made by the program when selecting 'File / Export / Print Score Summary to File'
• <YOURCALL>.TXT - Log file made by the program when selecting 'File / Export / Export to File (Generic)...'
• *.MC - Exported Function key files.
• *.TXT - Exported other files (example: Packet/Telnet buttons)

RTTY files

MMTTY files are not in the program installation package and should be downloaded separately when needed.

• MMTTY.exe - the MMTTY program
• MMTTY.ini - MMTTY configuration file
• MMTTY.* - other files used by the MMTTY program
• XMMT.ocx - needed file for MMTTY.exe
• Settings.txt - example file for the AEA PK-232 external controller
• UserPara.ini - MMTTY program settings

PSK and other modes

The MMVARI engine is used for most digital modes which is included in the N1MM installer. There is no need to download the MMVARI package for use with N1MM logger.

• MMVARI.ocx - the MMVARI engine
• Varicode.tbl - table used by the MMVARI engine

PSKCore files (all obsolete)

All PSKCore files below are obsolete and not required for use with N1MM logger anymore.

• PSKCore.dll  (obsolete, can be deleted from the directory)
• XMMT.ocx (obsolete, can be deleted from the directory)
• PSK63.dll (obsolete, can be deleted from the directory)
• WINPSKX.dll (obsolete, can be deleted from the directory)
• PSK.pal - color setting file for the WINPSK dll (obsolete, can be deleted from the directory)
• WINPSKX.oca - WINPSK support file (obsolete, can be deleted from the directory)

ADIF fields

N1MM logger complies to the latest ADIF standard. However in the N1MM logger database there is more information stored then we can export (and import) using ADIF. That is why a few N1MM logger specific tags have been added so when exporting an ADIF file and importing it again all information from the DXLOG table will be available. A rescore will update the fields not imported and to get the score and multipliers shown correct on the screen.

APP_N1MM_EXCHANGE1 - content of the Exchange1 field from the table DXLOG table.
APP_N1MM_POINTS - content of the Points field from the table DXLOG table.
APP_N1MM_RADIO_NR - content of the RadioNr field from the table DXLOG table.
APP_N1MM_MISCTEXT - content of the MiscText field from the table DXLOG table.
APP_N1MM_CONTINENT - content of the Continent field from the table DXLOG table.
APP_N1MM_CONTACTTYPE - content of the ContactType field from the DXLOG table.
APP_N1MM_RUN1RUN2:1 - content of the Run field from the DXLOG table.is the Run1/Run2 tag. 1 means radio 1 was the Run radio,  2 means radio 2 was the Run radio.

Callsign checking in the Digital Interface

Below how callsign checking is done in the Digital Interface windows.

It first checks to see if the callsign is of the right length (More than 2 less than 11). It then Checks to see if someplace in the first 6 characters there is a number. 3rd it check to see if there are no invalid characters in it. Then if it all that passes it goes thru the Busted Call Checker. If the Busted Call Checker returns an Error message then the call is invalid. Anything else from the Busted Call Checker makes it a valid call.

As text comes into the Receive screen of the Digital Interface it gets printed to the window and placed in a temp buffer. When a space or a CR or LF is encountered the program will send the text in the temp buffer to the check callsign routines, if it comes back as a valid callsign it is sent to another routine that looks back thru the last 25 characters of the Receive screen and colors them accordingly. At the time the space is encountered the temp holding buffer is cleared and things get sent there all over again. The whole process above takes just over a millisecond to complete.

Unlike other software DE before the call is not required,it looks for space mostly after callsign.

Take a look at this sequence it explains ho it picks up callsigns in the RX window:

A QWSCFGTWA5TTT WA5TTT UR 599 XXXXXXXXXX

The program sees the space between the TTT and the WA so it looks into its previous holding buffer which contains "QWSCFGTWA5TTT" that string does not equal a valid callsign even tho there is one in it. So because it encountered the space the buffer is cleared and the next string starts being placed into it. When it hits the third space it goes back and checks the buffer again this time it finds WA5TTT and it says it is a valid call. The program not looks back 25 characters and any time it finds WA5TTT it will color it accordingly and also place it in the grab window.

As for the clicking on callsigns it follows the same rule except there is a routine that looks to see the characters that are under the mouse if it is a valid call then it gets sent thru the routines to place it in the entry window. There is a ltrs/figs line of text that shows the actual text that is being converted. This will give you an idea of what text and is getting selected etc.

Problems will happen if the rules change in various countries and the rules in the Busted Call Checker can't keep up with the country changes so you get callsigns that do not come out of it ok. The main reason to add the Busted Call Checker routines in there is to cut down on a lot of garbage that would be getting colored that passed all of the check routines but were not really callsigns

Routers and Firewalls

A software firewall (like the Windows XP firewall, Zone Alarm, etc.) provides protection from the other computers behind your router. It's probably okay to turn off the Windows Firewall in a contest station.

Routers provide an important function called network address translation (NAT). If you look at your computer's IP address and see 192.168.x.y (or 10.x.y.z), then you're golden. The 192.168.x.y (and 10.x.y.z) address ranges are defined as local only and cannot be routeable across the Internet. If your PC has one of these addresses, it's as if you're behind a telephone switchboard and do not have a direct dial number. That's a good defense.

Software firewalls protect you from other computers behind your router. So if you take your laptop around with you and use various wireless networks, you absolutely need a software firewall. The other computers at Starbucks may be full of viruses, and you need a software firewall to protect you from them. Also, if you have a computer in your house that may be used for some less-than-safe surfing, you should have a software firewall. Kids may have permitted access for online gaming, peer-to-peer file sharing, or may have downloaded software that has spyware, etc. Protect your PC by running a software firewall. Finally, if you have a wireless network, make sure you control who access it. If your neighbor can access your network and has a bunch of malware on his machine, your machines could get infected, too.

Robert K5PI.

Adding N1MM to the Windows firewall

When you do not want to turn off the Windows Firewall you can leave your windows firewall on even though you are behind a router. Add N1MM to your exceptions list and better yet add the local subnet (usually 192.168.1.0 (255.255.255.0)) to the port exceptions.