|
|
|
| R2011b Documentation → xPC Target | |
Learn more about xPC Target |
|
| Contents | Index |
| On this page… |
|---|
The following UEI PowerDAQ board series have Analog Input frame driver blocks:
PD2-MF — 12, 14, and 16-bit series
PD2-MFS — 12, 14, and 16-bit series
PDXI-MF — 12, 14, and 16-bit series
PDXI-MFS — 12, 14, and 16-bit series
In frame-based mode, the boards for these driver blocks send interrupts to the xPC Target software. The xPC Target model is executed when each frame completes on the board. For proper use of the UEI frame driver blocks, note the IRQ values for each UEI board in the model and configure those boards appropriately with the model Configuration Parameters dialog.
Note To use the UEI PowerDAQ board series with the xPC Target Analog Input frame driver blocks, you need to upgrade the UEI PowerDAQ boards. Contact your UEI representative and request the xPC Target upgrade for these boards. |
Before you begin, observe the following usage notes for the UEI boards in a master/slave configuration:
You should set the slowest board as the master. If you do not want to use the slowest board as the master, you can explicitly set the Acquisition frequency parameter of the master board driver block to one that enables the slowest board in the configuration to work. You can derive the maximum speed of the board from the board name.
Slave boards do not need to be identical to the master board.
In the model, set the priority of slave blocks higher than master blocks. Right-click the slave or master block and select Block Properties. In the dialog, enter a value in the Priority property. For example, if you have multiple slave blocks, you can enter values of 2 for the slave blocks and 3 for the master block, where a lower number indicates a higher priority.
The number of channels in use on the master does not need to be the same as those used on any of the slave boards.
Connect the master and its slave(s) with the J6 connectors on the boards and the appropriate cables. This connects the acquisition clock and scan clock from the master board to all slave boards.
The number of slaves you can have is limited by the number of connection points available on the cable and the availability of PCI slots.
This topic describes how you determine the interrupt number to which the board is set. The methods vary depending on your hardware configuration.
This topic includes
Single UEI Board — How to use getxpcpci to get information about the PCI devices installed on the target machine. This method works if you have one UEI board in your system. The target machine BIOS assigns the IRQ number.
Guidelines for Multiple UEI Boards — How to get information about the PCI devices if you have two or more UEI boards configured in a master/slave configuration. This is an iterative method that requires you to reboot the target machine with the insertion of each UEI board.
Note To allow the PCI BIOS to set up the plugged-in PCI cards properly, disable (set to No) the Plug-and-Play (PnP) operating system feature. The xPC Target kernel is not a PnP operating system; you must disable this feature or PCI devices will not work on the xPC Target software. |
If you have one UEI board for your target machine, that board is the master.
On the host computer, open the model that you want to use with the UEI board.
In the Simulink > Configuration Parameters dialog box, select the xPC Target options node.
In the Real-time interrupt source parameter, select Auto (PCI only).
From the I/O board generating the interrupt list, select the value UEI-MFx. This specifies that the UEI MFx board generates the interrupt.
For the PCI slot (-1: autosearch) or ISA base address parameter, enter the same PCI address as for the UEI MFx Frame block PCI slot parameter. Enter -1 (for autodetection) if this is the only UEI board in the target system.
Click OK and save the model.
If you have two or more UEI boards in a master/slave configuration, use the following procedure. Note which UEI board you want to use as the master.
On the host computer, open the model that you want to use with the multiple UEI boards.
In the Simulink > Configuration Parameters dialog box, select the xPC Target options node.
In the Real-time interrupt source parameter, select Auto (PCI only).
From the I/O board generating the interrupt list, select the value UEI-MFx. This specifies that the UEI MFx board generates the interrupt.
From a MATLAB Command Window running on the host computer, type
getxpcpci all
Note the slot numbers for the UEI boards.
Determine the slot number for the master board.
For the PCI slot (-1: autosearch) or ISA base address parameter, enter the bus and the slot number of the master board. Use the format [bus, slot].
Click OK and save the model.
If the UEI A/D frame block is in a Function-Call Subsystem called from an IRQ Source block,
From the I/O board generating the interrupt list, select the value UEI-MFx. This specifies that a UEI MFx board generates the interrupt.
For the PCI slot (-1: autosearch) or ISA base address parameter, enter the same PCI address as for the UEI MFx Frame block PCI slot (-1: autosearch) parameter.
Only enter -1 (for autodetection) if this is the only UEI board in the target system.
If more than one UEI board is or will be in the target system, enter the bus and slot number using the format [bus, slot].
Repeat this procedure for each IRQ Source block calling separate subsystems.
Example models that illustrate the use of UEI frame driver blocks are in the xpcdemos directory. Correct operation of these models requires that the interrupt source be set correctly in the simulation parameters dialog.
Note that these examples use the UEI PD2-MF-16-333/16H driver block. Replace the block as appropriate for your target system.
xpcUEIFrame.mdl — A simple frame-based model that outputs to an xPC Target scope. The model runs each time the board completes a frame of data.
xpcUEIMasterSlaveframe.mdl — A master/slave frame-based model.
xpcUEIasync.mdl — A model that implements a UEI A/D frame block in a Function-Call Subsystem called by an IRQ Source block. To set the interrupt for the UEI board, you work with the IRQ Source block parameters.
In this example, the interval at which the IRQ Source block triggers the Function-Call Subsystem is the board frame completion time. The rest of the model runs at the model sample time. This latter point implies that there may or may not be a new frame of output data in the output signal when the rest of the model executes. However, if you place all processing of the data in the Function-Call Subsystem, this is not an issue.
xpcUEIDualasync.mdl — A model that implements multiple UEI A/D frame blocks in Function-Call Subsystems called by IRQ Source blocks. To set the interrupt for the UEI boards, you work with the IRQ Source block parameters.
xpcFrameloop.mdl — A model that illustrates how to perform sample-based processing on a frame of data. Because the fastest interrupt available is the frame completion interrupt, no part of the model can execute at a faster rate than frame completion. The For Iterator block executes once per frame completion and loops through the data.
 | Grouping the UEI Boards | Boards and Blocks — Alphabetical List |  |
Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |
