Multi User Support

It is possible to use N1MM logger in Multi-User Multi-Transmitter operation. For this to work you need at least two networked computers with a maximum of 15. These computers need to have network interface cards. The networking protocol used is TCP/IP. The network needs a so called "Master" station. The "Master" station is the one that sets the time, connects to packet/telnet, etc. The Master station has number 0.

Features

• Maximum of 16 networked computers with one 'master' station (0-15).
• Use of standard network interface cards (NIC's).
• IP-addresses are used during configuring.
• Talk capability between networked stations.
• Automatic time synchronization.
• Pass frequency information between stations.
• Packet
  • Distributed to all connected computers.
  • The ability to send packet commands to the master station, from there it will be send out to the cluster.
• Error messages when a station can't be questioned/updated.
• The Info window gives status information and extra options.
• The Config menu has a special Multi-User Tools menu.
• Auto resync when a station comes on-line.

Configuration

Assumed is that the network is setup and working correctly so every computer can ping each other. There is no need to 'see' all the other computers in the 'Networking environment' (My Network Places etc.) but it's easy when sharing/copying/updating files. You must be able to ping every computer from every other computer before proceeding with these instructions. It is not important if the network uses twisted-pair or coax cable etc.
A network connected using the computers serial ports as being used in older DOS programs is not supported.

When using the 10.x.x.x range and using Windows XP/SP2 the subnet mask 255.255.255.0, as can be used with other Windows versions, could give a problem. Windows XP/SP2 doesn't like this subnet mask, if that is the case use as subnet mask: 255.0.0.0

• Setup all the computers
  • Setup all the computers with their radio's as if they were being used stand-alone.
    So the radio can be controlled, PTT/CW/.Wav files are working etc. Just as you like it.
  • All computers have to use the same version of the program N1MM logger.
• Only for the "Master" station
  • Packet/Telnet has to be working only on this computer.
  • Set the computer clock to the right time. Every computer will use this time!
  • This has to be station 0 !!!
• All other networked stations (not the "Master" station 0) 
• Select the Telnet window to have all packet cluster info shown (received from the master station). 
• The Packet window won't give any info on a slave computer. 
• So always the Telnet window on the slaves, no matter if you use Packet or Telnet on the master computer. 
• Set up all the stations identically before starting Multi-User mode.
• Setup the Computer numbers with their associated names on all computers
  Your window will be similar to this one. This is an example of a five computer network.

  
  

  • Go to 'Config | Edit Station Computer Names'
    • Stn # (0-15): Stn Name - Enter the station number starting with 0 for the master station. The computer name may be entered after a : (e.g. 0:15m)
      The computer name can be chosen independently from the Windows computer (NetBIOS) name.
      The "Master" station MUST BE number 0 and the others must be numbered 1,2,3 in order.
    • Computer IP Address - Enter the computer IP-address or the computer name – this depends on if the computers are using DYNAMIC or STATIC IP addresses. If you don’t know which, it’s safest to use the Computer Name when setting up this window. If the computer uses DYNAMIC IP addresses, you should always use the Computer Name. If the computer uses static IP addresses, you can use either the IP address or the computer name. Most computers that interface to the internet are set for Dynamic IP addresses. 
    • NOTE: In the above example, the 10-160m, 15m, and 80m station computers are using STATIC IP addresses, and the 20m and 40m computers have DYNAMIC IP addresses
    • To check or create your “computer name”, go to: Control Panel > System. In the Systems Properties window that opens, click on the Computer Name tab. The computer name will appear there. To change the computer name, click on the “Change” button in this window
    • Checking the IP address is a bit more complicated: Control Panel > Network Connections > Right Click on the connection that’s used to access the internet and select Properties > In the new window, go to the middle box with the slider and find the line with Internet Protocol (TCP/IP) and double click on that line. In the new window on the “General” tab, check or set your IP address.
    • If you do not use a local IP for your address, put an asterisk in the description for the node, so that the program will know not to connect to that port.
    • An error dialog will be shown when a station connects from an unexpected IP-address.
      
  • All the computers should have the same settings in the same order. Don't swap any entries!
  • A warning is shown if a blank entry has been added to the multi-computer station table. A blank entry can cause computers to not be able to connect to each other.
• 
  

  Tip: The setup information is kept in the database. Set up the contest & the Multi-User configuration info on one computer including messages etc. Copy the database to the other computers and have it all set up.

• Start Multi-User mode 
  • Go to 'Config | Multi-User Mode'.
    Clicking on this selection will enable this option.

Multi-2 support: You need to identify which station is run1 and which is run 2. There is a large blue number in the info window to remind you what you have set for that station. Set up Run radio 2 in the Multi-User Tools menu as: Set station as Run 2. In the configurer under Setup Run radio 1 to use Port 1 and Run radio 2 to use Port 2 (so not both to Both, 1 or 2)

Multi-User Tools menu

Adding and deleting QSOs all works automatically. Also that the bandmaps are filled with spots from the packet/telnet connection from the "Master" station. Below are some tools which you may use.

Go to 'Config | Multi-User Tools'

• Multi Call Stacking Options - Multiple options can be selected (one selection per set below)
• Send Freq/mode to Call Stack Target Station  Alt+I

• Send Partner F-Keys to Stack Target VFOA/Radio 1
• Send Partner F-Keys to Stack Target VFOB/Radio 2
• Send Partner F-Keys to Stack Target - Disabled

• Wipe Partner Call if Logged By Stack Target - Disabled
• Wipe Partner Call if Logged By Stack Target - Enabled

• Partner Logging - Disabled
• Partner Logging - Enabled

• Talk to another station   Ctrl+E - Send a message to one or all stations. The text sent will appear in big red letters in the messages part of the Info window from the receiving station. Enter station number (0-15 or *) followed by a space followed by the text of the message.
  Default the program places a * and behind that the band of the station who sends the message.
  • Possible station numbers
  • * - will send the message to all stations
  • 0 - send a message to station 0 (Master station)
  • 1 - send a message to station 1
  • Etc.

  Omitting the number or '*' will send the message to all connected stations. 

  

• Force Time Sync Now - Force date and time synchronization with the "Master" computer. This happens automatically at start up and every 5 minutes thereafter.
  • There are tools for resyncing your time with Internet time standards. A nice one used by N1MM logger users is Dimension 4
• Set your pass frequency   Alt+Z - Send the frequency that you would like other stations to send contacts to. The pass frequency will be sent to all your Multi-User computers currently connected. If you just want stations sent to your CQ frequency, you do not need to set the pass frequency. At the present time, the pass frequency is reset only after restarting the program. If you put {PASS 3} in one of your CW or RTTY messages, the current pass (or CQ) frequency for station #3 will be sent in the message. When sent in CW, the program will automatically substitute 'R' for the decimal point. DO NOT enter 'R' in the pass frequency.
  • Enter 0 to reset your frequency.
  • The pass frequency is shown in the first bottom pane of the Entry window when entered and in the info window .

    
    

• Send Freq/Mode to Call Stack Target Station  Alt+I -  This command was originally put in for WRTC-2006 competitors. It allows the partner station to remotely load VFO B on a target station. NB Will only work when Multi-user mode is selected.
• Log QSOs at all stations - Check this option to log all QSOs on all stations. Selected by default. All other information (packet spots, pass frequencies) are still distributed to all networked stations.
• Show Connections - Show connection info from all the networked stations.

  

  Status messages:

  • Connected - a connection has been made with that station
  • Listening - listening for the master station, no connection made (yet)
  • Error - the Master station is not there (or not in Multi-User mode)
• Reset Serial Numbers on all Stations - All qso numbers on all attached stations will be set to 0. This is an option when the contest starts to have all attached computers start with 0 even when there are 'practice' QSOs in the log.

• Resync Logs by Date - Allows a computer to gather all differing QSOs from other computers in the network for a 48 hour period.
  • Enter the start date for the resync (48 hour contests). The date and time shown defaults to the time of the first contact in this computers log. If there is no log, then it defaults to the date of the contest from the log selection dialog.
  • The contests to resync have to be the same (all computers should have selected the same contest. Example: CQWWSSB).
  • Resync only pulls QSOs from other computers to the computer where the resync is requested. The resync is not bi-directional. It does not push QSOs to other stations. This way it does not load down the other computers as much.
  • When resyncing old logs you should just have to put in the correct starting point. The contacts must be logged with the correct station number (which is in the database). I.e. Station 0 will only send QSOs that are recorded for station 0. Station 1 will only send QSOs that are recorded for station 1.

• 

• Resync Last n Hours - Allows a computer to gather all differing QSOs from other computers for a period. The period is set in hours. For more info about resync see 'Resync Logs by Date'.
• Rescore last N Hours - Rescore the last N hours for the current contest. It may be run at any time but is rather slow.

• Trace Multi-User Messages - Check this option to trace the Multi-User messages send and received by the station to a trace file (*.TRC). A file name can be entered. This option is normally only used for error/bug tracking.
• Force Other Station to Stop Transmitting When I Transmit - Option to force other station to stop sending.
  • In M/2 and Multi-Single it stops other stations with the same run1/2 selection.
• Don't automatically change to S&P mode  - This option disables automatic change to S&P when QSY. Useful when there is more than one radio on the same band.
• Set station as Run 2 - Set this station as the Run 2 station (when in M/2).
• Don't work non-mults - Do not this allow computer to log non-multipliers. Also giving CQ on this computer/radio is not allowed when selected.
• Show Computer Name _ IP Address Info - Shows computer name and IP address info by running the program 'IPCONFIG /ALL'

Information

The picture below shows the bottom part of the Info window where multi user information is displayed. Right clicking on the green/red icons will show a menu. See the Info window for more information.

• Connection status:
  • Green- Connected
  • Red - Not connected
  • Light red - Connection in progress or connection lost, the program will try to solve this situation..
• Station name
• Pass frequency - clicking the pass frequency will send a message to the selected station. If the selected station is your own computer then the left VFO frequency will be changed to the current pass frequency.
• Is he running or S&P
• Who is the operator
• Rate information
• Run/pass frequency

Rules

The following 'smart' rules for run/pass frequency are implemented.

• Running
  • I'm on & running
    • If the running check box is checked, always send to run frequency.

• Not running
  • I have a run frequency, but I'm chasing a multiplier.
    • The run frequency holds for 1 min, then gets zeroed.
  • I'm not running, and I have a pass frequency way up the band.
    • The user will have to specify the pass frequency.
  • Don't pass, my pass frequency is no good.
    • I guess it is the operators responsibility to zero the pass frequency.
      Maybe a timer to remind if no QSOs on pass frequency for n minutes?
    • This is not yet implemented
  • Don't pass, my CQ frequency is no good.
    • Timer with no CQ's or QSOs on run frequency for 1 min?
    • This is not yet implemented

Displaying rules

Running - Show the run frequency

Not running - Show the pass frequency if non-zero, if no pass frequency then show last CQ frequency if non-zero.

Macro keys

Macro key substitution is supported by most programmable buttons in the program. For Multi-User mode there are a few specific macros which can be found on the macros chapter .

Features

• Call stacking: Call stacking between computers, enter a callsign on a remote computers 'stack'.
  • To indicate which station you want to stack for, right click on it's "cue-ball" in the info window, and select the option "Target for call stacking".
  • A maximum of one callsign can be stacked. If the stack is empty another one may be stacked.
• Prohibit transmitting
  • If another station is sending single operator or multi-one don't allow sending if another station is sending
  • If another station is sending multi-two or multi-multi don't allow sending on same band.
  • See also the option in the Multi-User tools under Config: Force Other Station to Stop Transmitting When I Transmit

Where to place the database files

Do NOT share the log on a server, place it locally on your hard disk.

• Sharing logs on a server will MOSTLY not work.  Mostly is not good enough. You will think you are ok, but are not. I do not check for Multi-User temporary errors. The program was NOT designed nor tested for this.
• Having the log on every PC provides redundancy, which is important in an RF-filled environment.
• It will not perform as well. Local access is almost always faster.

There is no harm in using a server to aid in copying files.  The mdb files are simply files. They may be moved around.  It is best to close the program before moving them, as with any program writing to an open file.

Other info

• Deleting QSOs made by another station in a Multi-User situation is not allowed, a warning message is shown.
• Station 0 sends all incoming spots to every station so the bandmaps are being filled. Use the Telnet window (not the Packet window) on the other computers in the network. If you send a message to the packet cluster from any station in the network it will be sent out to packet/telnet via computer 0. The received answer from the packet cluster will be send out on the network to all stations.
• The program can't be shutdown while initializing Multi-User otherwise unpredictable situations could occur.
• You will be prompted for the operator call if it has not been entered (with Ctrl+O).
  Periodic warning message will be shown if no operator has been specified
• The CQ/pass frequencies will be requested at startup.
• When going through the possible contests you will see a "contest" DELETEDQS.
  This is not a contest but deleted QSOs will be moved here by the program, this is especially for Multi-User support.
• Connection status is shown at the bottom of the info window.
• A connection is checked every 10 seconds.
• All connections are stopped/started when the database, the contest or the connection list is changed.
• Also Non-master stations are allowed to close telnet/packet ports.
• Time synchronization is only shown on the master station.
• If you Mark or Store spots on a local machine, they will be Marked or Stored on all other machines.
• The station name prefixes telnet/packet commands that are displayed. The prefix is not sent to the cluster. Example: [20M] sh/dx.
• When a connection drops out it will try to reconnect every 30 seconds.
• Note that Multi-Two MUST use Multi-User mode and keep run & mult station numbers the same throughout the contest. This is to keep the radio number in the Cabrillo output consequent. Cabrillo only outputs a radio number when using multi-two or multi-multi.
• Any station that is harmonically related with the frequency will be colored red in the Info window.
• For single operator and multi-one, the operator callsign will be colored red when transmitting.
• Group edits are not allowed in the Log window while in Multi-User mode.
• If on a station is selected 'Config | Multi-User tools | Don't use non-mults' giving CQ is not allowed.
• Only the master station will auto-reconnect to packet/telnet when enabled.
• Ctrl+Alt+M changes the run station number

Example Multi User setup

The example below uses file sharing and Netbios lookup for computer (you can see them in the Networking environment). This is not necessary for N1MM logger to work in Multi-User. When the computers can be 'pinged' from both sides this is enough to work. All lines with a * are not necessary to work but are nice to have for other purposes like updating of files etc. This does not mean that the action mentioned should not be done. It can also be done via other media (CD / diskettes). In that case the Windows network is not used, as the N1MM network is using the TCP/IP stack only.

Before the contest

Master computer:

• Enable File sharing for Windows networks (*)
• Enable "sharing" on master hard disk (*)
• Have all installation files ready on master (*)
• Set Master IP address according to Station Computer Names list (see below).
  • This could include a restart and a request for the Windows CD.
  • Note previous IP setting for restoration after contest.
• Note master Windows computer (NetBIOS) name & workgroup (*)
• Start N1MM Logger.
• Select a new empty database (e.g. PACC2003.MDB) on master.
• Start a new log for the contest (e.g. PACC) (check manual).
• Configure Function keys (SSB/CW/Packet).
• Edit Station Computer Names according to plan, e.g.:
  • Stn#:Stn Name Computer IP Address
  • 0:master 192.168.10.10
  • 1:160M 192.168.10.1
  • 2:80M 192.168.10.2
• Load the relevant country file (e.g. CTY-PACC.DAT) (Tools menu).
• Select the Master.dta file to use ('File | Choose Which Contest to Log').
• Establish DX cluster communications on the master computer (Packet or Telnet).
• Setup or disable internal firewall.

Non-master computers:

• Install Network card& TCP/IP when not already done.
• Setup or disable internal firewall.
• Enable File sharing for Windows networks (*)
• Set IP address according to Station Computer Names list.
  • Windows 95/98/ME: might include a restart& Windows CD.
  • Note previous IP setting for restoration after contest.
• Find master on the Windows network (*)
  • Use Search Computers in Network Neighborhood/Places using the masters Windows computer (NetBIOS) name).
• Install/Update N1MM Logger.
  • Copy from master via network (*)
• Copy database (eg.PACC2003.MDB) from master on this computer.
  • Copy from master via network (*)
• Copy WAV directory from master on this computer.
  • Copy from master via network (*)

All computers:

• Start N1MM Logger.
• Import windows settings.
• Open database (e.g. PACC2003.MDB) ('File menu) | Select: PACC log')
• Set Multi-User on.
• Setup configuration (Rig control, PTT, CW)
• Turn off Windows sounds if using WAV files.
  • Control Panel - Sounds - Scheme: No Sounds

Always:

• Make sure you are running the same version of the program on all computers.
• Make sure you are using the same contest on all computers.
• Make sure that all computers have the same time zone and daylight savings offset.
• Preferable, see if all computers have the same regional settings for numbers, dates, currency, etc.
• Preferable, see if all computers have the same short and long date and time formats.

During the contest

• Check master time setting regularly
  • Use Internet time server if possible so it is done automatically.
• Observe network status, and reconnect/resync if necessary on all computers.
  • Note that a resync only imports QSOs to the computer you import from! The computer where the import comes from is not being updated with the log from computer where you import to.

After the contest

• Make sure all used computers are connected.
• Do a resync on all computers.
• Check QSOs/multiplier status on all computers & compare.
• Copy & compact database (e.g. PACC2003.MDB) to backup directory.
• Restore IP settings & Windows sounds scheme on borrowed PCs.

Multi-user log synchronization

Multi-Multi Distributed - Multi User via the Internet

It is possible to setup some or all of the other stations outside your LAN on the internet. A use for that might be for one station away from the contest station to connect the contest station, and spot stations on a band privately so that only his operators could see them.  This was done in years past with spotting nets, and then packet nets. It is not done so much today.  Much more than this would violate the spirit, if not the letter of the rules.

There are some caveats when trying this. You need more than basic computer knowledge for this. You need to know about IP-addresses, firewall's, routers, port settings, NAT etc.

You need to know your computer (external) IP-address. When directly connected to the web this can be obtained using the program ipconfig.exe (NT, 2000, XP) or winipcfg.exe (98, ME). This command 'Ipconfig' should be entered in a DOS window to see the output. When your computer is in a LAN your connection to the internet will probably be made via a router. All computers will use internal IP-addresses, the router uses the external IP-address. This link will give your (external) ip-address in both cases: http://megawx.aws.com/support/faq/software/ip.asp

When a Multi-User connection connection is not working anymore check the IP-addresses. This address changes from time-to time (when dynamic). Mostly after a reboot from the PC when directly connected or a reboot from your router when in a lan.

The router should be setup to route incoming traffic to your PC IP-address. No port transformation should be done. Instructions for this will not be given in detail. With the many different kind of routers this can not be done. Remember, this is a specialist job!

