Bruker AQS User manual

BRUKER
Version
Communication
Control Unit CCU 9/10
AQS/AQX
Technical Manual
001

The information in this manual may be altered without notice.
BRUKER accepts no responsibility for actions taken as a result
of use of this manual. BRUKER accepts no liability for any mis-
takes contained in the manual, leading to coincidental damage,
whether during installation or operation of the instrument. Un-
authorised reproduction of manual contents, without written
permission from the publishers, or translation into another lan-
guage, either in full or in part, is forbidden.
This manual was written by
Jiri Tucek, Mirek Dudek
© December 10, 1998: Bruker Analytik GmbH
Rheinstetten, Germany
P/N: Z31561
DWG-Nr: 1273001

 %

  
  
 %
 &"  #"! !$! #

AQX CCU/9_4x00
AQS CCU/10_4x00
    

 %

  
  
 %
 &"  #"! !$! #


1. Starting with CU09/10 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1. 1. Special features of CU09/10 1. . . . . . . . . . . . . . . . . . . . . . . . . . . .
1. 2. Hardware Implementation 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1. 3. Software Implementation 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1. 4. Problems of Point–to–Point Connection to the O2 2. . . . . . . . . .
2. Specifications 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2. 1. Former AQX CCU Versions 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2. 2. Former AQS CCU Versions 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2. 3. Features 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2. 4. Construction 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2. 5. Part numbers of AQX CU09 P/N H2570 7. . . . . . . . . . . . . . . . . .
2. 6. Part numbers of AQS CU10 P/N H9503 8. . . . . . . . . . . . . . . . . .
2. 7. Accessories for CU09/10 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2. 8. Controls and Indicators 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2. 9. Operational Settings 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2. 9. 1. NVRAM Setting 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2. 9. 2. Configuration 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2. 9. 3. Installing DRAM 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2. 10. Connectors and Signal Allocations 19. . . . . . . . . . . . . . . . . . . . .
2. 11. Power Requirements 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3. Service Information 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3. 1. Operating Conditions 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3. 2. Network connection 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3. 3. Software Implementation 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3. 4. Problems of Point–to–Point Connection to the O2 25. . . . . . . . . .
3. 5. Handling 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3. 5. 1. Ifconfig down/up Procedure 25. . . . . . . . . . . . . . . . . . . . . . . . . . .
3. 5. 2. Switching the boot interface 26. . . . . . . . . . . . . . . . . . . . . . . . . . .
3. 6. Ethernet addresses 26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3. 7. Introduction Status of the AQX CU09 CCU 27. . . . . . . . . . . . . . . .
3. 7. 1. Modifications of the introduced layout 27. . . . . . . . . . . . . . . . . .
3. 7. 2. Jumper Configuration 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3. 7. 3. Configurations of the introduced layout 27. . . . . . . . . . . . . . . . .
3. 8. Introduction Status of the AQS CCU10 28. . . . . . . . . . . . . . . . . . .
3. 8. 1. Modifications of the introduced layout 28. . . . . . . . . . . . . . . . . .
3. 8. 2. Jumper Configuration 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3. 8. 3. Configurations of the introduced layout 29. . . . . . . . . . . . . . . . .
3. 8. 3. 1. NVRAM 30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3. 8. 3. 2. Firmware 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3. 8. 3. 3. Serial Boot Prom 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3. 9. AQX CU09 CCU History of Modifications 32. . . . . . . . . . . . . . . . . .

 %

  
  
 %
 &"  #"! !$! #

3. 10. AQS CU10 CCU History of Modifications 32. . . . . . . . . . . . . . . .
4. Condensed technical Description 33. . . . . . . . . . . . . . . . . . . . . . . .
4. 1. Architecture 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4. 1. 1. Block Diagram of CCU 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4. 2. Logical References to memory and I/O devices 35. . . . . . . . . . .
4. 2. 1. Firmware 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4. 2. 2. Flash EPROM 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4. 2. 3. Onboard memory 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4. 2. 4. VME bus port 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4. 2. 4. 1. Master Port 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4. 2. 4. 2. Slave Port 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4. 2. 5. Ethernet 10BaseT 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4. 2. 6. Fast Ethernet 10/100BaseT 37. . . . . . . . . . . . . . . . . . . . . . . . . . .
4. 2. 7. RS232 Interface 42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4. 2. 8. JTAG Interface 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4. 2. 9. Real Time Clock and NVRAM 44. . . . . . . . . . . . . . . . . . . . . . . .
4. 2. 10. Configuration and Status Register 45. . . . . . . . . . . . . . . . . . . .
4. 2. 11. Interrupt Router 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4. 2. 12. CIS access 48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures
Figure 1: CU09 Controls at Front Panel 6. . . . . . . . . . . . . . . . . . . . . . .
Figure 2: CU10 Controls at Front Panel 7. . . . . . . . . . . . . . . . . . . . . . .
Figure 3: CU09 Attaching SubD connectors to
the RS232/485 interfaces 10. . . . . . . . . . . . . . . . . . . . . . . .
Figure 4: CU 10 Attaching SubD connectors to
the RS232 interfaces 11. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5: Console Cable, MINI D, 8 pin to D_SUB, 9 pin 12. . . . . . . . .
Figure 6: Front View at LED Display and Reset Button 13. . . . . . . . . .
Figure 7: Jumper, Prom and DRAM Locations for CU09 17. . . . . . . .
Figure 8: Jumper, Prom and DRAM Locations for CU10 18. . . . . . . .
Figure 9: AMP Amplimite 050, 50 pin, female 19. . . . . . . . . . . . . . . . . .
Figure 10: AMP Amplimite 050, 50 pin, female 20. . . . . . . . . . . . . . . . .
Figure 11: Mini Metral 90 pin, female 20. . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12: Console Connector at CCU, MINI D, 8 pin, female 21. . . .
Figure 13: RJ45 Pin numbering 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14: Fast Ethernet Signal Assignment 21. . . . . . . . . . . . . . . . . . .
Figure 15: Block diagram CU09/10 33. . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables
Table 1: AQX CCU versions 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

 &
$
  
  
 &
 '"  #"! !%! #

Table 2: AQS CCU versions 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3: Table of CU09 Assembly Groups 7. . . . . . . . . . . . . . . . . . . . .
Table 4: Table of CU10 Assembly Groups 8. . . . . . . . . . . . . . . . . . . . .
Table 5: Part# of Accessories 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6: CU09 Configuration of Serial Interfaces 10. . . . . . . . . . . . . . . .
Table 7: CU10 Configuration of Serial Interfaces 11. . . . . . . . . . . . . . . .
Table 8: Parameters to be set 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9: DRAM configuration 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 10: RS232 Signal assignments 19. . . . . . . . . . . . . . . . . . . . . . . . .
Table 11: Firmware Proms 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 12: Boot Prom 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 13: CU04 through CU09 predestinate
the following address map: 35. . . . . . . . . . . . . . . . . . . . . . . . .

 %
  
  
 %

 &"  #"! !$! #

1. Starting with CU09/10
1. 1. Special features of CU09/10
CU09/10 provides the same devices and connectors as CU08 except the console connec-
tor which has been changed to the same type as on Indy (Mini D, 8 pin). Therefor, the
CU08–Indy Console Cable can be used in reverse direction to connect CU09/10 to O2.
Additionally, there is the Fast Ethernet device with 2 RJ45 sockets. Only one of these
sockets can be used at a time. Both sockets must not never be plugged but this would not
result in any damage.
The standard Ethernet (10Base2 or so called Cheapernet) is available but can not be run
by the ”unix 970501” included in ”xwin–nmr2.0”. A later version will manage both
ethernet devices.
1. 2. Hardware Implementation
All CU09/10 connections can be carried out as on CU08 except the RS485 at CU10. The
Cheapernet should be left unconnected.
The Fast Ethernet of CU09/10 is to be connected to the first or second ethernet interface
on O2, the so called ec0 or ec1 (see workaround).
There are two RJ45 Fast Ethernet sockets on CU09/10. They are connected inside to the
same signals but have crossed pin assignments.
The upper socket (signed ”FETH–HUB”) has to be used if CU09/10 will be connected to
an HUB. This is the normal way with twisted pair ethernet hosts.
The lower socket (signed ”FETH HOST”) has to be used to connect CU09/10 by the
same normal cable to another host (point–to–point connection).
That means, connect CU09 from socket ”FETH HOST” to the O2 by one of the following
cables:
     
    
    
You don’t need any longer the ”Mini Hub” (Part# O001114) that you might used to con-
nect the O2 to the CU08.
The Console interface can be connected
to a Terminal by cable HZ04112 or
to the O2 by cable HZ04161.
The LINK Led (2. led from left in upper row) shows a good link status after power up.
Otherwise one of the two link partners is down by software or power. The Fast Ethernet
cable can be pulled out and plugged in under power and activity. Autonegotiation and
link checking starts on both partners without software interaction if the link has been bro-
ken.
Unplugging, powering down or typing ifconfig ec1 down on O2 or
ifconfig fen down on spect break the link.
Exception with Indy
Attach the Fast Ethernet cable to the BNC Cheapernet connector via an
10BaseT ”Mini Hub”, Part# O001114 or

 %
  
  
 %

 &"  #"! !$! #

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 ecxdown
ifconfig ecxup
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).

 %
  
  
 %

 &"  #"! !$! #

Workaround
Swap logically both ethernet devices of the O2. That means, connect the spect to ether-
net controller ec0 on the motherboard of the O2. This can easy be carried out by modify-
ing the file netif.options.
Type on O2 as superuser:
vi /etc/config/netif.options
This file contains the 2 parameter entries of if1name=ec0 and if2name=ec1. Swap the
values of both parameters to:
if1name=ec1
if2name=ec0
Type:
:wq
init5
When the O2 is shut down swap also the connections, first connection between spect
and motherboard and the second between the general net and the additional interface and
reboot the O2 and than the spect.

 %
  
  
 %

 &"  #"! !$! #

2. Specifications
2. 1. Former AQX CCU Versions
The AQX_CCU is a CPU board specially designed for use in the AQX–Rack.
CCU version CU09 is the follower of CU08 with additional features. It is based on the
same processor R4600 or R4700, the same IO–Subsystem but provides a modified
memory interconnection and an Fast Ethernet–Subsystem. The processor–to–memory
data path runs at 50 MHz and is 64 bit wide. the memory–to–IO data path is 32 bit wide
and runs at 25 MHz.
AQX Software Constrains
CCU Versions Part No. La out No. EC Level AspectStation SGI Computers
     ''+ (!
 %% )!%!*!*
     ') %+!) %% )!%!*!*
 
+'   

   &!! &#. "')  -#% '&

    ''+ (!  ') %+!)
     &!! &#. "')  -#% '&
#*$%!** +)!!  ') %+!)

 )'+'+/(!*

,( +'   &!! &#. "')  -#% '&
#*$%!** +)!!  ') %+!)
    
#*$%!** +)!!  ') %+!)
%!  -!)*#'&*
2. 2. Former AQS CCU Versions
The AQS_CCU is a CPU board specially designed for use in the new AQS–Rack.
CCU version CU10 is based on the CU09 hardware and have the same features but with
the addition it contains a new extended AQS Bus System. Therefor, can be not used in
the old AQX System Rack.
AQS Software Constrains
CCU Versions Part No. La out No. EC Level AspectStation SGI Computers
 
,( +'     &!! &#. "')  -#% '& #*$%!** +)!!  ') %+!)
%!  -!)*#'&*
2. 3. Features
Operation frequency 50/25 MHz on board, 100 MHz on chip

 %
  
  
 %

 &"  #"! !$! #

processor peak performance is 55 VAX MIPS (related on drystones)
data and instruction cache size 16kbyte each
2 mbyte firmware
2 mbyte Flash EPROM Am29F016 (2,097,152 x 8–Bit)
VME bus master interface and slave interface to the dynamic RAM
Thin wire ethernet using Am7990
Fast Ethernet subsystem, based on DEC 21140A, National’s DP83840
and DP83223 supporting 10BaseT and 100BaseTX, Half– and Full Du-
plex and Autonegotiation; (100BaseT4 is not supported)
16–,32–,64–Mbyte dynamic RAM
8 RS232 channels using Z85C230, labeled as ”console”or ”tty00”, and
”tty01,...,tty09”;
2 RS485 channels using Z85C230, labeled as ”tty10” and ”tty20”
(connectable through one 8–pin Mini–D (”console”) and two 50–pin con-
nectors (”tty01,...,tty09”) at the front edge)
real time clock MK48T02 with 2 kbyte non volatile memory
configuration register, status register, interrupt register
component identification channel to handle the AQX/AQS component
identification system (CIS)
JTAG Boundary–Scan controller brings the JTAG test bus to the
Backplane.
CAN Bus controller based on PCF82C200 (not implemented)
2. 4. Construction
The CCU is a VME Bus module of 4 TE with an extended length. It consists of one
printed circuit board.
Board Size
The real size is 233.35 mm by 280 mm . This is the so called ”Double European Stan-
dard” format with a nominal plug in depth of 280 mm.

 %
  
  
 %
6
 &"  #"! !$! #
(98/12/10)
CU09 Front View
Figure 1: CU09 Controls at Front Panel
CU09 Front Panel
Fast Ethernet connector RJ-45
10Base2 (Thin Wire) BNC connector
Reset Button
R 232 console Mini D-8
Activity LED's
TTY01-TTY05 & TTY10
TTY06-TTY09 & TTY20
10/100 BA E-T
Fast Ethernet tatus LED's
to Hub's
Fast Ethernet connector RJ-45
to Host
VME access
Memory access
10Base2 Ethernet activity
Collision occurence
Good Link status
Receive activity
Transmit activity CU09
ECL

 %
  
  
 %
7
 &"  #"! !$! #
(98/12/10)
CU10 Front View
Figure 2: CU10 Controls at Front Panel
CU10 Front Panel
Fast Ethernet connector RJ-45
10Base2 (Thin Wire) BNC connector
Reset Button
RS232 console Mini D-8
Activity LED's
TTY01-TTY05
TTY06-TTY09
10/100 BASE-T
Fast Ethernet Status LED's
to Hub's
Fast Ethernet connector RJ-45
to Host
VME access
Memory access
10Base2 Ethernet activity
Collision occurence
Good Link status
Receive activity
Transmit activity CU10
ECL
Note: TTY10 and TTY20 are available on the A S backplane X3 connector.
2. 5. Part numbers of AQX CU09 P/N H2570
Table 3: Table of CU09 Assembly Groups
  
AQX_CCU Assembled PCB H5832
PCB Layout H3P2160 Plain PCB H5833

 %
  
  
 %

 &"  #"! !$! #

 
CU09 PAL set H5834
Front–Panel Assembly Set Hz0548
Front–Panel–Ident ”CCU/9” Hz3954
2. 6. Part numbers of AQS CU10 P/N H9503
   " !
  
AQS_CCU Assembled PCB H9503
PCB Layout H3P2380 Plain PCB H9504
CU10 PAL set H9505
Front–Panel Assembly Set Hz06237
Front–Panel–Ident ”CCU/10” Hz
2. 7. Accessories for CU09/10
   
  
CU09 to Terminal Cable DIN–8/D–SUB–25 male/male 3m HZ04112
CU09 to INDY Cable DIN–8/DIN–8 male/male 10m HZ10091
CU09 to O2 Cable DIN–8/D–SUB–9 male/female 10m HZ04161
CU09 SCSI Cable 50p 73104
CU09 Fast Ethernet UTP CAT5 RJ45 Cable 2m 83024
CU09 Fast Ethernet UTP CAT5 RJ45 Cable 5m 83025
CU09 Fast Ethernet UTP CAT5 RJ45 Cable 10m 83026
CU09 Fast Ethernet UTP CAT5 RJ45 Cable 0,5m 67980
CU09 Fast Ethernet UTP CAT5 RJ45 Cable 3m 67981
CU09 Fast Ethernet UTP CAT5 RJ45 Cable 7,5m 67986
Cheapernet set 2*50 Ohm + 2*T–coax–connector + 10m coax HZ03817
Cheapernet set 2*50 Ohm + 2*T–coax–connector + 25m coax H2606
Aspect Station RS232 Router H5468
AQX RS232/485 Extension Unit H5714
5 Port Ethernet 10 MHz Mini Hub O001114
AUI/10BASE–2 Micro Transceiver
AUI/10BASE–T Micro Transceiver O00744
8MB PS2 Modul 2MB*36 , 70ns 65173
16MB PS2 Modul 4MB*36 , 70ns 66123
32MB PS2 Modul 8MB*36 , 70ns 66124
8MB PS2 Modul 2MB*32 , 60ns 67924
16MB PS2 Modul 4MB*32 , 60ns 67946
32MB PS2 Modul 8MB*32 , 60ns 67945

 %
  
  
 %

 &"  #"! !$! #

