Copyright: ©1995 National Instruments Inc.
Citation: ©1995 National Instruments Inc.


Contents
VXIbus Interactive Control Program (VIC)
Help Contents

Introduction

How to Use Interface Tabs	Text Command Groups

Text Control Tab	Commander Word Serial

Word Serial Tab	Servant Word Serial

Bus Access Tab	High Level Bus Access

Interrupt/Signal Tab	Local Resorces Access

Trigger Tab	VXI Signal

Log Tab	VXI Interrupts

VXI Triggers

VXIbus Monitor	System Interrupts

System Configuration

Bus Extender

Auxiliary


VXIbus Interactive Control Program
VXIbus Interactive Control Program (VIC)

This section introduces you to VIC, the VXIbus Interactive Control program, which you can use to communicate directly with VXI devices either through commands you enter at the keyboard or through the interactive controls provided in VIC. This feature helps you learn how to communicate with devices, troubleshoot problems, and develop your application.

VIC is operated in the same manner as LabWindows/CVI. You can use it with or without a mouse. When you use VIC without a mouse, use the Tab and Shift-Tab> keys to jump from one field to the next, and the cursor keys to scroll the cursor within the window fields. Press Return (or Enter) to enter the selection. Press Delete or Backspace to delete text within a field.

Note:	Right-click on any element in the interface for a pop-up help description of the element.

VIC offers several choices to help you use your VXI devices. For general information on how to use these tabs refer to How to Use the User Interface Tabs section.

Text Control Tab

The Text Control tab is a line-oriented, interactive control panel. Its command set includes commands that correspond to NI-VXI function calls, in addition to auxiliary commands that are unique to VIC. To interact with devices, enter commands by typing them on the computer keyboard. After each function executes, VIC displays the device's response in the history window and a graphical representation of the command status.

The Text Control tab is designed to help you learn how to use the NI-VXI functions to program devices. Once you develop a sequence of steps that works successfully for your system, you can easily incorporate the sequence into an application program using the appropriate language and syntax.

Word Serial Tab

The Word Serial tab is a graphical, user interface panel that executes the Word Serial Protocol functions. These functions include command and query sending as well as buffer sending and receiving using the Word Serial Protocol.

Bus Access Tab

The Bus Access tab is a graphical, user interface panel that executes the high-level VXIbus access functions. These functions include reading from and writing to the VXI address space.

Interrupt Tab

The Interrupt tab is a graphical, user interface panel that allows you to manually assert, deassert, and acknowledge interrupts.

Signal Tab

The Signal tab is a graphical, user interface panel that allows you to enable and disable signal interrupts; enqueue, dequeue, and jam signals in the signal queue; and wait for signals.

Trigger Tab

The Trigger tab is a graphical, user interface panel that allows you to assert and deassert TTL and ECL triggers using VXI-defined trigger protocols.

VXIbus Monitor

The VXIbus status (BERR, SYSFAIL, ACFAIL, VXI interrupts, TTL/ECL triggers) is monitored and displayed graphically in all of the interface tabs.


How to Use the User Interface Tabs

These instructions apply to the Word Serial Tab, Bus Access Tab, Interrupt Tab, Signal Tab and Trigger Tab.

Note:	Right-click on any element of the panels to see a pop-up help description of the element.

•	Select a function from the Operation menu.

•	Enter your Input Parameters. The parameter options will change depending on which function you have chosen.

•	Certain parameters have a button to the right of the parameter field; click  on the button to fill in more details for the parameter. The information you enter here is linked to the parameter field, and the values will automatically update to match new information. For example, if you add information by clicking on the button, the value already entered in the parameter field may change to accommodate the new information.

•	Fill in a value in the Repeat Count box, indicating how many times to execute the run.

•	Click on the green Go! button. At any time during the run, you can stop the operation by clicking the red Stop button, or pressing the Escape key.

The Status LEDs on the right-hand side of the panel will light green for Okay and red for Error; right-click on each LED to see a pop-up help description of the button.

After command execution completes, VIC will automatically fill in the Output Parameters with the results of the command. Again, these parameters will change depending on which function you have chosen.

Corresponding Function Section

This section of the panel shows the command syntax for the currently selected command. Right click to select 'C Function' or 'VIC Command.' You can cut and paste this text into the Command box of the Text Control tab, or just record the information for future use.

Status Bar

This is the horizontal bar at the very bottom of the panel. The first box indicates the status of the test, for example, it might say "Running". The second box indicates the currently-selected device, or the active device. The third box indicates the logging mode.

VXIbus Monitor

The VXIbus status (BERR, SYSFAIL, ACFAIL, VXI interrupts, TTL/ECL triggers) is monitored and displayed graphically in all of the interface tabs.


VXIbus Monitor

This section is a visual monitor of the VXIbus.

•	To detach this monitor from the panel, right-click anywhere in the area and choose Detach.

•	Once detached, by default, the VXIbus Monitor window will stay on top of other windows on your screen. To move it to the back, right-click anywhere in the area and deselect Always on Top.

•	To reattach the monitor to the Main Window, either right-click anywhere in the area and choose Reattach, or simply close the window, and it will automatically be reattached where it belongs.

•	To turn off the monitor, right-click anywhere in the area and choose Disable.


Text Control Tab
How to Use the Text Control Tab

This tab is for experienced users who know the syntax of the commands they wish to enter.

Note:	Right-click on any element of the panel to see a pop-up help description of the element.

•	Type the command in the Command box and press Enter.

You can enter a partial name for a command. Make sure you specify enough characters to uniquely identify the command. for example, it's enough to enter vxiinr to engage the vxiinreg common. You can also use the automatic command completion feature of VIC to simplify entering commands. Simply type in a few characters and press Tab. VIC will automatically complete the command name. If more than one command matches, you can use Tab and Shift-Tab to cycle through possible command completions.

The History section, below the Command box, keeps a log of recently entered commands and command output for your information, and so you can cut and paste them into the command box as needed.

Use the user interface tabs to help you choose the commands you want without having to know the exact syntax of the command. Command syntaxes in the Text Control tab are slightly different from NI-VXI function calls. For detailed information on specific commands see the VIC Command Groups section.

Help

The help command gives online information about VIC commands with a quick reference for checking syntax and function of the VXI call. Type help followed by a command name to get more information about the particular command.

For an explanation of the status codes, refer to the corresponding function description in the NI-VXI Software Reference Manual for C.


Word Serial Tab

Through this graphical, user interface tab you can interactively execute the Word Serial Protocol functions. The following paragraphs describe the options in the Word Serial tab.

Note:	Right-click on any element of the panel to see a pop-up help description of the element.

For detailed instructions on how to use the interface tabs see the How to Use the User Interface Tabs section.

For an explanation of the status codes, refer to the corresponding function description in the NI-VXI Software Reference Manual for C.

Write

Purpose:	Transfers the specified string to a message-based Servant using the VXIbus Byte Transfer Protocol.

Select the logical address, mode, the string to write, and the repeat number (number of times to execute the function), and then select Go! to execute the command.

See the wswrt function description for more detailed information.

Read

Purpose:	Transfers data from a message-based device to the console using the VXIbus Byte Transfer Protocol.

Select the logical address, mode, count, and the repeat number (number of times to execute the function), and then select Go! to execute the command.

See the wssrd function description for more detailed information.

Cmd

Purpose:	Sends a Word Serial command to a message-based Servant device.

Select the logical address, command, and the repeat number (number of times to execute the function), and then select Go! to execute the command.

See the wscmd function description for more detailed information.

Query

Purpose:	Sends a Word Serial command to a message-based Servant device and gets the response from a message-based Servant.

Select the logical address, command, and the repeat number (number of times to execute the function), and then select Go! to execute the command.

See the wscmd? function description for more detailed information.

Resp

Purpose:	Gets the response for the previously sent Word Serial query.

Select the logical address and the repeat number (number of times to execute the function), and then select Go! to execute the command.

See the wsresp function description for more detailed information.

Trg

Purpose:	Sends the Word Serial Trigger command to a Servant device.

Select the logical address and the repeat number (number of times to execute the function), and then select Go! to execute the command.

See the wstrg function description for more detailed information.

Clr

Purpose:	Sends the Word Serial Clear command to a Servant device.

Select the logical address and the repeat number (number of times to execute the function), and then select Go! to execute the command.

See the wsclr function description for more detailed information.

SetTmo

Purpose:	Sets the timeout period for all the Word Serial functions.

Select the timeout period and the repeat number (number of times to execute the function), and then select Go! to execute the command.

See the wssettmo function description for more detailed information.

GetTmo

Purpose:	Gets the timeout period set for the Word Serial functions.

Select Go! to execute the command.

See the wsgettmo function description for more detailed information.


Bus Access Tab

Through this graphical, user interface tab you can interactively execute the High-Level VXIbus Access functions. The following paragraphs describe the options in the Bus Access tab.

Note:	Right-click on any element of the panel to see a pop-up help description of the element.

For detailed instructions on how to use the interface tabs see the How to Use the User Interface Tabs section.

For an explanation of the status codes, refer to the corresponding function description in the NI-VXI Software Reference Manual for C.

InReg

Purpose:	Reads a single word from the device specified by the logical address at the specified offset. Click the Panel Button next to Output Value to see the interpretation. (This will always interpret according to the last register read, not register control.)

Select the logical address, register offset, and repeat number (number of times to execute the function), and then select Go! to execute the command.

See the vxiinreg function description for more detailed information.

OutReg

Purpose:	Writes a single word to the device specified by the logical address at the specified offset. To compose the value click the Panel Button.

Select the logical address, register offset, value, and repeat number (number of times to execute the function), and then select Go! to execute the command.

See the vxioutreg function description for more detailed information.

In

Purpose:	Reads a single byte, word, or longword from the specified address in the specified address space with the specified access parameters.

Select the access parameters, width, address, and repeat number (number of times to execute the function), and then select Go! to execute the command.

See the vxiin function description for more detailed information.

Out

Purpose:	Writes a single byte, word, or longword to the specified address in the specified address space with the specified access parameters.

Select the access parameters, width, address, repeat number (number of times to execute the function), and the value, and then select Go! to execute the command.

See the vxiout function description for more detailed information.

Move

Purpose:	Moves a block of bytes, words, or longwords from a source location in any address space to a destination in any other address space.

Select the source space, source address, destination space, destination address, count, width, and repeat number (number of times to execute the function), and then select Go! to execute the command.

See the vximove function description for more detailed information.


Interrupt Tab

Through this graphical, user interface tab you can execute the VXI Interrupt functions. The following paragraphs describe the options in the Interrupt tab.

Note:	Right-click on any element of the panel to see a pop-up help description of the element.

For detailed instructions on how to use the interface tabs see the How to Use the User Interface Tabs section.

For an explanation of the status codes, refer to the corresponding function description in the NI-VXI Software Reference Manual for C.

Ack

Purpose:	Acknowledges the VXI interrupt.

Select the controller, the VXI interrupt, and repeat number, and then select Go! to execute the command.

See the acknowledgevxiint function description for more detailed information.

Assert

Purpose:	Asserts the VXI interrupt.

Select the controller, the status/ID, the VXI interrupt, and repeat number (number of times to execute the function), and then select Go! to execute the command.

See the assertvxiint function description for more detailed information.

Deassert

Purpose:	Deasserts the VXI interrupt.

Select the controller, the VXI interrupt, and repeat number (number of times to execute the function), and then select Go! to execute the command.

The following paragraphs describe the options in the Signal tab.

For an explanation of the status codes, refer to the corresponding function description in the NI-VXI Software Reference Manual for C.

See the deassertvxiint function description for more detailed information.


Signal Tab

Through this graphical, user interface tab you can interactively execute the Signal functions. The following paragraphs describe the options in the Signal tab.

Note:	Right-click on any element of the panel to see a pop-up help description of the element.

For detailed instructions on how to use the interface tabs see the How to Use the User Interface Tabs section.

For an explanation of the status codes, refer to the corresponding function description in the NI-VXI Software Reference Manual for C.

Enable

Purpose:	Sensitizes VIC to all received signals.

Select the repeat number (number of times to execute the function), and then select Go! to execute the command.

See the enablesignalint function description for more detailed information.

Disable

Purpose:	Desensitizes VIC to all received signals.

Select the repeat number (number of times to execute the function), and then select Go! to execute the command.

See the function disablesignalint description for more detailed information.

Deq

Purpose:	Dequeues a signal specified by the signalmask for the specified logical address from the signal queue.

Enter the logical address, the signalmask, and repeat number (number of times to execute the function), and then select Go! to execute the command.

See the signaldeq function description for more detailed information.

Enq

Purpose:	Puts the specified signal on the tail of the signal queue for the logical address.

Enter the signal and the repeat number (number of times to execute the function), and then select Go! to execute the command.

See the signalenq function description for more detailed information.

Jam

Purpose:	Puts the specified signal on the head of the signal queue for the logical address.

Enter the signal and the repeat number (number of times to execute the function), and then select Go! to execute the command.

See the signaljam function description for more detailed information.

Wait

Purpose:	Waits for a particular signal from a particular device.

Enter the logical address, the signalmask, and the repeat number (number of times to execute the function), and then select Go! to execute the command.

See the waitforsignal function description for more detailed information.


Trigger Tab

Through this graphical, user interface tab you can interactively execute the VXI trigger function SrcTrig.

Note:	Right-click on any element of the panel to see a pop-up help description of the element.

For detailed instructions on how to use the interface tabs see the How to Use the User Interface Tabs section.

For an explanation of the status codes, refer to the corresponding function description in the NI-VXI Software Reference Manual for C.

SrcTrig

Purpose:	Sources a trigger on an trigger line using the specified protocol.

Select the controller, the trigger line, the trigger protocol, the timeout period, and the repeat number, and then select Go! to execute the command.

See the srctrig function description for more detailed information.


How to Use the Log Tab

This is a configuration panel where you can save your current settings to whatever file you specify.

Note:	Right-click on any element of the panel to see a pop-up help description of the element.

•	In the Log Options section, click on the option you choose.

•	Enter the path for the Log File, or click browse to select the path interactively. Click on the Reset Log button to clear the contents of the file.

The following options are available for logging:

No Logging	Disables all logging.

Log Commands and Output	Logs all VIC interactions. Both VIC commands and command outputs are recorded. For graphical Tabs the corresponding VIC command is recorded.

Generate Script	Logs Commands only. This creates a VIC script that can be executed using the "$" command.

Generate C Functions	Records NI-VXI C functions corresponding to user actions. The generated log file can be inserted into a program.


VIC Command Groups

Notice that angle brackets ( < > ) enclose parameter names in the following descriptions (for example, <filename>). In addition, optional parameters have square brackets (for example, [,<count>]).

Commander Word Serial	Servant Word Serial

High Level Bus Access	Local Resources Access

VXI Signal	VXI Interrupts

VXI Triggers	System Interrupts

System Configuration	Bus Extender

Auxiliary


System Configuration Commands

VIC supports the following system configuration commands.

FindDevLA

GetDevInfo

SetDevInfo

CreateDevInfo

Return to Command Groups


finddevla

Purpose:	Returns the logical address of a device with the specified attributes.

Command

Syntax:	finddevla <namepat>[, <manid>[, <modelcode>[, <devclass>[, <slot>[, <mainframe>,[ <cmdrla>]]]]]]

where

namepat	Name pattern

manid	VXI manufacturer identification number

modelcode	Manufacturer's 12-bit model number

devclass	Device class of the device

0 = Memory Class Device

1 = Extended Class Device

2 = Message-Based Device

3 = Register-Based Device

slot	Slot location of the device

mainframe	Mainframe location of device (logical address of extender)

cmdrla	Commander's logical address

If namepat is "" or any other attribute is -1 or missing, that attribute is not used in the matching algorithm.

Example:	Find the logical address of a device with the device name "GPIB-VXI."

finddevla "GPIB-VXI"

Return to System Configuration Commands


getdevinfo

Purpose:	Returns specified information about a device in the NI-VXI RM table.

Command

Syntax:	getdevinfo [<la>, ]<field>

where

la	Logical address of device to get information about

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

field	Field identification number

Field	Description

0	Entire RM table entry for specified device

1	Device name

2	Commander's logical address

3	Mainframe

4	Slot

5	Manufacturer identification number

6	Manufacturer name

7	Model code

8	Model name

9	Device class

10	Extended subclass (if extended class device)

11	Address space used

12	Base of A24/A32 memory

13	Size of A24/A32 memory

14	Memory type and access time

15	Bit vector list of VXI interrupter lines

16	Bit vector list of VXI interrupt handler lines

17	Extender/controller information

Bits	Description

15-13	Reserved

12	1 = Child side extender
0 = Parent side extender

11	1 = Frame extender
0 = Not frame extender

10	1 = Remote controller

9	1 = Local controller

8	1 = External controller

7-0	Frame extender towards root frame

18	Asynchronous mode control state

19	Response enable state

20	Protocols supported

21	Capability/status flags

22	Status state (Passed/Failed, Ready/Not Ready)

Example:	Get the name of a device at Logical Address 4.

getdevinfo 4, 1

Return to System Configuration Commands


setdevinfo

Purpose:	Sets information about a device in the NI-VXI RM table.

Command

Syntax:	setdevinfo [<la>, ]<field>, <fieldvalue>

where

la	Logical address of device in RM table for which to set information

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

field	Field identification number

Field	Description

0	Entire RM table entry for specified device

1	Device name

2	Commander's logical address

3	Mainframe

4	Slot

5	Manufacturer identification number

6	Manufacturer name

7	Model code

8	Model name

9	Device class

10	Extended subclass (if extended class device)

11	Address space used

12	Base of A24/A32 memory

13	Size of A24/A32 memory

14	Memory type and access time

15	Bit vector list of VXI interrupter lines

16	Bit vector list of VXI interrupt handler lines

17	Extender/controller information

Bits	Description

15 - 13	Reserved

12	1 = Child side extender
0 = Parent side extender

11	1 = Frame extender
0 = Not frame extender

10	1 = Remote controller

9	1 = Local controller

8	1 = External controller

7 - 0	Frame extender towards root frame

18	Asynchronous mode control state

19	Response enable state

20	Protocols supported

21	Capability/status flags

22	Status state (Passed/Failed, Ready/Not Ready)

fieldvalue	Appropriate value to set for the specified field

Example:	Set the name of a device at Logical Address 4 to RELAY.

setdevinfo 4, 1, "RELAY"

Return to System Configuration Commands


createdevinfo

Purpose:	Creates a new entry in the RM table for the device at specified logical address.

Command

Syntax:	createdevinfo [<la>]

where

la	Logical address of device for which to create entry

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

Example:	Create a new entry for a device at Logical Address 4.

createdevinfo 4

Return to System Configuration Commands


Commander Word Serial Protocol Commands

VIC supports the following Commander Word Serial Protocol commands.

WSrd	WSrdf

WSwrt	WSwrtf

WScmd	WScmd?

WSresp	WStrg

WSclr	WSabort

WSLcmd	WSLresp

WSEcmd	WSSetTmo

WSgetTmo

Return to Command Groups


wsrd

Purpose:	Reads data from a message-based device and displays it on the console using the VXIbus Byte Transfer Protocol.

Command

Syntax:	wsrd [<la>, ]<count>, <mode>

where

la	Logical address of message-based Servant

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

count	Maximum number of bytes to transfer

mode	Mode of transfer (bit vector)

Bit	Description

