Quick Reference Manual

A SP Quick Reference Manual
supports software version AccuRay 1190 Release 7.0, Advant 1.8.3, Smart Platform ESP330.0C
Smart Platform Quick Reference Manual

References:
Smart Platform 1200 Installation and Maintenance Manual
Smart Platform 700 Installation and Maintenance Manual
Smart Platform Trouble shooting Procedures Manual
Smart Platform Utility Users Manual
Smart Platform Software Manual (086349-XXX, 280.0 and later)
Smart Platform Software Manual (086444-XXX, 300.4 and later)
Line Prompts
$$ Primary line prompt, AVOS shell
$! Secondary line prompt, AVOS shell
I> Object inspector prompt
: Editor prompt
gonzo:GONZO prompt
Special Functions
If the system prints "abnormal termination of utility"
message, type:
shift, Ctrl, |
or
shift, Ctrl, ~ (Euro keyboards)
Copyright © 2002, ABB University
A-1
C232 AccuRay Smart Platform Maintenance Course
To return to the AVOS prompt $$.
If the system shows the $> prompt, you are in the sub-
shell. Typing '(cr) at the $$ prompt will cause this.
Type '(cr) to return to $$ prompt. This usually hap-
pens when someone hits the 'key, located next to the
return key by mistake.
A-2
A - SP Quick Reference Manual
Unix Commands
General Commands - SP Utility User Guide, Section 9
$$cat /pathname/filename(cr)-Concatenate and print
files
example: $$cat /ss01/clm/startup(cr)
$$more /pathname/filename(cr)-Display paged file
example: $$more /ss01/clm/startup1(cr)
$$rm /pathname/filename(cr)-Remove file
example: $$rm /ss01/clm/frame.0105
$$cp /pathname/filename /pathname/filename(cr)-Copy
file
example: $$cp /ss01/clm/io.0105 /ss01/clm/io.ini(cr)
$$mv /pathname/filename /pathname/filename(cr)-Move
file
example: $$mv /ss01/clm/frame.0105 /ss01/clm/
frame.ini(cr)
$$df /bram1(cr)-List free space on /ss01
$$df /bram2(cr)-List free space on /appl
Debugging Commands - SP Utility User Guide, Section 10
$$derr(cr) Display Error History
$$dfree(cr) Display Memory Free Space
$$dobj(cr) Display Object List
$$dproc(cr) Display Processor
$$droot(cr) Display Root Directory
$$fsck /bram1 File System Consistency Check and inter-
A-3
active repair
$$fsck /bram2 File System Consistency Check and inter-
active repair
$$date(cr) Display current date and time
To enter Current Date and Time
$$date 01-04-2000 09:45(cr)
A-4
Smart Platform Bram Operations
NOTE:
umount (unmount) only worKs with the 086349-XX MPRC
Bram exhibits some of the characteristics of diskettes.
They can be unmounted in the same fashion as diskettes.
To unmount /ss01, move the working directory to root
$$cd(cr)
$$umount /bram1(cr)
To unmount /bram2, move the working directory to root
$$cd(cr)
$$umount /bram2(cr)
To mount bram
$$mount /bram1 /ss01(cr)
$$mount -r /bram2 /appl(cr)
Note: the system automatically mounts /bram2 read
only, during startup. This is the equivalent of
setting write protect.
A droot command can be used to check what is currently
mounted in the system.
$$droot(cr)
A-5
List bram Files
LIST FILES - SP Utility Manual Section 3.0
This procedure can be used as a quick check, to see if
bram is ok.
List files, short form (title only).
$$cd /ss01(cr)
or
$$cd /appl(cr)
$$ls *(cr)
List in spread fashion
$$lsf *(cr)
List long
$$ls -l *(cr)
Example: List contents of /ss01/clm
$$cd /ss01/clm(cr)
$$ls -l(cr)
This is the most commonly used form to check the re-
sults of a gstore operation.
Print Working Directory Name
$$pwd(cr)
Use this if you're not sure what directory you have
open, or if the system will not let you unmount a /bram
as required by fsck.
A-6
fsck Procedure
The fsck command can be used to repair diskette prob-
lems. fsck makes multiple passes. Make sure that the
bram diskette being checked is unmounted and inactive
while fsck is running. If corrective action is taken
on a mounted file system, the system must be restarted
immediately. This precaution is necessary so that bad
in-memory copies of the file system structures are not
used or written back to the bram.
Example:
Remove bad data clusters from /ss01
$$fsck /bram1(cr)
This procedure is interactive, answer y
to the questions, to perform necessary
repairs.
Restart the ASPC, by pressing the RESET button.
Wait for the ASPC to complete restart.
When the ASPC is fully operational, change direc-
tory to lost and found, to remove unconnected data
clusters
$$cd /ss01/lost+found(cr)
$$rm *(cr)
Restart the ASPC
A-7
Performing a gstore
1. Remove all unnecessary .date, .save and /or .bak
files, using the rm command. Failure to do may re-
sult in insufficient free space to save future
gstore files. There is no error message! gstore
saves a partial ini file and terminates. You must
use an ls -l command to check file length and de-
termine all data was saved. Also do a scanner
print to be sure all sensors are operational.
$$inspect(cr)
I>()[scanner01 print](cr)
I>:Q(cr)
$$
2. Store a current copy of the ini files on the /ss01
floppy
a. Install the ss01 diskette in the a: (or
b:) drive of the service work station.
b. Press F6 at the $$ , to open the gonzo
window.
Note: The console may respond with nonsense char-
acters and appear dead, until the gonzo win-
dow opens.
c. When the gonzo prompt appears, select
the 3.5 inch diskette drive you wish to back
up to:
A-8
gonzo:w a:\(cr) or w b:\(cr).
d. Save the initialization files to PC
floppy diskette by typing:
gonzo:< ss01.sav(cr)
e. When the transfer is finished, indicat-
ed by the return of the gonzo prompt, termi-
nate gonzo.
gonzo: f(cr)
gonzo: q(cr)
This will terminate gonzo and
close the window. You should return to the
$$ prompt.
Note:if you get gonzo confused, or fail to
terminate gonzo properly, typing shift ctrl
| (shift ctrl ~ -european keyboards)
3. Perform the required gstores.
$$gstore(cr)
Type 1 to save scanner01 to frame.ini
Type 2 to save fhi to fhi.ini
Type 3 to save ucHardware to io.ini
type 4 to save pmmInterface to pmm.ini
type 5 to save Application Information to appl.ini
type q to quit gstore and return to the $$ prompt
4. Restart the Smart Platform on the new initializa-
tion files and verify proper operation.
A-9
5. After verifying proper operation of the Smart Plat-
form, backup the ss01 to a fresh copy.a.In-
stall the ss01 diskette in the a: (or b:)
drive of the service work station.
b. Press F6 at the $$ , to open the gonzo
window.
Note: The console may respond with nonsense char-
acters and appear dead, until the gonzo win-
dow opens.
c. When the gonzo prompt appears, select
the 3.5 inch diskette drive you wish to back
up to:
gonzo:w a:\(cr) or w b:\(cr).
d. Save the initialization files to PC
floppy diskette by typing:
e. When the transfer is finished, indicat-
ed by the return of the gonzo prompt, termi-
nate gonzo.
gonzo: f(cr)
gonzo: q(cr)
A-10
Smart Platform SCN Procedure
REFER to Smart Platform Software Manual, chapters 5,6,
and 7. You must have a Rev. C manual for SP220 soft-
ware!
1. Start up the system on the current bram software.
Verify operation.
$$reset(cr)
2. Unmount the /brams.
$$umount /bram1(cr)
$$umount /bram2(cr)
3. Perform an fsck on each of the brams.
$$fsck /bram1(cr)
$$fsck /bram2(cr)
4. Remount the diskettes.
$$mount /bram1 /ss01(cr)
$$mount /bram2 /appl(cr)
5. Make copies of the five system diskettes (ss01,
sensors, product, appl1, appl2) using dos.
Open the dos window.
a>diskcopy a: b:
a>exit(cr)to return to the sp window.
6. Back the system up to floppy diskettes.
Type F6 to open the gonzo window.
Select the 3.5 inch drive you wish to back up to.
gonzo:w a:\(cr) or w b:\(cr)
A-11
Put the ss01 diskette in the selected diskette
drive.
Put the sensors diskette in the selected diskette
drive.
gonzo:< s1190.sav(cr)
Put the product diskette in the selected diskette
drive.
gonzo:< p1190.sav(cr)
Put the appl1 diskette in the selected diskette
drive.
gonzo:< appl1.sav(cr)
drive.
gonzo:f(cr)
gonzo:q(cr)
7. Check the current software revision.
$$cd /appl/lib(cr)
$$what -s *.lib
$$cd /ss01/clm(cr)
$$. revid(cr)
Visually examine the printout to ensure that the
system is not on the new revision. Updating the
same software twice will destroy the initializa-
A-12
tion files!
8. Print the SCN instructions.
Open a DOS window.
Put the SCN A diskette in the 3.5 inch drive.
At the dos prompt type:
c>print a:\readme(cr) or c>print b:\readme(cr)
When DOS asks for the name of the output device
type:
lpt1(cr)
9. Follow the printed instruction for the update pro-
cedure!
10. When the contents of the system have been up-
dated, restart the system on the new software. Be
sure the system works correctly! Verify proper
operation.
11. Check the current software revision.
$$cd /appl/lib(cr)
$$what -s *.lib
$$cd /ss01/clm(cr)
$$. revid(cr)
Visually examine the printout to ensure that all
the updates listed in the instructions took place!
12. Make copies of the five system diskettes
(ss01, sensors, product, appl1, appl2) using DOS.
Open the dos window.
A-13
a>diskcopy a: b:
a>exit(cr)to return to the sp window.
13. Backup the contents of bram to a new set of
the system floppy diskettes!
WARNING!
DO NOT USE YOUR ONLY COPY OF THE OLD LOAD! If the scn
has a problem, you need to be able to recover, by doing
a build bram (Chapter 3 - Software Manual), and restore
(described in chapter 5 - Software manual) the previous
software.
Type F6 to open the gonzo window.
Select the 3.5 inch drive you wish to back up to.
gonzo:w a:\(cr) or w b:\(cr)
Put the ss01 diskette in the selected diskette
drive.
Put the sensors diskette in the selected diskette
drive.
gonzo:< s1190.sav(cr)
Put the product diskette in the selected diskette
drive.
gonzo:< p1190.sav(cr)
drive.
A-14
drive.
gonzo:f(cr)
gonzo:q(cr)
A-15
OBJECT INSPECTOR
$$inspect(cr)
I>:h(cr)- Help, prints a list of inspector commands
I>:global(cr)-Print a global list of object names
I>:pa off-pa(ge) off
I>:pa on- pa(ge) on
NOTE: typing a q, while in pa(ge) on, when displaying
an object, will cause the return to the I>
Display Object
I>objectName(cr)
I>0xaddress(cr)
If the system responds with a 0x address
Type ~ (cr) to display the variable data list.
Modify Object
I>objectName->varibleName=value(cr)
I>0xaddress->variableName=value(cr)
I>0xaddress->NDXVAR[X]->V1=value(cr)NOTE: X = variable
number
I>:pm objectName - print method, lists all the methods
an obect can execute via
the message command.
I>:!(cr) -go to sub-shell for utility operations.
Type exit(cr) at $! prompt, will return to I>.
I>.(cr)- Repeat the last Inspect instruction
I>:q(cr)- quit, c-files resident (will not allow umount
A-16
of ss01)
I>:Q(cr)- quit, no files resident
A-17
Note:
The ~ key character has been reassigned on European
keyboards. You may have to experiment with the keys,
until you get the right one.
Special characters
' - Literal string
\ - Delimiter
: - Delimiter between arguments
CTRL BREAK or CTRL C- Terminate command
CTRL U- Delete line
If the system prints "abnormal termination of utility"
message, type:
shift, Ctrl, |
or
shift, Ctrl, ~ (Euro keyboards)
To return to the AVOS prompt $$.
If the system shows the $! prompt, you are in the sub-
shell. Typing :! while in inspect causes this. Type
exit(cr) to return to I> prompt.
A-18
Inspect Messages
Command format
I>(format)[objectName method:argument](cr)
format
char A one byte character string using typo-
graphic symbols such as A, &, and +.
int A signed integer number taking two
bytes.
short A signed integer number taking two
bytes.
long A signed integer number taking four
bytes.
Double A double precision (eight bytes) float-
ing point number.
DDB A Double Decimal Byte format used in the
PMM emulator.
bool Used to designate a boolean logic func-
tion. It can either be a long or a
char.
id Identifies an object id address. It is
a long size.
hid The same as an id but not part of the
initialization activity at startup.
objectName Selected from the names printed on the
global list.
A-19
method Selected from the list produced by :pm
(print method).
argument Arguments are used to pass information
to an object.
EXAMPLES:
I>()[pmmFrame01 stdzErrors](cr)
I>()[betaSensor01 stdzFor:0 mode:0](cr)
Note:
mode:0 = dirty standardize
mode:1 = clean standardize
See the Troubleshooting section of this manual for more
information.
A-20
Using the EDITOR
Enter EDITOR
$$ed /pathname/file.name(cr) Load the
editor and
read file
contents to
the editor
buffer.
: Editor
Prompt.
Use editor to modify file
:w(cr) Write the
file to dis-
kette.
:q(cr) Quit the text
editor.
EDITOR COMMANDS
a append
c change
d delete
i insert
p print
q quit
r read
A-21
u undo
w write
s substitute
/ Search delimiter
. terminate for a,c,i
A-22
editor Example
This example changes the primary prompt to Frame1 $$.
This is very helpful when more than one Smart Platform
is connected to the same work station. Hopefully this
will alert you that you are typing something in the
wrong window, before you kill the software. The com-
mand is inserted after line 19 because a programmer
told me that is were it goes!
$$cd /ss01/clm(cr) This allows the editor to ac-
cess
the work buffer.
$$ed startup(cr) Loadtheeditorandputthecontents
of startup in the work buffer.
: 1,$p(cr) Print the contents of the buffer.
:20i(cr) Insert text at line 20.
PS1='Frame1 $$ '(cr)
.(cr) Terminate the insert.
:w(cr) Write startup file back to
diskette.
:q(cr) Exit the editor
$$
A-23
ACE - 2.0 Function Keys
Alt F1 Show Function Key Meaning
Shift F1 Terminate This task
F2 Turn On Print Logging
Shift-F2 Turn Off Print Logging
F3 Turn On Disk Logging
Shift-F3 Turn Off Disk Logging
F4 Change or display configuration
F5 Terminate this task
F6 Run gonzo -s -b 19200
F7 Run Workstation Software
ESC Exit window
CTRL-SHIFT-DEL - Abort, the equivalent of the

three finger crash. Use this com-
mand to reboot the Personal Com-
puter.
WARNING!
The following command will cause a window to disappear!
CTRL-ALT-DEL Close active window

(but not port)
If this happens, re-open the window.
Type 2 to continue.
In the event of lost Serial Communication try:
A-24
Ctrl c
Ctrl u
Ctrl Break
A-25
DESQVIEW Operations
ALT Select Main Menu
O Open window
S Switch window
C Close window
R Rearrange window
Z Zoom
M Mark
Transfer
Scissors
OPEN WINDOW
AMS CONSOLE AC
CR41 STATUS LINESL
DOS(128K) D1
L6/CR41 CONSOLEL6
Memory Status MS
REMOTE ACCESS MGRRA
UNIX LINE UX
Error Messages EM
GONZO
CLOSE WINDOW
Are you sure?

Yes Y
No N
SWITCH WINDOW
AMS CONSOLE 1
CR41 STATUS LINE2
L6/CR41 CONSOLE3
A-26
Rearrange
Move M
Resize R
Position 123456789
Scroll S
Freeze F
Hide H
Put Aside
Change Colors
Video Options
Move
Done (cr)
Move M
Resize
Resize
Done (cr)
Move M
Resize
A-27
CREATING A HOT KEY
Warning:
DO NOT select any key already used by ACE or DESQ-
view.
Ctrl s and Ctrl q are used by UNIX to control
scrolling.
Hot Keys are only active in the window in which they
are created.
1. Position the cursor in the window, where the script
is to be activated.
2. Select the LEARN menu.
Hold shift, tap Alt
The console will display the LEARN Menu.
3. Select Start Script(cr)
4. The console will respond with Press The Key You
Want To Redefine.
DO NOT select any key previously used by console
function. Use a combination of Shift, Alt, Ctrl,
and a Function key or letter.
Example:
CTRL, f12
5. The console will display the key selected and ask
for a script name. Type a script name that means
something to you, preferably the same as the
script.
A-28
6. Type the script
Example: I>scanner01->
Warning: DO NOT type a (cr). This will become part of
the script. You can put the console into an endless
loop, if you do!
A-29
Hold shift, tap Alt
8. Select Finish Script(cr)
9. Try the script, by pressing the new hot key, to see
if it works.
Hold shift, tap Alt
11. Select Save Script(cr)
NOTE: The S(ave) option is only present when an
unsaved script exists in the system.
Display Scripts
Hold shift, tap Alt
2. Select Display Script(cr)
The console with display a list of scripts already
in the system.
3. Press Shift, PrtSc to print a copy of the scripts.
A-30
Troubleshooting
Things to try when you get an off-line debug message,
at the console!
OFF-LINE DEBUG>> Type e to print the
fault condition mes-
sage.
Type x to print the ex-
ception message log.
Type i 0 to initialize
the processor ID for a
newly installed sys
board.
Type d 1 100 to display
the first 100 memory lo-
cations.
Someone destroyed the contents of bram! Doing a reset
in the middle of a gonzo transfer or removing the basis
weight detector head with power on will do this!
You need to get to the avos prompt $$ and bram will not
load!
1. Put the toggle switch (located above the reset but-
ton on the MPRC) down (off-line debug position)
2. Press the reset push button.
A-31
3. At off-line debug, type one of the following:
off-line bebug>>g(cr) The ASPC will try
to do a reset and
reload.
off-line debug>>g 1(cr) The ASPC will load
and execute avos,
to get you a $$, so
you can load bram.
If everything looks ok, frame power is up, but the head
package will not jog and you suspect the motor control-
ler is bad, try this!
Check that the bram board did not fall off, or vibrate
out of place during shipment. Be sure it is correctly
mounted in the bottom connector of the MPRC card. The
upper connector is the hot spare connection, which is
not normally used by the system.
If frame power will not stay on, You may have a SAFETY
circuit problem!
Check:
power supply voltages
card temperatures
motor controller temperature
broken alarm grid
A-32
Turn power off.
Remove the yellow trip wire from the 240 circuit break-
er
Turn power on, try to find out what is causing the safe-
ty circuit problem!
Check the Health Pages for Safety interupt set. Look
at the Electronics health report pages.
Scannthe Smart Platform in Workstation Mode.
The frame command line of the health page performs this
function.
If the smart Platform will not scan, check fokReason
to determine why the frame is not ok.
$$inspect(cr)
I>pmmFrame01->fokReason(cr)
The system will respond with an address.
Example:
pmmFrame010x357ac2
Enter the 0x address to display the error message.
Example:
I>0x357ac2(cr)
The system will print the object at the indicated ad-
dress, which will have an error message like, "sheet
break".
Remember the objectName, not the address, because the
A-33
address will change because of what is going on in the
system at the time. Entering the objectName pmmFrame01
will cause the system to print the pointer to the cur-
rent error message.
A-34
inspect Messages
I>()[scanner01 print](cr)
Prints out the sensor configuration for the indi-
cated scanner, showing real sensors, dependant
sensors, and sensors which are asleep.
I>()[pmmInterface print](cr)
Prints out the pmmObject configuration for the in-
terface, showing real sensors, dependant sensors,
and sensors which are asleep.
I>()[pmmFrame01 stdzErrors](cr)
Prints out the last standardize condition for each
sensor on the scanner. For sensors which have
failed standardize, it gives all the failed pa-
rameters. For individual sensor, use the pmm
name, such as pmmBeta01
Useful Messages:
Override Inherent sheet break or 20 minutes
I>()[betaSensor01 overrideInherentSheet-
Break](cr)
I>()[ashSensor01 overrideInherentSheetBreak](cr)
Put a sensor to sleep
I>()[betaSensor01 sleep](cr)
Wake up a sensor
I>()[betaSensor01 wakeUp](cr)
Cancel a bad position request
A-35
I>()[scanner01 cancel:0x____________________(cr)
Fill in the 0x address from the scanner request list
in ft, displays values, menu item 4.
Exercising the Basis Weight Shutter
I>()[betaSensor01 private$openShutter](cr)
I>()[betaSensor01 private$closeShutter](cr)
Exercising the Basis Weight Electrometer Clamp
I>()[betaSensor01 private$clampElectrometer](cr)
I>()[betaSensor01 private$unclampElectrome-
ter](cr)
Exercising IR gain via software
Use the IR health report , Page 2 ro exercise the
Gain
function.
Exercising the Reflection IR Flag
I>()[IRSensor01 private$insertReflector](cr)
I>()[IRSensor01 private$removeReflector](cr)
A-36
Exercising the Ash Shutter
I>()[ashSensor01 private$openShutter](cr)
I>()[ashSensor01 private$closeShutter](cr)
Exercising the Ash Electrometer Clamp
I>()[ashSensor01 private$clampElectrometer](cr)
I>()[ashSensor01 private$unclampElectrometer](cr)
Exercising the caliper head/pressure/vacuum
I>()[caliperSensor01 private$setupCaliperHardware:n
pressure:n Vacuum:n](cr)
CaliperHardware Pressure
vacuum
Where "n" is:0 open head on on
1 close head off off
Exercising the optipak clamp/vacuum
I>()[optipakSensor01 private$setupOptipakHardware:n
Vacuum:n](cr)
OptipakHardware vacuum
Where "n" is: 0 unclamp on
1 clamp off
A-37
Tools
$$ft(cr) Frame Tuning tool
$$genrpt(cr) Display/ modify Sensor
standardize limits and/
or Calibration con-
stants
Used to calculate new head constants for OPTIPAK and/
or GLOSS Sensors.
$$aim(cr) Analog Input Monitor
Utility
$$dim(cr) Display/ modify Digital I/O
status
$$monitor(cr) Real Time Monitor
$$pe -a(cr) Print error ALL error messages.
$$smr(cr) Signal Monitor Report
A-38
Basis Weight Troubleshooting
Purpose: Verify proper operation of the Basis Weight
sensor, [On Sheet at the frame, not scanning].
1. At the $$ prompt, select the inspector.
$$inspect(cr)
2. When the object inspector responds with I>, select
the AVOS sub- shell.
I>:!(cr)
3. Select the dim tool.
$!dim(cr)
4. Check the status of the frame micro controller by
selecting the board and output port.
Verify that the correct bits are set for the LED
outputs indicated in the Measurement Platform
Junction box and the shutter is closed. Exit the
tool by typing:
q(cr)
5. Select the analog input tool aim.
$!aim(cr)
6. Check the electrometer voltage. AIZ value should
be displayed. AIZ value = ____________
Exit the tool by typing:
q(cr)
7. Exit the sub-shell by typing:
$!exit(cr)
A-39
8. Open the Basis Weight shutter
I>()[betaSensor01 private$openShutter](cr)
A-40
the AVOS sub-shell.
I>:!(cr)
10. Select the fio tool.
$!dim(cr)
11. Check the status of the controller board by se-
lecting menu item 1.
Verify that the correct bits are set, and the LED
outputs in the Junction Box indicate the shutter
is open.
NOTE: The SmartPlatform automatically unclamps
the electrometer.
q(cr)
$!aim(cr)
13. Check the electrometer voltage. AIS value should
be displayed. AIS value = __________
q(cr)
$!exit(cr)
15. Clamp the electrometer.
I>()[betaSensor01 private$clampElectrometer](cr)
A-41
the AVOS sub-shell.
I>:!(cr)
17. Select the fio tool.
$!dim(cr)
18. Check the status of the fdi board by selecting
menu item 1
Verify that the correct bits are set and the LED
outputs in the Junction Box indicate that the Clamp
bit is set.
q(cr)
$!aim(cr)
20. Check the electrometer voltage. AIZ value should
be displayed. AIZ value = __________
q(cr)
$!exit(cr)
22. Return the system to normal Conditions
I>()[betaSensor01 private$unclampElectrome-
ter](cr)
I>()[betaSensor01 private$closeShutter](cr)
A-42
Basis Weight Standardize
1. Perform a clean standardize at the operator sta-
tion.
or
At the $$ prompt, select the inspector.
$$inspect(cr)
I>()[betaSensor01 stdzFor:0 mode:0](cr)
Note:
mode:0 = dirty standardize
mode:1 = clean standardize
2. When the standardize completes
I>()[pmmBeta01 stdzErrors]
3. Check the standardize results
I>betaSensor01->stdzResultsPending(cr)
I>0x_____________________________(cr)
NOTE: Type the address listed by
the system.
4. Exit to sub-shell
I>:!(cr)
5. Use the health report to display the standardize
results for betaSensor01.
F7
6. Compare the Standardize results on the health re-
port.
A-43
A-44

Quick Reference Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Quick Reference Manual

Uploaded by

Copyright:

Available Formats

A SP Quick Reference Manual

Smart Platform Quick Reference Manual

$! Secondary line prompt, AVOS shell

I> Object inspector prompt

If the system prints "abnormal termination of utility"

shift, Ctrl, ~ (Euro keyboards)

Copyright © 2002, ABB University

To return to the AVOS prompt $$.

shell. Typing '(cr) at the $$ prompt will cause this.

Type '(cr) to return to $$ prompt. This usually hap-

pens when someone hits the 'key, located next to the

return key by mistake.

Copyright © 2002, ABB University

General Commands - SP Utility User Guide, Section 9

$$cat /pathname/filename(cr)-Concatenate and print

example: $$cat /ss01/clm/startup(cr)

$$more /pathname/filename(cr)-Display paged file

example: $$more /ss01/clm/startup1(cr)

$$rm /pathname/filename(cr)-Remove file

example: $$rm /ss01/clm/frame.0105

$$cp /pathname/filename /pathname/filename(cr)-Copy

example: $$cp /ss01/clm/io.0105 /ss01/clm/io.ini(cr)

$$mv /pathname/filename /pathname/filename(cr)-Move

example: $$mv /ss01/clm/frame.0105 /ss01/clm/

$$df /bram1(cr)-List free space on /ss01

$$df /bram2(cr)-List free space on /appl

Debugging Commands - SP Utility User Guide, Section 10

$$derr(cr) Display Error History

$$dfree(cr) Display Memory Free Space

$$dobj(cr) Display Object List

$$dproc(cr) Display Processor

$$droot(cr) Display Root Directory

$$fsck /bram1 File System Consistency Check and inter-

Copyright © 2002, ABB University

$$fsck /bram2 File System Consistency Check and inter-

$$date(cr) Display current date and time

To enter Current Date and Time

$$date 01-04-2000 09:45(cr)

Copyright © 2002, ABB University

Smart Platform Bram Operations

umount (unmount) only worKs with the 086349-XX MPRC

Bram exhibits some of the characteristics of diskettes.

They can be unmounted in the same fashion as diskettes.

To unmount /ss01, move the working directory to root

To unmount /bram2, move the working directory to root

$$mount /bram1 /ss01(cr)

$$mount -r /bram2 /appl(cr)

Note: the system automatically mounts /bram2 read

only, during startup. This is the equivalent of

setting write protect.

A droot command can be used to check what is currently

mounted in the system.

Copyright © 2002, ABB University

List bram Files

LIST FILES - SP Utility Manual Section 3.0

This procedure can be used as a quick check, to see if

List files, short form (title only).

List in spread fashion

Example: List contents of /ss01/clm

This is the most commonly used form to check the re-

sults of a gstore operation.

Print Working Directory Name

Use this if you're not sure what directory you have