 | <num> baudrate (on internal clock) |
| "d" fullduplex (halfduplex is default) |
| "t" external TX Clock (depends on hardware) |
| "r" external RX Clock (depends on hardware) |
| "z" NRZ mode (depends on hardware, NRZI mode is default) |
| "c" KISS: CRC mode; HDLC: Soft-DCD (depends on hardware) |
| "m" DAMA master |
| "s" synchronize channel with
other "s"-channels |
| "u" user port - sets generic user port
options. |
| "y" auto sysop: Stations which connect on this port without digipeaters in
their path are automatically sysops. |
| "-" deactivate port |
| "." dummy, if there are no arguments needed on special hardware |
The parameters baudrate, "d", "t", "r", "z" and
"c" depend on hardware. Check out the hardware or driver documentation.
Examples:
MODE 3 19200d ;port 3 19200 baud fullduplex
MODE 3 38400trz ;port 3 38400 baud ext. clock, NRZ
MODE 3 - ;special case: turn off port 3
When a MODE command is entered, all Layer1 modules of all channels get
initialized. This is not problematic, only frames currently being transmitted or received
are involved. QSOs are not affected. A Mode-Command may re-initialize "hanging"
SCCs. Therefore you should always try a Mode-Command first before a RESET or RESTART since
all QSOs get lost in this case. The port number is not relevant, a "MO 11" will
do the job.
Turn off port y
On this port, you will always be sysop as long as there are no
digipeaters in your path. For security reasons, on RMNCs this may only be set in the MRMNC
compiler. On these ports the loop detector is inactive.
ATTENTION: This attribute should only be set on local(wired) links.
Even here, it must be impossible to connect back to the node, otherwise everything can be
reprogrammed freely.
C Only relevant in KISS mode: Force CRC mode. On some PC/Flexnet drivers: Activation of
software DCD.
S Channel synchronization (see separate discussion)
U This port is a user port. Activates following features (on RMNC fullmaster only
partially implemented):
• Port never goes into DAMA-Slavemode
• TxDelay-Measurement (see separate discussion)
• If in DAMA mode: Disconnect of users who poll the digi several times (i.e. they are
no proper DAMA slaves)
If a connection is interrupted due to one of the conditions above, a warning message is
issued, but only if the user is connected directly, i.e. without any digipeaters in the
path.
