Bruker AQS, Technical Manual

Page: 8 / 54

%
%
&" #"! !$! #
replace the AUI/10Base2 ”Micro Transceiver” by an
AUI/10BaseT ”Micro Transceiver”, Part# O00744
which fits to the cable.
The Fast Ethernet will adjust itself to the 10 MHz speed of the Indy.
The console interface of CU09/10 can be connected to the Indy by the
Console cable Part# HZ10091.
Exception with Aspectstation
Attach the Fast Ethernet cable to the BNC Cheapernet connector via an
10BaseT ”Mini Hub”, Part# O001114.
The Fast Ethernet will adjust itself to the 10 MHz speed of the Aspectstation..
The console interface of CU09 can be connected to the Aspectstation by the
Console cable Part# Hz04161.
1. 3. Software Implementation
Fast Ethernet needs the
unix 970501
included in
xwin–nmr2.0
or later.
The ethernet address of the exchanged CU08 has to be cleared on the O2 by typing
arp –d spect
Suggestion
If you, nevertheless, meet problems in booting the
spect
and before you try it again, you
should expect the O2 (
ec0
or
ec1
) to be in an undefined state and type:
ifconfig ecx down
ifconfig ecx up
depending on the interface to which the
spect
is connected to.
1. 4. Problems of Point–to–Point Connection to the O2
Both link partners of a Fast Ethernet Connection exchange their abilities (10 or 100 MBit
and Half or Full Duplex) after power up and without software interaction. They decide
then for the fastest common possibility. This procedure is called Autonegotiation respec-
tively Parallel Detection.
The main interface of the O2 is only able to operate in Half Duplex and behaves like an
Hub. The secondary interface is ready for Full Duplex but there is no software support for
this on O2. The CU09/10 is able to run Half and Full Duplex.
This situation leads to an improper mode decision and to a Full Duplex link at the secon-
dary interface which can’t work.
To ensure an Half Duplex decision, the Full Duplex mode is switched off on CU09/10 by
software. This decreases the performance by at least 10 % and leads to collisions.
Furthermore, the point–to–point connection with O2 causes errors during the boot se-
quence.
This problem can be solved by connecting the O2 to the CU09/10 via an Hub or by con-
necting the CU09/10 to the main interface of the O2 (which behaves like an Hub).