RPN digipeaters accept WIDE1-1 only UI-View Digipeater Settings - Robust Packet Network
    Respecting New n-N Paradigm and WIDE1-1 Policy

IARU 1 adopts New n-N Paradigm (New Type Digi)
In the course of the IARU Conference in 2008 discussion took place about the pros and cons of the usage of TRACEn-N versus WIDEn-N. In the end IARU decided to adopt the New n-N Paradigm for its Region 1.
Operators in European countries are requested to use traceable WIDEn-N digipeaters only and so change path settings (unproto address) towards WIDE1-1 for mobile operation and fixed stations who need for other reasons to be digipeated (i.e. no internet available & remote living area)
UI-View users must check the uiview32.ini file to make sure that UITRACE=WIDE and UIFLOOD=TRACE are updated to these values. (Original UI-View version is the exact opposite ! ). Section alias (ALIAS=) should have following alias WIDE1-1 .

Alias RELAY adjust to WIDE1-1
Digipeater setup must adjust RELAY to WIDE1-1. By doing so double transmissions of the same packets will be surpressed.

TRACEn-N adjust to SSSn-N (Rarely used in Europe)
TRACEn-N, known as function of UIFLOOD, may be modified to seperate regional areas in the APRS network. (i.e. the different European countries or special interest groups like Robust Packet Network).
In the USA this modification is used to individualize the differnt states.
To stick to Robust Packet Network, SSS might be changed to any letter code. So it is possible to create a complete unique 'Club Code':
Operators with a path setting (unproto address) RPN1-1 would just be digipeated within the Robust Packet Network. (If digipeaters are set up by Alias choice RPN1-1 to react only on those)

Yes, very unique variant but think of operation with the ISS where operators have to insert the path RS0ISS otherwise the orbiter would never answer.

Unproto Pfad (UI-View32 format)
Now that the network has been configured the operators have to adjust their unproto settings as well. See some examples:
APRS stationary - igates - digipeaters
APRS,WIDE1-1 mobile [1 hop]
APRS,RPN1-1 [1 hop] spezific interest (here: Robust Packet Network)

UIDIGI configuration
RPN to be replaced by any country or regional code if wished.

UI-View32 configuration
The form below automatically generates a part of the configuration ini-file. This part will replace the section [DIGI_OPTIONS] in the uiview32.ini file. This file can be found under:
C:\Programs\Peak Systems\UI-View32\UIView32.INI
This new configuration makes sure that the traceable WIDEn-N setting will be used. In addition to the relief of the network by eliminating duplicates, this traceability is a key element of improving efficiency in the New n-N Paradigm controlled APRS network.

Callsign & SSID
Special Interest Group / Country

Results of UI-View32 configuration amendment
After the configuration amendment UI-View32 digipeater setup should look like follows:
UI-View32 Digipeater Setup
TRACEn-N swaped to WIDEn-N (traceable WIDE)
WIDEn-N swaped to RPNn-N (not traceable RPN)

You have to use the full term WIDE1-1,DF8LS-10 which would give stations as well the opprtunitiy to just let themselves be digipeated by you (in the example DF8LS-10) which makes sometimes sense for stations that are too close to hear each other and that don't hear the same digipeaters in total but one specific digipeater (i.e. offroad camper on tour in Scandinavia). Further more the callsign must be part of the Aliases in order to use it as substituted Sub Alias

Unproto update
Don't forget to change unproto address to APRS (UI-View32 format)

Dupe secs

To have a closer look at what 'Dupe secs' really does the original text from the UI-View Manual is presented below

Dupe secs
Dupe secs

So different from what was said in other documentations it is not the time a digipeater listens to other digipeaters that meight have done the job already.
It is the time that a digipeater investigates within itself if it has treated a packet already. This is because the packet comes in from another digipeater shortly after which could make the own digipeater 'think' is has to take action.

So not quiet as smart as if it would check that in the first place but still a triple packet preventer.