Copyright: (c) Peak Systems, 2003


IGATE.INI Editor
UI-View32 IGATE.INI Editor

The UI-View32 IGATE options are configured by editing IGATE.INI.

Before UI-View32 V1.90, it was necessary to edit IGATE.INI with a text editor such as NotePad. This editor now provides an easier way to do it.

When you have edited IGATE.INI, UI-View32 will detect that the file has changed and reload it, you do not need to restart UI-View32.

PLEASE read the help before you make any changes!


Inet to RF

You use this section to specify callsigns/aliases that will have traffic, besides messages to your local stations, gated from the internet to RF. You can also use it to specify callsigns that will never have any traffic gated. NOTE - think at least twice about what traffic you gate to RF! If you misuse this feature, then you will make yourself very unpopular with the local APRS community!

You can use * (asterisk) as wildcard in the callsigns, so G4* means all callsigns starting with G4, MB7* means all callsigns starting with MB7, etc.

For each callsign you input, you must select an option from the drop-down list -

BEACONS - gate all APRS posit beacons heard from this callsign.

ALL - gate all frames heard from this callsign.

OBJECT - gate objects if their name matches this callsign.

DEST - gate all frames addressed to this destination address.

RECIP - gate all frames that are messages with this callsign as the recipient (addressee).

NONE - do not gate any traffic from this callsign, not even messages to local stations.

When you have input a callsign and selected the required option from the drop-down list, you can add it to the list by clicking the Add button, or pressing the return key when the cursor is in the Callsign text box.

To delete a callsign from the list, click on it in the list, and press the Delete key.

To edit a callsign, double-click it in the list.

NOTE - The order of callsigns in the list is significant. When checking a callsign against the list, UI-View32 starts at the top, and stops as soon as a match is found. G4IDE would match against both G4IDE = ALL and G4* = NONE, and which came first in the list would obviously make a difference whether traffic from G4IDE was gated. In general, entries for specific callsigns should be put before entries with wildcards. The order of the entries in the list can be changed by dragging them up and down with the mouse.


Setup

Port(s) and (Paths) - NOTE these settings are for traffic that is gated because of entries you put in the Inet to RF section. See below for the rules used for gating messages to local stations.

Port(s) - Specifies the port or ports on which to output the traffic. Separate multiple ports with commas. E.g. 1,2,3.

Path(s) - Specifies the unproto path(s) to use. If you specify more than one port in Port(s), then you can specify a different path for each port. You separate multiple paths with '|' (pipe) characters. E.g. RELAY,WIDE|WIDE3-3|WIDE,WIDE. Please note - The path does not include the destination address, because the destination address for gated traffic is always the address configured in the UI-View32 'APRS Compatibility' dialogue.

Use default - If this option is checked, then the unproto paths configured in UI-View32 Station Setup are used, and Path(s) is ignored.

Rules for gating messages to local stations - The port used is the last port on which the station was heard. The path used is the path configured in UI-View32 Station Setup for that port.

Max digis for local - Specifies how many digis a frame can pass through and the sender still be regarded as a local station. The default of 0 means that only stations heard direct are regarded as local. You can effectively disable the checking by putting any number greater than eight, because no AX25 frame should ever pass through more than eight digis.

No-gate aliases - If a frame has any of these digi aliases in its unproto path, then a UI-View IGATE will not pass it to the internet servers. This provides a mechanism for APRS users to stop their frames being gated to the internet via your IGATE. Separate multiple aliases with commas.

Show Inet entry point callsign - If this option is checked, then the IGATE's callsign is inserted in all frames passed to the internet servers. It is inserted as an extra digi, and is suffixed with the text specified in Inet entry point tag. Note - this option can be set via 'Insert station callsign' in  the 'APRS Server Setup' dialogue.

An example:-

G4IDE's IGATE hears this frame - G8MZX>APRS,RELAY,WIDE*:>Some text

If Show Inet entry point callsign is checked, the frame header is altered before the frame is passed to an internet server:-

G8MZX>APRS,RELAY,WIDE*,G4IDE,I:>Some text

Gate LAN to Inet - If UI-View32 is being used as a local server, and it is also connected to an internet server, then checking this option allows traffic heard on the LAN to be gated to the internet. NOTE - unless you are sure you understand what this means, do not check this option.

Gate all RF to INET - By default UI-View32 only gates APRS packets from RF to the internet, and it does not gate digipeated copies of packets heard direct. If you check this option then -

•	Non-APRS frames are gated.

•	Digipeated copies of packets heard direct, including your own packets, are gated.

This option is designed to be used when an IGATE is on a satellite RF frequency. It is recommended that you do not select this option for a normal IGATE.


Inet to RF limits

This sections is used to specify limits on the number of frames your system will gate from the internet to RF. Limits are specified for the maximum number of frames that will ever be gated in one minute, two minute and three minute periods. There are two sets of limits, one for all frames except messages for local stations, and one for messages for local stations.

When you connect to an internet server, six green indicators will appear at the top of the map window. The top row is for frames other than local messages, the bottom row is for local messages. In each row one indicator is for each time period. They will turn red if the limit for a time period is exceeded. The Statistics window shows how many frames your system has gated, and how many have been dropped because the limits were exceeded.


Convert PNTS

There is a system used in Japan called NAVITRA that sends information in $PNTS frames. UI-View32 understands the $PNTS posit frames, and can optionally convert them to normal APRS format when they are gated. This section allows you to say whether you want to convert them.

Convert PNTS Inet to RF - If this option is checked, then $PNTS posits will be converted to APRS format as they are gated from the internet to RF.

Convert PNTS RF to Inet - If this option is checked, then $PNTS posits will be converted to APRS format as they are gated from RF to the internet.