| Version 2.7 (R14SP1+) xPC Target™ Release Notes | ![]() |
This table summarizes what's new in Version 2.7 (R14SP1+):
New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems | Related Documentation at Web Site |
|---|---|---|---|
Yes | Yes | No |
New features and changes introduced in this version are
xPC Target™ Explorer has been enhanced and now fully supports the following:
Scopes of type file
Access to target PC file systems
Ability to export and import target PC environments
Designating a default target PC
Ability to view PCI device information
See the xPC Target™ Getting Started Guide and the xPC Target™ User's Guide for details on xPC Target Explorer.
The following tools are obsolete and have been removed from xPC Target:
xpcrctool
xpcsetup
xpcscope
xpctgscope
Use xPC Target Explorer to perform the same activities.
This release of xPC Target introduces the concept of a default target PC and multiple target PCs to help you work with xPC Target Explorer, command-line interface objects, and the build process. External mode is supported only with the default target PC. See the xPC Target™ Getting Started Guide for details.
In previous releases, you could build models that contained From/To xPC Target blocks without setting the Real-Time Workshop® parameter RTW system target file to xpctarget.tlc. To accommodate the use of multiple target PCs, you now must perform the following to run a model that contains From/To xPC Target blocks:
Configure the Real-Time Workshop parameter RTW system target file for the model. Set this value to xpctarget.tlc. You access this dialog from the Simulink® model Simulation > Configuration Parameters menu.
Specify the correct target PC environment on the xPC Target options node of the Real-Time Workshop parameters dialog. In particular, either select Use default target PC or enter the target name of the target PC to which you want to connect. If you have only one target PC, the model uses the default target PC and you do not need to perform this configuration.
To use existing models with these blocks, you must set the Real-Time Workshop parameter RTW system target file to xpctarget.tlc before running them. Note that the xpcsliface command behavior does not change.
xPC Target now supports the monitoring of test-pointed Stateflow® states. This is available only through the MATLAB® command-line interface. It is not yet supported by xPC Target Explorer or xPC Target Scope blocks.
To support target PC file systems, the xPC Target COM API has been enhanced to support a new object, xPCFileSystem. To support this object, the following methods were added:
CD
CloseFile
GetFileSize
Init
MKDIR
OpenFile
PWD
ReadFile
RemoveFile
RMDIR
ScGetFileName
ScGetWriteMode
ScGetWriteSize
ScSetFileName
ScSetWriteMode
ScSetWriteSize
WriteFile
xPC Target 2.7 has new driver blocks, including support for the following boards:
Manufacturer | Board |
|---|---|
National Instruments® | PCI/PXI-6602 |
Adlink | 6208A |
Commtech | Fastcom 422/2-PCI |
UEI | PD2-DIO-64 series, PDL-DIO-64 series, PDXI-DIO-64 series |
Quatech® | DSCP-200/300 |
The drivers for the following boards have been updated:
Manufacturer | Boards |
|---|---|
General Standards | ADADIO |
Measurement Computing™ | PCI-DAS1602/12 D/A |
Sensoray | 626 |
In addition, the RS-232 sublibrary has changed:
FIFO read and write blocks have been added to support all RS-232 sublibrary composite drivers.
The following demos have been added to the xpcdemos directory:
udphost.mdl
udphostpost.mdl
udpsendreceiveA.mdl
udpsendreceiveB.mdl
udptarget.mdl
udpxpctargetsteam.m
xpcserialasciisplit.mdl
xpcserialasciitest.mdl
xpcserialbinarysplit.mdl
xpcserialbinarytest.mdl
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 2.7.2 (R14SP2) xPC Target™ | Version 2.6.1 (R14SP1) xPC Target™ | ![]() |
| © 1984-2008- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |