ARIM Messaging Program for the ARDOP TNC
Logo ARIM Messaging Program v0.20 Help Logo

Introduction

ARIM means "Amateur Radio Instant Messaging" and the arim program is a host mode program for the ARDOP TNC being developed by Rick KN6KB and John G8BPQ.

A while ago I was involved in the development of the "US Edition" of the FSQCALL program. This was based on the source code released by FSQCALL developers Murray ZL1BPU and Con ZL2AFP. Among other features, it allowed the sending of short text messages to specific stations using a simple selective call feature. I saw a potential for "instant messaging" in this, so in the US Edition I tried to emphasize that use case with UI changes to make "messaging" more natural. However, the lack of Forward Error Correction (FEC) made me wish for something more.

When the ARDOP TNC project was announced by KN6KB I starting planning a host mode program that could take advantage of the connectionless FEC mode it offered. ARIM is the result. It is written in C and developed on Ubuntu Linux but should compile and run on any modern Linux installation (including Raspbian for Raspberry Pi). Using Microsoft Windows? No problem, Arim will build and run in the excellent Cygwin environment for Microsoft Windows. This lets you run arim on the same host as ARDOP_Win if you like. The only build dependency beyond the standard C libaries is the ncurses library. Arim is distributed as source code under the terms of the GPL v3.0 license. The goals of this project are:

The ARIM program is very much a work in progress and I am interested in feedback. I monitor the ardop_users Yahoo group and can be reached there, or at the arim-ham Yahoo group where files and other information will be posted.

The ARIM Screen Layout Color Coded Display Option Downloading and Installing
Configuration Rig Control/PTT Attaching to a TNC
Press 'f' to set FEC mode and repeat count Press 'h' for Help Scrolling back the Monitor View
Press 'r' to toggle the Recents view Change the Calls Heard timestamp format Press <ESC> to abort send or receive
Using the command line Sending an unproto message Sending commands to the TNC
Sending a message (to TNC) Composing a message (to outbox) Working with the message inbox
Working with the message outbox Working with sent messages Reading messages
Querying another station for information Retrieving files from another station Working with the files folder
Reading files Beaconing Using message send repeats
Viewing and changing TNC settings Logging  

The ARIM Screen Layout

The ARIM screen is divided into different sections. Some of these can host more than one "view". The current view is identified by the title at the bottom of these sections.

ARIM

  • Title Bar This includes ARIM version and TNC attach status.
  • Traffic Monitor View This usually displays inbound and outbound ARIM and ARDOP frames. The different frame types are identified by a letter code:
    • [B] indicates an ARIM beacon frame.
    • [M] indicates an ARIM message frame.
    • [Q] indicates an ARIM query frame.
    • [R] indicates an ARIM response frame.
    • [A] indicates an ARIM ACK frame.
    • [N] indicates an ARIM NAK frame.
    • [I] indicates an ARDOP ID frame.
    • [U] indicates an "unproto" (non-ARIM) ARDOP FEC or ARQ frame.
    • [E] indicates a bad ARDOP frame.
    • [!] indicates a bad ARIM frame.
    The direction of data flow is shown by the << (outbound) and >> (inbound) arrows. A 250 line scrollback buffer allows review of past traffic. Outbound frames sent from arim to the TNC are printed in bold text to make them stand out. To enable timestamping of frames in the monitor view set the mon-timestamp parameter in the [ui] section of the arim.ini file to TRUE. This area is also used for:
    • Listing the message inbox contents in response to the li command.
    • Listing the message outbox contents in response to the lo command.
    • Listing sent messages in response to the ls command.
    • Listing the file folder contents in response to the lf command.
    • Displaying the FEC Control Menu in response to the 'f' hot key.
    • Displaying the Help contents in response to the 'h' hot key.
    Any of these secondary views can be closed by pressing the 'q' key. When view titles are enabled these views will be identified by their title at the bottom of the monitor view area.
  • TNC Command/Response View This usually displays the stream of TNC asynch responses when attached, together with any commands sent to the TNC by the operator. TNC commands are sent by pressing SP for the command prompt, and prefixing the command with the ! (bang) character. The direction of data flow is shown by the << (outbound) and >> (inbound) arrows. Outbound commands sent from arim to the TNC are printed in bold text to make them stand out. This area is also used for:
    • Listing recently received messages in response to the 'r' hot key.
    • Composing multi-line messages in response to the 'sm' and 'cm' commands. The message is entered line by line at the command prompt and displayed here.
    • Displaying messages from the inbox or outbox in response to the rm command.
    Any of these secondary views can be closed by pressing the 'q' key.
  • Command Line Press <SP> to open a command prompt here. Commands can be directed to the TNC (if attached) by prefixing them with the '!' character. Text prefixed with the ':' character is sent over the air as "upproto" ARDOP FEC frames if attached to a TNC. Unproto transmissions allow interoperation with stations using ARDOP Chat FEC mode.
  • Calls Heard List Here are displayed the callsigns of stations heard on the air, listed in reverse chronological order (most recent first). Each entry also shows the frame type and time heard. Time heard can be either last time heard, indicated by "(LT)" in the list title, or elapsed time since last heard, indicated by "(ET)". The format is HH:MM:SS for last time heard, and DD:HH:MM for elapsed time.
  • Status Bar A hot key menu appears here normally but status and warning messages appear here temporarily also. At the far right is a group of status indicators:
    • ARIM/TNC status indicator - format is I/B:T/R where ARIM state is either I (idle) or B (busy) and TNC state is either T (transmitting) or R (receiving). When busy, new transmissions are blocked. However, pressing the <ESC> key when busy will cancel the current operation and return ARIM to the idle state so that a new message or query can be sent immediately.
    • FEC mode and repeat count indicators - format is fecmode:fecrepeat. These can be changed by pressing 'f' to open the FEC Control Menu and selecting new values.
    • Beacon status indicator - shows the beacon interval time in minutes, or "OFF" if disabled. Use the btime command to change the beacon interval time.

Color Coded Display Option

Color coding can be enabled by setting the color-code parameter in the [ui] section of the arim.ini file to TRUE (the default). When this is done elements in the traffic monitor view, calls heard list and TNC command view are color coded to highlight the different frame/command types and group related traffic flows together.

ARIM

The traffic monitor view and TNC command view reflect very different types of information so different color coding schemes are used for each. The calls heard view is just a reflection of information in the traffic monitor view and uses the same color coding conventions.

  • Traffic Monitor/Calls Heard ARIM frame types are color coded according to frame type and the callsign to which they are addressed. This makes it possible to distinguish traffic sent to or from the TNC call or net call from other traffic appearing on the monitor view. Outgoing frames are distinguished from incoming frames by use of a bold font.
    • ARIM Message/Ack frames (mycall) [M] and [A] frames sent to or from the TNC 'mycall' callsign are colored green.
    • ARIM Message frames (netcall) [M] and [A] frames sent to or from the TNC 'netcall' callsign are colored cyan. This makes net traffic stand out in the traffic monitor view.
    • ARIM Query/Response frames [Q] and [R] frames sent to or from the TNC 'mycall' callsign are colored yellow.
    • ARIM Nak frames [N] frames sent to or from the TNC 'mycall' callsign are colored red.
    • ARIM Beacon frames [B] frames sent or received from any station are colored magenta.
    • ARIM Error frames [!] frames addressed to the TNC 'mycall' or 'netcall' callsigns are colored red.
    • ARDOP ID frames [I] frames sent or received from any station are colored blue.
    • ARDOP Error frames [E] frames sent or received from any station are colored red.
    • Other frames All other monitored frames are colored white. This includes various ARDOP frame types (e.g. ARQ frames) and ARIM frames not addressed to the TNC callsign or net callsign.
  • TNC Commands TNC command are distinguished by function and direction of travel. This makes it easier to follow the interactions between the arim host program and the TNC and recognize the TNC state changes seen in the asynchronous response stream.
    • Commands from Host to TNC These are bolded and colored cyan.
    • Asynch Responses from TNC These are color coded as follows:
      • PTT TRUE asynch responses are colored red.
      • PTT FALSE asynch responses are colored green.
      • BUFFER status asynch responses are colored yellow.
      • BUSY status asynch responses are colored magenta.

Downloading and Installing

The prerequisite for arim is the ARDOP TNC. Two versions are available, ardopc for Linux and ARDOP_Win for the Windows. Starting with v0.18, ARIM is compatible with ARDOP TNC versions 0.9.0 and higher ONLY; it will NOT work with earlier versions. Information about downloading and installing these is found here:

Next, you need to either build arim from source or download a precompiled binary package. To build from source, download the source code tarball:

Current ARIM Version 0.20 source and help file

To install extract the files into a directory of your choice: tar xzvf filename. This creates the arim directory containing source code files, a makefile, a model arim.ini file and two child directories: files for shared files and help containing this help file.

To build, cd into the arim directory and run make. You will need the gcc compiler and the ncurses development libraries and headers (ncurses-dev on Linux/Raspbian and libncurses-devel on Cygwin). See the INSTALL file included with the source code for more information.

To configure, open the arim.ini file in a text editor and edit as needed. You must define at least one TNC, by setting callsigns, grid square, TNC IP address and port number and name.

To run, cd into the arim directory and type ./arim.

If you prefer to install precompiled versions of arim, here are download links for 32 and 64-bit Ubuntu Linux (and derivatives like Linux Mint), Raspbian (on Raspberry Pi) and 32 and 64-bit Cygwin for Windows:

Current Version 0.20 binary and help file (32-bit Ubuntu Linux)

Current Version 0.20 binary and help file (64-bit Ubuntu Linux)

Current Version 0.20 binary and help file (Raspbian on Raspberry Pi)

Current Version 0.20 binary and help file (32-bit Cygwin on Windows)

Current Version 0.20 binary and help file (64-bit Cygwin on Windows)

If you plan to run arim in the Cygwin environment on Windows, then Cygwin must be installed first. The installer for Cygwin is found on the Installing and Updating Cygwin Packages page and this Cygwin Walkthrough and Beginner's Guide may be helpful in getting started.

When using Cygwin, you will work in the Cygwin Terminal. A shortcut to the Cygwin Terminal should be placed on your Windows desktop by the Cygwin installer.

To install extract the files into a directory of your choice: tar xzvf filename. This creates the arim directory containing the executable file, a model arim.ini file and two child directories: files for shared files and help containing this help file.

To configure, open the arim.ini file in a text editor and edit as needed. You must define at least one TNC, by setting callsigns, grid square, TNC IP address and port number and name.

To run, cd into the arim directory and type ./arim.

Configuration

ARIM reads an "ini" format configuration file named arim.ini at startup. This file must be in the same directory as the arim executable file.

ARIM

Multiple TNCs can be defined. A subset of the ARDOP TNC parameters are initialized here, but these can be overridden from the TNC command line after the program starts. Most options have reasonable default values which are used if they are not found in the .ini file.

Rig Control/PTT

The ARIM program has no rig control features! It depends on the rig control features embedded in the ARDOP TNC.

  • ARDOP_Win: Choose "Optional Radio Setup" from the File menu. This opens the "Radio Settings" dialog where you may configure rig control. Be sure to check the "Enable TNC Control of Radio or PTT" box at the bottom of the dialog.
  • ardopc: Starting with version 0.8.3.1-BPQ ardopc supports PTT. According to the announcement:
    I've added hardware PTT to this version. All support PTT via the RTS line on a serial port, and the PI version also supports PTT on PI pin 11 (GPIO Pin 17). This is enabled by adding a 4th parameter to the ardopc command line, e.g.
    ./ardopc 8515 hw:1,0 hw:0,0 GPIO
    ./ardopc 8515 hw:1,0 hw:0,0 /dev/ttyUSB0
    ardop_ptc 5 0 0 com1

I use VOX on my rig and it seems that Signalink cards work too. In both cases the VOX hold or SignaLink DLY must be set to minimum.

Attaching to a TNC

Make sure the ARDOP TNC is running. Press the spacebar to open the command prompt.

ARIM

Enter the att command, a space and the TNC number, eg. att 1. The TCP connection will be made and initialization commands from the program to the TNC will scroll by in the TNC Command view. The title bar will display the number and name of the attached TNC.

To detach from the TNC, open the command prompt and enter the det command.

Scrolling back the Monitor View

A 250 line scrollback buffer allows review of past traffic. Press the UP or DOWN arrow keys or the PAGEUP, PAGEDOWN, HOME or END keys to start scrolling.

ARIM

The status bar is updated to indicate that scrolling is active. This state persists unless you stop using the movement keys for more than 30 seconds or press 'c' to cancel. Until then the view won't auto-scroll to the end when new traffic is posted.

Press 'f' to set FEC mode and repeat count

Press the 'f' hot key to open the FEC Control Menu in the monitor view area.

ARIM

Press a key to select one of the options. All FEC modes are listed here, as well as options to set the FEC frame repeat count to either 0, 1, 2 or 3. Use the UP and DOWN arrow keys or the PAGEUP, PAGEDOWN, HOME and END keys to scroll the menu contents. Press 'q' to quit. Note that these are ARDOP settings; the ARIM message repeat count found in the .ini file is a different thing. The ARDOP FEC repeat count affects all FEC transmissions by the TNC.

NOTE: In all views, the current FEC mode and repeat count are indicated in the status bar, to the left of the beacon time indicator. The format is fecmode:fecrepeat. In this example we see mode 4FSK.200.50 and a repeat count of 0 (the default).

Press 'h' for Help

Press the 'h' hot key to open the Help contents in the monitor view area.

ARIM

Here is a listing of all hot keys and commands. Use the UP and DOWN arrow keys or the PAGEUP, PAGEDOWN, HOME and END keys to scroll the contents. Press 'q' to quit.

Press 'r' to toggle the Recents view

Press the 'r' hot key to toggle on the Recents view in the TNC command view area.

ARIM

Here is a listing of headers for messages recently received. They are numbered in reverse chronological order (most recent first). The 4 digit hex number at the end of each line is the message checksum. Use the UP and DOWN arrow keys or the PAGEUP, PAGEDOWN, HOME and END keys to scroll the contents. Press 'r' to toggle the Recents view off.

To read messages from the Recents list, press the spacebar to open the command prompt and enter the command rr nbr, where nbr is the message number. This opens the message viewer in the TNC command view area below.

ARIM

The message number and size in lines are shown in the Status Bar. Use the UP and DOWN arrow keys or the PAGEUP, PAGEDOWN, HOME and END keys to scroll through the message. Press 'q' to quit the message viewer and return to the Recents view.

Change the Calls Heard timestamp format

Press the 't' hot key to switch the Calls Heard list timestamp format between:

  • Time last heard (LT) in format HH:MM:SS UTC.
  • Elapsed time since last heard (ET) in format DD:HH:MM.

Press <ESC> to abort send or receive

Sometimes it's necessary to abort a transmission in progress or halt a receive operation instead of waiting for it to time out. To do this press the <ESC> key to cancel the operation and return ARIM to the idle state. When transmitting, this makes the TNC stop sending, flushes the transmit buffer, and cancels any pending message repeats. When receiving (or waiting for) an ARIM frame the time out counters are reset and any pending response is cancelled, making the TNC available for a new send operation immediately. A confirmation message will appear briefly on the Status Bar and the Busy/Idle indicator will reflect the change.

Using the command line

Open the program and press the spacebar to open the command prompt.

ARIM

There are three different uses for the command line.

Sending an unproto message

A TNC must be attached. Open the program and press the spacebar to open the command prompt.

ARIM

Prefix the message with the ':' character. Press ENTER to send the message out over the air as raw ARDOP FEC frames, rather than being formatted as an ARIM message. The message will appear in the monitor view tagged with the [U] indicator.

Sending commands to the TNC

A TNC must be attached. Open the program and press the spacebar to open the command prompt.

ARIM

Prefix the message with the '!' character. Press ENTER to send the command to the TNC. The command trace will appear in the TNC command monitor view, followed by the TNC's response if it was a query. To set a TNC parameter, follow the command with the parameter, e.g. !CWID TRUE. To query a TNC parameter, send the command without any argument, e.g. !CWID. Complete control over the TNC is available using this interface. ARDOP TNC commands are documented in the Host Interface Spec for the ARDOP TNC by Rick Muething, KN6KB and available on the Yahoo ardop_development group files area. NOTE: use with caution. Some ARDOP TNCs may not support the full command set listed in the Host Interface Spec.

Sending a message (to TNC)

When attached to a TNC, messages can be composed and sent immediately using the sm call [msg] command, where call is the callsign of the recipient and msg (optional) is optonal message text which may follow the callsign if the message is short and you wish to bypass the message composer to save time. To send a message without using the composer, press the spacebar to open the command prompt and enter the command like this:

ARIM

The message will be sent immediately after pressing the ENTER key to complete the command. For longer messages, press the spacebar to open the command prompt and enter the command like this:

ARIM

The message composer opens in the TNC command view.

ARIM

Enter the message line-by-line at the command prompt. When done, enter /ex at the start of a new line to close the message composer view and send the message on its way.

ARIM

The monitor view shows the outbound message and the inbound ACK from the recipient station.

To cancel a message enter /can at the start of a new line. This will discard the message and close the message composer view.

Note: if the TNC is busy when the message is sent, the message will be stored in the Outbox.

Composing a message (to outbox)

Whether or not attached to a TNC, messages can be composed and stored in the message outbox using the cm call command where call is the callsign of the recipient. Press the spacebar to open the command prompt and enter the command like this:

ARIM

The message composer opens in the TNC command view.

ARIM

Enter the message line-by-line at the command prompt, then enter /ex at the start of a new line to close the message composer view and send the message to the outbox. To cancel a message enter /can at the start of a new line. This will discard the message and close the composer view.

Working with the message inbox

Press the spacebar to open the command prompt and enter the li command to open the message inbox viewer in the monitor view area.

ARIM

Use the UP and DOWN arrow keys or the PAGEUP, PAGEDOWN, HOME and END keys to scroll through the message header list. Each message is given a number for use with commands. A list of available commands is printed in the Status Bar:

  • rm nbr Read message number nbr in the message viewer.
  • km nbr Kill (delete) message number nbr.
  • sv nbr fname Save message nbr to file fname.
  • fm nbr call Forward message number nbr to station call. Only available when attached to a TNC.
Press 'q' to quit the viewer.

Working with the message outbox

Press the spacebar to open the command prompt and enter the lo command to open the message outbox viewer in the monitor view area.

ARIM

Use the UP and DOWN arrow keys or the PAGEUP, PAGEDOWN, HOME and END keys to scroll through the message header list. Each message is given a number for use with commands. A list of available commands is printed in the Status Bar:

  • rm nbr Read message number nbr in the message viewer.
  • km nbr Kill (delete) message number nbr.
  • sm nbr Send message nbr if attached to a TNC.
Press 'q' to quit the viewer.

Working with sent messages

Press the spacebar to open the command prompt and enter the ls command to open the sent message viewer in the monitor view area.

ARIM

Use the UP and DOWN arrow keys or the PAGEUP, PAGEDOWN, HOME and END keys to scroll through the message header list. Each message is given a number for use with commands. A list of available commands is printed in the Status Bar:

  • rm nbr Read message number nbr in the message viewer.
  • km nbr Kill (delete) message number nbr.
  • sv nbr fname Save message nbr to file fname.
  • fm nbr call Forward message number nbr to station call. Only available when attached to a TNC.
Press 'q' to quit the viewer.

Reading messages

When in the inbox or outbox viewer, press the spacebar to open the command prompt and enter the rm nbr command where nbr is the message number. This opens the message viewer in the TNC command view area below.

ARIM

The message number and size in lines are shown in the Status Bar. Use the UP and DOWN arrow keys or the PAGEUP, PAGEDOWN, HOME and END keys to scroll through the message. Press 'q' to quit the message viewer and return to the message header view.

Query another station for information

A TNC must be attached. Press the spacebar to open the command prompt and enter the sq call query command where call is the callsign of the target station and query is one of these:

  • version Query version of ARIM program and attached ARDOP TNC.
  • gridsq Query gridsquare of target station (from arim.ini file).
  • pname Query name of attached ARDOP TNC (from arim.ini file).
  • info Query info text for the attached ARDOP TNC (from arim.ini file).
  • heard Query calls heard list of target station.
  • flist Query file list of target station. Each ARIM instance may offer text files for retrieval including "dynamic files" which return the output of a command or script.
  • file name Query file name, a file from the list obtained by the flist query. NOTE: the maximum file size is set by the max-file_size parameter in the [arim] section of the arim.ini file. At this time the absolute maximum is 8192 bytes.

ARIM

The target station will send the requested information in a response message.

ARIM

The response message will appear in the monitor view tagged with the [R] indicator. It will be stored in the message inbox for later viewing, and also appear in the Recents list.

Retrieving files from another station

Use the sq call flist query to get a list of files from station call.

ARIM

The list will be returned in the response message which is stored into the inbox.

ARIM

To see it, open the message inbox view with the li command, then use the rm nbr command to read the file list message:

ARIM

Note the name of the file you wish to get. NOTE: Static files have their size in bytes listed with the file name. Dynamic files have the (d) label listed with the file name to indicate that their size is variable.

Press 'q' to close the message viewer and 'q' again to close the message inbox view.

Now use the sq call file fname command to query the file fname from station call. NOTE: file names are case sensitive!

ARIM

The file will be returned in the response message.

ARIM

The message is stored into the inbox where it can be viewed or saved to disk.

ARIM

NOTE: the maximum file size is set by the max-file-size parameter in the [arim] section of the arim.ini file. The file list returned by the flist query is filtered so that only static files less than the max size are listed, and the output of dynamic files is limited to the max size. At this time the absolute maximum allowed is 8192 bytes. The location of the ARIM files folder is set by the files-dir parameter in the [arim] section of the arim.ini file.

Working with the files folder

Press the spacebar to open the command prompt and enter the lf command to open the files folder viewer in the monitor view area.

ARIM

Use the UP and DOWN arrow keys or the PAGEUP, PAGEDOWN, HOME and END keys to scroll through the file list. Each file is given a number for use with commands. A list of available commands is printed in the Status Bar:

  • rf nbr Read file number nbr in the file viewer.
  • ri Read the arim.ini file. Very convenient.
  • sf nbr call Send file number nbr to station call if attached to a TNC.
Press 'q' to quit the viewer.

Reading files

When in the files folder viewer, press the spacebar to open the command prompt and enter the rm nbr command where nbr is the message number. This opens the file viewer in the TNC command view area below.

ARIM

The file name and size in lines are shown in the Status Bar. Use the UP and DOWN arrow keys or the PAGEUP, PAGEDOWN, HOME and END keys to scroll through the file. Press 'q' to quit the file viewer and return to the files folder view.

Beaconing

Beaconing can be configured for each TNC by the btime parameter in the relevant [tnc] section of the arim.ini file. This parameter defines the beacon interval time in minutes, with '0' meaning that beaconing is disabled.

When attached to a TNC, beaconing can be managed using the btime and btest commands. Use btime nbr to set the beacon interval to nbr minutes, and btest to test the beacon. The beacon status indicator in the Status Bar shows the interval time when beaconing is enabled, or "OFF" when disabled.

Using message send repeats

In difficult conditions it may be helpful to enable automatic repeats of messages if they are nak'd or an ACK timeout occurs. Three parameters control message send repeat behavior:

  • send repeats - this is the number of times a message send will be repeated in the absence of an ACK response from the recipient.
  • ack timeout period - after sending a message, this is the maximum time in seconds that ARIM will wait for an ACK before repeating it.
  • FEC mode downshifting - if enabled, downshifting causes each message repeat to be made in a more robust FEC mode than the previous repeat in hopes of getting through in poor conditions. The starting FEC mode is automatically restored at the conclusion of the message repeats.
These parameters are set in the [arim] section of the arim.ini file, but can also be modified on-the-fly from the ARIM command prompt so that the operator an adapt to changing conditions. Here are the commands you can use from the command prompt:
  • srpts - sets the number of times a message send will be repeated in the absence of an ACK response from the recipient. Value must be in the range 0-5. Setting it to '0' disables send repeats. Example: srpts 3
  • ackto - sets the message ACK timeout in seconds. Value must be in the range 10-999. Example: ackto 30
  • fecds - enables or disables FEC mode downshifting when repeating messages. Value must be either TRUE or FALSE (not case sensitive, T or F are ok). Examples: fecds TRUE or fecds t
  • srset - Opens a pop-up dialog showing the message send repeat settings. Example: srset

    ARIM

To change one of these, press the spacebar to open the command prompt and enter the command like this:

ARIM

The change will be confirmed by a message on the Status Bar. When in doubt, use the srset command to check settings.

Viewing and changing TNC settings

TNC parameters are set in the [tnc] section of the arim.ini file and loaded when attaching to a TNC. However, some of these settings can be modified on-the-fly from the ARIM command prompt with these commands:

  • mycall - the TNC callsign. Useful for testing or changing SSID quickly. Example: mycall NW8L-4
  • netcall - the net callsign. Useful for testing or quick net changes. Example: netcall RRNET
  • gridsq - the grid square locator, which is contained in ARIM beacon frames. Example: gridsq DM65qf
  • pname - the TNC name, which is advertised in ARIM beacon frames, and also returned in reponse to the ARIM 'pname' query. Example: name ARIM/ardopc
  • tncset - Opens a pop-up dialog showing the TNC settings including IP address, port number, and other parameters. Example: tncset

    ARIM

To change one of these, press the spacebar to open the command prompt and enter the command like this:

ARIM

The change will be confirmed by a message on the Status Bar. When in doubt, use the tncset command to check settings.

Logging

Two logs can be enabled; the traffic log and the debug log. The traffic log is enabled by default and logs the content of all ARIM and ARDOP data frames sent and received by the TNC, with timestamping of each entry. The debug log is disabled by default. It logs all TNC commands sent and received by the ARIM program as well as exceptions encountered in operation like data wait timeouts, communication errors etc.

Set the traffic-log parameter in the [log] section of the arim.ini file to TRUE to enable traffic logging and to FALSE to disable it. Set the debug-log parameter in the [log] section of the arim.ini file to TRUE to enable debug logging and to FALSE to disable it.

Logs are kept in the logs subdirectory of the arim working directory. They are automatically rotated every 24 hours. The file name format is name-YYYYMMDD.log where name is either traffic or debug, followed by the date, e.g. traffic-20161114.log.

Copyright © 2016 by Robert Cunnings NW8L.  Last modified: 23 December 2016.