Store 
| Products & Services | Solutions | Academia | Support | User Community | Company |
 |
Download Product Updates | | |  |
Get Pricing | | | |
Trial Software |
| Documentation → xPC Target |
| Products & Services | Solutions | Academia | Support | User Community | Company |
|
Download Product Updates | | | |
Get Pricing | | | |
Trial Software |
| Documentation → xPC Target |
| Contents | Index |
| Learn more about xPC Target |
This table summarizes what's new in Version 3.2 (R2007a):
New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems | Related Documentation at Web Site |
|---|---|---|---|
Yes | Yes | Bug
Reports | No |
New features and changes introduced in this version are
xPC Target now supports the encoding and decoding of messages specified via a CANdb file (see Accessing CANdb DBC Format Databases from the xPC Target Environment in the xPC Target I/O Reference). The CANDBC library (available from within the CAN library) includes blocks for the decoding and formatting of these messages. The CAN library also includes a CANDBC Translator block, which translates the CANdb message to one that xPC Target can write into the transmit FIFO with a FIFO mode Write block.
The new xpccandbcfifo model illustrates how to read the CANdb messages contained in matlabroot\toolbox\rtw\targets\xpc\xpcdemos\demo.dbc.
xPC Target now supports the selection of signals using signal labels (see the Signal name parameter of the Signal Properties Dialog Box in the Simulink documentation) in addition to block paths. This is supported for target application objects, C and COM API, and xPC Target Explorer.
xPC Target has the following new target application object functions:
xPC Target has the following new C API functions:
xPC Target has the following new COM API functions:
xPC Target Explorer can now display signals by their label instead of by block path. You can view signals by their labels by right-clicking the Model Hierarchy node and selecting View Only Labeled Signals. To view signals by their block paths, right-click the Model Hierarchy node and select View All Signals. Hovering over the signal label or block path displays the signal block path or signal label, respectively. For details, see Signal Monitoring with xPC Target Explorer in the xPC Target User's Guide.
xPC Target has new API functions and structures to display the contents of a folder.
The new C API structure is dirStruct. The new C API functions are:
The new COM API structures are FSDir and FSDiskInfo. The new COM API functions are:
The From xPC Target block now allows you to manually enter a cell array of signals (Signal name parameter) to read. Using a cell array of signal names, the From xPC Target block will output a vector of signal values. This can improve the performance of the application. In previous releases, this parameter accepted only one signal.
You cannot download a target application that was built from a different version of xPC Target than the xPC Target kernel on the target PC. Attempts to download such a target application generates an error message on the target PC monitor:
Mismatch between model and kernel versions
In previous releases, downloading a mismatched target application causes the target PC to crash.
xPC Target now supports the logging and monitoring of discrete states in a model. In previous releases, you could not log and monitor discrete states (see Signal Logging in the xPC Target User's Guide).
xPC Target now supports the Microsoft® Visual C++® 2005 Express Edition compiler. See Host PC Requirements in the xPC Target Getting Started Guide for details.
Note If you use Microsoft Visual C++ 2005 Express Edition, xPC Target does not support the generation of COM objects from the xPC Target model. |
xPC Target now supports the parallel ports of your target PC (see Parallel Ports in the xPC Target I/O Reference). This feature also enables you to generate interrupts using parallel ports.
xPC Target 3.2 has new driver blocks, including support for the following boards:
Commtech Fastcom 422/2-PCI-335 board (see xPC Target RS-232 and 422/485 Drivers (Composite) in the xPC Target I/O Reference)
Measurement Computing™ PCI-DAS1002 and PCI-DAC6703 (see Measurement Computing PCI-DAS1002 and Measurement Computing PCI-DAC6703 in the xPC Target I/O Reference)
Quanser Q4 (see Quanser Q4 in the xPC Target I/O Reference)
National Instruments PCI-6528 (see National Instruments PCI-6528 in the xPC Target I/O Reference)
xPC Target now enables you to write your own custom device drivers for xPC Target. This documentation is only available for download as a PDF file. See http://www.mathworks.com/products/xpctarget/ for details on how to access this file.
If you upgrade your xPC Target software from a previous version, you must recreate the target boot disk and you must rebuild your xPC Target applications.
 | Version 3.3 (R2007b) xPC Target | Version 3.1 (R2006b) xPC Target |  |
Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
| © 1984-2009- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |
