Configure Status

The status message is what is transmitted in the background by YAAC to further describe your station beyond the information included in the beacon (position) message, per the APRS specification 1.0.1, section 16. The status message configuration panel looks like this:

The options that can be set for the status message are:

• Whether the station message is to be transmitted at all. Note that enabling sending a status message without any payload in the message just wastes channel time for everyone, so if your status text is empty for enabled status messaging, you will be warned and required to confirm you wish to do this before the changed status is saved.
• Whether an automatic Maidenhead-format location or timestamp should be prefixed to the message.
• The actual status text to be sent, and (if Maidenhead is selected), what APRS symbol should be appended to the Maidenhead locator. The status text can include references to macros using the syntax {M:macroname} inserted in the status text. At status transmission time, the macro references will be replaced in the transmitted status with the current values of the named macros. If a referenced macro is undefined at transmission time, the reference will be replaced with nothing at that point in the text.

  Note that specifying Maidenhead location prefix will be cross-checked against the enabled regular position beacons; this is because, due to the limited precision of a Maidenhead "square" (2.5 minutes of latitude and 5 minutes of longitude), your station location may appear to jump back and forth if specifying location both by standard APRS position reports and by the Maidenhead location in the status message. If the difference between the two locations is more than either 0.5 minutes of latitude or longitude or your configured position ambiguity (whichever is greater), you will be warned of the issue and asked if you really want your station position jumping back and forth when saving the changed status information.

• Which digipeat paths should be used for the status message. Several standard choices are provided (including the path of no digipeat aliases at all), but other custom paths may be entered in the User-Defined Digipeat Path text field. If more than one path is selected, they will be used alternately by the proportional pathing algorithm (each lower path used half as often as the path before it).
• Whether meteor-scatter (continuous packet burst) mode should be used. This is only applicable if the RF transmitting port is configured for timeslotting.
• What transmission intervals the status message should be transmitted at. This overrides the application-wide defaults set on the configuration dialog's Transmit tab. Note that if a port the status message is being transmitted through is using timeslotting, the transmit will not actually occur until the next timeslot after the scheduled status transmit time.

None of the changes are stored until the Save Changes button is pressed.