Connecting to RS232/RS485 of CU09
There are two devices which can be used to adapt ”tty01,...tty09, tty10 and tty20” to the
separate Sub–D–9 Connectors (see Figure 3: ):
AspectStation1 RS232 Router, (only for RS232), P/N H5468
AQX RS232/485 Extension Unit, P/N H5714
Both devices have to be connected to the CCU by one or two cables of the following
type:
SCSI Cable P/N 73104
Connecting to RS232/RS485 of CU10
The RS485 Channels (tty10 and tty20) are only avalable at the AQS Backplane, Connec-
tor X3.
Connecting the RS232 Channels ”tty01,...tty09” to the separate Sub–D–9 Connectors the
following parts can be used (see Figure 4: )
AspectStation1 RS232 Router, ( for RS232 only), P/N H5468
AQS RS232 Extension Unit, P/N H9508
RS232 devices have to be connected to the CCU by one or two cables of the following
type:
SCSI Cable P/N 73104

 %
  
  
 %
10
 &"  #"! !$! #
(98/12/10)
Figure 3: CU09 Attaching SubD connectors to the RS232/485 interfaces
AQX RS232/485 Extension Unit P/N H5714
AspectStation1 RS232 Router P/N H5468
AspectStation1 RS232 Router P/N H5468
AQX CCU/9
P/N H2570, EC50
"console"
(tty00)
S 7
S 8
S 9
"tty01,...,tty05"
"tty06,...,tty09"
tty20
tty10
tty01 tty02 tty03
tty04 tty05 tty06 tty07 tty08 tty09
tty01 tty02 tty03
tty04tty05not used
not used CAN
tty06 tty07 tty08
tty09
Connections made with
SCSI Cable P/N 73104
hin wire Ethernet
BNC Connector
RJ45 Connector
to other Hosts (St5)
RJ45 Connector
to HUB (St4)
Fast Ethernet Link Status
Table 6: CU09 Configuration of Serial Interfaces
UNIX
Special File / ev/tty00 / ev/tty01,...,05 / ev/tty06,...,09 / ev/tty10 / ev/tty20 / ev/can
Function (Console) RS232 RS485 CAN Bus
CCU
Connector ST6 ST7 ST8 ST7 ST8 ST8
AQX Ext. U.
Connector N/A ST2,...,ST6 ST7,...,ST10 ST13 ST11 N/A

 %
  
  
 %
11
 &"  #"! !$! #
(98/12/10)
Figure 4: CU 10 Attaching SubD connectors to the RS232 interfaces
AQS RS232 Extension Unit P/N H9508
AspectStation1 RS232 Router P/N H5468
AspectStation1 RS232 Router P/N H5468
AQS CCU/10
P/N H9503, EC00
"console"
(tty00)
S 7
S 8
S 9
"tty01,...,tty05"
"tty06,...,tty09"
tty01 tty02 tty03
tty04 tty05 tty06 tty07 tty08 tty09
tty01 tty02 tty03
tty04tty05not used
not used CAN
tty06 tty07 tty08
tty09
Connections made with
SCSI Cable P/N 73104
hin wire Ethernet
BNC Connector
RJ45 Connector
to other Hosts (St5)
RJ45 Connector
to HUB (St4)
Fast Ethernet Link Status
Table 7: CU10 Configuration of Serial Interfaces
UNIX
Special File / ev/tty00 / ev/tty01,...,05 / ev/tty06,...,09 / ev/tty10 / ev/tty20 / ev/can
Function (Console) RS232 RS485 CAN Bus
CCU
Connector ST6 ST7 ST8 ST2 ST2 ST8
AQS Ext. U.
Connector N/A ST2,...,ST6 ST7,...,ST10 N/A N/A N/A

Plug, front view
1
2
3
4
5
6
7
8
9
Plug, front view
MINI D, 8 pin, male
D-sub. 9pin, female
2
1
5
4
3
8
6
7
 %
  
  
 %
12
 &"  #"! !$! #
