Jtalert Sound Files
Phuong Fulsom
The Configurer is our name for the tabbed dialog that appears when you click Config on the Entry Window top menu, and then choose Configure Ports, Mode Control, Audio, Other. The Configurer has many tabs with program settings influencing all aspects of the behavior of the program. Be careful in setting up items on the different tabs, to be sure that you understand that the option you are choosing is what you want.
Configurer settings are remembered by the program in the N1MM Logger.ini file, which is in the N1MM Logger+ user files area. Function key definitions, telnet clusters, call history, and country information are not saved in the .ini file, but in the database that was in use when you loaded them. That means, for example, that function key definitions loaded or modified when you are using one database will only appear in that database. You will need to export them from that database and load them into another database before they would show up there. The N1MM Logger.ini file contains the name of the database file you were last using, which the program will load when it is started, as well as the name of the current contest and other recently-opened contests.
This example screen shot shows a case in which three COM ports are being used. COM6 is used for radio control of an Elecraft K3. COM2 is being used for a Winkeyer for CW keying. COM10 is connected to a TNC or terminal unit for RTTY. The radio has two receivers and the program is configured for SO2V (Single Operator, 2 VFOs) with two Entry windows, one for each VFO/receiver.
Warning: At the moment, there is no provision for both controlling radio PTT via radio command and simultaneously introducing a delay before the Logger begins to send a stored message, so if you need to protect external equipment (see below) you should not use this option.
Under 32 and 64 bit bit Windows operating systems, using the parallel and serial ports for PTT and CW keying requires a special dll called inpout32.dll. This dll is installed with the Logger, but if the file is not installed for some reason, information on finding and installing it can be found in the Installation chapter.
Select which function keys to send messages. Each type of message has a combo box for you to set the appropriate function key. If the program is sending the wrong message check here first. The only restriction is that a key must mean the same thing in Running and in S&P. Function keys do not have to be unique for a selected message. There is little reason to do so although if you want it can be done. For the following messages a function key can be selected
In SO1V mode, there is only one Digital Interface window, DI-1. In SO2V and SO2R modes, there are two Digital Interface windows, DI-1 and DI-2. Each DI window is associated with one of the two Entry windows. Each DI window is opened from the Window > Digital Interface menu item in the corresponding Entry window. The Digital Modes tab in the Configurer is used to configure both Digital Interface windows.
To set up a port for a Winkeyer (or for a device that embeds a Winkeyer chip), select the COM port number that Windows has assigned to the Winkeyer, check the CW/Other check box for that port, click on the Set button, and check the WinKey check box. You do not need to change any of the other settings on the port setup dialog.
Winkeyer is fed ASCII characters from N1MM Logger (via COM or USB Ports), and converts the ASCII to timed CW. The pot speed range is from a minimum of 10 wpm to a maximum of 55 wpm. Winkeyer can also be used to control PTT. Winkeyer PTT can be used on modes other than CW. Note: This only works for Winkeyer versions 10, and 21 and greater.
If the option to ignore the speed pot has not been selected, setting the speed using the speed control pot changes BOTH the paddle speed and the N1MM sending speed. Setting the speed using the entry window changes both the paddle sending speed and N1MM sending speed but ONLY UNTIL the next time the speed pot is adjusted, i.e. the absolute position of the speed pot then overrides any changes made in the entry window.
The mode control tab determines how (and whether)the mode will be controlled on the connected radio, whether the program sets the mode when changing frequency or not, and what mode it changes it to. This dialog also gives you control over the mode used when contacts are logged.
Digital Mode Behavior is Different
There is a difference in mode control behavior between the situation where the DI window and digital engine window are open and the situation where they are closed. This is due to the way serial ports are used by the digital engines and by the Logger. The digital engines are separate processes from the rest of the Logger, and a single serial port cannot be shared between two processes. Since serial ports can be a scarce resource in a complex contest station, the Logger allows time-sharing of serial ports between digital (FSK & PTT) and non-digital (CW & PTT) uses. It does this by switching the ports between the processes depending on whether the DI window is open or not. When the DI window is opened, serial ports that have the Digital box checked in the Configurer are closed by the Logger so that they can be opened by the digital engine. When the DI window is closed, these ports are released so that the Logger can open them for use in other modes.
Thus, whether the DI window is open or closed can make a significant difference to the hardware configuration. Whenever a serial port is time-shared between the Logger and a digital engine, that port cannot be used for PTT or CW keying in non-digital modes while the DI window is open.
Once the DI window is open, changing modes on the radio does not close the DI window and the software does not switch out of digital mode, which means that radio mode-driven mode control does not work when the DI window is open. Mode changes in this state must be performed from the software. If the software is commanded from the Entry window to use a non-digital mode, the DI engine is closed by the software in order to free up any time-shared ports for the Logger to use.
For RTTY, if you are using FSK, you should normally select RTTY. If you are using AFSK, you should normally select AFSK or LSB/USB, depending on whether your radio offers a specialized AFSK mode or not.
The program uses a variety of antenna-related interfacing options, depending on your hardware and preferences. For example, antenna selection can be controlled by using a band decoder in conjunction with BCD values 0-15 on a real LPT port. Note that USB-to-parallel adapters do not work in this or other parallel port interfacing functions, because they do not allow program control of individual pins on the port.
Antenna selection can also be controlled by one of two serial port protocols, the proprietary MicroHam protocol and the Open Two Radio Switching Protocol (OTRSP). Rotators can be controlled either by using the N1MM Rotor Program, or by various third-party software packages that make use of UDP broadcasts sent by N1MM Logger+.
In N1MM Logger+, the Real-Time Score Reporting function has been integrated with the rest of the program. Instead of checking a box on the Other tab of the Configurer to start it, it now has its own tab in the Configurer.
External UDP broadcasts contain data communicated to other application programs running either on the same computer or on a different networked computer. The use that is made of the broadcast data depends on the capabilities of the receiving application program. Some examples include the sending of score data to an online score reporting website, bearing data to a rotor control program, and contact data to a general-purpose logging program (either for logging purposes or to facilitate lookup of other data available to that program). The data contents of these broadcasts are described in detail in the Appendices > External UDP Broadcasts page.
To enable external UDP broadcasts, before December 2015 some lines needed to be added manually to the N1MM Logger.ini file, This editing function has now been incorporated in the External Broadcasts tab of the Configurer, shown above. If you had been using External Broadcasts before this change, the contents of your existing External Broadcast section should be reflected on the tab. For example, if you have IsBroadcastContact=True is in your existing ini file, then the Contact box on the tab should be checked.
To set up your UDP broadcasts, you need to decide which broadcasts to enable, by checking the relevant box, and then fill in the IP addresses and UDP ports to which you want each broadcast to go. Typically, UDP broadcasts are used to communicate with other programs, so begin by reviewing the documentation of the program you want to communicate with, to learn what port it wishes to receive data on. In most cases, the port number will be 12060, the default.
In filling in the IP Addresses and Port numbers for each broadcast, you need to put in the 4-part IP address, separated from the port number by a colon. Each IP/Port pair is separated from the next by a single space, as shown in the example on the tab.
Broadcast Data Details
When properly configured, N1MM Logger+ sends external UDP packets to other applications. Details about those packets can be found in the >Appendices >External UDP Broadcasts section of this documentation.
This command is useful only in Networked Computer mode. When checked, together with Contact, at any station on the network, that station will rebroadcast every contact that it receives to the UDP port specified. The XML format is the same as for Contact.
Spots
N1MM Logger+ sends external UDP packets about spots (including spots generated internally as well as spots received from telnet clusters) to other applications. Details about these packets can be found in the >Appendices >External UDP Broadcasts section of this documentation.