0	Not DOR

0 = Abort if not DOR

1 = Poll till DOR

1	END bit termination suppression

0 = Terminate transfer on END bit

1 = Do not terminate transfer on END

2	LF character termination

1 = Terminate transfer on LF bit

0 = Do not terminate transfer on LF

3	CR character termination

1 = Terminate transfer on CR bit

0 = Do not terminate transfer on CR

4	EOS character termination

1 = Terminate transfer on EOS bit

0 = Do not terminate transfer on EOS

8-15	EOS character (if enabled)

Example:	Read and display 10 bytes from the device at Logical Address 5 (mode = poll until DIR; terminate transfer on END bit).

wsrd 5, 10, 1

Return to Commander Word Serial Protocol Commands


wsrdf

Purpose:	Transfers data from a message-based device to a file, using the VXIbus Byte Transfer Protocol.

Command

Syntax:	wsrdf [<la>, ]<filename>, <count>, <mode>

where

la	Logical address of message-based Servant

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

filename	File name to which to transfer data

count	Maximum number of bytes to transfer

mode	Mode of transfer (bit vector) (same as in wsrd)

Example:	Read 10 bytes from a device at Logical Address 5 (mode = poll till DIR, terminate transfer on END bit), and write them to the file "temp.dat."

wsrdf 5, "temp.dat", 10, 1

Return to Commander Word Serial Protocol Commands


wswrt

Purpose:	Transfers the specified string to a message-based Servant using the VXIbus Byte Transfer Protocol.

Command

Syntax:	wswrt [<la>, ]<string>[, <mode>]

where

la	Logical address of message-based Servant

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

string	Buffer to send

mode	Mode of transfer (bit vector)

Bit	Description

0	Not DIR

0 = Abort if not DIR

1 = Poll till DIR

1	END bit termination

0 = Clear END bit on the last byte

1 = Set END bit on the last byte

Example:	Send the string "laddrs?" to a device at Logical Address 5.

wswrt 5, "laddrs?"

Return to Commander Word Serial Protocol Commands


wswrtf

Purpose:	Transfers data from the specified file to a message-based Servant using the VXIbus Byte Transfer Protocol.

Command

Syntax:	wswrtf [<la>, ]<filename>[, <count>]

where

la	Logical address of message-based Servant

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

filename	Name of file from which to transfer data

count	Maximum number of bytes to transfer

Example:	Send the data in the file "temp.dat" to a device at Logical Address 5.

wswrtf 5, "temp.dat"

Return to Commander Word Serial Protocol Commands


wscmd

Purpose:	Sends a Word Serial command to a message-based Servant device.

Command

Syntax:	wscmd [<la>, ]<command>

where

la	Logical address of message-based Servant

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

command	Word Serial command

Example:	Send an Identify Commander command to a device at Logical Address 5.

wscmd 5, 0xbe00

Return to Commander Word Serial Protocol Commands


wscmd?

Purpose:	Sends a Word Serial query to a message-based Servant device and gets the response.

Command

Syntax:	wscmd? [<la>, ]<command>

where

la	Logical address of message-based Servant

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

command	Word Serial query

Example:	Send a Read STB command to a device at Logical Address 5 and get the response.

wscmd? 5, 0xcfff

Return to Commander Word Serial Protocol Commands


wsresp

Purpose:	Gets the response to the previously sent Word Serial query (when sent as a command using wscmd rather than as a query using wscmd?). This function is intended for debug use only.

Command

Syntax:	wsresp [<la>]

where

la	Logical address of message-based Servant

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

Example:	Get the response.

wsresp 5

Return to Commander Word Serial Protocol Commands


wstrg

Purpose:	Sends the Word Serial Trigger command to a message-based Servant device.

Command

Syntax:	wstrg [<la>]

where

la	Logical address of message-based Servant

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

Example:	Send the Word Serial Trigger command to a device at Logical Address 5.

wstrg 5

Return to Commander Word Serial Protocol Commands


wsclr

Purpose:	Sends the Word Serial Clear command to a message-based Servant device.

Command

Syntax:	wsclr [<la>]

where

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

la	Logical address of message-based Servant

Example:	Send a Clear command to a device at Logical Address 5.

wsclr 5

Return to Commander Word Serial Protocol Commands


wsabort

Purpose:	Aborts the Commander Word Serial operation(s) currently in progress.

Command

Syntax:	wsabort [<la>, ]<abortop>

where

la	Logical address of message-based Servant

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

abortop	Option for aborting Word Serial operation

1 = ForcedAbort: aborts wswrt, wsrd, and wstrg

2 = UnRecCom: aborts wscmd, wslcmd, and wsecmd

3 = ForcedAbort: aborts wscmd, wslcmd, and wsecmd

4 = ForcedAbort: aborts all Word Serial operations

5 = Async ForcedAbort: aborts all Word Serial operations immediately.

Note:	Be cautious when using <abortop> option 5. During a Word Serial query, the Servant may be left in an invalid state if the operation is aborted after writing the query and before reading the response register. When using this option, the Word Serial operation is aborted immediately as compared to using options 1, 3, and 4, where the operation is not aborted until the response is read in that situation.

Example:	Abort wswrt operation to Logical Address 5.

wsabort 5, 1

Return to Commander Word Serial Protocol Commands


wslcmd

Purpose:	Sends a Longword Serial command to a message-based Servant device and gets the response.

Command

Syntax:	wslcmd [<la>, ]<command>, <respflag>

where

la	Logical address of message-based Servant

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

command	Longword Serial command

respflag	Response flag

0 = Do not get the response

1 = Get the response

Example:	Send a user-defined Longword command 0xfffffffe to a device at Logical Address 5 and get the response.

wslcmd 5, 0xfffffffe, 1

Return to Commander Word Serial Protocol Commands


wslresp

Purpose:	Gets the response for the previously sent Longword query.

Command

Syntax:	wslresp [<la>]

where

la	Logical address of message-based Servant

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

Example:	Gets the response for the previously sent Longword query from Logical Address 5.

wslresp 5

Return to Commander Word Serial Protocol Commands


wsecmd

Purpose:	Sends an Extended Longword Serial command to a message-based Servant device and gets the response.

Command

Syntax:	wsecmd [<la>, ]<cmdext>, <command>, <respflag>

where

la	Logical address of message-based Servant

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

cmdext	Upper 16 bits of 48-bit Extended Longword Serial command

command	Lower 32 bits of 48-bit Extended Longword Serial command

respflag	Response flag

0 = Do not get the response

1 = Get the response

Example:	Send a user-defined Extended Longword command 0xfffdfffffffe to a device at Logical Address 5 and get the response.

wsecmd 5, 0xfffd, 0xfffffffe, 1

Return to Commander Word Serial Protocol Commands


wssettmo

Purpose:	Sets the timeout period for all Word Serial commands.

Command

Syntax:	wssettmo <timeout>

where

timeout	Timeout period (in milliseconds)

Example:	Set the timeout value to 3 seconds (3,000 msec).

wssettmo 3000

Return to Commander Word Serial Protocol Commands


wsgettmo

Purpose:	Gets the timeout period set for all Word Serial commands.

Command

Syntax:	wsgettmo

Example:	Get the timeout value.

wsgettmo

Return to Commander Word Serial Protocol Commands


Servant Word Serial Protocol Commands

VIC supports the following Servant Word Serial Protocol commands.

WSSenable

WSSdisable

WSSrd

WSSwrt

WSSabort

Return to Command Groups


wssenable

Purpose:	Enables all Servant Word Serial Protocol commands.

Command

Syntax:	wssenable

Example:	Enable all Servant Word Serial Protocol commands.

wssenable

Return to Servant Word Serial Protocol Commands


wssdisable

Purpose:	Inhibits all Servant Word Serial Protocol commands from being received.

Command

Syntax:	wssdisable

Example:	Inhibit all Servant Word Serial Protocol commands from being received.

wssdisable

Return to Servant Word Serial Protocol Commands


wssrd

Purpose:	Receives the specified number of bytes from a message-based Commander using the VXIbus Byte Transfer Protocol.

Command

Syntax:	wssrd <count>, <mode>

where

count	Maximum number of bytes to receive

mode	Mode of transfer (bit vector)

(Bit 0)

0 = Do not send DIR signal to Commander

1 = Send DIR signal to Commander

Example:	Receive 10 bytes from the Commander device.

wssrd 10, 0

Return to Servant Word Serial Protocol Commands


wsswrt

Purpose:	Transfers the specified string to a message-based Commander using the VXIbus Byte Transfer Protocol.

Command

Syntax:	wsswrt <string>, <mode>

where

string	Buffer to send

mode	Mode of transfer (bit vector)

(Bit 0)

0 = Do not send DOR signal to Commander

1 = Send DOR signal to Commander

(Bit 1)

0 = Do not send END with the last byte

1 = Send END with the last byte

Example:	Send the string "mydata 1.2.3" to the Commander device.

wsswrt "mydata 1.2.3", 2

Return to Servant Word Serial Protocol Commands


wssabort

Purpose:	Aborts the Servant Word Serial operation currently in progress.

Command

Syntax:	wssabort <abortop>

where

abortop	Option for aborting Word Serial operation (bit vector)

Bit	Option

1	Aborts wsswrt

2	Aborts wssrd

3	Aborts wsssendresp

15	Initialize Word Serial Servant hardware. This includes aborting all Word Serial Servant operations, clearing all errors, removing all pending Word Serial Servant interrupts, and disabling the interrupts.

Example:	Abort wsswrt operation to Logical Address 5.

wssabort 5, 1

Return to Servant Word Serial Protocol Commands


High-Level VXIbus Access Commands

VIC supports the following high-level VXIbus access commands.

VXIin

VXIout

VXIinReg

VXIoutReg

VXImove

Return to Command Groups


vxiin

Purpose:	Reads a single byte, word, or longword from the specified address in the specified address space with the specified access parameters.

Command

Syntax:	vxiin <accessparms>, <address>, <width>

where

accessparms	(Bits 0 to 1) VXI address space

1 = A16

2 = A24

3 = A32

(Bits 2 to 4) Access privilege

0 = Nonprivileged data access

1 = Supervisory data access

2 = Nonprivileged program access

3 = Supervisory program access

4 = Nonprivileged block access

5 = Supervisory block access

(Bits 5 to 6)

0 = Reserved

(Bit 7) Byte order

0 = Motorola

1 = Intel

(Bits 8 to 15)

0 = Reserved

address	VXI address

width	Data width

1 = Byte

2 = Word

4 = Longword

Example:	Read the ID register (2 bytes) of a device at Logical Address 4 (address = 0xc100).

vxiin 1, 0xc100, 2

Return to High-Level VXIbus Access Commands


vxiout

Purpose:	Writes a single byte, word, or longword to the specified address in the specified address space with the specified access parameters.

Command

Syntax:	vxiout <accessparms>, <address>, <width>, <value>

where

accessparms	(Bits 0 to 1) VXI address space

1 = A16

2 = A24

3 = A32

(Bits 2 to 4) Access privilege

0 = Nonprivileged data access

1 = Supervisory data access

2 = Nonprivileged program access

3 = Supervisory program access

4 = Nonprivileged block access

5 = Supervisory block access

(Bits 5 to 6)

0 = Reserved

(Bit 7) Byte order

0 = Motorola

1 = Intel

(Bits 8 to 15)

0 = Reserved

address	VXI address

width	Data transfer width

1 = Byte

2 = Word

4 = Longword

value	Value to write

Example:	Write a value of 0x1000 to the Offset register (2 bytes) of a device at Logical Address 4
(address = 0xc106).

vxiout 1, 0xc106, 2, 0x1000

Return to High-Level VXIbus Access Commands


vxiinreg

Purpose:	Reads a single word from the specified register offset on the specified logical address.

Command

Syntax:	vxiinreg [<la>, ]<reg>

where

la	Logical address

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

reg	Offset within VXI Logical Address registers

Example:	Read the ID register (reg = 0) of a device at Logical Address 4.

vxiinreg 4, 0

Return to High-Level VXIbus Access Commands


vxioutreg

Purpose:	Writes a single word to the specified register offset on the specified logical address.

Command

Syntax:	vxioutreg [<la>, ]<reg>, <value>

where

la	Logical address

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

reg	Offset within VXI Logical Address registers

value	Value to write

Example:	Write the Offset register (reg = 6) of a device at Logical Address 4 with 0x2000.

vxioutreg 4, 6, 0x2000

Return to High-Level VXIbus Access Commands


vximove

Purpose:	Moves a block of bytes, words, or longwords from a source location in any address space to a destination in any address space with the specified access parameters.

Command

Syntax:	vximove <srcparms>, <srcaddr>, <destparms>, <destaddr>, <length>, <width>

where

srcparms

and destparms	(Bits 0 to 1) Source and destination address space

1 = A16

2 = A24

3 = A32

Note:	You can't use 'Local address space' in VIC.

(Bits 2 to 4) Access privilege

0 = Nonprivileged data access

1 = Supervisory data access

2 = Nonprivileged program access

3 = Supervisory program access

4 = Nonprivileged block access

5 = Supervisory block access

(Bits 5 to 6)

0 = Reserved

(Bit 7) Byte order

0 = Motorola

1 = Intel

(Bits 8 to 15)

0 = Reserved

srcaddr

and destaddr	Address (offsets within source and destination address spaces)

length	Number of elements to transfer

width	Data transfer width

1 = Byte

2 = Word

4 = Longword

Example:	Move 100 bytes from A24 space at 0x200000 to A32 space at 0x20000000.

vximove 2, 0x200000, 3, 0x20000000, 100, 1

Return to High-Level VXIbus Access Commands


Local Resource Access Commands

VIC supports the following local resource access commands.

GetMyLa

VXIinLR

VXIoutLR

SetModid

ReadModid

Return to Command Groups


getmyla

Purpose:	Gets the logical address of the local VXI device.

Command

Syntax:	getmyla

Example:	Get the logical address of the local VXI device.

getmyla

Return to Local Resource Access Commands


vxiinlr

Purpose:	Reads a single byte, word, or longword from the specified register on the local VXI device.

Command

Syntax:	vxiinlr <reg>, <width>

where

reg	Offset within VXI Logical Address registers

width	Data transfer width

1 = Byte

2 = Word

4 = Longword

Example:	Read the register at offset 0 (2 bytes) on the local device.

vxiinlr 0, 2

Return to Local Resource Access Commands


vxioutlr

Purpose:	Writes a single byte, word, or longword from the specified register on the local VXI device.

Command

Syntax:	vxioutlr <reg>, <width>, <value>

where

reg	Offset within VXI Logical Address registers

width	Data transfer width

1 = Byte

2 = Word

4 = Longword

value	Value to write

Example:	Write the register at offset 0 (2 bytes) with 0x1000 on the local device.

vxioutlr 0, 2, 0x1000

Return to Local Resource Access Commands


setmodid

Purpose:	Controls the MODID lines of the VXIbus backplane.

Command

Syntax:	setmodid <enable>, <modid>

where

enable	1 = Set MODID enable bit

0 = Clear MODID enable bit

modid	Bit vector for Bits 0 to 12, corresponding to Slots 0 to 12

Example:	Set all the MODID lines.

setmodid 1, 0xffff

Return to Local Resource Access Commands


readmodid

Purpose:	Reads the MODID lines of the VXIbus backplane.

Command

Syntax:	readmodid

Example:	Read the MODID lines.

readmodid

Return to Local Resource Access Commands


VXI Signal Commands

VIC supports the following VXI signal commands.

RouteSignal

EnableSignalInt

DisableSignalInt

SignalDeq

SignalEnq

SignalJam

WaitForSignal

Return to Command Groups


routesignal

Purpose:	Selects whether each type of signal is enqueued on a software queue or handled by the signal handler.

Command

Syntax:	routesignal [<la>, ]<modemask>

where

la	Logical address to set handler for

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

modemask	A bit vector that specifies whether each type of signal is enqueued or handled by the signal handler. A zero in any bit position causes signals of the associated type to be queued. All other signals are handled by the signal handler.

If la is a message-based device:

Bit	Event Signal

14	User-Defined events

13	VXI Reserved events

12	Shared Memory events

11	Unrecognized Command events

10	Request False (REQF) events

9	Request True (REQT) events

8	No Cause Given events

Bit	Response Signal

7	Unused

6	B14

5	Data Out Ready (DOR)

4	Data In Ready (DIR)

3	Protocol error (ERR)

2	Read Ready (RR)

1	Write Ready (WR)

0	Fast Handshake (FHS)

If la is not a message-based device:

Bit	Type of Signal (status/Id) values

15 - 8	Active high bit (if 1 in bits 15 to 8, respectively)

7 - 0	Active low bit (if 0 in bits 15 to 8, respectively)

Example:	Put REQT, REQF and Unrecognized Command signals on the signal queue and handle the rest of the signals using the signal handler for Logical Address 5.

routesignal 5, 0xf1ff

Return to VXI Signal Commands


enablesignalint

Purpose:	Sensitizes VIC to receive all signals.

Command

Syntax:	enablesignalint

Return to VXI Signal Commands


disablesignalint

Purpose:	Desensitizes VIC to not receive signals.

Command

Syntax:	disablesignalint

Return to VXI Signal Commands


signaldeq

Purpose:	Gets a signal specified by the signalmask for the specified logical address from the signal queue.

Command

Syntax:	signaldeq [<la>, ]<signalmask>

where

la	Logical address of signal to dequeue for (-1 = any)

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

signalmask	Bit vector (same as in routesignal command)

(0xffff = any)

Example:	Dequeue the first signal on the signal queue.

signaldeq -1, 0xffff

Return to VXI Signal Commands


signalenq

Purpose:	Puts the specified signal on the tail of the signal queue for the logical address.

Command

Syntax:	signalenq <signal>

where

signal	Signal to enqueue at the end of the queue

Example:	Enqueue the signal 0x1111 on the end of signal queue.

signalenq 0x1111

Return to VXI Signal Commands


signaljam

Purpose:	Puts the signal on the head of the signal queue for the logical address.

Command

Syntax:	signaljam <signal>

where

signal	Signal to jam on the front of the queue

Example:	Enqueue the signal 0x1111 on the front of signal queue.

signaljam 0x1111

Return to VXI Signal Commands


waitforsignal

Purpose:	Waits for one of the specified signals to be received.

Command

Syntax:	waitforsignal [<la>, ]<signalmask>, <timeout>

where