(98/12/10)
Connecting to the Console
CU09/O2 console cable 10m P/N HZ04161
This is the CU08/Indy console cable which can be used for CU09 in reverse direc-
tion.
CU09/Terminal console cable 3m P/N HZ04112
This cable was originally designed to connect a plotter to the Indy.
Figure 5: Console Cable, MINI D, 8 pin to D_S B, 9 pin
Pin # Signal
1 DTR
2 CTS
3 TxD
4 GND
5 RxD
6 RTS
7 DSR
8 GND
Pin # Signal
1 Shield
2 RxD
3 TxD
4 DTR
5 GND
6 DSR
7 RTS
8 CTS
9 NC
Connecting to Fast Ethernet
10–MBit Mini Hub, Part# O001114
Fast Ethernet Cable Types
Cable Type Category Part Number Length
TP CAT 5 83025 5m
TP CAT 5 83026 10m

 %
  
  
 %

 &"  #"! !$! #

2. 8. Controls and Indicators
" ,) )'&+ ". +  "*($/ & *+ ,++'&
**
%')/**
*+!)&++"-"+/
'$$"*"'&',)&
''"&#*++,*
"-+"-"+/
)&*%"++"-"+/ 


*+,++'&
+"-"+/*
*++!)&+++,*
Reset Button
The general hardware reset signal of CCU and VME–Bus can be initiated
by pushing the ”Reset Button”. It stays active for about 80 milliseconds.
Activity LED’s
The 4 digit LED–Display forms a hexadecimal coded value with MSB at the left side. Lighting re-
flects a logical ”One”.
The display shows the 4 bit contents of the Status–Register (see Figure 6: ) written on D7–D4 if this
value is less than 8, usually after power–up or reset.
If the MSB is set in the Status–Register the lower 3 digits from right to left reflect the activities of
the Ethernet–DMA, the CPU access to DRAM and the activity of the CPU on VME bus.
The intention is that after power–up or reset a basic test procedure changes the LED value at success
in steps from zero up to eight where eight means all tests have been passed and the monitor is run-
ning.
Fast Ethernet Status LED’s
The status information is available on the LED outputs pins of the DP83840.
LED1 Transmit activity, DP83840 pin 42
LED2 Receive activity, DP83840 pin 41
LED3 Good Link Status, DP83840 pin 38
LED4 Collision, DP83840 pin 36
”Collision ” ON indicates the occurrence of collisions in 10BASE–T or
100BASE–TX operation.
”Good Link Status” ON indicates valid link on the network connection and ready
state for normal operation.

 %
  
  
 %

 &"  #"! !$! #

OFF indicates that the PHY did not find a valid link on the net-
work connection. Transmit and receive operation are not pos-
sible.
In this situation the hardware is performing Autonegotiation
without any software interaction.
”Receive Activity” ON indicates that a packet is being received in 10BASE–T or
100BASE–TX mode.
”Transmit Activity” ON indicates that a packet is being transmitted in 10BASE–T
or 100BASE–TX mode.
2. 9. Operational Settings
2. 9. 1. NVRAM Setting
The NVRAM contains a set of parameters which are used by the software. After power
up, the monitor checks the parameter called magic.. If magic. is anything else than
RISCPROM, e.g. if a new and empty NVRAM has just been inserted, the monitor does the
whole set of diagnostic tests and sets the NVRAM parameters to the following default
values:
netaddr=0x149.236.99.99
netmask=0xffffff00
lbaut=9600
rbaut=9600
bootfile=bfs()/usr/diskless/clients/spect/root/unix
bootmode=c
console=0
cpuid=0
resetpc=xxxxxxxx
resetra=xxxxxxxx
eth_addr_ch1=0x
eth_addr_ch2=0x
version=5.40
magic=RISCPROM
model=CCU R4600
vendor=BRUKER
rootname=0
use_bootparams=1
keyswtch=0
keyboard=AT
This procedure takes a few minutes. The monitor prints a test protocol and at last its
prompt (>>) on tty0 which is the default console output.
The NVRAM parameters can be printed with the monitor by
printenv
and can be changed by
setenv parameter value
A problem crops up if magic is equal to RISCPROM and lbaud and rbaud doesn’t meet
the bauderate of the connected terminal or console doesn’t meet the interface to which
the terminal is connected to. Then no printout or input is possible. To correct this