Scannex ip.buffer, Руководство пользователя

Страница: 67 / 152

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
10.1.3. When using a Y-lead
Firmware 2.91 and later
The ip.buffer detects that it is in a Y-lead configuration and will wait until data is
transmitted before deciding on the DCE/DTE mode 8 . The ip.buffer will show
“
Rx pin: Both – analyzing
” while waiting for the data to start, and “
Rx pin: 2-
Y
” or “
Rx pin: 3-Y
” when completed.
If the transmitting device requires handshake lines to be asserted from the ip.buffer to
transmit, then you may need to force the DCE/DTE orientation in the ip.buffer.
Firmware 2.90 and earlier
If the ip.buffer is connected in parallel to another logging device the ip.buffer will see two
transmit lines (one from the device being logged, and one from the other device). In this
case, depending on which logging device is connected first, the ip.buffer may not be able
to decide which pin to log data from
9 .
There are two solutions:
1. Cut all pins other than the ground and transmit on the cable that connects to
the ip.buffer. The ip.buffer will always get it right.
2. Force the DCE/DTE of the ip.buffer. You can determine which way round it
should be by temporarily unplugging the secondary device. Then force this in
the Serial port’s Source page. (The Rx/Tx setting.) Once you have forced the pin
out, the secondary device can be reconnected.
If two Scannex devices are connected using a Y-lead (e.g. Neip.buffer
or ip.ip.buffer) then please email Scannex for extra instructions and
suggestions.
8 The first character sent will be lost as the ip.buffer has to enable the DCE/DTE mode.
9 If the ip.buffer is set to “Auto”, and sees two transmit lines it will default to the standard PC pin
out (a DTE).
Page 63
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
10.1.3. When using a Y-lead
Firmware 2.91 and later
The ip.buffer detects that it is in a Y-lead configuration and will wait until data is
transmitted before deciding on the DCE/DTE mode 8 . The ip.buffer will show
“
Rx pin: Both – analyzing
” while waiting for the data to start, and “
Rx pin: 2-
Y
” or “
Rx pin: 3-Y
” when completed.
If the transmitting device requires handshake lines to be asserted from the ip.buffer to
transmit, then you may need to force the DCE/DTE orientation in the ip.buffer.
Firmware 2.90 and earlier
If the ip.buffer is connected in parallel to another logging device the ip.buffer will see two
transmit lines (one from the device being logged, and one from the other device). In this
case, depending on which logging device is connected first, the ip.buffer may not be able
to decide which pin to log data from
9 .
There are two solutions:
1. Cut all pins other than the ground and transmit on the cable that connects to
the ip.buffer. The ip.buffer will always get it right.
2. Force the DCE/DTE of the ip.buffer. You can determine which way round it
should be by temporarily unplugging the secondary device. Then force this in
the Serial port’s Source page. (The Rx/Tx setting.) Once you have forced the pin
out, the secondary device can be reconnected.
If two Scannex devices are connected using a Y-lead (e.g. Neip.buffer
or ip.ip.buffer) then please email Scannex for extra instructions and
suggestions.
8 The first character sent will be lost as the ip.buffer has to enable the DCE/DTE mode.
9 If the ip.buffer is set to “Auto”, and sees two transmit lines it will default to the standard PC pin
out (a DTE).
Page 63