
7
17 Jun. 2021 | DST/AB/014
CURTISSWRIGHTDS.COM
KAD/UBM/105
Getting the most from the
KAD/UBM/105
Each of the 12 bus connections can be independently
selected as RS-232, RS-422 or RS-485. For RS-232 (single
ended), use a DATA(x)+ pin and leave the corresponding
DATA(x)- pin unconnected. Both data pins are required when
a differential mode is selected (RS-422 or RS-485).
The following figure shows how to optionally terminate the
RS-422 and RS-485 receivers by using the internal
termination resistor provided on the module (TERM[x] pin). It
is important to ground each source of RS-232, RS-422 or
RS-485. Star grounding provides optimal noise rejection. For
details on grounding, see TEC/NOT/063 - Grounding and shielding of
the Axon and Acra KAM-500.
Figure 2: Optional RS-422/RS-485 third pin termination
Maximum message length
The maximum message length is 1,024 bytes. This length
includes the bytes used for the start pattern and the end byte
(if an end byte is used).
Parser Data Endianness example
With ABCD characters being transmitted, setting Parser Data
Endianness to:
First byte at low end of word - module outputs DW0 = AB and
DW1 = CD
First byte at high end of word - module outputs DW0 = BA
and DW1 = DC
Error codes
Parser slot count
If any channel is configured with a rate higher than 1 MHz, the
total number of parser slots that can be set up is reduced as
shown in the following table.
Packetizer format
The KAD/UBM/105 recognizes bytes as having a start bit,
data bits (seven or eight, programmable), a parity bit
(optional), and a stop bit. The KAD/UBM/105 gathers groups
of bytes into standard iNET-X parser-aligned blocks. Each
output packet can contain multiple blocks. If configured to
receive 7-bit bytes, each byte is padded to 8 bits using a zero
at the most significant bit before saving. The generalized
iNET-X payload structure for parser-aligned packets is shown
in Figure 3 on page 8 and examples of parser block formats
are shown in Figure 4 on page 9.
A parser block is created for each logical message, based on
the gaps between sequences of bytes. A new parser block is
created at the start of each iNET-X packet and also when the
time gap between successive bytes exceeds a programmable
threshold.
The gap time threshold is programmed in characters. By
setting the threshold value to just under the minimum gap
time allowable between messages (under the protocol being
used), it is possible to correctly split the bytes of the incoming
stream into individual messages, as required. If multiple
messages are received back-to-back, in a burst with no such
gap, they are packetized as a single message. Conversely, if a
single message continues past the end of one packet with no
DATA(0)+
DATA(0)-
TERM(0)
TERMINATED
DATA(0)+
DATA(0)-
TERM(0)
UNTERMINATED
CODE1
1. Error codes are in hexadecimal.
DESCRIPTION
116 Parity error.
216 Bad stop bit.
416 Last character not found in 1.024 characters (in
report word only; not in packetizer error code).
016, 316,
516, 616, 716
Reserved for future use.
MAXIMUM
BIT-RATE
CONFIGURED
AVAILABLE PARSER SLOT COUNT
<1 Mbps 511
1-2 Mbps 440
2-4 Mbps 160
4-5 Mbps 96