la	Logical address of the device sourcing the signal (-1 = any la

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

signalmask	Bit vector (same as in routesignal command)

(0xffff = any signal

timeout	Time period to wait (in milliseconds)

Example:	Wait for two seconds for REQT signal from Logical Address 5.

waitforsignal 5, 0x0200, 2000

Return to VXI Signal Commands


VXI Interrupt Commands

VIC supports the following VXI interrupt commands.

RouteVXIint

EnableVXItoSignalInt	DisableVXItoSignalInt

EnableVXIint	DisableVXIint

VXIintAcknowledgeMode	AcknowledgeVXIint

AssertVXIint	DeassertVXIint

Return to Command Groups


routevxiint

Purpose:	Selects whether VXI interrupts are handled as VXI signals or routed to the VXI interrupt handler for the specified controller.

Command

Syntax:	routevxiint <controller>, <sroute>

where

controller	Controller for which to configure interrupt routing

-1 = Local controller or the immediate remote controller

sroute	Bit vector of VXI interrupt levels to route. Bits 6 to 0 correspond

to VXI interrupt levels 7 to 1, respectively.

1 = Handle as a VXI signal for appropriate level

0 = Handle as a VXI interrupt for appropriate level

Example:	Handle VXI interrupt 4 as a VXI signal and handle the rest as VXI interrupts for the controller at Logical Address 5.

routevxiint 5, 0x08

Return to VXI Interrupt Commands


enablevxitosignalint

Purpose:	Sensitizes VIC to the specified VXI interrupt levels being processed as VXI signals for the specified controller.

Command

Syntax:	enablevxitosignalint <controller>, <levels>

where

controller	Controller for which to enable VXI interrupt

-1 = Local controller or the immediate remote controller

levels	Bit vector of VXI interrupt levels to enable. Bits 6 to 0 correspond to VXI interrupt levels 7 to 1, respectively.

1 = Enable for appropriate level

0 = Leave at current setting

Example:	Enable VXI interrupt 4 on the controller at Logical Address 5 to be handled as a VXI signal.

enablevxitosignalint 5, 0x08

Return to VXI Interrupt Commands


disablevxitosignalint

Purpose:	Desensitizes VIC to the specified VXI interrupt levels being processed as VXI signals for the specified controller.

Command

Syntax:	disablevxitosignalint <controller>, <levels>

where

controller	Controller for which to disable VXI interrupt

-1 = Local controller or the immediate remote controller

levels	Bit vector of VXI interrupt levels to disable. Bits 6 to 0 correspond to VXI interrupt levels 7 to 1, respectively.

1 = Disable for appropriate level

0 = Leave at current setting

Example:	Disable VXI interrupt 4 on the controller at Logical Address 5 to be handled as a VXI signal.

disablevxitosignalint 5, 0x08

Return to VXI Interrupt Commands


enablevxiint

Purpose:	Sensitizes VIC to the specified VXI interrupt levels being processed as VXI/VME interrupts (not as VXI signals) for the specified controller.

Command

Syntax:	enablevxiint <controller>, <levels>

where

controller	Controller for which to enable VXI interrupt

-1 = Local controller or the immediate remote controller

levels	Bit vector of VXI interrupt levels to enable. Bits 6 to 0 correspond to VXI interrupt levels 7 to 1, respectively.

1 = Enable for appropriate level

0 = Leave at current setting

Example:	Enable VXI interrupt 4 on the controller at Logical Address 5 to be handled as a VXI/VME interrupt (not as a VXI signal).

enablevxiint 5, 0x08

Return to VXI Interrupt Commands


disablevxiint

Purpose:	Desensitizes VIC to the specified VXI interrupt levels being processed as VXI/VME interrupts (not as VXI signals) for the specified controller.

Command

Syntax:	disablevxiint <controller>, <levels>

where

controller	Controller for which to disable VXI interrupt

-1 = Local controller or the immediate remote controller

levels	Bit vector of VXI interrupt levels to disable. Bits 6 to 0 correspond to VXI interrupt levels 7 to 1, respectively.

1 = Disable for appropriate level

0 = Leave at current setting

Example:	Disable VXI interrupt 4 on the controller at Logical Address 5 to be handled as a VXI/VME interrupt (not as a VXI signal).

disablevxiint 5, 0x08

Return to VXI Interrupt Commands


vxiintacknowledgemode

Purpose:	Specifies whether the VXI interrupt acknowledge cycle for the specified controller for the specified levels should be handled as Release On Acknowledge (ROAK) or as Release On Register Access (RORA).

Command

Syntax:	vxiintacknowledgemode <controller>, <modes>

where

controller	Controller to configure

-1 = Local controller or the immediate remote controller

modes	Bit vector of VXI interrupt levels to set to ROAK or RORA

1 = Set to RORA VXI interrupt

0 = Set to ROAK VXI interrupt

Example:	Handle VXI interrupt 2 as RORA and the rest as ROAK for controller at Logical Address 5.

vxiintacknowledgemode 5, 0x02

Return to VXI Interrupt Commands


assertvxiint

Purpose:	Asserts an interrupt line in a particular controller.

Command

Syntax:	assertvxiint <controller>, <level>, <statusId>

where

controller	Controller for which to assert VXI interrupt

-1 = Local controller or the immediate remote controller

level	Interrupt level

statusId	Status/ID to present during IACK cycle

Example:	Assert interrupt 4 in Controller 1 with status/ID of 0x1234.

assertvxiint 1, 4, 0x1234

Return to VXI Interrupt Commands


deassertvxiint

Purpose:	Deasserts an interrupt line in a particular controller.

Command

Syntax:	deassertvxiint <controller>, <level>

where

controller	Controller for which to deassert VXI interrupt

-1 = Local controller or the immediate remote controller

level	Interrupt level

Example:	Deassert interrupt 4 in Controller 1.

deassertvxiint 1, 4

Return to VXI Interrupt Commands


acknowledgevxiint

Purpose:	Performs an IACK cycle on the VXIbus in the specified controller for the specified level.

Command

Syntax:	acknowledgevxiint <controller>, <level>

where

controller	Controller for which to acknowledge VXI interrupt

-1 = Local controller or the immediate remote controller

level	Interrupt level

Example:	Acknowledge interrupt 4 in Controller 1.

acknowledgevxiint 1, 4

Return to VXI Interrupt Commands


VXI Trigger Commands

The VIC utility supports the following VXI trigger commands.

SrcTrig	SrcTTLtrig

SrcECLtrig

EnableTrigSense	EnableTTLsense

DisableTrigSense	DisableTTLsense

WaitForTrig	WaitForTTLtrig

EnableECLsense	DisableECLsense

WaitForECLtrig	AcknowledgeTrig

MapTrigToTrig	UnmapTrigToTrig

TrigAssertConfig	TrigCntrConfig

TrigExtConfig	TrigTickConfig

Return to Command Groups


srctrig

Purpose:	Sources the specified protocol on the specified TTL, ECL, or external trigger line on the specified controller.

Command

Syntax:	srctrig <controller>, <line>, <protocol>, <timeout>

where

controller	Controller on which to source trigger line

-1 = Local controller or the immediate remote controller

line	Trigger line to source

Value	Trigger line

0 to 7	TTL trigger lines 0 to 7

8 to 13	ECL trigger lines 0 to 5

40 to 49	External source/destination (GPIO 0 to 9)

50	TIC counter

60	TIC TICK timers

protocol	Trigger Protocol

0 = ON

1 = OFF

2 = Start

3 = Stop

4 = Sync

5 = Semi-sync

6 = Async

7 = Semi-sync (and wait for acknowledge)

8 = Async (and wait for acknowledge)

0xFFFF = Abort previous acknowledge pending (5 and 6)

timeout	Timeout value in milliseconds

Example:	Source VXIbus TTL trigger line 4 on Controller 1 with Continuous ON protocol.

srctrig 1, 4, 0, 0

Return to VXI Trigger Commands


srcttltrig

Purpose:	Assert or de-assert a trigger on a TTL trigger line using a VXI protocol in a specified controller. This function is obsolete, use srctrig instead.

Command

Syntax:	srcttltrig <controller>, <line>, <protocol>, <timeout>

where

controller	Controller on which to source TTL trigger
-1 = Local controller or the first remote controller

line	0-7 corresponding to TTL lines 0-7

protocol	Trigger protocol

0 = ON

1 = OFF

2 = Start

3 = Stop

4 = Sync

5 = Semi-sync

6 = Async

7 = Semi-sync (and wait for acknowledge)

8 = Async (and wait for acknowledge)

0xFFFF = Abort previous acknowledge pending (5 and 6)

timeout	Timeout value in milliseconds.

Example:	Source VXIbus TTL trigger line 5 on controller 1 using Start protocol

srcttltrig 1, 5, 2, 1000

Return to VXI Trigger Commands


srcecltrig

Purpose:	Assert or de-assert a trigger on a ECL trigger line using a VXI protocol in a specified controller. This function is obsolete, use srctrig instead.

Command

Syntax:	srcecltrig <controller>, <line>, <protocol>, <timeout>

where

controller	Controller on which to source TTL trigger
-1 = Local controller or the first remote controller

line	0-5 corresponding to ECL lines 0-5.

protocol	Trigger protocol

0 = ON

1 = OFF

2 = Start

3 = Stop

4 = Sync

5 = Semi-sync

6 = Async

7 = Semi-sync (and wait for acknowledge)

8 = Async (and wait for acknowledge)

0xFFFF = Abort previous acknowledge pending (5 and 6)

<timeout>	Timeout value in milliseconds.

Example:	Source VXIbus ECL trigger line 5 on controller 1 using Start protocol

srcecltrig 1, 5, 2, 1000

Return to VXI Trigger Commands


enabletrigsense

Purpose:	Enables the sensing of the specified trigger line, or starts up the counter or tick timer for the specified protocol.

Command

Syntax:	enabletrigsense <controller>, <line>, <protocol>

where

controller	Controller on which to enable sensing of TTL trigger line

-1 = Local controller or the immediate remote controller

line	Trigger line to enable sensing

Value	Trigger line

0-7	TTL trigger lines 0 to 7

8-13	ECL trigger lines 0 to 5

50	TIC counter

60	TIC tick timers

protocol	Trigger Protocol

0 = ON

1 = OFF

2 = Start

3 = Stop

4 = Sync

5 = Semi-sync

6 = Async

Example:	Enable sensing of VXIbus TTL trigger line 4 on Controller 1 for Semi-sync protocol.

enabletrigsense 1, 4, 5

Return to VXI Trigger Commands


enablettlsense

Purpose:	Enable sensing of the specified VXIbus TTL trigger line for the specified protocol on the specified controller. This function is obsolete, use enabletrigsense instead.

Command

Syntax:	enablettlsense <controller>, <line>, <protocol>

where

controller	Controller on which to source TTL trigger
-1 = Local controller or the first remote controller

line	0-7 corresponding to TTL lines 0-7

protocol	Trigger protocol

0 = ON

1 = OFF

2 = Start

3 = Stop

4 = Sync

5 = Semi-sync

6 = Async

7 = Semi-sync (and wait for acknowledge)

8 = Async (and wait for acknowledge)

0xFFFF = Abort previous acknowledge pending
(5 and 6)

Example:	Enable sensing of VXIbus trigger Start protocol on TTL trigger line 5 on controller 1

enablettlsense 1, 5, 2, 1000

Return to VXI Trigger Commands


disabletrigsense

Purpose:	Disables the sensing of the specified trigger line, counter, or tick timer that was enabled by enabletrigsense.

Command

Syntax:	disabletrigsense <controller>, <line>

where

controller	Controller on which to disable sensing of TTL trigger line

-1 = Local controller or the immediate remote controller

line	Trigger line to disable sensing

Value	Trigger line

0 - 7	TTL trigger lines 0 to 7

8 - 13	ECL trigger lines 0 to 5

50	TIC counter

60	TIC tick timers

Example:	Disable sensing of VXIbus TTL trigger line 4 on Controller 1.

disabletrigsense 1, 4

Return to VXI Trigger Commands


disablettlsense

Purpose:	Disable sensing of the specified VXIbus TTL trigger line on the specified controller. This function is obsolete, use disabletrigsense instead.

Command

Syntax:	disablettlsense <controller>, <line>

where

controller	Controller on which to source TTL trigger
-1 = Local controller or the first remote controller

line	0-7 corresponding to TTL lines 0-7

Example:	Disable sensing of VXIbus TTL trigger line 5 on controller 1

disablettlsense 1, 5

Return to VXI Trigger Commands


waitfortrig

Purpose:	Waits for the specified TTL trigger line to be encountered on the specified controller.

Command

Syntax:	waitfortrig <controller>, <line>, <timeout>

where

controller	Controller waiting for trigger line to be encountered

-1 = Local controller or the immediate remote controller

line	Trigger line to wait on

Value	Trigger line

0 - 7	TTL trigger lines 0 to 7

8 - 13	ECL trigger lines 0 to 5

50	TIC counter

60	TIC tick timers

timeout	Timeout value in milliseconds

Example:	Wait for VXIbus TTL trigger line 4 to be sourced on Controller 1.

waitfortrig 1, 4, 10000

Return to VXI Trigger Commands


waitforttltrig

Purpose:	Waits for the specified TTL trigger line to be encountered on the specified controller. This function is obsolete, use waitfortrig instead.

Command

Syntax:	waitforttltrig <controller>, <line>, <timeout>

where

controller	Controller on which to source TTL trigger
-1 = Local controller or the first remote controller

line	0-7 corresponding to TTL lines 0-7.

timeout	Timeout value in milliseconds.

Example:	Wait for a VXIbus trigger on TTL trigger line 5 of controller 1

waitforttltrig 1, 5, 1000

Return to VXI Trigger Commands


enableeclsense

Purpose:	Enable sensing of the specified VXIbus ECL trigger line for the specified protocol on the specified controller. This function is obsolete, use enabletrigsense instead.

Command

Syntax:	enableeclsense <controller>, <line>, <protocol>

where

controller	Controller on which to source TTL trigger
-1 = Local controller or the first remote controller

line	0-5 corresponding to ECL lines 0-5.

protocol	Trigger protocol

0 = ON

1 = OFF

2 = Start

3 = Stop

4 = Sync

5 = Semi-sync

6 = Async

7 = Semi-sync (and wait for acknowledge)

8 = Async (and wait for acknowledge)

0xFFFF = Abort previous acknowledge pending (5 and 6)

Example:	Enable sensing of VXIbus trigger Start protocol on ECL trigger line 5 on controller 1

enableeclsense 1, 5, 2, 1000

Return to VXI Trigger Commands


disableeclsense

Purpose:	Disable sensing of the specified VXIbus ECL trigger line on the specified controller. This function is obsolete, use disabletrigsense instead.

Command

Syntax:	disableeclsense <controller>, <line>

controller	Controller on which to source TTL trigger
-1 = Local controller or the first remote controller

line	0-5 corresponding to ECL lines 0-5

Example:	Disable sensing of VXIbus ECL trigger line 5 on controller 1

disablettlsense 1, 5

Return to VXI Trigger Commands


waitforecltrig

Purpose:	Waits for the specified ECL trigger line to be encountered on the specified controller. This function is obsolete, use waitfortrig instead.

Command

Syntax:	waitforecltrig <controller>, <line>

where

controller	Controller on which to source TTL trigger
-1 = Local controller or the first remote controller

line	0-5 corresponding to ECL lines 0-5

timeout	Timeout value in milliseconds

Example:	Wait for a VXIbus trigger on ECL trigger line 5 of controller 1

waitforecltrig 1, 5, 1000

Return to VXI Trigger Commands


acknowledgetrig

Purpose:	Acknowledges the specified TTL/ECL or external trigger on the specified controller.

Command

Syntax:	acknowledgetrig <controller>, <line>

where

controller	Controller on which to acknowledge trigger interrupt

-1 = Local controller or the immediate remote controller

line	Trigger line to acknowledge

Value	Trigger line

0 - 7	TTL trigger lines 0 to 7

8 - 13	ECL trigger lines 0 to 5

40 - 49	External source/destination lines 0 to 9

Example:	Acknowledge a trigger interrupt for TTL line 4 on Controller 1.

acknowledgetrig 1, 4

Return to VXI Trigger Commands


maptrigtotrig

Purpose:	Maps the specified TTL, ECL, Star X, Star Y, external connection, or miscellaneous signal line to another.

Command

Syntax:	maptrigtotrig <controller>, <srctrig>, <desttrig>, <mode>

where

controller	Controller on which to map signal lines

-1 = Local controller or the immediate remote controller

srctrig	Source line to map to destination

desttrig	Destination line to map from source

Value	Source or Destination

0 - 7	TTL trigger lines 0 to 7

8 - 13	ECL trigger lines 0 to 5

14 - 26	Star X lines 0 to 12

27 - 9	Star Y lines 0 to 12

40 -49	External source/destination lines 0 to 9

40	Front panel In (connector 1)

41	Front panel Out (connector 2)

42	ECL bypass from front panel

43	Connection to EXTCLK input pin

44 - 9	Hardware-dependent external lines 4 to 9

50	TIC counter pulse output (TCNTR)

51	TIC counter finished output (GCNTR)

60	TIC TICK1 tick timer output

61	TIC TICK2 tick timer output

mode	Signal conditioning mode (0 = no conditioning)

Bit	Conditioning Effect

0	Synchronize with next CLK10 edge

1	Invert signal polarity

2	Pulse stretch to one CLK minimum

3	Use EXTCLK (not CLK10) for conditioning

All other values reserved for future expansion

Example:	Map VXIbus TTL trigger line 4 on Controller 1 out the front panel.

maptrigtotrig 1, 4, 41, 0

Return to VXI Trigger Commands


unmaptrigtotrig

Purpose:	Unmaps the specified TTL, ECL, Star X, Star Y, external connection, or miscellaneous signal line that was mapped to another line using maptrigtotrig.

Command

Syntax:	unmaptrigtotrig <controller>, <srctrig>, <desttrig>

where

controller	Controller on which to unmap signal lines

-1 = Local controller or the immediate remote controller

srctrig	Source line to unmap to destination

desttrig	Destination line mapped from source

Value	Source or Destination

0 - 7	TTL trigger lines 0 to 7

8 - 13	ECL trigger lines 0 to 5

14 - 26	Star X lines 0 to 12

27 - 39	Star Y lines 0 to 12

40 - 49	External source/destination lines 0 to 9

40	Front panel In (connector 1)

41	Front panel Out (connector 2)

42	ECL bypass from front panel

43	Connection to EXTCLK input pin

44 - 49	Hardware-dependent external lines 4 to 9

50	TIC counter pulse output (TCNTR)

51	TIC counter finished output (GCNTR)

60	TIC TICK1 tick timer output

61	TIC TICK2 tick timer output

Example:	Unmap VXIbus TTL trigger line 4 on Controller 1 that was mapped out the front panel.

unmaptrigtotrig 1, 4, 49

Return to VXI Trigger Commands


trigassertconfig

Purpose:	Configures the specified TTL/ECL trigger line assertion method.

Command

Syntax:	trigassertconfig <controller>, <line>, <mode>

where

controller	Controller on which to configure assertion mode

-1 = Local controller or the immediate remote controller

line	Trigger line to configure

Value	Trigger line

0 - 7	TTL trigger lines 0 to 7

8 - 13	ECL trigger lines 0 to 5

0xFFFF	General assertion configuration (all lines)

mode	Configuration mode

Bit	Specific Line Configuration Modes

0	1 = Synchronize falling edge of CLK10
0 = Synchronize rising edge of CLK10

Bit	General Configuration Modes

1	1 = Pass trigger through asynchronously
0 = Synchronize with next CLK10 edge

2	1 = Participate in Semi-sync with external rigger acknowledge protocol
0 = Do not participate

Example:	Configure TTL trigger line 4 on Controller 1 to synchronize to CLK10 for any assertion method and do not participate in Semi-sync.

trigassertconfig 1, 4, 0

Return to VXI Trigger Commands


trigcntrconfig

Purpose:	Configures TIC chip internal 16 bit counter.

Command

Syntax:	trigcntrconfig <controller>, <mode>, <source>, <count>

where

controller	Controller on which to configure the TIC counter

-1 = Local controller or the immediate remote controller

mode	Configuration mode

Value	Configuration Modes

0	Initialize the counter

2	Reload the counter leaving enabled

3	Disable/abort any count in progress

source	Trigger line to configure as input to counter

Value	Trigger line

0 -7	TTL trigger lines 0 to 7

8 - 3	TTL trigger lines 0 to 5

70	CLK10

71	EXTCLK connection

count	Number of input pulses to count before terminating

Example:	Configure the counter to count 25 assertions on TTL trigger line 5 on Controller 1.

trigcntrconfig 1, 0, 5, 25

Return to VXI Trigger Commands


trigextconfig

Purpose:	Configures the external trigger lines.

Command

Syntax:	trigextconfig <controller>, <line>, <mode>

where

controller	Controller on which to configure the external connection

-1 = Local controller or the immediate remote controller

line	Trigger line to configure

Value	Trigger line

40 - 49	External source/destination lines 0 to 9

40	Front panel In (connector 1)

41	Front panel Out (connector 2)

42	ECL bypass from front panel

43	EXTCLK

44 - 49	Hardware-dependent external lines 4 to 9

mode	Configuration mode

Bit	Configuration Modes

0	1 = Feed back any line mapped as input into the crosspoint switch
0 = Drive input to external pin

1	1 = Assert input (regardless of feedback)
0 = Leave input unconfigured

2	1 = If assertion selected, assert low
0 = If assertion selected, assert high

3	1 = Invert external input (not feedback)
0 = Pass external input unchanged

All other values are reserved for future expansion.

Example:	Configure external line 41 (front panel Out) to not be fed back and left tristated for use as a mapped output via maptrigtotrig.

trigextconfig -1, 41, 0

Return to VXI Trigger Commands


trigtickconfig

Purpose:	Configures TIC chip internal dual 5 bit tick timers.

Command

Syntax:	trigtickconfig <controller>, <mode>, <source>, <tcount1>, <tcount2>

where

controller	Controller on which to configure the TIC chip internal dual 5 bit

tick timers

-1 = Local controller or the immediate remote controller

mode	Configuration mode

Value	Configuration Modes

0	Initialize the tick timers (rollover mode)

1	Initialize the tick timers (non-rollover mode)

2	Reload the tick timers leaving enabled

3	Disable/abort any count in progress

source	Trigger line to configure as input to counter

Value	Trigger line

40 - 49	External source/destination lines 0 to 9

70	CLK10

71	EXTCLK connection

tcount1	Number of input pulses (as a power of two) to count before asserting TICK1 output (and terminating the tick timer if configured for non-rollover mode)

tcount2	Number of input pulses (as a power of two) to count before asserting TICK2 output

Example:	Configure the tick timers to interrupt every 6.55 milliseconds by dividing down CLK10 as an input.

trigtickconfig -1, 0, 70, 16, 0

Return to VXI Trigger Commands


System Interrupt Handler Commands

VIC supports the following system interrupt handler commands.

EnableSysfail	DisableSysfail

EnableACfail	DisableACfail

EnableSoftReset	DisableSoftReset

AssertSysReset

EnableSysReset	DisableSysReset

Return to Command Groups


enablesysfail

Purpose:	Sensitizes VIC to SYSFAIL interrupts from the specified controller.

Command

Syntax:	enablesysfail <controller>

where

controller	Controller on which to enable interrupt

-1 = Local controller or the first remote controller

Example:	Enable the SYSFAIL interrupt on the embedded CPU (or first remote controller).

enablesysfail -1

Return to System Interrupt Handler Commands


disablesysfail

Purpose:	Desensitizes VIC to SYSFAIL interrupts from the specified controller.

Command

Syntax:	disablesysfail <controller>

where

controller	Controller on which to disable interrupt

-1 = Local controller or the first remote controller

Example:	Disable the SYSFAIL interrupt on the embedded CPU (or first remote controller).

disablesysfail -1

Return to System Interrupt Handler Commands


enableacfail

Purpose:	Sensitizes VIC to ACFAIL interrupts from the specified controller.

Command

Syntax:	enableacfail <controller>

where

controller	Controller on which to enable interrupt

-1 = Local controller or the first remote controller

Example:	Enable the ACFAIL interrupt on the embedded CPU (or first remote controller).

enableacfail -1

Return to System Interrupt Handler Commands


disableacfail

Purpose:	Desensitizes VIC to ACFAIL interrupts from the specified controller.

Command

Syntax:	disableacfail <controller>

where

controller	Controller on which to disable interrupt

-1 = Local controller or the first remote controller

Example:	Disable the ACFAIL interrupt on the embedded CPU (or first remote controller).

disableacfail -1

Return to System Interrupt Handler Commands


enablesoftreset

Purpose:	Enables the local Soft Reset interrupt being generated from a write to the Reset bit of the local CPU's Control register.

Command

Syntax:	enablesoftreset

Example:	Enable the local Soft Reset interrupt.

enablesoftreset

Return to System Interrupt Handler Commands


disablesoftreset

Purpose:	Disables the local Soft Reset interrupt being generated from a write to the Reset bit of the local CPU's Control register.

Command

Syntax:	disablesoftreset

Example:	Disable the local Soft Reset interrupt.

disablesoftreset

Return to System Interrupt Handler Commands


assertsysreset

Purpose:	Asserts SYSRESET* on the backplane of the specified controller.

Command

Syntax:	assertsysreset <controller>

where

controller	Controller on which to assert SYSRESET*

-1 = From local controller or the first remote controller

-2 = All extenders

mode	Mode of execution

0 = Do not disturb original configuration

1 = Force link between SYSRESET* and local reset
(SYSRESET* resets local CPU)

2 = Break link between SYSRESET and local reset
(SYSRESET* does not reset local CPU)

Example:	Assert the SYSRESET* interrupt on the embedded CPU (or first remote controller) without changing the current configuration.

assertsysreset -1, 0

Return to System Interrupt Handler Commands


enablesysreset

Purpose:	Sensitizes VIC to SYSRESET* interrupts from the specified controller.

Command

Syntax:	enablesysreset <controller>

where

controller	Controller on which to enable interrupt

-1 = Local controller or the first remote controller

Example:	Enable the SYSRESET* interrupt on the embedded CPU (or first remote controller).

enablesysfail -1

Return to System Interrupt Handler Commands


disablesysreset

Purpose:	Desensitizes VIC to SYSRESET* interrupts from the specified controller.

Command

Syntax:	disablesysreset <controller>

where

controller	Controller on which to disable interrupt

-1 = Local controller or the first remote controller

Example:	Disable the SYSRESET* interrupt on the embedded CPU (or first remote controller).

disablesysfail -1

Return to System Interrupt Handler Commands


Bus Extender Commands

The VIC utility supports the following Bus Extender commands.

MapECLtrig

MapTTLtrig

MapUtilBus

MapVXIint

Return to Command Groups


mapecltrig

Purpose:	Routes the VXIbus ECL trigger lines for the specified VXI extender in the specified directions.

Command

Syntax:	mapecltrig <extender>, <lines>, <directions>

where

extender	Logical address of VXI extender

lines	Bit vector of ECL lines to enable. Bits 5 to 0 correspond to ECL lines 5 to 0, respectively.

1 = Enable for appropriate line

0 = Disable for appropriate line

directions	Bit vector of directions for ECL lines. Bits 5 to 0	correspond to ECL lines 5 to 0, respectively.

1 = Into the VXI extender

0 = Out of the VXI extender

Example:	Route VXIbus ECL trigger line 4 out of the mainframe through the VXI extender at Logical Address 1.

mapecltrig 1, 0x08, 0

Return to Bus Extender Commands


mapttltrig

Purpose:	Routes the VXIbus TTL trigger lines for the specified VXI extender in the specified directions.

Command

Syntax:	mapttltrig <extender>, <lines>, <directions>

where

extender	Logical address of VXI extender

lines	Bit vector of TTL lines to enable. Bits 7 to 0 correspond to TTL lines 7 to 0, respectively.

1 = Enable for appropriate line

0 = Disable for appropriate line

directions	Bit vector of directions for TTL lines. Bits 7 to 0 correspond to TTL lines 7 to 0, respectively.

1 = Into the VXI extender

0 = Out of the VXI extender

Example:	Route VXIbus TTL trigger line 4 out of the mainframe through the VXI extender at Logical Address 1.

mapttltrig 1, 0x08, 0

Return to Bus Extender Commands


maputilbus

Purpose:	Maps the utility bus for the specified VXI extender.

Command

Syntax:	maputilbus <extender>, <utilmode>

where

extender	Logical address of VXI extender

utilmode	Bit vector of utility bus signals corresponding to the utility bus signals.

1 = Enable for corresponding signal and direction

0 = Disable for corresponding signal and direction

Bit	Utility Bus Signal and Direction

5	ACFAIL into the mainframe

4	ACFAIL out of the mainframe

3	SYSFAIL into the mainframe

2	SYSFAIL out of the mainframe

1	SYSRESET* into the mainframe

0	SYSRESET* out of the mainframe

Example:	Map SYSFAIL into the mainframe through the VXI extender at Logical Address 5. Map SYSRESET into and out of the mainframe. Do not map ACFAIL at all.

maputilbus 5, 0xB

Return to Bus Extender Commands


mapvxiint

Purpose:	Maps the specified VXI interrupts for the specified VXI extender in the specified directions.

Command

Syntax:	mapvxiint <extender>, <levels>, <directions>

where

extender	Logical address of VXI extender

levels	Bit vector of VXI interrupt levels to enable. Bits 6 to 0 correspond to VXI interrupt levels 7 to 1, respectively.

1 = Enable for appropriate level

0 = Disable for appropriate level

directions	Bit vector of directions for VXI interrupt levels. Bits 6 to 0 correspond to VXI interrupt levels 7 to 1, respectively.

1 = Into the VXI extender

0 = Out of the VXI extender

Example:	Map VXI interrupt 4 on the extender at Logical Address 5 to go out of the mainframe.

mapvxiint 5, 0x08, 0x00

Return to Bus Extender Commands


Auxiliary Commands

The VIC utility supports the following auxiliary commands.

help	?

DisableMonitor	EnableMonitor

Set

PParms	PWidth

Peek	Poke

RMentry?	LAddrs?

NumLAddrs?	CmdrTable?

A16memMap?	A24memMap?

A32memMap?

ReadRegister?	WriteRegister

DeviceNumber?	deviceladd?

DeviceConfigure?	DeviceInformation?

DeviceReset?	$

!	*

Version	Quit

Return to Command Groups


help

Purpose:	Provides help on the specified command. If the specified command is not unique, it lists all commands with that prefix, e.g. help vxi will list all commands with the prefix vxi.

Command

Syntax:	help <command>

where

command	A valid command or a keyword for group of commands. The keywords for help are: cwsc, swsc, hldbac, lra sigc, intr, trig, sih, scc, bec, aux, and all.

Return to Auxiliary Commands


?

Purpose:	Provides help on the specified command. If the specified command is not unique, it lists all commands with that prefix, e.g. ? vxi will list all commands with prefix vxi.

Command

Syntax:	? <command>

where

command	A valid command or a key word for group of commands. The key words for help are: cwsc, swsc, hldbac, lra sigc, intr, trig, sih, scc, bec, aux, and all.

Return to Auxiliary Commands


disablemonitor

Purpose:	Disables the VXIbus Monitor, which monitors the status of the VXIbus in the system.

Command

Syntax:	disablemonitor

Return to Auxiliary Commands


enablemonitor

Purpose:	Enables the VXIbus Monitor, which monitors the status of the VXIbus in the system, through the specified controller. If no controller is specified, enables the monitoring for the last controller being modified (-2 = OR of all controllers).

Command

Syntax:	enablemonitor [<controller>]

Example:	Monitor Controller 24.

enablemonitor 24

Return to Auxiliary Commands


set

Purpose:	Invokes device-level calls. The status bar displays the device name in white letters on a blue background. At this stage, you should not specify la in the VIC commands that require it as the first parameter, such as Word Serial Commands.

To leave device-level calls mode, use set with no arguments, or with the device on which VIC is running, i.w. the la of the embedded or CPU-MXI card.

Command

Syntax:	set <la> or <devname>

Note:	<la> refers to logical address of device. <devname> refers to the name of the device inside " ". Partial names will work for <devname>.

Example:	Set for the device call for "GPIB-VXI."

set "GPIB-VXI"

Return to Auxiliary Commands


pparms

Purpose:	Sets the specified access parameters. These access parameters are used in peek and poke VIC commands. If no parameter is specified, it displays the current access parameters.

Command

Syntax:	pparms [<accessparms>]

where

accessparms	(Bits 0 to 1) VXI address space

1 = A16

2 = A24

3 = A32

(Bits 2 to 4) access privilege

0 = Nonprivileged data access

1 = Supervisory data access

2 = Nonprivileged program access

3 = Supervisory program access

4 = Nonprivileged block access

5 = Supervisory block access

(Bits 5 to 6)

0 = Reserved

(Bit 7) Byte order

0 = Motorola

1 = Intel

(Bits 8 to 15)

0 = Reserved

Example:	Set access parameters to A16 space, nonprivileged data, and Motorola byte order.

pparms 1

Return to Auxiliary Commands


pwidth

Purpose:	Sets the specified width. This width is used in peek and poke VIC commands. If no parameter is specified, it displays the current width.

Command

Syntax:	pwidth [<width>]

where

width	Data transfer width

1 = Byte

2 = Word

4 = Longword

Example:	Set width as byte transfer.

pwidth 1

Return to Auxiliary Commands


peek

Purpose:	Reads a single byte, word, or longword (depending on the width set by the pwidth VIC command) from the specified address (in the address space with access parameters set by the pparms VIC command).

Command

Syntax:	peek <address>

where

address	VXI address

Example:	Read the ID register of a device at Logical Address 4.

peek 0xc100

Return to Auxiliary Commands


poke

Purpose:	Writes a single byte, word, or longword (depending on the width set by the pwidth VIC command) to the specified address (in the address space with access parameters set by the pparms VIC command).

where

address	VXI address

value	Value to write

Command

Syntax:	poke <address>, <value>

Example:	Write a value of 0x1000 to the Offset register of a device at Logical Address 4.

poke 0xc106, 0x1000

Return to Auxiliary Commands


rmentry?

Purpose:	Returns Resource Manager (RM) information about a device.

Command

Syntax:	rmentry? [<la>]

where

la	VXI logical address

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

Example:	Return RM information about a device at Logical Address 4.

rmentry? 4

Return to Auxiliary Commands


laddrs?

Purpose:	Gives a list of known logical addresses.

Command

Syntax:	laddrs?

Return to Auxiliary Commands


numladdrs?

Purpose:	Gives the number of known logical addresses.

Command

Syntax:	numladdrs?

Return to Auxiliary Commands


cmdrtable?

Purpose:	Displays the system hierarchy information.

Command

Syntax:	cmdrtable?

Return to Auxiliary Commands


a16memmap?

Purpose:	Gives A16 memory map of the system.

Command

Syntax:	a16memmap?

Return to Auxiliary Commands


a24memmap?

Purpose:	Gives A24 memory map of the system.

Command

Syntax:	a24memmap?

Return to Auxiliary Commands


a32memmap?

Purpose:	Gives A32 memory map of the system.

Command

Syntax:	a32memmap?

Return to Auxiliary Commands


readregister?

Purpose:	Reads the register (word access) on the specified logical address.

Command

Syntax:	readregister? <la>, <reg>[, <"OFF/ON">]

where

la	VXI logical address

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

reg	Offset within VXI Logical Address registers

Note:	The flag "ON" or "OFF" (default = "OFF") gives more information on the individual fields of the register. Valid registers are all even numbers between 0 and 62 as well as the following register names:  A24PL, A24PH, A32PL, A32PH, ATTR, DHIG, DLOW, DTYP, ICON, ID, IST, OFFS, PROT, RESP, SNL, SNH, STAT, SUBC, VNUM.

Example:	Read the ID register of a device at Logical Address 4.

readregister? 4, 0, "ON"

Return to Auxiliary Commands


writeregister

Purpose:	Writes the register (word access) on the specified logical address with the specified value.

Command

Syntax:	writeregister <la>, <reg>, <value>

where

la	VXI logical address

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

reg	Offset within VXI Logical Address registers

value	Value to write

Note:	Valid registers are even numbers between 0 and 62 as well as the following register names:  CONT, DEXT, DHIG, DLOW, ICON, LADD, OFFS, SIGN.

Example:	Write the Offset register of a device at Logical Address 4 with 0x2000.

writeregister 4, OFFS, 0x2000

Return to Auxiliary Commands


devicenumber?

Purpose:	Gets the number of devices in the system if issued by the Resource Manager; otherwise, it gives the number of immediate Servants.

Command

Syntax:	devicenumber?

Example:	Find the number of devices in the system.

devicenumber?

Return to Auxiliary Commands


deviceladd?

Purpose:	Gets a list of all the devices in the system if issued by the Resource Manager; otherwise, it gives a list of all the immediate Servants.

Command

Syntax:	deviceladd?

Example:	Find all the Servants.

deviceladd?

Return to Auxiliary Commands


deviceconfigure?

Purpose:	Gives the current hierarchy information for the specified logical address. If the logical address is not specified, it gives the current hierarchy information for all the devices in the system.

Command

Syntax:	deviceconfigure? [<la>]

where

la	VXI logical address

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

Example:	Get the hierarchy information for device at Logical Address 5.

deviceconfigure? 5

Return to Auxiliary Commands


deviceinformation?

Purpose:	Gives the device information for the specified logical address. If the logical address is not specified, it gives the information for all the devices in the system.

Command

Syntax:	deviceinformation? [<la>]

where

la	VXI logical address

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

Example:	Get the device information for the Logical Address 5.

deviceinformation? 5

Return to Auxiliary Commands


devicereset?

Purpose:	Soft resets the device for the specified logical address. SYSFAIL generation is inhibited while the device is in the self-test state. The command waits for five seconds or until the selected device has indicated passed (whichever occurs first). If the device passes its self-test, SYSFAIL generation is re-enabled. If the device fails its self-test, SYSFAIL generation is inhibited.

Command

Syntax:	devicereset? <la>

where

la	VXI logical address

Note:	When using device-level commands, don't specify the la. The la of the active device will be use.

Example:	Soft reset the device at Logical Address 4.

devicereset? 4

Return to Auxiliary Commands


$

Purpose:	Executes VIC commands from a file.

Command

Syntax:	$ [<filename>]

where

filename	File from which to execute commands. If <filename> is not specified $ will bring up a file selection dialog so that you can choose the name interactively.

Example:	Execute the VIC commands in the file "temp.dat."

$ "temp.dat"

Return to Auxiliary Commands


!

Purpose:	Executes the specified previously executed command. If no parameter is specified, it executes the last VIC command in the history of commands.

Command

Syntax:	! [<command string>]

where

command string	Command string

Return to Auxiliary Commands


*

Purpose:	Executes the last VIC command for the specified number of times. If no parameter is specified, it executes the last VIC command once.

Command

Syntax:	* [<repeat number>]

where

repeat number	Number of times to execute the last command

Example:	Execute the last VIC command 10 times.

* 10

Return to Auxiliary Commands


version

Purpose:	Shows the version of the NI-VXI software in use.

Command

Syntax:	version

Return to Auxiliary Commands


quit

Purpose:	Quits the VIC utility.

Command

Syntax:	quit

Return to Auxiliary Commands


Device-Level Calls

Use the set command to enter device-level mode. In this mode you can communicate with only one device. The name of the active device is displayed on the Status Bar.