The used incoming port is equal to 12070 + Station Nr (0-15) to allow port forwarding in routers. 12070 is used for the first PC in the list, 12071 for the second etc.

Firewall - Open port 12070 + Station Nr (0-15) for incoming traffic.

Router - You probably should use NAT to route incoming traffic on port 12070 + Station Nr (0-15) to your PC IP-address.

'Config | Edit Station Computer Names'

• Computers using N1MM logger in the local network need to use the local IP address, computers outside the local network need to use the external ip-address from the external network. The router on the external network should use port forwarding to the correct computer using N1MM logger.
• Example setup:
  • The address 192.168.1.11 is the local IP-address at my end (PA1M).
  • The first two entries are two instances of N1MM logger on two different PC's from Tom (N1MM).
  • Example 'Port redirection table' in the router used at PA1M, the given names differ per router brand:
    • Service name : N1MM (does not matter)
    • Protocol: TCP
    • Public Port: 12072
      • 12072 = 12070 + 2, my local pc which needs to be connected from the 'outside'
    • Private IP: 192.168.1.11
    • Private Port: 12072
    • Active: Yes
  • NB the IP-address given in this example is not the IP-address used by Tom, N1MM anymore :-)

The latencies when we tested were in the 100 mSec range.

The list of IP addresses needs to be different on each machine. Make sure the remote machine has its external IP address, and the local machine(s) has its internal address.

Example at PA1M: 0:N1MM 64.252.138.65 1:PA1M 192.168.0.1

Example at N1MM: 0:N1MM 192.168.0.1 1:PA1M 63.133.11.55

A good legal use for this within todays rules would be for remote spotting stations that could check for your station needs before stacking a spot for you. This could give guys stuck at home without much of a station some way to contribute to a multi-op.

The purpose of this is to support IARU HQ stations, and to perhaps inspire a new entry class like "multi-multi distributed". I think it would add a lot to the experience of smaller stations to be able to participate in a Multi-Multi-Distributed effort and get some of the comraderie that comes with Multi-Multi operation. Maybe not, but without trying, how will we ever know? And anyway it interests me, and I do this for fun...

It is a neat idea to have the 10m station in OA, 15m in 6W, 160m in TF etc.

Do we need a new category like Multi-Multi Distributed?

Most rules have provisions that the stations need to be on the same property, and be connected by wires, or be separated by no more the 500m? I think the IARU HQ is the only contest where they look the other way in that regards. In most other contests this will probably be illegal unless of course you create your own contest category (MMD). Maybe only as a demonstration one year (and send in as check log) just to test the technology.