Files
RotRouter/docs/N1MM_Radio_Info.md
erikbrockoandClaude Opus 5.5 debc6650d4 add stations and an Auto tab following each station's band
Parse N1MM RadioInfo packets, map sender IPs to configured stations,
and let the front-end auto-select the rotator for the selected
station's current band.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-14 02:34:20 +00:00

7.0 KiB
Raw Permalink Blame History

Radio Info

<?xml version="1.0" encoding="utf-8"?>
<RadioInfo>
    <app>N1MM</app>
    <StationName>CW-80m</StationName>
    <RadioNr>1</RadioNr>
    <Freq>352211</Freq>
    <TXFreq>352211</TXFreq>
    <Mode>CW</Mode>
    <mycall>W1ABC</mycall>
    <OpCall>W1ABC</OpCall>
    <IsRunning>False</IsRunning>
    <FocusEntry>204626</FocusEntry>
    <EntryWindowHwnd>275678</EntryWindowHwnd>
    <Antenna>8</Antenna>
    <Rotors></Rotors>
    <FocusRadioNr>1</FocusRadioNr>
    <IsStereo>False</IsStereo>
    <IsSplit>False</IsSplit>
    <ActiveRadioNr>1</ActiveRadioNr>
    <IsTransmitting>False</IsTransmitting>
    <FunctionKeyCaption></FunctionKeyCaption>
    <RadioName></RadioName>
    <AuxAntSelected>-1</AuxAntSelected>
    <AuxAntSelectedName></AuxAntSelectedName>
    <IsConnected></IsConnected>
</RadioInfo>

Radio Info Notes

  • app is a short name of the logger program sending the packet. Examples: “N1MM”, “DXLab”, “Logger32”, “UcxLog”, “Log4OM”
  • StationName is the NetBios name of the computer that is sending these messages. It is the name used in Multi-Computer networking. Windows limits it to 15 characters. If the computer name is greater than 15 characters long, the first 15 characters will be used.
  • RadioNr is the radio number associated with a specific XML packet – in other words, the source of the information in that packet. When in SO2V or SO2R mode, N1MM+ sends two packets every ten seconds – one packet each from RadioNr1 and RadioNr2
  • Freq is the receive frequency represented as values to the tens digit with no delimiter. For example: 160 meters: 181234; 40 meters: 712345; 10 meters: 2812345; 6 meters: 5012345
  • TXFreq is the transmit frequency represented as values to the tens digit with no delimiter. For example: 160 meters: 181234; 40 meters: 712345; 10 meters: 2812345; 6 meters: 5012345
  • Mode is the logging mode and could be any one of the following: CW, USB, LSB, RTTY, PSK31, PSK63, PSK125, PSK250, QPSK31, QPSK63, QPSK125, QPSK250, FSK, GMSK, DOMINO, HELL, FMHELL, HELL80, MT63, THOR, THRB, THRBX, OLIVIA, MFSK8, MFSK16
  • mycall is the station callsign
  • OpCall is the callsign entered by the operator after OPON (or Ctl-O). Defaults to the station call
  • IsRunning represents the value of the RUN versus S&P radio buttons in the Entry Window. If you are on your CQ frequency, IsRunning will normally be True
  • FocusEntry is the Windows assigned handle of the Entry Window with program focus
  • EntryWindowHwnd allows external software to send commands to a specific EntryWindow (i.e. using AHK to send F1 to EW2 etc.)
  • Antenna is the currently selected antenna for this radio (0-63), from the Antenna tab in the Configurer
  • Rotors is the name of the currently selected rotor from the Antenna table in the Configurer
  • FocusRadioNr Receive Radio Focus or keyboard focus – the Green Dot in the Entry Window. Enables signal switching for SO2R operation, facilitating the routing of Microphone, Audio, PTT, CW signals to/from the selected radio. FocusRadioNr toggles between 1 and 2 when the program, a mouse click, or the \ key selects the opposite Entry Window
  • IsStereo enables audio switching for SO2R operation.The ` key (backquote) toggles its value between True and False
  • ActiveRadioNr Transmit Radio Focus – the Red Dot in the Entry Window. Enables signal switching for SO2R operation, facilitating the routing of Microphone, Audio, PTT, CW signals to/from the selected radio. ActiveRadioNr toggles between 1 and 2 when the program or pressing the [Pause] key selects the opposite Entry Window
  • IsSplit Transceiver is in Split VFO mode (for example: vfoA=Rx, vfoB=Tx). Not available on all – especially older – rigs
  • IsTransmitting The program (as distinct from the radio) is in transmit (True) or receive (False) mode. See IsTransmitting warning, below
  • FunctionKeyCaption The label of the Function Key that was pressed to initiate this transmission
  • RadioName The name of the radio, as shown in the Entry Window (i.e. “TS-590”)
  • AuxAntSelected is normally “-1”, until the user presses an Entry Window function key containing the {auxantsel} macro. A UDP packet containing the selected antenna number is sent once per keypress, after which <AuxAntSelected> reverts to “-1”
  • AuxAntSelectedName is normally blank, until the user presses an Entry Window function key containing the {auxantsel} macro. A UDP packet containing the selected antenna name is sent once per keypress, after which <AuxAntSelectedName> reverts to a blank field
  • IsConnected indicates whether a radio is connected. It may take some time for a disconnection (False) to be registered

The program sends Radio Info packets at 10 second intervals, or immediately after an event where any of the information in one of these fields changes (for example: user changes bands, spins the VFO dial, switches from Run to S&P, or selects vfoB).

Transmitting with <IsTransmitting> = False

The IsTransmitting tag in RadioInfo only displays as True when N1MM+ has initiated a transmission. When a transmission is initiated external to N1MM+ – for example, a microphone PTT button or CW paddle key – IsTransmitting will still be displayed as False. Be careful when using IsTransmitting to control external devices that need to know when the radio is in Tx or Rx.

RadioInfo broadcasts in SO2V

Using RadioInfo broadcasts when the Logger is in SO2V mode may require special consideration. In SO2V, packets in which RadioNr and ActiveRadioNr are different from each other should not be relied upon for information about the transmit frequency.

Explanation: N1MM+ treats the two VFOs in SO2V similarly to the way it treats the two radios in SO2R. Broadcasts with RadioNr = 1 relate to VFO A (the main receiver in most dual-receiver radios), and broadcasts with RadioNr = 2 relate to VFO B (the subreceiver in radios so equipped). In each of these broadcasts, the exported value of TxFreq is normally the same as the receive frequency (Freq), regardless of which VFO is active (as if RadioNr 1 and RadioNr 2 were two separate radios). The exception is the special case when the program is in Split mode. In this case (and only in this case) TxFreq will indicate the frequency in the other VFO to reflect the Split mode status.

What this means is that programs receiving RadioInfo broadcast packets and requiring knowledge of the transmit frequency or band (such as programs controlling amplifiers or antenna switches) must take the ActiveRadioNr into account. In SO2V mode, the TxFreq reported in packets in which RadioNr is not the same as ActiveRadioNr will generally not be the actual transmit frequency. This is not likely to be a major problem when the two VFOs are on the same band, but if the two VFOs are on different bands, the TxFreq reported in these inactive radio packets will be misleading. To determine the correct transmit frequency, when N1MM+ is in SO2V such programs should only use TxFreq from packets in which RadioNr and ActiveRadioNr have the same value.