2.5. Optical media drives................................................................................................................................ 6
2.6. Memory bank configurations................................................................................................................... 6
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 Single User Workstation
If there is only one EasyVision connected to one or more readers/USITs, the situation is like that before
release 4.2. To differentiate between such a single EasyVision RAD and those in a cluster configuration, we
call the single system a Single User Workstation.
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.
The Workspot (Client)
The EasyServer makes all images available to all EasyVisions in the cluster. The EasyVisions which also
run the RAD applications (the Workspots) don’t have an own image database and use the image database
of the RAD server. The hardware configuration of the Workspot may vary from an UltraSparc 60 with lots of
memory for fast and intensive image postprocessing, to a PC with a Java enabled Web Browser for basic
image viewing.
1.1. D
OCUMENTATION STRUCTURE
Delivered with the system
- System Manual EasyVision RAD 4.2
- Network Manual
- Printer Compatibility
Delivered with the software
- Release Bulletin EasyVision RAD 4.2 Level n
- DICOM Conformance Statement
Delivered with the Sun workstation
- Unit Manual EasyVision RAD Sun Ultra or SunBlade
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.
ECHNOLOGY
1.3. T
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)
Terminal Name : USIT 1
Terminal IP Address : 192.0.0.2
EV rad Names : EV 1
EV rad IP Adresse : 192.0.0.1
Display : EV1
Hosts : 192.0.0.1 EV1
192.0.0.3 AC 5000F
192.0.0.4 AC 5000E
IP Name : EV 1
IP Address : 192.0.0.1
3.2. PCR M
ULTI READER CONFIGURATION
Client USITReader USITReader
IDT
EasyVision
(Work spot)
Server Name : USIT 1
Server IP Address : 192.0.0.2
Terminal Name : USIT 3
Terminal IP Address : 192.0.0.4
EV rad Name : EV 1
EV rad IP Address : 192.0.0.1
Client USIT
Server Name : USIT 1
Server IP Address : 192.0.0.2
Terminal Name : USIT 2
Terminal IP Address : 192.0.0.3
EV rad Name : EV 1
EV rad IP Address : 192.0.0.1
Server Name : USIT 1
Server IP Address : 192.0.0.2
Terminal Name : USIT 4
Terminal IP Address : 192.0.0.5
EV rad Name : EV1
EV rad IP Address : 192.0.0.1
Display : EV1
Hosts : 192.0.0.1 EV1
192.0.0. 9 AC 500F-B
192.0.0.10 AC 500E-B
IP Name : EV 2
IP Address : 192.0.0.6
hub
Ethernet
Server USIT
Fast Ethernet
Hospital
Network
Reader
EasyVision
(server)
IDT
IP Name : EV 1
Terminal Name: USIT 1
Terminal IP Address : 192.0.0.2
EV rad Name : EV 1
EV rad IP Address : 192.0.0.1
Display : EV1
Hosts : 192.0.0.1 EV1
192.0.0.7 AC 5000F- A
192.0.0.8 AC 5000E- A
IP Address : 192.0.0.1
Remark:
Hostnames and IP Addresses are
examples and should be adapted to
the network
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.
4.1. C
In this cluster concept two networks are determined. Network connection via Base-T Ethernet.
Hardcopy unit board Ethernet card (Quad / Single) Dome Md2 greyscale framebuffer for 2 monitors Creator card (True color) Twin SCSI Card
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.
For a client/server environment installation, see chapter 4.3 Client / server.
Internal hard drive
CRT: Color 17", 21"; greyscale 21"
Image disks PTI 2
Memory Extension
2. TIME AND PERSONNEL NEEDED
The total installation can be done by just one person.
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!
There are no transport lockings.
• All components of the system should be placed on a table.
Do not place the system on the floor to avoid damage (kicking the system with feet, water (cleaning
personnel), dust and dirt etc.).
• Place peripheral cabinet(s) next to the Sun workstation.
• Place keyboard within reach on the table.
• Place mouse + mouse pad within reach on the table.
• Place the mains distribution unit within reach on the table. The mains distribution unit contains the
• If a network is not connected to EasyVision, connect the loopback connector to the Ethernet connection
at the end of the adaptor cable. This suppresses the UNIX message 'no carrier' (to console).
• Diagnostic purpose in Forth Diagnostics, see Unit Manual.
In case of a Single/Quad Ethernet card: The unused controllers must have an Ethernet loopback connector
4.5. L
Hardcopy units with point-to-point connection are connected to the EasyVision via split cable by a DATA
and CONTROL cable (SUB-D 37p connectors). Connect the Data and Control cables.
Ensure that the correct connections have been made for the DATA and CONTROL cables. Interchanging
Refer to the chapter "Connecting a Printer" in this Section 2.
4.6. M
THERNET LOOPBACK CONNECTOR
________________
ASER HARDCOPY UNIT (POINT-TO-POINT
these cables may destroy the hard copy interface board.
________________
AINS CABLES
NOTE
connected
NOTE
)
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.
4.7. C
Relieve the power cable, network cable and hardcopy cables with Ty-Raps or flexible cable wrapper
delivered.
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.
6.2. SCSI P
Note: The maximum length of a SCSI chain, including the printer SCSI cable, is 3 meters !!!
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.
6.3. N
ARDCOPY UNIT
RINTER
ETWORK PRINTER
The network printer is connected to the network.
6.4. P
A PostScript printer can be connected to the parallel port (max. length - 3m).
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.
2.1. P
After power on the factory-defined Power On Self Test (POST) phase and the OpenBoot PROM phase are
performed automatically (see also chapter "Sun Troubleshooting Overview", paragraphs "Factory Defined
Boot Mode" and "After Power Is Switched On").
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.
OpenBoot PROM phase
During the OpenBoot PROM phase (high level POST) you will first see "Testing Memory" on the screen. If
the OpenBoot PROM phase passes error free the system will boot automatically. If an error occurs, a
message on the screen will appear telling you which unit failed.
Now the system should boot, as the SunOS and Application Software has already been loaded at the
factory.
2.2. S
OWER ON SELF TEST AND OPENBOOT
TART-UP MENU
PROM
PHASES
After boot up the system will display the Start- up Menu. If no selection (number + <Enter>) is made within
10sec, automatically the Application will be started!
1. Start Application
2. Start Customizing
3. Go to Service Menu
4. Go to Installation/Configuration Menu
0. Shutdown
Select item 4 to start the configuration program.
2.3. C
Regarding configuration please refer to the Release Bulletin EasyVision RAD Release 4.2.chapter
configuration.
Regarding customization refer to the instructions for use of the EasyVision RAD.
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. HARD COPY UNIT CALIBRATION
5.1. I
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.
The HCU calibration is done in two major steps:
1. The density calibration (Gamma Correction) with HCU calibration and verification of it
2. The pixel size calibration
Note: Both the density calibration and pixel calibration have to be carried out for all media of all printers
connected.
5.2. P
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)
5.3. HCU D
NTRODUCTION
RECONDITIONS
ENSITY CALIBRATION
In order to use only the test image PrinterCalibration in its original unmodified condition all testimages must
be deleted and then loaded again.
6. Click [Test images]. The Test images window is displayed.
7. In the area Printer test images click [Load]. 23 test images are loaded into the database.
8. Click [Exit].
9. Exit the application and go to Service Menu.
10. Select 4. Printer Menu:
Service Menu
1. Diagnostics Menu (sunvts and product diagnostics)
2. Sun OS Menu (optical disk format and Sun Os commands)
3. File Menu (file transfer and manipulation commands)
4. Printer Menu (printer tests)
5. Monitor Menu (Monitor test images and adjustment)
6. PCR Systems (PCR diagnostics menu)
11. Select 1 HCU Calibration:
Printer Menu
1 HCU Calibration (start hardcopy unit calibration)
2 Start Printer Status Request
3 Start Data Channel Printer Test
4 Start Printer Test
5 Start S-bus/PCI Printer Visual Interface Test
0 Return to Service Menu
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/configuredPrinters.dat at the EasyVision RAD with the node name
de25sj (in this example).
13. Click
to open the hardcopy gamma correction window.
14. Right-click on the spiral icon Media and select the media in the hardcopy unit you want to calibrate the
printer for.
It is important to measure all 4 arrays (4 times 16 density values = 64 density values). This is
necessary because of the tolerances between the darkest and the lightest areas on the film.
The maximum density must be between 2.9 and 3.1 optical density.
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
Check whether Application default Standard has been selected.
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].
Click [Exit] to terminate the Hard Copy Gamma Correction.
5.3.1. V
ERIFICATION OF THE DENSITY CALIBRATION
Checking the results of the Hard Copy calibration, proceed as follows.
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.
• Left-click [Media] until your selected media size appears.
• Right-click on the Units selection spiral until
your preferred unit of length is displayed.
• Click [Print] in the Hardcopy Pixel Size calibration panel.
• Measure the distances of Length X and Length Y on the film as accurately as possible with a ruler. If X
and Y do not match, enter the lengths individually in their respective fields. The field resolution displays
the number of pixels per unit of length selected.
• 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
The selection "Specific" may be repeated for other supported media.
________________
• Click [Save] in the Hardcopy pixel size calibration panel.
• Click [Exit] to terminate the Hard Copy Pixel Size calibration.
• Click [Exit] to terminate the Hard Copy calibration.
5.5. C
HECKING THE RESULTS
• Select the printer you want to check
• click on the information icon on the top icon bar to check the results and the status of the calibration
The Printer information status panel will be displayed:
This panel supplies information about which media are calibrated (both density and pixel) on the
selected printer plus additional information.
5.1.1. Diagnostics Menu .............................................................................................................................. 11
5.1.2. SunOS Menu ..................................................................................................................................... 12
5.1.4. Printer Menu ...................................................................................................................................... 13
5.1.6. PCR systems menu........................................................................................................................... 13
5.1.6.1. File Transfer Settings Menu........................................................................................................... 13
5.1.6.2. File Transfer Menu......................................................................................................................... 14
5.1.6.3. Serial Interface Menu..................................................................................................................... 14
5.2.1. Diagnostics Menu .............................................................................................................................. 16
5.2.2. SunOS Menu ..................................................................................................................................... 16
5.2.4. Printer Menu ...................................................................................................................................... 18
7.5.5. Max Operations ................................................................................................................................. 29
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).
To access the service menu environment select 3 Go to Service Menu in the StartUp menu. Then at the
password: prompt enter password
1. Diagnostics Menu (sunvts and product diagnostics)
2. SunOs Menu (optical disk format and Sun Os commands)
3. File Menu (file transfer and manipulation commands)
4. Printer Menu (printer tests)
5. Monitor Menu (Monitor test images and adjustment)
6. PCR Systems (PCR diagnostics menu)
0 Logout
5.1.1. D
ERVICE MENU VIA SUN CONSOLE
Service Menu
===========
Enter the number of your choice: 1
IAGNOSTICS MENU
Diagnostics Menu
================
1. Start SunVts (Sunvts hardware diagnostics)
After using SunVTS, use ëExit...í in the workspace pop-up menu
to return to this menu
2. Start EasyStore DOR Test (sa0)
3. Start CT/MR input DOR Test (sa1)
4. Start Dials Test
5. Check Modemís SW Settings
Type ~. to quit the check and return to this menu.
6. Initialize Modem
7. Set Speed of Serial port
8. Start PCI Reader Interface Test
0. Return to the service menu
Enter the number of your choice: 0
Select 8. Start PCI Reader Interface Test
The System will prompt:
Connect PCR Reader testbox. Press <Enter> to continue :
after the testbox has been connected and powered press Enter, The system will respond:
PCR Reader Interface test takes about 5 seconds
if the system didn’t detect any fault condition it will return the message
PCR Reader Interface test succeeded
press <Enter> to continue
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
poll control line , timed out
PCR Reader Interface test failed
Press <Enter> to continue :
Caution
The test program will finish the test with the following message
even if the test box was not connected during the test.
ëReader Interface Testí ended normal, status 0
Control channel and Data channel are both ok up to test box
Press <Enter> to continue:
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.
5.1.2. SUNOS M
SunOs Menu
==========
1. Optical Disk Format Menu.
2. SunOs: a C-shell is started in the service directory.
Type ëexití to return to this menu.
3. ADB Convert (synchronize Anatomy DataBase and Processing Keys)
3. SunOS: OpenWindows is started in the service-directory
Use ëExit...í in the workspace pop-up menu to return to this menu
0 Return to the service menu
Enter the number of your choice: 0
5.1.3. F
1 Logfiles Inspection (a C-shell is started in the log directory)
Use 'ls -l', 'more', 'tail -31l' to examine
the logfiles.
Type 'exit' to return to this menu.
2 Images Inspection (a C-shell is started in the images directory)
Use 'ls -l' to examine the image files.
Type 'exit' to return to this menu.
3 Create file /tmp/logfiles.zip containing logfiles and config files.
1 HCU Calibration (start hardcopy unit calibration)
2 Start Printer Status Request
3 Start Data Channel Printer Test
Data is sent to the HCU via the data channel, then
press print on the HCU control panel for output
4 Start Printer Test
5 Start S-bus/PCI Printer Visual Interface Test (Led board required)
0 Return to Service Menu
Enter the number of your choice:
ONITOR MENU
Monitor Menu
============
1 Start Monitor Color Map Test
2 Show LCD testimage (POPO_1288x1024.gif)
0 Return to Service Menu
Enter the number of your choice:
SYSTEMS MENU
PCR Systems Menu
================
1 File Transfer- and Compression Settings Menu
2 File Transfer Menu (log and image file transfer)
3 ADB Convert (synchronize Anatomy Data Base and Processing Keys)
4 Set Serial Interface Parameters
5 PCR Reader Documentation
0 Return to Service Menu
Enter the number of your choice:
5.1.6.1. File Transfer Settings Menu
File Transfer Settings Menu:
============================
Actual Configuration:
EasyVision RTAC: sz/rz
EasyVision RTAC: sz/rz
Compression: Zip
1 EasyVision RTAC: Use kermit (works only with modem
terminal
2 EasyVision RTAC: Use kermit connections)
3 EasyVision RTAC: Use sz/rz (works only with modem terminal
4 EasyVision RTAC: Use sz/rz connections)
5 EasyVision RTAC: Use ftp (works only with TCP/IP and ftp-
server running on RTAC host)
6 Zip (mostly used compression SW on DOS based
computers)
7 UNIX compress ( tar| mostly used compression SW on UNIX
based computers)
0 Return to Service Menu
Enter the number of your choice:
5.1.6.2. File Transfer Menu
File Transfer Menu
==================
Actual Configuration: RTAC EasyVision : sz/rz
EasyVision RTAC sz/rz
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/to.
Then start the desired protocol by typing its
name followed by the appropriate arguments:)
0 Return to Service Menu
Enter the number of your choice:
5.1.6.3. Serial Interface Menu
Serial Interface Menu:
======================
Actual Configuration:
Device: ttyb
Mode: Modem
N Set Mode to Nullmodem (RTAC-cable-EV)
M Set Mode to M odem (RTAC-modem-EV)
!!! NOTE !!!
Donít forget to (re)set this flag to Modem
if Modem connection is desired later on!
!!! NOTE !!!
Insert the CD-ROM containing the PCR Reader Documentation
and press Return to continue:
OpenWindows and the Acrobat Reader will be started.
On ‘File’ and ‘Open’ the 'Open' window of the Acrobat Reader will be displayed.
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 14:13:51 on term/b
PMSN-ICS Solaris 2.5.1 adapted for EasyVision June 1996
+-----------------------------------------------------------------+
| WARNING : Access for authorised persons only |
+-----------------------------------------------------------------+
Last local login: Tue Dec 2 11:26:37 MET 1997
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)
0 Logout
Enter the number of your choice:
IAGNOSTICS MENU
Diagnostics Menu
================
1 Start SunVts (Sun hardware diagnostics)
2 Start EasyStore DOR Test (sa0)
3 Start CT/MR input DOR Test (sa1)
4 Start Dials Test
0 Return to Service Menu
Enter the number of your choice:
5.2.2. SUNOS M
SunOS Menu
==========
1 Optical Disk Format Menu
2 SunOS: a C-shell is started in the service-directory
Type 'exit' to return to this menu.
1 Logfiles Inspection (a C-shell is started in the log directory)
Use 'ls -l', 'more', 'tail -31l' to examine
the logfiles.
Type 'exit' to return to this menu.
2 Images Inspection (a C-shell is started in the images directory)
Use 'ls -l' to examine the image files.
Type 'exit' to return to this menu.
3 Create file /tmp/logfiles.zip containing logfiles and config files.
0 Return to Service Menu
Enter the number of your choice:
The following protocols are available:
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/logfiles.zip)
The next options are available:
1 Use short filenames
2 Use long filenames
1 Start Printer Status Request
2 Start Data Channel Printer Test
Data is sent to the HCU via the data channel, then
press print on the HCU control panel for output
3 Start Printer Test
4 Start S-bus Printer Interface Test (HCU testbox required)
5 Start S-bus Printer Visual Interface Test (Led board required)
0 Return to Service Menu
Enter the number of your choice:
For test contents see Service Manual Imager Compatibility
YSTEMS MENU (REMOTE
)
SunOS 5.6
login: Service
Password: <Host ID>
Last login: Thu Sep 14 13:04:52 from 130.143.187.215
PMSN-EVM Sun Microsystems Inc. SunOS 5.6 Generic August 1997
+---------------------------------------------------+------------+
| WARNING : Access for authorised persons only |
+---------------------------------------------------+------------+
Last local login: Tue Sep 12 16:24:18 MET DST 2000
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)
Default Remote File Transfer Modes:
RTAC -> EV : sz/rz
EV -> RTAC : sz/rz
Compression: Zip
Could not find Release Info File for PCR User Terminal Server.
Might be wrong release/version/level.
Press Return to continue.
PCR Systems Menu:
1 File Transfer- and Compression Settings Menu
2 File Transfer Menu (log and image file transfer)
0 Return to Main Menu
Enter the number of your choice: 1
File Transfer Settings Menu:
Actual Configuration:
EasyVision --> RTAC : sz/rz
EasyVision <-- RTAC : sz/rz
Compression : Zip
1 EasyVision --> RTAC : Use kermit (works only with modem
2 EasyVision <-- RTAC : Use kermit terminal connections)
3 EasyVision --> RTAC : Use sz/rz (works only with modem
4 EasyVision <-- RTAC : Use sz/rz terminal connections)
5 EasyVision <--> RTAC : Use ftp (works only with TCP/IP,
and ftp server must be
running on RTAC host)
6 Zip (Most used compression S/W on DOS based computer)
7 UNIX compress (tar| Most used compression S/W on UNIX based
computer)
1 EasyVision --> RTAC : Use kermit (works only with modem
2 EasyVision <-- RTAC : Use kermit terminal connections)
3 EasyVision --> RTAC : Use sz/rz (works only with modem
4 EasyVision <-- RTAC : Use sz/rz terminal connections)
5 EasyVision <--> RTAC : Use ftp (works only with TCP/IP,
and ftp server must be
running on RTAC host)
6 Zip (Most used compression S/W on DOS based computer)
7 UNIX compress (tar| Most used compression S/W on UNIX based
computer)
0 Return to Service Menu
Enter the number of your choice: 0
PCR Systems Menu:
1 File Transfer- and Compression Settings Menu
2 File Transfer Menu (log and image file transfer)
0 Return to Main Menu
Enter the number of your choice: 2
File Transfer Menu:
Actual Configuration: RTAC -> EasyVision: ftp
EasyVision -> RTAC: ftp
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).
Actual Configuration: RTAC -> EasyVision: ftp
EasyVision -> RTAC: ftp
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).
0 Return to Service Menu
Enter the number of your choice: 0
PCR Systems Menu:
1 File Transfer- and Compression Settings Menu
2 File Transfer Menu (log and image file transfer)
0 Return to Main Menu
Enter the number of your choice: 0
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)
Application License Prog. Expiration date Key Comment Host-ID
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
#
127.0.0.1 localhost
#
192.168.12.64 ev1 loghost
222.222.222.221 evppp
222.222.222.222 remoteppp
192.168.12.80 ev2
Explanation:
127.0.0.1 localhost for loopback
192.168.12.64 ev1 loghost own IP-address, always followed by loghost
222.222.222.221 evppp own PPP connection IP address
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.
Log files of the application software are written to /var/adm/cdslog.
Important logs are:
file name software task / usage
cdRecordableServer_cdRecordable.log CD-R server
computeServer_compute.log
dbServer_db.log database server
hcServer_hcs0.log hardcopy unit server, printing
networkReaderServer_dmsReader.log Reader server for DMS Readers: AC3/000, 9000
networkReaderServer_networkReader.log Reader server for DICOM Readers: AC5/000, Compano
networkServer_export.log Network server for export jobs
networkServer_import.log Network server for import jobs
printJobServer_printJob.log
systemMonitor_systemMonitor.log System monitor, observes all software tasks
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.
Critical processes: dBServer
SetupServer
Non-critical processes: a specific application, e.g. BCR, 3D etc
http server
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.
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 error.log file.
Lmgrd.startup
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 license.dat file has been uploaded in the
/easydata directory. Only in case of a Server or Standalone:
Wrong Host-ID Example:
17:01:39 (lmgrd) FLEXlm (v5.12a) started on ev1 (Sun) (12/10/1997)
17:01:39 (lmgrd) FLEXlm Copyright 1988-1996, Globetrotter Software, Inc.
17:01:39 (lmgrd) World Wide Web: http://www.globetrotter.com
17:01:39 (lmgrd) License file: "/easydata/license.dat"
17:01:39 (lmgrd) Starting vendor daemons ...
17:01:39 (lmgrd) Started easylicd (internet tcp_port 32810 pid 2336)
17:01:39 (easylicd) Wrong hostid, exiting (expected 8087f687, got 8087f688).
17:01:39 (lmgrd) Please correct problem and restart daemons
17:01:45 (lmgrd) lmgrd will now shut down all the vendor daemons
install.log
The installation logfile install.log can be found in the /var/adm/cdslog/setup directory. In this file errors during
installation are written.
7.1. C
OLLECTING LOG FILES
There is a function implemented in the software to collect automatically or manually all log and config files
and compress it to a ZIP archive named evlog.zip. This file is only generated on EasyVision RAD systems
and contains additional PCR specific files, different to other EasyVisions where the file is named
logfiles.zip.
evlog.zip is created in the sub-directory /var/adm (see procedure below). An existing evlog.zip file is
renamed to evlog0.zip, evlog0.zip to evlog1.zip, and so on (up to evlog3.zip).
evlog.zip 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,
lease send always evlog.zip not logfiles.zip.
evlog.zip contains:
-
all log and messages files
-
all config, customization and calibration files
-
license.dat (software license)
-
all PCR relevant files of /easydata/UI/configuration
-
setup database (ZIP)
evlog.zip can be generated manually using the following procedure:
First of all a TCP connection is created between the hosts who want to communicate via the DICOM
protocol. The following example gives the connection between an EasyVision (EV1) and a DICOM node
(DICOM1) at port 50082. In fact the DICOM connection is initiated at the port (DICOM listen port) written in
the Conformance Statement, but the child process is transferred to port 50082. Now the server can start
another TCP connection.
The next line is written in the logfile:
Jul 25 10:06:23 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 10:06:26 EV1 sunConfig: Info:RELEASED TCP CONNECTION from host: [EV1] to
host: [DICOM1].
7.3. A
SSOCIATION
PDU T
YPES
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.
Two Application Entities establish an association by agreeing on an application context. The requester of an
association proposes an Application Context Name and the acceptor returns either the same or a different
Application Context Name. The returned name specifies the application context to be used for this
association.
According to the DICOM Standard a single DICOM Application Context Name is "1.2.840.10008.3.1.1.1".
7.5.2. L
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:
Jul 25 10:06:30 EV1 sunEasyVision: ObjC [DULConnection@0xdd9328 __abort:reason:]
Sent: [ABORT_PDU_TYPE] with SOURCE: [ABORT_AS_DUL_PROVIDER] and REASON:
[ABORT_INVALID_PDU_PARAMETER] from: [EV1] to: [DICOM1] (aborting...). -- (TBX,W)
Jul 25 10:06:30 EV1 sunEasyVision: Info:RELEASED TCP CONNECTION from host: [EV1]
to host: [DICOM1].
7.5.3. P
The maximum PDU length the remote DICOM node can handle. In this case a maximum of 16384 bytes is
allowed.
7.5.4. I
The implementation identification notification allows implementations of communicating AEs to identify each
other at Association establishment time. It is intended to provide respective (each network node knows the
other's implementation identity) and non-ambiguous identification in the event of communication problems
encountered between two nodes. This negotiation is required.
Implementation identification relies on two pieces of information:
defined registered value by the ISO
defined registered value by the ISO
The version name extracted from the EasyVision software.
The implementation version name of the remote DICOM node.
The maximum number of outstanding operations and/or sub-operations it may invoke or performed
asynchronously.
The EasyVision does not support asynchronous operations. (see Conformance Statement)
7.6. V
The verifying of the DICOM syntaxes starts with (e.g. verifying SC-Image Store):
Mar 17 11:14:23 EV1 networkServer_network_EV1: Info:START VERIFYING:
[1.2.840.10008.5.1.4.1.1.7] from: [EV1] to: [DICOM1]
LOG: boolean 1: logging per attribute 0: no specific logging per attribute
REPAIR: boolean 1: repair attribute 0: not repair attribute
REJECT: boolean 1: do not put image in database 0: put image in database
PMSNET: boolean 1: convert to PMSNet 0: do not convert PMSNet
GCOM: boolean 1: convert to GCOM 0: do not convert GCOM
PURE: boolean 1: accept only DICOM attributes 0: do not accept only DICOM attrbutes
IMPORTANT ........................................................................................................................................... 3
SUN WORKSTATION ............................................................................................................................ 3
2.4. System Disk ............................................................................................................................................ 4
2.6. DVD / CD Drive ....................................................................................................................................... 6
2.8. Power Supply .......................................................................................................................................... 6
2.9. Various Ultra 10/60, SunBlade Parts ...................................................................................................... 7
3.4. Power Supply .......................................................................................................................................... 8
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:
c2t11d0sx = 1st image disk
c2t10d0sx = 2nd image disk
c2t9d0sx = 2rd image disk
c2t8d0sx = 4th image disk
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.
6. Save the file vfstab and quit textedit.
7. Delete the file /etc/vfstab% created by textedit by entering rm /etc/vfstab%
8. Shutdown and power-off the EasyVision (disconnect the mains power cable!).
9. Power-off the peripheral cabinets (disconnect the mains power cable!).
10. Now replace or add the image disk(s):
For external image disk(s):
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!).
For internal image 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!).
11. Power-on the peripheral cabinet(s).
12. Power-on the EasyVision and press <Stop> + <a> during memory initialization.
13. At the ok prompt enter boot -r
14. At the EASYVISION STARTUP MENU :
- Select 3 Go to Service Menu
- Password: password
- Select 2 SunOS Menu
- Select 3 SunOS: OpenWindows
15. At the # prompt enter format
16. Select the replaced disk (cXt11, cXt10 etc.).
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.
Power supply is not an
FRU, replace complete
Peripheral Cabinet
4. MONITOR
Step Action Refer to Remark
1 Replace Monitor A monitor is an FRU
2 Adjust Monitor Manual: System Manual EasyVision
Section:
Adjustments
5. DOME MD2 FRAMEBUFFER
5.1. U
LTRA
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. U
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. SUNB
LADE
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.
1.3. Power Connector .................................................................................................................................. 3
1.4. Bus Termination.................................................................................................................................... 3
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
6.
HARDCOPY UNIT INTERFACE BOARD .......................................................................................... 21
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)
SCSI AddressJumper JumperJumperJumper
0 OUT OUT OUT OUT
1 OUT OUT OUT IN
2 OUT OUT IN OUT
3 OUT OUT IN IN
4 OUT IN OUT OUT
5 OUT IN OUT IN
6 OUT IN IN OUT
7 OUT IN IN IN
8 IN OUT OUT OUT
9 IN OUT OUT IN
A IN OUT IN OUT
B IN OUT IN IN
C IN IN OUT OUT
D IN IN OUT IN
E IN IN IN OUT
F IN IN IN IN
ID3 = Wide SCSI only
OUT =jumper not installed
IN = jumper installed
1.2. D
DDRESSING
EVICE NAMES
ID3 ID2 ID1 ID0
Example: c0t3d0s0:
c = controller
t = target
d = disc
s = slice (partition)
1.3. P
All SCSI devices use +5Vdc and +12Vdc
The DC power connector pinning is shown in the figure below.
Pin 1:
Pin 2:
Pin 3:
Pin 4: +5V
1.4. B
The SCSI bus is terminated with a SCSI Terminator at the end of the SCSI chain.
This means that from all SCSI devices the SCSI terminator (chips) must be removed. For factory delivered
systems this has already been done. In case of replacing or addin g a (optional) SCSI device you should
check if the SCSI termination has been removed!
Applies to EasyVision based on Ultra 5, Ultra 10, Ultra 60, SunBlade with EVRAD R4.2 L3 or higher
software. The CD-recordable drive is installed in the Peripheral 2 or 4 cabinet.
LEXTOR PLEXWRITER
SCSI address =4.
2.2. P
HILIPS
CDD 3600
Applies to EasyVision based on Ultra 5, Ultra 10 and Ultra 60 with EVRAD R4.2 L3 or higher software.
The CD-recordable drive is installed in the Peripheral 1 cabinet.
Do not mount the CDD 3600 drive in the Peripheral 2 or Peripheral 4 Cabinet!
The optical disk drive is delivered in the Peripheral 2 or Peripheral 4 Cabinet.
In case of an upgrade:
• Make sure that the EasyStore option has been purchased and the License file has been updated
before you start upgrading.
• When the optical disk drive has been installed and attached to the SCSI bus the operating system and
application software has to be reinstalled to incorporate the OD drive in the system.
• After the complete software has been installed start the configuration tool.
• Edit the EasyVision configuration.
• In the configuration screen click on Peripheral Settings.
• Click Storage Drive = Present and click Exit.
• In the entry field Storage drivename enter a name for the drive, e.g. Storage drive on EVRAD.
• Execute the configuration.
Set the jumper settings :
SCSI address =3.
Terminators resistors removed
Use the disk as is and do NOT install the SCSI Narrow to Wide adapter.
The jumper settings of the SCSI.
SCSI address =B (11) Image disk
SCSI address =A (10) for 1
additional image disk.
SCSI address =9 for 2 additional
image disk.
SCSI address =8 for 3 additional
image disk.
4.8. IBM DRVS 9.1 GB (KIT: 4522 300 15062)
Applies to EasyVision based on Ultra 5, Ultra 10, Ultra 60.
The hard disk drive is factory installed in the Peripheral 2 cabinet
Use the disk as is and do NOT install the SCSI Narrow to Wide adapter.
The jumper settings of the SCSI.
SCSI address =B (11) Image disk
SCSI address =A (10) for 1
additional image disk.
SCSI address =9 for 2 additional
image disk.
SCSI address =8 for 3 additional
image disk.
4.9. IBM 4.5 GB / 9.1 GB (KIT: 4522 300 15061)
Applies to EasyVision based on Ultra 5, Ultra 10, Ultra 60 with external image disk.
The hard disk drive is factory installed in the Peripheral 2 or Peripheral 4 Cabinet
To install a DOME GreyScale FRAMEBUFFER in an Ultra 60 the following procedure must be done:
• 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.
5.2. SUN PGX F
PGRADING AN ULTRA
RAMEBUFFER
60
Applies to EasyVision based on Ultra 5 and Ultra 10.
The PGX card is usually factory installed in the Sun computer. In case of an upgrade: