Philips EasyVision RAD R4.2V2 Service Manual
Philips EasyVision RAD R4.2V2 Service Manual
2V2
SETTING-TO-WORK
3
FAUTFINDING 4
REPLACEMENT
5
PROGRAMMINGS
6
ADJUSTMENTS
7
EXPLANATIONS
8
DRAWINGS
9
10
DMC Hamburg
Printed in Hamburg, Germany
© 2003 Philips Medical Systems
ALL RIGHTS RESERVED
11
List of pages and drawings (LOPAD) Manual Order No: 4512 984 22362
released: 11/2003
__________________
0.1
1 ______________________
3.1 Z0 (a/02.0) A4
__________________ Z2-1 (99.0) A3
1-1...1-9 (a/03.1) Z2-2 (99.0) A3
__________________ Z2-3 (99.0) A3
2-1...2-12 (a/03.1) Z2-3.1 (03.0) A3
__________________ Z2-3.2 (03.0) A3
3-1...3-14 (a/03.1) Z2-3.3 (03.0) A3
__________________ Z2-3.4 (03.0) A3
4-1...4-30 (a/03.1) Z2-3.5 (03.0) A3
_________________ Z2-4 (99.0) A3
5-1...5-10 (a/03.1) Z2-5 (99.0) A3
__________________ Z2-6 (99.0) A3
6-1...6-26 (a/03.1) Z2-7 (99.0) A3
__________________ Z2-8 (99.0) A3
7-1...7-4 (a/03.1) Z2-9 (99.0) A3
__________________ Z2-10 (99.0) A3
8-1...8-14 (a/02.0) Z2-11 (99.0) A3
__________________ ____________________
Contents
1. INTRODUCTION..................................................................................................................................... 3
1.1. Documentation structure ......................................................................................................................... 3
1.2. Technology.............................................................................................................................................. 4
1.3. Tools........................................................................................................................................................ 4
4. NETWORK CONNECTIONS.................................................................................................................. 9
4.1. Client Server Clusters ............................................................................................................................. 9
1. INTRODUCTION
EasyVision RAD release 4.2 is a workstation as well as an acquisition system for PCR Readers. Beside that
the EasyVision RAD serves as an image processing system with printing capabilities. PCR Readers can
connect with both DMS interface and via Ethernet to an EasyVision RAD.
Moreover the EasyVision RAD 4.2 supports multi reader configurations with:
- 1 DMS Reader
- up to 2 network Readers
dependent on the performance of the hardware used.
The EasyServer
Within an EasyVision RAD cluster, the EasyVisions use a common place to store their images. The system
which does this is called the EasyServer. It controls the configuration of the cluster by controlling the
software licenses, it handles the import from modalities, the printing to film, and all communication outside
the cluster, for instance with the archive, external DICOM databases, or other clusters and workstations of
other vendors.
1.2. TECHNOLOGY
EasyVision RAD system are mostly sold as part of a PCR system treating the special needs of CR images.
Data can be imported from other modalities or other workstations as well.
EasyVision Release 4 is based on a client/server computing technology. This means a different configuration
will appear: Users on a workspot use information that resides in a database on a central server and is
received from a larger variety of sources.
1.3. TOOLS
To remove and replace EasyVision field replaceable units (FRUs), you will need the following tools and
materials:
• Standard toolkit
• Anti-static discharge kit
• Service network hub 10/100Mbit
• Service PC + null modem cable (25pin) for back-up of configuration files.
See Remote Service Manual for pin layout)
• Densitometer for laserprinter (e.g. X-Rite 331)
• Reflection densitometer for paperprinter (e.g. X-Rite 400)
• Hardcopy Unit test box
• Printer test tool
• Multimeter.
2. PRODUCT DATA
2.1. COMPUTERS
Ultra 10: The Sun Ultra 10 is a single processor PCI based workstation/server using the UltraSPARC-
II 64-bit architecture. The system has a PC style mini-tower layout.
Ultra 60: The Sun Ultra 60 is PCI based workstation using the UltraSPARC-II 64-bit architecture. The
system has a PC style mini-tower layout and is functionally equivalent to the Sbus based
Ultra 2 workstation.
SunBlade The Sun Blade 1000/2000 workstation is a dual processor workstation that uses the
1000/ 2000: UltraSPARC III family of processors. The workstation offers super-scalar processor
technology, multiprocessing, high-performance memory interconnection, highbandwidth
input/output (I/O), and accelerated graphics.
SunBlade The Sun Blade 1500 workstation is a single processor workstation that uses the
1500 UltraSPARC IIIi family of processors.
2.3. FRAMEBUFFERS
Color Greyscale
PseudoColor PGX(+) Pseudo Color TrueColor MD2/PCI
PCI/PGX(+) UPA/FFB
Ultra 10 (4xPCI + 1x UPA) Onboard* 3x 1x 2x
Ultra 60 (4xPCI + 2x UPA) No No 2x 2x
SunBlade 1000/2000 No No 2x 2x
(4xPCI + 2x UPA)
2.4. MONITORS
Display matrix: 1280 x 1024 Landscape oriented
Framebuffer type Color Monitors Greyscale monitors
18" Color 21" Color 21" Greyscale
Pseudo Color PGX(+) single head Yes Yes Yes,
True Color (FFB) single head Yes Yes Yes,
Greyscale (Md2) dual head No No Yes
Ultra 10
Slot 1 Slot 2
Bank 1 128 128
Bank 2 128/256 128/256
Ultra 60
Slot 1 Slot 2 Slot 3 Slot 4
Bank 1 32 32 32 32
Bank 2 32 32 32 32
Bank 3 64/128 64/128 64/128 64/128
Bank 4 64/128 64/128 64/128 64/128
SunBlade 1500
SDRAM Number of Physical bank Module DIMM Minimal Maximum
Organization DRAMs per DIMM Configuration Capacity Memory Memory
2.7. CONNECTIVITY
Connectivity SCSI parallel parallel parallel Ethernet
(DMS) 3M printer
Interf.
USIT x
AC500/5000 x
PCR Preview Unit x
AC3/3000 PCR9000 (DMS) X
Printers 3M Interf. X
Printers DICOM x
Printers SCSI X
Printers PostScript X
IDT
IDT
hub
Ethernet Fast Ethernet
Hospital
Network
4. NETWORK CONNECTIONS
Building blocks to build a network, like hubs, switches and other related parts, are NOT part of the
EasyVision delivery. These parts have to be purchased locally.
In this cluster concept two networks are determined. Network connection via Base-T Ethernet.
Section 2 Installation
Contents
4. CABLING ................................................................................................................................................ 4
4.1. SunBlade 1500........................................................................................................................................ 4
4.2. Ultra 10 / 60, SunBlade 1000 / 2000....................................................................................................... 5
4.3. Client / server network connection.......................................................................................................... 6
4.4. Ethernet Loopback Connector ................................................................................................................ 7
4.5. Laser Hardcopy Unit (point-to-point)....................................................................................................... 7
4.6. Mains Cables .......................................................................................................................................... 7
4.7. Cable Relief............................................................................................................................................. 7
5. PERIPHERAL CABINETS...................................................................................................................... 8
5.1. SCSI-chain configurations ...................................................................................................................... 8
5.1.1. ULTRA 10 PTI 2 Configurations.......................................................................................................... 8
5.1.2. ULTRA 10 PTI 2 + PTI 1 Configurations ............................................................................................. 9
5.2. ULTRA 60 PTI 2 + PTI 1 Configuration ................................................................................................ 10
5.2.1. Onboard SCSI only............................................................................................................................ 10
5.2.2. Onboard SCSI and Twin SCSI card .................................................................................................. 10
5.3. SunBlade Configuration ........................................................................................................................ 11
8. CONNECTIVITY ................................................................................................................................... 13
8.1. Printers .................................................................................................................................................. 13
8.2. NetView ................................................................................................................................................. 13
8.3. DICOM .................................................................................................................................................. 13
1. WHAT IS DELIVERED
The main part of this section describes the hardware installation per system. This can be a standalone
EasyVision, a Server or a Workspot! Look at the commercial order what is appropriate for your environment.
The total installation of a stand-alone EasyVision can be done within eight hours. Even the installation of a
small network can be completed within 8 hours.
3. PHYSICAL INSTALLATION
The software has been installed at the factory. The software installation keeps track of the SCSI chain
configuration. For this reason it is very important to build the same hardware configuration as assembled in
the factory. The SCSI chains on the SUN and corresponding peripheral cabinets are labeled with stickers
(SCSI-A, SCSI-B or SCSI-C).
If the SCSI chain changes for any reason (e.g. an option) the OS and AS software must be reinstalled!
4. CABLING
NOTE
Check all external and internal interface cables (e.g., the SCSI cable to the image hard disk, CD-ROM), as
they may have moved during transport.
________________
• Connect the video cable from the monitor to the workstation's video connector.
• Connect the monitor power cable to the power distribution unit.
• Connect keyboard and mouse.
• Network kit or cable must be obtained locally. EasyVision can be connected to the network via a twisted
pair (TP) connection.
This figure illustrates the cable connections for the SunBlade 1500 workstation.
Example:
IDT
PreView
Unit
network
Modem
Workspot #1 Workspot #n
NOTE
In case of a Single/Quad Ethernet card: The unused controllers must have an Ethernet loopback connector
connected
________________
NOTE
Ensure that the correct connections have been made for the DATA and CONTROL cables. Interchanging
these cables may destroy the hard copy interface board.
________________
Fit the correct mains plug to the mains cable of the power distribution unit provided. A couple of mains plugs
are delivered with the system but if the correct one for your environment is not there, you will have to obtain
one locally.
• Connect the mains cable between the Sun workstation and the power distribution unit.
• Connect the mains cable between the peripheral cabinet(s) and the power distribution unit.
• Connect the mains cable between the monitor and the power distribution unit.
• Connect the mains cable to a mains wall socket.
• The hardcopy unit's power cable may now be connected to the mains supply (if relevant).
NOTE
Make sure that the HCU has been connected to the same mains distribution point as the EasyVision. This is
important to protect both the HCU interface of the EasyVision RAD and the interface of the HCU from
voltage differences dangerous for the electronic interface components.
Relieve the power cable, network cable and hardcopy cables with Ty-Raps or flexible cable wrapper
delivered.
5. PERIPHERAL CABINETS
Note
The last peripheral cabinet in each SCSI chain must be terminated with a SCSI terminator.
________________
CAUTION
If the SCSI chain configuration has been changed, the OS and application software be re-installed
________________
Desktop:
PTI 2 (1)
ID(1) ID(2) ES
50cm X
X X
70cm X
n h X X
PTI 2 (1) X
X
Configuration 1
50cm 50cm
ES ID(1) ID(2) ID(3) ID(4)
X
70cm 70cm X X
n h h n
X X X
PTI 2 (1) PTI 2 (2) X
X
X X
Configuration 2
NOTE
In case of 4 image disks, you may use 1 SCSI chain (See right hand side of configuration 3)
________________
Configuration 3
Desktop:
Configuration 1
+
CD-R
50cm 30cm
70cm 150cm
n h h n
PTI 1
PTI 2 (1)
Configuration 1
+
CD-R 50cm
30cm
50cm 70cm
n n h n
PTI 1
PTI 2 (1)
Configuration 2
+
CD-Rec 50cm 50cm
30cm
50cm 70cm 70cm
n n h n h n
PTI 1 PTI 2 (2)
PTI 2 (1)
Configuration 3
+
CD-Rec 50cm 50cm 50cm
30cm
50cm 70cm 70cm 50cm
n n h n h n n n
PTI 1 PTI 2 (2) PTI 2 (2)
PTI 2 (1)
In case of 3 devices (or less), only the onboard SCSI card is available. The next figure shows the
configuration.
Printer
PTI 2 (EasyStore + Image Disk)
PTI 1 (CD-Rec)
n 50cm n 50cm 15cm
n n n
SCSI booster
Onboard SCSI + 3m cable
In case of more than 3 devices, a twin SCSI card is needed. The next figure shows the configuration.
h 70 cm n
Twin SCSI 1 n 50 cm n
h 70 cm n n 50 cm n
Twin SCSI 2
n < 300 cm n
Onboard SCSI
Printer
6. CONNECTING A PRINTER
See Z drawings for connection possibilities.
In the service manual Imager Compatibility you will find a compatibility list of the hardcopy units supported
by the EasyVision. Furthermore you will find the settings for the various hardcopy units, when connected to
EasyVision. Usually the HCU service engineer will configure the HCU and will have the information
necessary to do this. In some cases however he may not be aware of special settings when connecting to
EasyVision.
See Z drawings.
To connect an SCSI Printer, remove the SCSI terminator from the peripheral enclosure.
Connect the printer SCSI-cable and SCSI adapter narrow/narrow between the SCSI connector of the
peripheral enclosure and the printer itself or if relevant to a SCSI booster.
Put the SCSI terminator on the second SCSI connector of the printer or in case of a SCSI booster the
termination is done by the SCSI extender (so no external terminator required).
For detailed installation information of SCSI printers please refer to the installation manual delivered with the
printer.
Contents
1. INTRODUCTION ................................................................................................................................. 3
2. POWER ON......................................................................................................................................... 3
2.1. Power On Self Test and OpenBoot PROM phases ............................................................................ 3
2.2. Start-up Menu...................................................................................................................................... 3
2.3. Configuration / Customization ............................................................................................................. 3
3. POWER OFF....................................................................................................................................... 4
3.1. Power-off in Application Mode............................................................................................................. 4
3.2. Power-off in Service Mode .................................................................................................................. 4
3.3. When the System Does Not Respond Normally ................................................................................. 4
4. MONITOR ADJUSTMENT.................................................................................................................. 5
1. INTRODUCTION
The operating system, application software and license file are factory installed. For software configuration
and customization see Release Bulletin.
2. POWER ON
Check if the mains switch of the Sun computer and its peripheral devices are in the ON position.
Switch on the complete system by switching on the switch of the power distribution box. The light on the
mains switch box is always on when power is applied to it.
POST phase
During the POST phase the blinking Caps Lock LED on the keyboard will tell you the POST is in progress.
At successful completion of the POST phase the OpenBoot PROM firmware takes control.
Now the system should boot, as the SunOS and Application Software has already been loaded at the
factory.
1. Start Application
2. Start Customizing
3. Go to Service Menu
4. Go to Installation/Configuration Menu
0. Shutdown
Regarding customization refer to the instructions for use of the EasyVision RAD.
3. POWER OFF
3.1. POWER-OFF IN APPLICATION MODE
NOTE
Client/Server environment: If you turn the EasyServer off, the database is no longer accessible for the
clients.
________________
1. Click .
2. Click .
3. Click [Confirm].
5. When shutdown has completed indicated by the OK prompt switch off the power.
3. When shutdown has completed indicated by the OK prompt switch off the power.
1. Press <Stop>+<A>.
2. When the ok prompt appears, boot the operating system by entering boot.
NOTE
If the system does not respond to the mouse and keyboard, pressing <Stop>+<A> will not be effective. You
may have to switch the power off, wait at least 10 seconds, and switch the power back on again. Then try
pressing <Stop>+<A> once more.
________________
4. MONITOR ADJUSTMENT
The brightness and contrast settings are not factory set. To adjust the settings the monitor must be switched
on for at least 30 minutes. Please refer to the Instructions For Use of the EasyVision RAD for how to adjust
the monitor(s).
Should two monitors be placed next to each other pay particular attention to the fact that brightness
perception may differ, depending on the position with respect to the monitor. You must sit in the central
position to verify if there is equal brightness.
NOTE
When you configured EasyVision you should have selected "Normal" for the Monitor correction. (see
Release Bulletin chapter: Configuration). The other selections (Dark and Bright) are only necessary if this
procedure does not give the correct results.
________________
5.1. INTRODUCTION
After the system has been configured and customized, the correct density calibration (gamma correction
curve) and the pixel size calibration must be carried out on the EasyVision.
The HCU calibration is necessary to establish a correction (curve) between the EasyVision RAD and a
printer (HCU). This correction adapts the EasyVision printing chracteristics to individual deviations of the
printer chracteristics such as laser power adjustment, film chracteristics, developer chemistry or temperature
etc.
5.2. PRECONDITIONS
The hard copy unit is setup properly with respect to its configuration (this has to be done by the printer
manufacturers service engineer)
The printers self-calibration has been checked or corrected (manufacturers service engineer or hospital
personnel)
The densitometer has been calibrated and is operating correctly (Philips service personnel)
2. Click .
3. Click .
4. Click .
7. In the area Printer test images click [Load]. 23 test images are loaded into the database.
8. Click [Exit].
The Hard Copy Unit start screen is displayed. HCU Gamma correction and pixel correction must be
carried out for all configured printers and media sizes.
12. Right-click on the printer select spiral icon and select the printer you want to calibrate:
Note: The printer identification strings such as dicom_0_de25sj in the example above tells you that
this is the DICOM printer No. 0 (the first) connected to the EasyVision RAD with the IP node name
de25sj. The relation about which identification string belongs to which physical printer must be
taken from the file /easydata/[Link] at the EasyVision RAD with the node name
de25sj (in this example).
14. Right-click on the spiral icon Media and select the media in the hardcopy unit you want to calibrate the
printer for.
13 12 5 4
14 11 6 3
15 10 7 2
16 9 8 1
16. Click [Print]. Wait until the Printing Active panel disappears to indicate that printing is complete.
Fill in all measured density values in the Imager Calibration Form at the end of this chapter. Start
with the table EasyVision RAD calibration and fill in the 16 values of an array of 16 squares in one
column e.g. upper left upper right etc. (Don’t use the original form make copies of it for spare).
The result will be all 4 density numbers of all matching grey levels in one row.
Take the 4 readings belonging to one grey level (1 row) calculate the average and enter the result in
the column average of that grey level. Repeat this for all 16 grey levels.
Enter the 16 averages in the row 'Measured density' in the Hard Copy Gamma Correction screen
on the EasyVision; use the TAB key to always select the nearest field on the right
Click [Save].
Select Specific. Only that media type will be calibrated which is displayed under Media at the top left
of the Hard Copy Gamma Correction panel.
All: in which the calibration is valid for all media types for the printer selected
Matching: in which the calibration is valid for all media of the same size of the printer selected
Click [Save].
1. Make sure the same printer has been selected as in the calibration procedure.
2. Right-click the printer select spiral icon and select the printer you want to check.
Note: The printer identification strings such as dicom_0_de25rb in the example above tells you: this is
the DICOM printer No. 0 (the first) connected to the EasyVision RAD with the IP node name de25rb.
3. Click [Print Verify].
4. Click [Print]. The printing active panel is displayed and the verification film is printed.
5. Click [Exit].
6. Perform the measurement on the verification film as described in 5.2 step 18 on page 8.
7. Enter the measured density values in the column average of the Calibration Verification form.
8. Transfer the density numbers of the row Target density from the Hard Copy Gamma Correction screen
to the column Target density of the Verification form.
Example
• Click .
• Select either Specific or All Matching Sizes in the Save Media dialog box:
Specific in which only the selected media will be calibrated; (recommended)
All Matching Sizes in which all media of the same size on the selected printer will be calibrated.
NOTE
This panel supplies information about which media are calibrated (both density and pixel) on the
selected printer plus additional information.
EasyVision Calibration
Upper Upper Lower Lower Average Target Deviation Dev. Lower Upper Calibration
Left Right Left Right Density in o. D. in [%] error error necessary
limit limit
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
Calibration Verification
Upper Upper Lower Lower Average Target Deviation Dev. Lower Upper Calibration
Left Right Left Right Density in o. D. in [%] error error successfull
limit limit
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
Date: System:
Time: Operator:
Section 4 Faultfinding
Contents
1. INTRODUCTION ................................................................................................................................. 3
1. INTRODUCTION
In case of a standalone system you can start with chapter 4 Sun SPARC computers.
NOTE
________________
2. CLIENT/SERVER ENVIRONMENT
Flow Chart:
EV Cluster Power-on
EasyServer in No
System Power-on
application ?
Yes
Workspots in No
System Power-on
application ?
Yes
Cluster No
see Release Bulletin
configured?
Yes
DataBase No
EV Networking
accessible?
Yes
Application
A typical EasyVision RAD Release 4 / PCR network looks like the picture below. There are two networks:
The EasyVision cluster network (fast ethernet) and the modality network (standard Ethernet).
Another remark at this picture is that because the EasyServer is connected to two networks, it also has two
IP addresses (static router functionality), one for each network device (Ethernet controller).
IDT
PCR network
10/100 Mbit
Single / Quad card
EasyVision RAD R4.2
Server
Cl t
Modem
Onboard card
EasyVision R4.x network
10/100 Mbit
Workspot #1 Workspot #n
In case of problems:
For EasyVision RAD Release 4.2V2 the following Sun SPARC computers are used:
Ultra 10, Ultra 60, SunBlade (see belonging Unit Manual).
Flow Chart:
Run POST
No
Press Stop-A
Reboot System
Press Stop-A
4.1.2. ULTRA 60
Parameter name Value Default Value
scsi-initiator-id 7 7
keyboard-click? false false
keymap
ttyb-rts-dtr-off false false
ttyb-ignore-cd true true
ttya-rts-dtr-off false false
ttya-ignore-cd true true
ttyb-mode 9600,8,n,1,- 9600,8,n,1,-
ttya-mode 9600,8,n,1,- 9600,8,n,1,-
pcia-probe-list 1,2 1,2
pcib-probe-list 1,3,2,4,5 1,2,2,4,5
mfg-mode off off
dial-level max min
#power-cycles 74
system-board-serial # 5014450026841 (example)
system-board-date 35bd5758 (example)
fcode-debug? false false
output-device screen:r1280x1024x76 screen
input-device keyboard keyboard
load-base 16384 16384
boot-command boot boot
auto-boot? true true
watchdog-reboot? false false
diag-file
diag-device net net
boot-file /kernel/unix
boot-device disk disk net
local-mac-address? false false
ansi-terminal true true
screen-#columns 80 80
screen-#rows 34 34
silent-mode? false false
use-nvramrc? false false
nvramrc
security-mode none none
security-password
security-#badlogins 0
oem-logo 00 00 00 00 00 00 00 00 ...
oem-logo? true false
oem-banner
oem-banner? false false
hardware-revision
last-hardware-update
diag-switch? false false
5. SERVICE MENU
To access the service menu environment select 3 Go to Service Menu in the StartUp menu. Then at the
password: prompt enter password
Service Menu
===========
0 Logout
Diagnostics Menu
================
after the testbox has been connected and powered press Enter, The system will respond:
if the system didn’t detect any fault condition it will return the message
If the system detects any fault condition during this test run, i.e. if power is not applied to the test box or the
test cable is not connected to the Sun computer the system will respond:
EasyVision RAD R4 (a/03.1) 4-11
Copyright © 2003 Philips Medical Systems
ALL RIGHTS RESERVED
Section 4 Fault Finding
Caution
The test program will finish the test with the following message
even if the test box was not connected during the test.
after pressing <Enter> the system will output the Diagnostics Menu
There is no detailed error handling available which is capable to detect different levels of faulty conditions
and which allows conclusions on errors.
SunOs Menu
==========
File Menu
=========
Printer Menu
============
Monitor Menu
============
Actual Configuration:
EasyVision RTAC: sz/rz
EasyVision RTAC: sz/rz
Compression: Zip
EasyVision RAD R4 (a/03.1) 4-13
Copyright © 2003 Philips Medical Systems
ALL RIGHTS RESERVED
Section 4 Fault Finding
Actual Configuration:
Device: ttyb
Mode: Modem
Double click on the line /cdrom/ac500 or /cdrom/ac5000 to select the appropriate system.
The documentation files available on this CD-ROM are listed In the ‘Files’ area on the right)
Double click on the line of the document you want to open and view.
The first page of the document will be displayed
login: Service
Password: <Enter HostID>
Last login: Tue Dec 2 [Link] on term/b
+-----------------------------------------------------------------+
| WARNING : Access for authorised persons only |
+-----------------------------------------------------------------+
Service Menu
============
0 Logout
Diagnostics Menu
================
SunOS Menu
==========
kermit
rb
rx
rz
sb
sx
sz
Files can be moved into the Zip file with long or short filenames
In case you want to use the Zip file on a DOS or MS-Windows 3.x
system, you should choose for short files names. In that case the
name of each file that is added to the Zip file will be converted
into a number. The original names will be saved in a file "index".
This index file will also be included into
the Zip file (/tmp/[Link])
Printer Menu
============
SunOS 5.6
login: Service
Password: <Host ID>
Last login: Thu Sep 14 [Link] from [Link]
PMSN-EVM Sun Microsystems Inc. SunOS 5.6 Generic August 1997
+---------------------------------------------------+------------+
| WARNING : Access for authorised persons only |
+---------------------------------------------------+------------+
Service Menu
============
0 Logout
Could not find Release Info File for PCR User Terminal Server.
Might be wrong release/version/level.
Actual Configuration:
EasyVision --> RTAC : sz/rz
EasyVision <-- RTAC : sz/rz
Compression : Zip
Actual Settings:
Compression : Zip
1 Collect&Send Logfiles
2 Send Image Files (Menu)
3 Manual File Transfer (a C-shell is started; go to the directory
where
you want to send/receive files from/into.
Then
start the desired protocol by typing its name
followed by the appropriate arguments).
1 Collect&Send Logfiles
2 Send Image Files (Menu)
3 Manual File Transfer (a C-shell is started; go to the directory
where
you want to send/receive files from/into.
Then
start the desired protocol by typing its name
followed by the appropriate arguments).
Service Menu
============
1 Diagnostics Menu (sunvts and product diagnostics)
2 SunOS Menu (optical disk format and SunOS commands)
3 File Menu (file transfer and manipulation commands)
4 Printer Menu (Printer tests)
5 PCR Systems (PCR diagnostics menu)
0 Logout
6. FILE SYSTEM
6.1. /DBADMIN
6.1.1. /EASY/SERVICE/IMAGES/EXPORT
6.2. /EASYDATA
Example:
Explanation:
hosts:
The hosts file is a local database that associates the names of hosts with their Internet Protocol (IP)
addresses. The hosts file can be used in conjunction with, or instead of, other hosts databases, including
the Domain Name System (DNS), the NIS hosts map and the NIS+ hosts table. Programs use library
interfaces to access information in the hosts file.
The hosts file has one entry for each IP address of each host. If a host has more than one IP address, it
will have one entry for each, on consecutive lines.
#
# Sun Host Database
#
# If the NIS is running, this file is only consulted when booting
#
[Link] localhost
#
[Link] ev1 loghost
[Link] evppp
[Link] remoteppp
[Link] ev2
Explanation:
6.2.1. /VAR/ADM/CDSLOG
autoExportServer_autoExport_ev1.env setupDbServer_setup.startup
autoExportServer_autoExport_ev1.log systemMonitor_systemMonitor_ev1.env
autoExportServer_autoExport_ev1.startup systemMonitor_systemMonitor_ev1.log
computeServer_compute_ev1.env systemMonitor_systemMonitor_ev1.startup
computeServer_compute_ev1.log [Link]
computeServer_compute_ev1.startup uiDataHandling_uiDataHandling_ev1.env
dbServer_db8087f688.env uiDataHandling_uiDataHandling_ev1.log
dbServer_db8087f688.log uiDataHandling_uiDataHandling_ev1.start
dbServer_db8087f688.startup up
deleteServer_delete_ev1.env uiDentalView_uiDentalView_ev1.env
deleteServer_delete_ev1.log uiDentalView_uiDentalView_ev1.log
EasyVision RAD R4 (a/03.1) 4-23
Copyright © 2003 Philips Medical Systems
ALL RIGHTS RESERVED
Section 4 Fault Finding
deleteServer_delete_ev1.startup uiDentalView_uiDentalView_ev1.startup
dorServer_dor_ev1.env uiPerfusion_uiPerfusion_ev1.env
dorServer_dor_ev1.log uiPerfusion_uiPerfusion_ev1.log
dorServer_dor_ev1.startup uiPerfusion_uiPerfusion_ev1.startup
hcServer_hcs0_ev1.env uiRF_uiRF_ev1.env
hcServer_hcs0_ev1.log uiRF_uiRF_ev1.log
hcServer_hcs0_ev1.startup uiRF_uiRF_ev1.startup
httpServer_http_ev1.env uiStackView_uiStackView_ev1.env
httpServer_http_ev1.log uiStackView_uiStackView_ev1.log
httpServer_http_ev1.startup uiStackView_uiStackView_ev1.startup
[Link] uiVolume_uiVolume_ev1.env
networkServer_export_ev1.env uiVolume_uiVolume_ev1.log
networkServer_export_ev1.log uiVolume_uiVolume_ev1.startup
networkServer_export_ev1.startup xConfig_xConfig.env
networkServer_import_ev1.env xConfig_xConfig.log
networkServer_import_ev1.log xConfig_xConfig_ev1.startup
networkServer_import_ev1.startup xEasyReview_xEasyReview_ev1.env
setup xEasyReview_xEasyReview_ev1.log
setupDbServer_setup.env xEasyReview_xEasyReview_ev1.startup
setupDbServer_setup.log
EasyVision RAD provides log files for operating system and application software.
Messages logged by the Solaris operating system can be found in the directory /var/adm in the files named
messages, messages.1 and messages.2 . The logs contain messages of the operating system like errors,
start-up messages and warnings.
The file messages contains the latest logs. When this file reaches a defined size messages.2 is deleted,
messages.1 renamed to messages.2 and messages becomes messages.1.
System Monitor
The system monitor performs the task to run other processes. If a process crashes, the system monitor tries
to restart that process. It also knows if a process is critical or not, and can decide to stop that specific
program or to stop the whole application.
Server
Each process has its own error log files. It depends on which configuration (software options) you have what
logfiles are written in the logfile directory.
AutoExport Server
This process is responsible for all auto export actions.
ComputeServer
The compute server performs tasks for other facilities, such as 3D calculation, BCR, etc.
dbServer
The database server handles all read, write, seek etc actions in the image database.
deleteserver
The delete server is a process dat performs several possibilities of deletion tasks. These tasks can be
configured on the Customizing panel. For example, Protect, Protect until printed, Protect until stored on
optical disk, Auto-expiration Interval of 12 hours etc.
dorServer
This server handles the optical disk as a normal image database.
httpServer
Serves http requests over serial (PPP) or network.
network server
There are two network servers: import and export.
setupDBserver
The setup database server handles the configuration of a system. The setupDbServer runs on the Server
system. Once the Server system is running, the clients can take their own configuration and the
configuration of the remote hosts or modalities from the setup database. In case of a stand-alone, the Server
is integrated in the same machine.
UI...
The ui.. processes, e.g. uiRF, uiVolume, (dependent of applications) give detailed information about the
packages mentioned with the question mark.
If such an application is unstable, messages are written in the ui? logfile. If a critical error occurs, this error is
also written in the [Link] file.
[Link]
The license manager checks if the license is correct for the requested application. Without a license for a
specific package it is impossible to run that application. The [Link] file has been uploaded in the
/easydata directory. Only in case of a Server or Standalone:
[Link]
The installation logfile [Link] can be found in the /var/adm/cdslog/setup directory. In this file errors during
installation are written.
[Link] is created in the sub-directory /var/adm (see procedure below). An existing [Link] file is
renamed to [Link], [Link] to [Link], and so on (up to [Link]).
[Link] is also generated automatically when the software detects a crash of a system process.
When sending error logs to the field assistance group in Hamburg, please, please,
please send always [Link] not [Link].
[Link] contains:
- all log and messages files
- all config, customization and calibration files
- [Link] (software license)
- all PCR relevant files of /easydata/UI/configuration
- setup database (ZIP)
Jul 25 [Link] EV1 sunConfig: Info:CREATED TCP CONNECTION from host: [EV1] to
host: [DICOM1] at port: [50082].
When the TCP connection is released the following line appears in the logfile
Jul 25 [Link] EV1 sunConfig: Info:RELEASED TCP CONNECTION from host: [EV1] to
host: [DICOM1].
The Protocol Data Units (PDUs) are the DICOM packets (containing messages/data/comments) exchanged
between peer entities within a DICOM layer. It consists of protocol control information and user data. PDUs
are constructed by mandatory fixed fields followed by optional variable fields that contain one or more items
and/or sub-items.
After creating a TCP connection the PDU types are associated. The EasyVision sends a PDU type to the
remote DICOM node as the requestor.
Jul 25 [Link] EV1 sunConfig: Info:SENT: [ASSOCIATE_RQ_PDU_TYPE] from: [EV1] to : [DICOM1].
Next the EasyVision receives a PDU type from the remote DICOM node. The remote DICOM node is the acceptor.
Jul 25 [Link] EV1 sunConfig: Info:ESTABLISHED DICOM ASSOCIATION from: [EV1] to : [DICOM1].
ID ABSTRACT_SYNTAX TRANSFER_SYNTAX
REJECT_REASON
007 1.2.840.10008.[Link].1.1 1.2.840.10008.[Link]
This means that the abstract syntax CR-Image Store via the transfer syntax JPEG Lossless (see DICOM
Conformance Statement) is not accepted.
EasyVision RAD R4 (a/03.1) 4-27
Copyright © 2003 Philips Medical Systems
ALL RIGHTS RESERVED
Section 4 Fault Finding
In this example CR-Image Storage (1.2.840.10008.[Link].1.1) is accepted via Implicit VR Little Endian
(1.2.840.10008.1.2), Explicit VR little Endian (1.2.840.10008.1.2.1), and Explicit VR Big Endian
1.2.840.10008.1.2.2).
ApplicationContextName: [1.2.840.10008.[Link]]
LOCALMaxDataPDULength: [0]
PEERMaxDataPDULength: [16384]
LOCALImplementationClassUID: [1.3.46.670589.5.2.2]
PEERImplementationClassUID: [[Link].1107.5.1995.1]
LOCALImplementationVersionName: [EVCTMR21]
PEERImplementationVersionName: [SIEMENS_DICOM_10]
MaxOperationsInvoked: [1]
MaxOperationsPerformed: [1]
According to the DICOM standard a PDU Length of 0 means that the maximum length is unlimited. Some
DICOM nodes do not understand a maximum PDU length of 0 bytes. The following error message is written:
In this case a PDU length = 0, but the remote system expects a value greater than 6 bytes (header). In fact
it expects 6 bytes plus the real PDU length or shorter. 0 < x =< PDU length
The DICOM association shall be disconnected because of the invalid PDU Length:
The verifying of the DICOM syntaxes starts with (e.g. verifying SC-Image Store):
(See the advanced DICOM menu configuration for changing LOG, REPAIR, REJECT, PURE)
In this case all Non Pure DICOM attribute (0x0011, 0x1110 and 0x0009, 0x1051) are not accepted.
First of all the requestor sends a PDU Type release to the remote DICOM node. Next a response is
received, and finally the TCP connection is closed.
Section 5 Replacements
Contents
1. IMPORTANT ........................................................................................................................................... 3
4. MONITOR ............................................................................................................................................... 8
1. IMPORTANT
After a hardware modification reboot always with: ok boot -r
2. SUN WORKSTATION
2.1. MOTHERBOARD
2.2. NVRAM
2.3. MEMORY
5. Within textedit delete all lines which are related to the image disk(s).
Depending on the SCSI-Controller-Port on which the image disks are connected the entries in vfstab
are different.
If the first controller is used the image disk entries are related to:
c1t11d0sx = 1st image disk (t11)
c1t10d0sx = 2nd image disk (t10)
c1t9d0sx = 2rd image disk (t9)
c1t8d0sx = 4th image disk (t8)
If the the second controller is used the image disk entries are related to:
Delete for instance the following text (make sure all "Additional image disks"-entries including all
"...... /dbadmin ufs ......"-entries are deleted!).: This means the whole line.
8. Shutdown and power-off the EasyVision (disconnect the mains power cable!).
Disconnect the peripheral cabinet and remove the defective image disk and replace it with the new one
(mind the jumper settings of the new disk!).
Open the Sun computer(see Service Manual) and replace the defective image disk by a new one (mind
the jumper settings of the new disk!).
12. Power-on the EasyVision and press <Stop> + <a> during memory initialization.
17. The following question is asked, when the disk is not labeled "Disk not labeled. Label it now?".
Answer with: y
18. After labeling the disk quit the format menu, exit OpenWindows and exit the Service Menu.
19. Re-install the Application Software. During installation you will be asked which disks shall be used as
image disk(s). See also: Release Bulletin Chapter Installing the Application Software.
21. Execute configuration ("Keep existing image database" is grayed out, because there is no image
database yet!) If necessary, the amount of the used image-disk-size can be reduced at this point as
well.
3. PERIPHERAL CABINET
3.1. IMAGE DISKS
Step Action Refer to Remark
1 Modify vfstab Follow chapter 2.5 Image Disk
2 Remove the image disk Manual: System Manual EasyVision
Section: Installation Database is lost !
Chapter: Peripheral Cabinets
2 Set jumpers on new image Manual: System Manual EasyVision
disk Section: Programmings
3 Replace the image disk Manual: System Manual EasyVision Mount disk in peripheral
Section: Installation cabinet.
Chapter: Peripheral Cabinets
2 Set jumpers on new CD-R Manual: System Manual EasyVision New CD-R drive has same
drive Section: Programmings SCSI settings as defect
CD-R drive.
3 Replace the CD-R drive Manual: System Manual EasyVision Mount disk in peripheral
Section: Replacements cabinet.
Chapter: CD-R drive
4. MONITOR
5.1. ULTRA 10
When a Dome framebuffer has been installed in the field the following commands must be entered to
activate the board.
• Go to the ok prompt.
• Enter setenv output-device /pci/DOME,Md2PCI
• Enter reset
Connect the video cable to the Dome framebuffer board. The first framebuffer channel always has the Dome
logo displayed. Start the configuration and edit the EasyVision “Framebuffer / Monitor settings”. Select
automatic configuration and leave this panel. Execute the configuration.
If the Dome framebuffer is removed and the onboard frame buffer is used, the following must be done:
• Stop the application and shut the system down in a proper way.
• Power on
• At memory test of the Sun press <Stop>+<A>
• At the ok prompt enter
setenv output-device screen
reset
5.2. ULTRA 60
To install a Dome GreyScale framebuffer in an Ultra 60 the next procedure must be done:
• Stop the application and shut the system down in a proper way.
• Remove the existing frame buffer and install the Dome GreyScale framebuffer.
• Connect the video cable to the Dome frame buffer board. The first frame buffer channel always has
the Dome logo displayed (the first frame buffer is the first VGA connector, which is located next to the
fixating bolt).
• Start the configuration and edit the EasyVision “Framebuffer / Monitor settings”. Select automatic
configuration (the Dome framebuffer should be selected) and leave this panel. Execute the
configuration.
If the Dome frame buffer is removed and a UPA TRUE COLOR framebuffer is used, the following must be
done:
• Stop the application and shut the system down in a proper way.
• Remove the Dome GreyScale framebuffer and install the UPA TRUE COLOR framebuffer(s).
• Connect the video cable to the UPA TRUE COLOR framebuffer.
• Start the configuration and edit the EasyVision “Framebuffer / Monitor settings”. Select automatic
configuration and leave this panel. Execute the configuration.
•
5.3. SUNBLADE
To install a Dome GreyScale framebuffer in a SunBlade computer the next procedure must be done:
• Stop the application and shut the system down in a proper way.
• Remove the existing frame buffer and install the Dome GreyScale framebuffer.
• Connect the video cable to the Dome frame buffer board. The first frame buffer channel always has
the Dome logo displayed (the first frame buffer is the first VGA connector, which is located next to the
fixating bolt).
• Start the configuration and edit the EasyVision “Framebuffer / Monitor settings”. Select automatic
configuration (the Dome framebuffer should be selected) and leave this panel. Execute the
configuration.
If the Dome frame buffer is removed and a UPA TRUE COLOR framebuffer is used, the following must be
done:
• Stop the application and shut the system down in a proper way.
• Remove the Dome GreyScale framebuffer and install the UPA TRUE COLOR framebuffer(s).
• Connect the video cable to the UPA TRUE COLOR framebuffer.
Start the configuration and edit the EasyVision “Framebuffer / Monitor settings”. Select automatic
configuration and leave this panel. Execute the configuration.
Section 6 Programmings
Contents
2. CD-R DRIVES....................................................................................................................................... 4
2.1. Plextor PlexWriter ................................................................................................................................. 4
2.2. Philips CDD 3600.................................................................................................................................. 4
5. FRAMEBUFFERS .............................................................................................................................. 18
5.1. Dome Md2 .......................................................................................................................................... 18
5.1.1. Upgrading an Ultra 5/10 ................................................................................................................. 18
5.1.2. Upgrading an Ultra 60 .................................................................................................................... 19
5.2. SUN PGX Framebuffer ....................................................................................................................... 19
5.3. SUN Creator 3D Framebuffer ............................................................................................................. 20
1.1. ADDRESSING
In general all wide SCSI devices have four jumpers to set their SCSI address. In case of narrow SCSI, the
devices have three jumpers (ID3 is not available)
c = controller
t = target
d = disc
s = slice (partition)
Pin 1: +12V DC
Pin 2: +12V Return
Pin 3: +5V Return 4 3 2 1
Pin 4: +5V
2. CD-R DRIVES
Applies to EasyVision based on Ultra 5, Ultra 10 and Ultra 60 with EVRAD R4.2 L3 or higher software.
WARNING
Do not mount the CDD 3600 drive in the Peripheral 2 or Peripheral 4 Cabinet!
________________
Jumperblock:
4. IMAGE DISKS
jumper on
underside
See Sun Blade 1000/2000 Service Manual or Sun Blade 1000/2000 Service Booklet located inside the Sun
Blade 1000/2000.
Address B
12 1
12 1
12 1
12 1
Use the disk as is and do NOT install the SCSI Narrow to Wide adapter.
Use the disk as is and do NOT install the SCSI Narrow to Wide adapter.
Use the disk as is and do NOT install the SCSI Narrow to Wide adapter.
NOTE
5. FRAMEBUFFERS
Use only VGA cables with 15 pin sub-D VGA connectors at both ends; cables with BNC connectors will not
work with Philips/FIMI monitors.
• Go to the OK prompt.
• Enter setenv output-device /pci/DOME,Md2PCI
• Enter reset
Enter configuration program and configure the board. See chapter Framebuffer/ Monitor Settings in the
Release Bulletin.
If the DOME FRAMEBUFFER is removed and the Onboard frame buffer is used do the following:
• Go to the OK prompt.
• Enter setenv output-device screen
• Enter reset
Enter configuration program and configure the board. See chapter Framebuffer/ Monitor Settings in the
Release Bulletin.
• Stop the application and shut the system down in a proper way.
• For Solaris 8 only: Do not remove the UPA TRUE COLOR FRAME BUFFER(s) and install the DOME
GreyScale FRAMEBUFFER.
• Connect the video cable to the DOME frame buffer board. The first frame buffer channel always has
the DOME logo displayed (the first frame buffer is the first VGA connector, which is located next to the
fixating bolt).
• Start the configuration and edit the EasyVision "Framebuffer / Monitor settings". Select automatic
configuration (the DOME FRAMEBUFFER should be selected) and leave this panel.
See chapter Framebuffer/ Monitor Settings in the Release Bulletin.
• Execute the configuration.
If the DOME frame buffer is removed and a UPA TRUE COLOR FRAMEBUFFER is used, the next sequence
of instructions must be executed:
• Stop the application and shut the system down in a proper way.
• Remove the DOME GreyScale FRAMEBUFFER and install the UPA TRUE COLOR
FRAMEBUFFER(s).
• Connect the video cable to the UPA TRUE COLOR FRAMEBUFFER.
• Start the configuration and edit the EasyVision "Framebuffer / Monitor settings". Select automatic
configuration and leave this panel. See chapter Framebuffer/ Monitor Settings in the Release
Bulletin.
• Execute the configuration.
The PGX card is usually factory installed in the Sun computer. In case of an upgrade:
EasyVision based on Ultra 10 and Ultra 60. There are no jumper settings.
The HCU board is usually factory installed in the Sun computer. In case of an upgrade:
The DMS Reader interface board is usually factory installed in the Sun computer when ordered.
In case of an upgrade:
8. ETHERNET CONTROLLERS
The Quad Fast Ethernet Controller (Qfe) offers four independent switchable 10/100Mb Ethernet channels
with auto negotiation and provides operations of up to 100 meters of Twisted Pair without repeaters. The
Ethernet channel hme0 included (always integrated in a Sun Ultra 5/10/60) there are five independent
network channels available in one EasyVision. In consequence each channel must be configured as a
separate Ethernet controller with its own IP address and netmask. This provides the advantage of separating
the net load to different network segments.
Each of the network interfaces of the adapter have been assigned a unique MAC address. The OpenBoot
firmware reports this MAC address via the local-mac-address property in the device nodes corresponding to
the network interfaces.
A system is free to use this assigned MAC address. Instead the MAC address of hme0 can be used. In such
cases, the system-wide MAC address applies to all network interfaces on the system.
To use the MAC addresses assigned to the network interfaces of the Quad FastEthernet adapter, set the
NVRAM configuration variable local-mac-address? to true:
In the EasyVision configuration screen select under Controller→ qfe → New (for the 1st channel qfe0, the
other channels likewise). If channel qfe1/2/3 is configured before qfe0 the number 0 has to be changed to the
number of the connected channel.
In case of an upgrade:
The Sun FastEthernet Adapter is factory installed in the Sun computer. There are no jumper settings.
In case of an upgrade:
In case of an upgrade:
Jumper settings:
Section 7 Adjustments
Contents
1. MONITOR CALIBRATION
There are two different menu locations. One is in the monitor menu which displays patterns. The other one is
in the Workspace menu (Open Windows) and is used to calibrate the Brightness uniformity and
Convergence for Color monitors.
For the specific monitor procedures see the Monitor Service Manual.
To access the monitor menu environment select entry number 4 (Go to Service Menu) in the StartUp menu.
Then at the password: prompt enter password
Service Menu
============
0 Logout
Monitor Menu
============
The following test patterns are shown in sequence by following the instructions on the screen:
• Grey scale / Color scale pattern
• Color scale / Grey scale pattern
• Crosshatch / circle
• Resolution
• 25% White
To verify the brightness value setting. Refer to the monitor manual for the specific value.
• Black screen
To verify the black level setting of the monitor, which is always 1 Cd/m2.
• All mixed
There is special monitor software to adjust the color monitor brightness uniformity and convergency. This
software can only operate in the open windows environment and requires the monitor calibration tool.
The procedure is as follows:
NOTE
Due to a hardware problem in the SUN systems the serial port does not always recognize the monitor
calibration tool. For this reason it may be necessary to boot the system with the monitor calibration tool
connected.
________________
Start-up menu:
1 Start Application
2 Start Customization
3 Goto Service menu
4 Go to Installation / Configuration menu
0 Shut down
Service Menu:
1 Diagnostics Menu (sunvts and product diagnostics).
2 SunOS Menu (optical disk format and SunOS commands).
3 File menu (File transfer and manipulation commands).
4 Printer menu (Printer tests).
5 Monitor menu (Monitor test images and adjustments).
0 Logout
SunOs Menu
==========
Move the cursor to the canvas (background) and click the right mouse button. Select in this Workspace
menu the Color monitor adjustment entry.
The Cyberscreen Color Monitor Maintenance Software is started. Refer to the color monitor documentation
for the adjustment procedure.
Section 8 Explanations
Contents
1.1. INTRODUCTION
Scope
This chapter describes the basic elements of the UNIX operating system.
Objectives
After studying this chapter, the Philips service engineer has some knowledge of:
- how the operating system is organized
- the different possibilities in UNIX and is able to:
• manipulate files, directories and devices
• maintain the file system
1.2. HISTORY
Designed in 1969, the UNIX system was originally developed for medium-sized minicomputers (DEC PDP
series) by Bell Laboratories and later moved to large, powerful mainframe computers as well as
microcomputers. Bell Laboratories has consistently introduced new versions of UNIX every few years. There
are consequently, many versions of UNIX. Also under the great influence of AT&T, the operating system was
further developed to a so called System V.
It is a C-based operating system (Bourne shell).
The university of California at Berkeley introduced a variation of the standard system: the Berkeley Software
Distribution (BSD) Version 4.2 using C shell which is a more extended system.
The UNIX version used in SUNOS 4.1 operating system is a heavily enhanced version of the 4.2 and 4.3
BSD UNIX system. It also includes features of AT&T, system V.3 UNIX.
To arrive at a more standardized version of UNIX Sun introduced, in 1993, a new Operating System called
"Solaris". Solaris (= SunOS 5.x) is based on the industry standard: UNIX System V Release 4 (SVR4).
Solaris is a total system-software solution, integrating the following:
1.3. FEATURES
Multitasking capability.
Offers the computer the ability to perform several tasks simultaneously. Background tasks are those that can
be executed without user's intervention.
Foreground tasks requires user's intervention.
Multi-user capability.
Permits several users to use the same computer simultaneously. More than one user can access the same
data at the same time.
Transportability.
Is easier to modify the UNIX system code for installation on a new computer than to rewrite another
operating system. More than 90% of the kernel program (explanation follows) is written in C and the rest in
machine-specific language. At worse, only 10% of the kernel program must be rewritten to move the kernel
to an entirely new machine architecture.
Large selection of powerful UNIX-supplied programs can be divided into two classes:
1. Integral utilities: Parts of the UNIX system that provide such assistance to the operating system that are
absolutely necessary for the practical operation of a computer with UNIX. An example is the UNIX
system command interpreter, the SHELL program;
2. Tools: Application programs that are not necessary to the computer's basic operation. An example is the
word processing "vi".
1.4. STRUCTURE
The UNIX system's parts may be functionally categorized into three levels:
• the KERNEL
• the SHELL
• the tools and applications
1.4.1. KERNEL
The kernel is the heart of the operating system, controlling the hardware and actually turning parts of the
computer system on and off at program's commands.
The kernel manages all the physical resources. Kernel functions include:
• implements the file system and permits processes to create, read, write, and remove these files
• schedules the tasks, keeps track of all active processes and decides which gets to run next
• manages the device drivers, software routines which control physical devices such as graphics display,
mouse, keyboard, disk, tape, serial ports and Ethernet
• supports facilities for creating, examining, and modifying processes
• performs system management functions, such as halting, booting, and error handling
• performs miscellaneous functions which make resources like memory available to processes
The file system, which resides on the disk and provides an organization for all the UNIX system data, is also
considered a resource and is managed directly by the kernel. The kernel program resides on the disk in a
single file, typically known as vmunix.
1.4.2. SHELL
The shell is a program that connects and interprets the commands typed by a user. It interprets user
requests, calls programs from memory, and executes them one at a time or in a series.
The shell program translates the typed commands into commands that the kernel understands.
The C shell (csh), with a C-like syntax, has more useful features for interactive use, such as command
aliasing, job control, and a history mechanism.
The Bourne shell (sh), the standard UNIX system command interpreter, while providing fewer interactive
features, runs faster and has a simpler syntax for writing shell programs.
The tools and applications level adds special capabilities to the operating system.
Either the CPU is executing the kernel program, a shell program, or another command program. Unix is a
time-sharing system.
After pressing RETURN on a terminal which is properly set up, a UNIX system banner line will appear,
requesting for a username.
After the UNIX reads your username, it will usually prompt for a password and when both are entered
correctly it will display a prompt.
Login: username
Password:
EV1#
The C shell (standard prompt = # (super user), here represented by EV1#) is ready to accept a command
request.
To conclude this first session the command logout or a ^D (Ctrl D) is required. Sometimes the command exit
is needed before the logout command.
EV1# logout
Login:
Because in the UNIX system there are several possible options and arguments for most commands, the
command line format statement allows us to describe all possible command lines in general terms.
The use of brackets ([ ]) around an option or an argument indicates that they are not always required.
The three sequential points (...) indicates that there may be more than one option or argument.
The space character is used as a delimiter.
Examples:
EV1# date
EV1# who
Remark
The UNIX system distinguishes between uppercase and lowercase letters; an uppercase character is
interpreted differently from the lowercase version.
8-6 (a/02.0) EasyVision RAD R4
Copyright © 2002 Philips Medical Systems Germany
ALL RIGHTS RESERVED
Explanations Section 8
This UNIX system has the on-line documentation so it is possible to get more information about a particular
command. The man command diplays information from the reference manuals. It displays complete pages
about UNIX subjects.
-a Show all manual pages matching name within the MANPATH search path. Manual pages are
displayed in the order found.
-d Debug. Displays what a section-specifier evaluates to, method used for searching, and paths
searched by man.
-f file… man attempts to locate manual pages related to any of the given files. It strips the leading
path name components from each file, and then prints one-line summaries containing the
resulting basename or names. This option also uses the windex database.
-F Force man to search all directories specified by MANPATH or the [Link] file, rather than
using the windex lookup database. This is useful if the database is not up to date. If the
windex data base does not exist, this option is assumed.
-k keyword Print out one-line summaries from the windex database (table of contents) that contain any of
the given keywords. The windex database is created using catman(1M).
-l List all manual pages found matching name within the search path.
-M path Specify an alternate search path for manual pages. path is a colon-separated list of
directories that contain manual page directory sub-trees. For example, if path is
/usr/share/man:/usr/local/man, man searches for name in the standard location, and then
/usr/local/man. When used with the - k or - f options, the -M option must appear first. Each
directory in the path is assumed to contain subdirectories of the form man*, one for each
section. This option overrides the MANPATH environment variable.
-r Reformat the manual page, but do not display it. This replaces the man - -t name
combination.
-s section Specify sections of the manual for man to search. The directories searched for name is
limited to those specified by section. section can be a digit (perhaps followed by one or more
letters), a word (for example: local, new, old, public), or a letter. To specify multiple sections,
separate each section with a comma. This option overrides the MANPATH environment
variable and the [Link] file. See each Paths below for an explanation of how man conducts
its search.
-t man arranges for the specified manual pages to be troffed to a suitable raster output device (see
troff(1). If both the - and -t flags are given, man updates the troffed versions of each named
name (if necessary), but does not display them.
NAME
lists the name or names that are used for the command as well as a brief one-line description of the
command's purpose
SYNOPSIS
gives the general command line format for invoking the command
DESCRIPTION
explains in some detail the action of the command
OPTIONS
explains the different options of the command
FILES
if present, lists the file or files that are associated with the command program
BUGS
Basic commands UNIX system documentation
Examples:
This demonstrates this facility, assume information is requested about the command “man”.
EV1# man man
Reformatting page. Wait... done
NAME
pwd - return working directory name
SYNOPSIS
/usr/bin/pwd
AVAILABILITY
SUNWcsu
DESCRIPTION
pwd writes an absolute path name of the current working directory to standard output.
Both the Bourne shell, sh(1), and the Korn shell, ksh(1), also have a built-in pwd command.
ENVIRONMENT
See environ(5) for descriptions of the following environment variables that affect the execution of pwd:
LC_MESSAGES and NLSPATH.
EXIT STATUS
The following exit values are returned:
0 Successful completion.
>0 An error occurred.
If an error is detected, output will not be written to standard output, a diagnostic message will be written to
standard error, and the exit status will not be 0.
SEE ALSO
cd(1), ksh(1), sh(1), shell_builtins(1), environ(5)
DIAGNOSTICS
`Cannot open ..'' and ``Read error in ..'' indicate possible file system trouble and should be referred to a
UNIX system administrator.
NOTES
If you move the current directory or one above it, pwd may not give the correct response. Use the cd(1)
command with a full path name to correct this situation.
Key Function:
The UNIX file system is a structure for organizing information or data. The data is grouped into named
entities called files. The UNIX system recognizes at least three types of files:
1. Ordinary files This type of file is used to store data. Executable programs (commands) are also stored as
ordinary files.
2. Directory files A directory file contains a list of files.
3. Special files These files are used to reference physical devices, such as terminals, printers, disks, and
tape drives. They are read from and written to, just like ordinary files, but such requests cause activation
of the associated physical device.
There are three classes of file users and three modes of file access offering the UNIX file system a total of
nine different kinds of access permission.
1. Owner - The owner is usually the system user who created the file. The super-user can change the
individual ownership of a file if necessary. The owner has full control over restricting or
permitting access to the file at any time.
2. Group - A system user who is not the file owner may access the file if this user belongs to the group of
system users who are allowed to access the file. However, this user cannot restrict or permit
access to the file; only the owner is allowed to do this.
3. Other - This category refers to any other user of the system.
There are three ways of accessing a file. The meaning of these access modes is somewhat different for
ordinary files than it is for directories:
Where:
“- The dash in the file type field indicates that the file is an ordinary file.
” Other possibilities:
D the entry is a directory;
L the entry is a symbolic link;
b the entry is a block special file;
c the entry is a character special file;
p the entry is a fifo (or "named pipe") special file;
- the entry is an ordinary file;
| the entry is a FIFO.
This describes a file that is readable, writable, and executable by the user and
readable by the group and others.
-rwsr-xr-x
This describes a file that is readable, writable, and executable by the user, readable and
executable by the group and others, and allows its user-ID to be assumed, during
execution, by the user presently executing it.
-rw-rwl---
This describes a file that is readable and writable only by the user and the group and can
be locked during access.
10876 The size of the file in bytes for the special files, the device driver and number of
units
May 16 9:42 The date and time when the file was last changed (modification time)
cp copy a file
-i prompt for confirmation
ln creating filename aliases (link)
rm remove a file
-i prompt for confirmation
u user's permissions
g group's permissions
o others' permissions
a all permissions (user, group, and other)
+ Add permissions.
- Take away permissions.
= Assign permissions absolutely.
Examples:
chmod ugo+r *
chmod go-rwx *
NOTE
Be aware with x and w permision file can be deleted, without file access permissions.
________________
1.6. VI EDITOR
To re-enter the command mode simply press the <ESC> key. The screen will blink or beep, when already in
this mode.
/exp Go forward to exp hjkl Unit cursor motion a Append after cursor
?exp Go backward to exp
G Goto last file line A Append at line end
n Repeat previous search 3G Goto line 3
N Reverse previous search 0 Goto line start c Change character
$ Goto line end
:w Write buffer to disk
:w newfile Write buffer to newfile H Goto screen top cw Change a word
:w >> file Append buffer to file M Goto screen middle
:w ! file Write absolutely L Goto screen bottom c3w Change 3 words
Wirings
CT/MR
RD GN BU WT
X1 = MAINS
X2 = KEYBOARD TERM.
X3a/b = SERIAL PORT A & B SCSI EASY STORE SCSI PRINTER
X4 = PARALLEL
1 0
X5 = TWISTED PAIR ETHERNET [Link] L=0m5
X6 = VIDEO ONBOARD
X7 = HCU (HARDCOPY UNIT) VIDEO
SCSI
X8 = READER/F (DMS)
X10a/b = PCI SCSI chain A&B
CONNECTIONS:
L=1m5/0m7
X10b
SEE Z2-7
note: 110/230VAC
selection required WZF (OPTIONAL)
PERIPHERAL-2 CABINET
SCSI
HDD4 BOOSTER
WZI X6
SCSI W/N
X8
SUN ULTRA 5 L=0m15
X7
DSL
SCSI HDD3
POWER
ON/OFF
TERM.
X10b X10a
1 0
[Link] L=0m5 MAINS
110VAC 230VAC
X3b X4
SCSI
X2 X3a X6 POSTSCRIPT PRINTER
X1 X5
MAINS
WZF
L=0m5 PERIPHERAL-2 CABINET
X5
X2 HDD2
WZJ
MOUSE
u sun
u
u
u
u
u
u
u
X10a
WZ
CABLE CONNECTIONS
EASYVISION RAD STANDALONE ULTRA 5
SCSI
CT/MR
RD GN BU WT
X1 = MAINS
X2 = KEYBOARD
VIDEO CONNECTIONS: TERM.
X3a/b = SERIAL PORT A & B SEE Z2-7 SCSI EASY STORE SCSI PRINTER
X4 = PARALLEL
1 0
X5 = TWISTED PAIR ETHERNET [Link] L=0m5
X6 = VIDEO ONBOARD
X10a/b = PCI SCSI chain A&B SCSI
L=1m5/0m7
X10b
note: 110/230VAC
selection required
SCSI
BOOSTER
WZI X6
SCSI W/N
SUN ULTRA 5 L=0m15
POWER
ON/OFF
X10b X10a
MAINS
110VAC 230VAC
X3b X4
X5
X2
WZJ
MOUSE
u sun
u
u
u
u
u
u
u
L=max 3m
X4
WZK
KEYBOARD
WZS
MAINS DISTRIBUTION UNIT
WZ
CABLE CONNECTIONS
EASYVISION RAD CLIENT ULTRA 5
X1 = MAINS
POWER X2 = KEYBOARD WZF (OPTIONAL) CONTROL
X3a/b = SERIAL PORT A & B L=0m5 PERIPHERAL-2 CABINET
X4 = PARALLEL
X5 = TWISTED PAIR ETHERNET CT/MR
X6 = VIDEO ONBOARD
X7 = HCU (HARDCOPY UNIT)
X8 = READER/F (DMS)
RD GN BU WT
X10a/b = PCI SCSI chain A&B
VIDEO CONNECTIONS: TERM.
SEE Z2-8 note: 110/230VAC SCSI EASY STORE SCSI PRINTER
selection required
1 0
[Link] L=0m5
SCSI
WZI
L=1m5/0m7
X10b
SUN ULTRA 10
X1
MAINS IN
WZF (OPTIONAL)
PERIPHERAL-2 CABINET
SCSI
WZJ HDD4 BOOSTER
MOUSE
230VAC 110VAC
SCSI W/N
u sun
u
u
u
u
u
uu
L=0m15
POWER
WZK ON/OFF
KEYBOARD TERM. SCSI HDD3
1 0
[Link] L=0m5 MAINS
SCSI
POSTSCRIPT PRINTER
X2
WZF
X2 L=0m5 PERIPHERAL-2 CABINET
HDD2
X10b
DMS X3b
READER X7 X8
X3a
X8
SCSI HDD1 L=max 3m
X4
1 0
[Link] L=0m5
X6 X6 X10a SCSI
ETHERNET PRINTER
X4 L=0m7
X10a
X5
X5
WZ
CABLE CONNECTIONS
EASYVISION RAD SERVER/STANDALONE ULTRA 10
SCSI
X1 = MAINS
POWER X2 = KEYBOARD WZF (OPTIONAL)
X3a/b = SERIAL PORT A & B L=0m5 PERIPHERAL-2 CABINET
X4 = PARALLEL
X5 = TWISTED PAIR ETHERNET CT/MR
X6 = VIDEO ONBOARD
X10a/b = PCI SCSI chain A&B
RD GN BU WT
VIDEO CONNECTIONS: TERM.
SEE Z2-8 note: 110/230VAC SCSI EASY STORE SCSI PRINTER
selection required
1 0
[Link] L=0m5
SCSI
WZI
SUN ULTRA 10
X1
MAINS IN
SCSI
WZJ BOOSTER
MOUSE
230VAC 110VAC
SCSI W/N
u sun
u
u
u
u
u
uu
L=0m15
POWER
WZK ON/OFF
KEYBOARD
MAINS
POSTSCRIPT PRINTER
X2
X2
X10b
X3b
L=1m5/0m7
X10b
X3a
L=max 3m
X4
X6 X6 X10a
X4
X5
X5
WZS
MAINS DISTRIBUTION UNIT
WZI SCSI
WZJ
MOUSE SUN ULTRA 60
X10b
u sun
u
u
u
u
u
u
u
X10b L=1m5/0m7
X1 or
MAINS IN X11 L=1m5/0m5 WZF (OPTIONAL)
WZK X4 PERIPHERAL-2 CABINET
SCSI
KEYBOARD BOOSTER
HDD4
SCSI W/N
X2 X2
L=0m15
X3b SCSI
TERM. HDD3
1 0
[Link] L=0m5 MAINS
X5
X5
SCSI
X0 POSTSCRIPT PRINTER
WZF
L=0m5 PERIPHERAL-2 CABINET
X11 HDD2
WZ
CABLE CONNECTIONS
EASYVISION RAD SERVER/STANDALONE ULTRA 60
SCSI
X0 = NOT USED
X1 = MAINS
X2 = KEYBOARD
X3a/b = SERIAL PORT A & B WZF (OPTIONAL)
POWER
X4 = PARALLEL L=0m5 PERIPHERAL-2 CABINET
X5 = TWISTED PAIR ETHERNET
X6 = VIDEO ONBOARD CT/MR
X10a/b = PCI SCSI chain A&B
X11 = SCSI ONBOARD
RD GN BU WT
VIDEO CONNECTIONS: note: 110/230VAC TERM.
SEE Z2-9 auto-sensing SCSI EASY STORE SCSI PRINTER
1 0
[Link] L=0m5
WZI SCSI
WZJ
MOUSE SUN ULTRA 60
u sun
u
u
u
u
u
uu
X10b L=1m5/0m7 or
X1 X11 L=1m5/0m5
MAINS IN
WZK X4
SCSI
KEYBOARD BOOSTER
SCSI W/N
X2 X2
L=0m15
X3a X3b
MAINS
X5
X5
X0 POSTSCRIPT PRINTER
X11
X6 X6
L=max 3m
X4
X10b X10a
WZS
MAINS DISTRIBUTION UNIT
WZ
CABLE CONNECTIONS
EASYVISION RAD CLIENT ULTRA 60
R B
POWER
ON/OFF
ON/OFF
X7
X2 X3a X6 X2 X3a X6
X1 X5 X1 X5
MAINS MAINS
A3 99-11-12 Schr.
WZ
VIDEO CONNECTIONS
EASYVISION RAD ULTRA 5
R B
WZI WZI
SUN ULTRA 10 SUN ULTRA 10
X1 X1
MAINS IN MAINS IN
POWER POWER
ON/OFF ON/OFF
X7
X2 X2
X7
TRUE COLOUR
X3b FRAME BUFFER (UPA) X3b
X3a X3a
X7
X7
X4 X4
X6 X6 X6 X6 X6
A3 99-11-12 Schr.
WZ
VIDEO CONNECTIONS
EASYVISION RAD ULTRA 10
R B
WZI WZI
SUN ULTRA 60 SUN ULTRA 60
X1 X1
MAINS IN MAINS IN
X4 X4
X2 X2
X5 X5
X0 X0
X11 X11
X7 X7 X7 X7 X7
TRUE COLOUR FRAME BUFFER
(UPA) X8 X8
TRUE COLOUR FRAME BUFFER
(UPA)
A3 99-11-12 Schr.
WZ
VIDEO CONNECTIONS
EASYVISION RAD ULTRA 60
X1
MAINS IN X1
POWER
ON/OFF
MAINS IN
X4
110VAC 230VAC 230VAC 110VAC
X3b X4
X2
X2 X3a X6 POWER
X1 X5
MAINS ON/OFF
X3a X3b
X5 X5
X5
X0
*
X2
X11
X3b
X3a
X6
X4
X6
WZI
SUN ULTRA 10 SERVER
* X5
X5
X1
MAINS IN
230VAC 110VAC
*
*
POWER
FAST ETHERNET CAT. 5 OR HIGHER
ON/OFF
CLIENT/SERVER NETWORK
X2 X5
*
115/230V EUROPE
X3b
X3b USA
X3a 13VAC OR 9VDC
X5
NETWORK/MODEM CONNECTIONS
CLIENT/SERVER ULTRA 10
X1
MAINS IN X1
POWER
ON/OFF
MAINS IN
X4
110VAC 230VAC 230VAC 110VAC
X3b X4
X2
X2 X3a X6 POWER
X1 X5
MAINS ON/OFF
X3a X3b
X5 X5
X5
X0
*
X2
X11
X3b
X3a
WZI X6
SUN ULTRA 60 SERVER
X4
X6
X1
MAINS IN
X4 * X5
X5
X2
X3b *
X3a X3b
*
X5 FAST ETHERNET CAT. 5 OR HIGHER
*
X5
CLIENT/SERVER NETWORK
X0
TELEPHONE SOCKET
115/230VAC
FAST ETHERNET HUB
X11
115/230V EUROPE
Reader USITs
X6 USA
13VAC OR 9VDC
X9
X9
NETWORK/MODEM CONNECTIONS
CLIENT/SERVER ULTRA 60