Mathworks XPC TARGET RELEASE NOTES

xPC Target™ Release Notes

How to Contact The MathWorks

www.mathworks. comp.soft-sys.matlab Newsgroup www.mathworks.com/contact_TS.html Technical Support

suggest@mathworks.com Product enhancement suggestions

bugs@mathwo doc@mathworks.com Documentation error reports service@mathworks.com Order status, license renewals, passcodes

info@mathwo

com

rks.com

Web

Bug reports

Sales, prici

ng, and general information

508-647-7000 (Phone)

508-647-7001 (Fax)

The MathWorks, Inc. 3 Apple Hill Drive Natick, MA 01760-2098

For contact information about worldwide offices, see the MathWorks Web site.

xPC Target™ Release Notes

The software described in this document is furnished under a license agreement. The software may be used or copied only under the terms of the license agreement. No part of this manual may be photocopied or reproduced in any form without prior written consent from The MathW orks, Inc.

FEDERAL ACQUISITION: This provision applies to all acquisitions of the Program and Documentation by, for, or through the federal government of the United States. By accepting delivery of the Program or Documentation, the government hereby agrees that this software or documentation qualifies as commercial computer software or commercial computer software documentation as such terms are used or defined in FAR 12.212, DFARS Part 227.72, and DFARS 252.227-7014. Accordingly, the terms and conditions of this Agreement and only those rights specified in this Agreement, shall pertain to and govern theuse,modification,reproduction,release,performance,display,anddisclosureoftheProgramand Documentation by the federal government (or other entity acquiring for or through the federal government) and shall supersede any conflicting contractual terms or conditions. If this License fails to meet the government’s needs or is inconsistent in any respect with federal procurement law, the government agrees to return the Program and Docu mentation, unused, to The MathWorks, Inc.

Trademarks

MATLAB and Simulink are registered trademarks of The MathWorks, Inc. See

www.mathworks.com/trademarks for a list of additional trademarks. Other product or brand

names may be trademarks or registered trademarks of their respective holders.

Patents

The MathWorks products are protected by one or more U.S. patents. Please see

www.mathworks.com/patents for more information.

Summary by Version ............................... 1

Contents

Version 4.3 (R2010a) xPC Target

Version 4.2 (R2009b) xPC Target

Version 4.1 (R2009a) xPC Target

Version 4.0 (R2008b) xPC Target

Version 3.4 (R2008a) xPC Target

Version 3.3 (R2007b) xPC Target

Version 3.2 (R2007a) xPC Target

Version 3.1 (R2006b) xPC Target

Version 3.0 (R2006a+) xPC Target

Version 2.9 (R2006a) xPC Target

.................... 5

.................... 10

.................... 17

.................... 22

.................... 29

.................... 37

.................... 41

.................... 46

................... 49

.................... 55

Version 2.8 (R14SP3) xPC Target

Version 2.7.2 (R14SP2) xPC Target

Version 2.7 (R14SP1+) xPC Target

Version 2.6.1 (R14SP1) xPC Target

Version 2.6 (R14+) xPC Target

...................... 71

.................... 59

.................. 61

................... 63

.................. 68

iii

Version 2.5 (R14) xPC Target ....................... 75

Version 2.0.3 (R13SP2)

Version 2 (R13) xPC Target

Version 1.2 (R12.1) xPC Target

Version 1.1 (R12) xPC Target

Compatibility Sum mary for xPC Target Software

............................. 87

......................... 88

...................... 93

....................... 96

.... 99

iv Contents

SummarybyVersion

This table provides quick access to what’s new in each version. For clarification, see “Using Release Notes” on page 2 .

xPC Target™ Release Notes

Version (Release)

Latest Versi V4.3 (R2010a

V4.2 (R2009b)

V4.1 (R2009a)

V4.0 (R2

V3.4 (R2008a)

V3.3 (R2007b)

V3.2 (

V3.1 (R2006b)

008b)

R2007a)

New Features and Changes

Yes

)

Details

Yes Details

Yes Detai

Yes Details

Version Compatibilit Consideratio

Yes Summary

Yes

Summa

Yes Summary

Fixed Bugs and Known Problems

Bug Reports Includes fix

Bug Reports Includes fixes

Bug Repor Includes

Bug Reports Includes fixes

Bug Rep Inclu

Bug Reports Includes fixes

fixes

orts

des fixes

Related Documentation at Web Site

Printable R elease Notes: PDF

Current product documentation

V3.0 (R2006a+)

.9 (R2006a)

V2.8 (R14SP3)

Yes

ails

Det

Yes Details

Yes

mary

Sum

Yes Summary

Reports

Bug

ludes fixes

Inc

Bug Reports Includes fixes

xPC Target™ Release Notes

Version (Release)

V2.7.2 (R14SP2)

V2.7 (R14SP1+)

V2.6.1 (R14SP1)

V2.6 (R14+)

V2.5 (R14)

V2.0.3 (R13SP2)

V2 (R13)

V1.2 (R12.1)

New Features and Changes

Yes Details

No No No

Yes Details

Version Compatibility Considerations

Yes Summary

Fixed Bugs and Known Problems

Bug Reports Includes fixes

Fixed Bugs

Fixed Bugs Open Bugs

Fixed Bugs

No bug fixes

Related Documentation at Web Site

Printable R elease Notes: PDF

V2.0.3 product documentation

V1.1 (R12)

Yes Details

Yes Summary

No bug fixes

Using Release Notes

Use release notes when upgrading to a newer version to learn about:

• New features

• Changes

• Potential impact on your existing files and practices

SummarybyVersion

Review the release notes for other MathWorks™ products required for this product (for example, MATLAB

or Simulink®). Determine if enhancements,

bugs, or compatibility considerations in other products impact you.

If you are upgrading from a software version other than the m ost recent one, review the current release notes and all interim versions. For example, when you upg rade from V1.0 to V1.2, review the release notes for V1.1 and V1.2.

What Is in the Release Notes

New Features and Changes

• New functionality

• Changes to existing functionality

Version Compatibility Con si derations

When a new feature or change introduces a reported incompatibility between versions, the Compatibility Considerations subsection explains the impact.

Compatibility issues reported after the product release appear under Bug Reports at The MathWorks™ Web site. Bug fixes can sometimes result in incompatibilities, so review the fixed bugs in Bug Reports for any compatibility impact.

Fixed Bugs and Known Problems

The MathWorks offers a user-searchable Bug Reports database so you can view Bug Reports. The development team updates this database at release time and as more information becomes available. Bug Reports include provisions for any known workarounds or file replacem ents. Information is available for bugs existing in or fixed in Release 14SP2 or later. Information is not avail able for all bugs in earlier releases.

Access Bug Reports using y our MathWorks Account.

xPC Target™ Release Notes

About Functions Being Removed

This section lists functions removed or in the process of being removed. Functions typically go through several stages across multiple releases before being co mplete ly removed. This provides time for you to make adjustments to your code.

• Announcement – The release notes announce the planned removal, but

there are no functional changes; the function runs as it did before.

• Warning – When you run the function, it displays a warning message

indicating it will be removed in a future release; otherwise the function runs as it did before.

• Error – When you run the function, it produces an error. The error message

indicates the function was removed and suggests a replacement function, if one is available.

• Removal – When you run the function, it fails. The error message is the

standard message when MATLAB does not recognize an entry.

Functions might be in a stage for one or more releases before moving to another stage. Functions are listed in the Functions Being Removed sectio n only when they enter a new stage and their behavior changes. For example, if a function displayed a warning in the previous release and errors in this release, it appears on the list. If it continues to display a warn i ng , it does n ot appear on the list because there was no change between the releases.

Not all functions go through all stages. For example, a function’s impending removal might not be announced, but instead the first notification might be that the function displays a warning.

The release notes include actions you can take to mitigate the effects of a function’s removal, such as adapting your code to use a replacement function.

Version 4.3 (R2010a) xPC Target

This table summarizes what’s new in Version 4.3 (R2010a):

Version 4.3 (R2010a) xPC Target™

New Features and Changes

Yes Details belo

Version Compatibility Consideratio

Yes—Details labeled as Compatibility Considerations, below. See also Summary

• “Updated E

• “Support f

• “Support

• “New setx

• “.NETAP

• “New MPL

• “xPC Ta

• “Simul

• “xPC T

• “Mult

or Bus-off Failure Recovery in CAN Systems” on page 6

for Diamond Systems Athena II Board” on page 6

pcenv Property” on page 6

I xPC Target Framework Updates” on page 6

rget Demos” on page 7

ink SimState Support” on page 8

arget Compiler Support Changes” on page 8

iple Ethernet Cards of the Same Type” on page 8

Fixed Bugs and Known Problems

Bug Reports Includes fix

thernetRxBlock”onpage5

PATI EEPROM Write Block” on page 7

Related Documentation at Web Site

Printable Release Notes: PDF

Current product documentation

• “Recr

Upda

The E pac sam set

eate Target Boot Disk and Rebuild Applications” on page 9

ted Ethernet Rx Block

thernet Rx block has been updated to allow the filtering of Ethernet

kets. This change enables to use multiple Ethernet Rx blocks with the

edeviceID.However,youmustconfigure each block to filter a unique

of packets.

xPC Target™ Release Notes

The block dialog box now contains the tabs Rx and Filter. Rx contains the original block parameters. Filter contains the filter characteristics you choose for the received Ethernet frames.

Support for Bus-off Failure Recovery in CAN Systems

The following CAN setup blocks have b ee n updated to support the ability to recover from CAN bus failures.

• Softing CAN-AC2-PCI with SJA1000 Setup

• Softing CAN-AC2-104 with SJA1000 Setup

• Softing CAN-AC2-PCI with Philips SJA1000 FIFO Setup

• Softing CAN-AC2-104 with Philips SJA1000 FIFO Setup

Each block now has two additional parameters: Show bus-off status output and Bus-off recovery.

Support for Diamond Systems Athena II Board

The Diamond Systems Athena II board is now supported. Use the Prometheus/Athena blocks to access this board. For further informatio n, see Diamond Prometheus, Athena, and Athena II in the xPC Target™ I/O Reference.

New setxpcenv Property

The target application setxpcenv function has a new property,

EthernetIndex. Use this property to specify the index number of a particular

Ethernet card. Otherwise, the software assumes that there is only one Ethernet card available, and uses the first Ethernet card found.

.NET API xPC Target Framework Updates

The .NET API xPC Target Framework has the following updates:

•

MinimumTet and MaximumTet property added to the MathWorks.xPCTarget.FrameWork.xPCApplication class

Version 4.3 (R2010a) xPC Target™

• SaveParameterSet and Load Para meterSet methods added to the

MathWorks.xPCTarget.FrameWork.xPCParameters class

• TriggerSlope property added to the

MathWorks.xPCTarget.FrameWork.xPCScope class

New MPL PATI EEPROM Write Block

The new MPL PATI EEPROM Write block writes MPL boot code on the EEPROM. U se this block before running a model that contains MPL blocks. See the xPC Target MPL PATI EEPROM Write block for more information.

xPC Target Demos

This release contains the following new and changed demos:

• The .NET API xPC T arge t Framework has a new demo, located in

matlabroot\toolbox\rtw\targets\xpc\api\xPCFrameworkSamples\FileSystemBrowser

This is a C# application project developed with the Microsoft®Visual Studio executable to connect to target PC and a host PC. See the Readme.t xt file in the demo directory for instructions.

• The series of CAN I/O and CAN I/O FIFO demos using CAN_MESSAGE

and standard data types have been reorganized:

2008 IDE. It illustrates how to build a standalone W indows

- CAN (CAN_MESSAGE Data Types) — Contains demos that use

CAN_MESSAGE data types. Many of these demos are updated from previous releases to use CAN_MESSAGE data types instead of the standard data types. See “xPC Target CAN Library” in the xPC Target I/O Reference.

- CAN Legacy (Standard Data Types) — Contains demos that use

standard data types. These are the legacy demos from previous release s. See “xPC Target FIFO CAN Demonstrations for CAN-AC2-PCI and CAN-AC2-104 Boards” in the xPC Target I/O R eference.

• New Ethernet Rx block demo, Ethernet Rx Block Filtering.

xPC Target™ Release Notes

Simulink SimSta

The Simulink pro state(see“Savi Release Notes) simulating, on blocks. The so model on the ta behavior, the message like

Simulink is unable to acc ess the simulation state...

To prevent w SimState be box in the C your model

Reference

xPC Targe

The xPC T

• Intel

• Open Wa

ng and Restoring the Complete SimState” in the Simulink

. The xPC Target software now supports this behavior when

ahostPC,aSimulinkmodelthatcontainssomexPCTarget

ftware does not support this behavior when executing such a

rget PC. If an xPC Target block does not support the SimState

software generates a message. For example, you might get a

the following:

arning or error messages from blocks that do not support the

havior, clear the Save complete SimState in final state check

onfiguration Parameters Data Import/Export node for

. S ee “xPC Target Support and SimState” in the xPC Target I/O

for a list of blocks that do not support SimState behavior.

t Compiler Support Changes

arget software now supports the following compilers:

isual Fortran 11.0 comp i ler

tcom 1.8

te Support

duct supports the ability to save complete model simulation

xPC Tar

• Intel

• Open W

• Micr

Mult

If yo PC m iss

• Th

get software no longer supports the following compilers:

Visual Fortran 10.1 compiler

atcom 1.7

osoft Visual Studio 7.1

iple Ethernet Cards of the Same Type

ur target PC has multiple Ethernet cards of the same type, your target

ight have communication issues. Situations that might cause these

ues include:

e p resence of more than one Ethernet card on the target PC

Version 4.3 (R2010a) xPC Target™

• Updated xPC Target releases

Changes to the xPC Target kernel might cause these issues.

See“AreMultipleEthernetCardsintheTargetPCCausingCommunication Issues?” in the xPC Target User’s Guide for details on how to resolve this issue.

Compatibility Considerations

If you have an updated xPC Target releases, you might have this communication issue. See “Are Multiple Ethernet Cards in the Target PC Causing Communication Issues?” in the xPC Target User’s Guide for details on how to resolve this issue.

Recreate Target Boot Disk and Rebuild Applications

Compatibility Considerations

If you upgrade your xPC Target software from a previous versio n, you must recreate the target PC boot image and you must rebuild your xPC Target applications. See “xPC Target Boot O p tions” in the xPC Target Getting Started Guide.

xPC Target™ Release Notes

Version 4.2 (R2009b) xPC Target

This table summarizes what’s new in Version 4.2 (R2009b):

New Features and Changes

Yes Details belo

Version Compatibility Consideratio

Yes—Details labeled as Compatibility Considerations, below. See also Summary

• “Changed C

• “CAN Messa

• “New .NET

Applicat

• “Enhanc

Packets

• “Enhanc

• “Natio

• “Enhan

• “Supp

• “New P

ions that Interface with a Target PC” on page 12

ed UDP Send and Receive Block Allows Sending Variable Length

”onpage13

ed J1939 Support for Address Claiming” on page 13

nal Instruments PCI-6225 Support” on page 14

ced File Scopes” on page 14

ort to Load Parameter Sets from Target PC File System” on page 14

roperty for Target A pplication Object set Method” on page 15

Fixed Bugs and Known Problems

Bug Reports Includes fix

AN Block Messaging” on page 10

ge Warning Message No Longer Appears” on page 12

API xPC Target Framework Enables Users to Create

Related Documentation at Web Site

• “New x

• “xPC

• “Re

Cha

u can use the new CAN Pack and CAN Unpack blocks that are available

th your xPC T a rget license to perform message packing and message

PC Target Support for Multicore Processors” on page 15

Target Compiler Support” on page 16

Target Demos” on page 16

create Target Boot Disk and Rebuild Applications” on page 16

nged CAN Block Messaging

Version 4.2 (R2009b) xPC Target™

unpacking functions. Refer to the CAN Blocks Transition document for more information. Thes e new blocks add the following functionality:

• Consolidate multiple blocks to handle basic and advanced pack and

unpack functions, which include manually specified signals and CANdb file-specified signals.

• Improved compatibility with Vector Informatik CANdb files.

The message ha n d ling capability of the xPC Target CAN block library has changed. These b locks now use the CAN_MESSAGE data type. In previous releases, these blocks transferred data as 8 bytes in a double.

The Send and Receive blocks (includingFIFOWriteandReadblocks) for the Softing CAN-AC2-PCI with Philips SJA1000 CAN Controller and CAN-AC2-104 (PC/104) with Philips SJA1000 CAN Controller boards support the new message handling capability. The Send and Receive blocks for the Softing CAN-AC2 (ISA) with Philips PCA 82C200 CAN Controller and CAN-AC2 (ISA) with Intel 82527 CAN Controller support only the old message handling capability.

Compatibility Considerations

If you have models that use old CANDBC blocks from the xPC Target block library (available by typing warning message. (In the previous release, you saw this message when typing

xpclib; this message now appears only when typing xpcobsoletelib.) These

models will continue to work as before. You should update your models to use the new CAN Pack and the CAN Unpack blocks available from the xPC Target block library, as the old CAN Message blocks might be removed from a future release of the xPC Target product.

For i nformation on how you can identify obsolete blocks and transition to the new blocks, see CAN Blocks Transition.

The following blocks have been moved to the xPC T arget library of obsolete drivers:

• CAN Message Packing

• CAN Message Packing (CANdb)

xpcobsoletelib), you will see an obsolescence

xPC Target™ Release Notes

• CAN Message Filter

• CAN Message Unpacking

• CAN Message Unpacking (CANdb)

• CANDBC Translator

• FIFO Mode CAN Message

• Object Mode CAN Message

You can still access these d riverblocksbytypingthecommand

xpcobsoletelib at the MATLAB Command Window. Existing models that

use these drivers will still work. However, their support is not guaranteed for future releases. Do not use these driver blocks in new models. Instead, use the corresponding blocks contained in the CAN Message Handling blocks library.

CAN Message Warning Message No Longer Appears

In xPC Target Version 4.1 (R2009a), typing xpclib in the MATLAB Command Window caused a C AN _M ESSAG E warning. This warning now appears only when you type .

xpcobsoletelib.

New .NET API xPC Target Framework Enables Users to Create Applications that Interface with a Target PC

The xPC Target environment now provides a .NET API for the Microsoft .NET Framework. You can use this xPC Target API framework in any integrated development environment (IDE) that also supports the Microsoft .NET Framework environment. Use this API framework to create custom standalone applications (for example, Windows Forms applications running on a host PC that communicates with your target application running on a target PC). See “xPC Target API for M icrosoft .NET F ramework” in the xPC Target API Guide.

To access the types available from the xPC Target environment, reference this namespace in your application:

using MathWorks.xPCTarget.FrameWork;

The primary object is xPCTargetPC.

Version 4.2 (R2009b) xPC Target™

Enhanced UDP Sen Sending Variabl

The UDP library h following bloc

• UDP Receive

• UDP Send

The default b existing UDP

ks are updated:

ehavior of these blocks remains the same as before. Your

models will continue to work without modification.

Enhanced J1

The J1939 l J1939” in t

The follow

• J1939 Con

The foll new J193

• J1939 P

The fol

Board, Transp Max Re

ibrary has been enhanced to suppo rt address claiming. See “SAE

he xPC Target I/O Reference.

ing block is new:

troller Application

owing blocks have changed to take into account the capabilities of the

9 Controller Application block:

rotocol Stack — See the reference for the updated block parameters.

lowing parameters have been removed: TX CAN Board, RX CAN

TX CAN Port, RX CAN Port, Transport Protocol Enabled, ort Protocol Max Send (# of Fragments), Transport Protocol

ceive(#ofFragments).

e Length Packets

as been enhanced to support variable length packets. The

939 Support for Address Claim ing

d and Receive Block Allows

llowing parameters are new: Max CAN Message Receive (Per

The fo

le Time), Max CAN Message Transmit (Per Sample Time),

Samp

le Transport Protocol, Maximum Concurrent Sessions, Enable

Enab

ess Claiming.

Addr

• J193

9 Receive Message — See the reference for the updated block

ameters. The following parameters have been removed: J1939

par

tocol Stack Id, Node Address (0–255).

Pro

following parameter is new: CA ID.

The

xPC Target™ Release Notes

• J1939 Transmit Message — See the reference for the updated block

parameters. The following parameters have been removed: J1939 Protocol Stack Id, Node Address (0–255).

The following parameter is new: CA ID.

Compatibility Considerations

If you have existing models that use the updated J1939 blocks, note that you must now add the J1939 Controller Application block to your model. Y ou must then configure the J1939 Protocol Stack, J1939 Receive Message, and J1939 Transmit Mes sage blocks to correctly reference the controller application.

National Instruments PCI-6225 Support

xPC Target 4.2 now supports National Instruments PCI-6225 as part of its support for the National Instruments

M series data acquisition boards.

Enhanced File Scopes

xPC Target file scopes now support dynamic naming and multiple files. For further information, see:

• “Acquiring Signal Data into Multiple, Dynamically Named Files with

Scopes of Type File” in the xPC Target User’s Guide.

• See the

the

• See “Acquiring Signal Data into Multiple, Dynamically Named Files on the

Target PC” in the xPC Target User’s Guide.

DynamicFileName, FileName,andMaxWriteFileSize properties in

set method.

Support to Load Parameter Sets from Target PC File System

The xPC Target software now enables you to load parameter sets from the target PC file system. The Configuration P arameters dialog box has the following changes for xPC Target models. In the Application tunable parameter options section of the xPC Target options node, the following parameters are new:

• Load a parameter set from a file on the target file system

Version 4.2 (R2009b) xPC Target™

• File name

See “xPC Target Options” in the xPC Target Getting Started Guide.

New Property for Target Application Object set Method

The target application set method has a new property,

CommunicationTimeOut. Use this property to increase the

time-out value for the communication between the target and host PC.

New xPC Target Support for Multicore Processors

If your target PC has multicore processors, the xPC Target software can now take advantage of these processors for background tasks.

To enable this feature, do one of the following. By default, this feature is off.

• At the M ATLAB Command Window, type:

setxpcenv('MulticoreSupport','on')

• In the xPC Target Explorer Settings node, select the Multicore CPU

support check box.

If you use polling mode, enabling the multicore processor feature also removes the following restrictions. O ther restrictions still apply. (See “Polling Mode” in the xPC Target User’s Guide for further details on these restrictions.)

• Host-target communication is now available during the execution of the

target application.

• Target screen now updates during the execution of the target application.

• External interrupts are now allowed during the execution of the real-tim e

model. This does not mean that you can trigger your model with an external interrupt.

• File scopes can now log data into a file on the target PC.

xPC Target™ Release Notes

xPC Target Compi

The xPC Target so

The xPC Target s compiler.

xPC Target Dem

This release

• UDP demos

- Target to Ho

UDP blocks t

- Target to T

UDP blocks

• CAN I/O and

- CAN I/O - S

simple CA

- CAN I/O F

Demonst (FIFO) m

ftware now supports the Intel Visual Fortran 10.1 compiler.

oftware no longer supports the Intel Visual Fortran 9.1

contains the following new demos:

st Transmission using UDP — Demonstrates how to use

o send data from a target PC to a host PC.

arget T ransmission using UDP — Demonstrates how to use

to send data between two target PCs.

CAN I/O FIFO demos using CAN_MESSAGE data type

imple Use Case (with CAN_MESSAGE) — Demonstrates

N I/O communication using the Softing

IFOMode-SimpleUseCase(withCAN_MESSAGE)—

rates CAN I/O communication using the First In First Out

ode of the Softing CAN-AC2-PCI board.

ler Support

CAN-AC2-PCI board.

- CAN I/O

Functi the Fir The FI

Recre

ate Target B oot Disk and Rebuild Applications

FIFO Mode - Simple Use Case (with CAN_MESSAGE and

on Call Output) — Demonstrates CAN I/O communication using

st In First Out (FIFO) mode of the Softing CAN-AC2-PCI board.

FO Read block uses a function call output format.

Compatibility Considerations

u upgrade your xPC Target software from a previous version, you must

If yo

eate the target PC boot image and you must rebuild your xPC Target

recr

lications. See “xPC Target Boot Options” in the xPC Target Getting

app

rted Guide.

Sta

Version 4.1 (R2009a) xPC Target

This table summarizes what’s new in Version 4.1 (R2009a):

Version 4.1 (R2009a) xPC Target™

New Features and Changes

Yes Details belo

Version Compatibility Consideratio

Yes—Details labeled as Compatibility Considerations, below. See also Summary

New featur

• “Target P

• “New Func

page 18

• “J1939 L

• “Suppor

Board”

• “Suppo

MSerie

• “ Enha

• “xPC T

es and changes introduced in this version are

C Boot CD/DVD Creation Tool” on page 17

tion Summarizing Diagnostic Information for Targe t PC” on

ibrary Enhanced to Support Transport Protocol” on page 18

t for the GE Fanuc PCI-5565PIORC Shared/Reflective Memory

on page 19

rt for Counters and Incremental Encoders for National Instruments

s Boards” on page 19

nced Floating-Point Performance ” on page 19

argetDemos”onpage20

Fixed Bugs and Known Problems

Bug Reports Includes fix

Related Documentation at Web Site

• “xPC

• “CAN

• “Sav

• “Re

Tar

xP di

Target Compiler Support” on page 20

db Blocks” on page 20

e complete SimState in final state Check Box” on page 21

create Target Boot Disk and Rebuild Applications” on page 21

get PC Boot CD/DVD Creation Tool

C Target Explorer now enables you to create a target PC boot CD or DVD

rectly from the CD boot image file. In the previous release, you needed to

xPC Target™ Release Notes

usethird-partyCDwritingsoftwaretowriteISOimagefiles. See“Booting Target PCs from C D or DVD” in the xPC Target Getting Started Guide.

New Function Summarizing Diagnostic Information for Target PC

Anewfunction,getxpcinfo, has been added to help you capture diagnostic information for your xPC Target configuration. This function stores this information in a text file. You can send this text file to MathWorks Technical Support if you encounter host PC/target PC configuration problems.

J1939 Library Enhanced to Support Transport Protocol

The J1939 library has been enhanced to support transport protocol. See “SAE J1939” in the xPC Target I/O Reference.

The following block is new:

• J1939 Protocol Stack

The following blocks and their names have been updated.

• J1939 Database (CANdb) Setup

• J1939 Message Trigger

• J1939 Receive Message

• J1939 Transmit Message

Compatibility Considerations

This release updates the following J1939 blocks. The previous versions of these blocks are available by typing the command MATLAB Com mand Window. If you have existing models that contain these blocks, they will continue to work. It is recommended that you update your models with the new blocks and use them going forward.

• J1939 Database (CANdb) Setup

• J1939 Message Trigger

xpcobsoletelib in the

Version 4.1 (R2009a) xPC Target™

• J1939 Receive Message

• J1939 Transmit Message

In addition, the following blocks are obsolete:

• J1939 Pack

• J1939 Unpack

The J1939 Receive Message and J1939 Transmit Message now contain the functionality from these blocks.

Support for the GE Fanuc PCI-5565PIORC Shared/Reflective Memory Board

Support for the GE Fanuc PCI-5565PIORC shared/reflective memory board has been added. See “GE Fanuc (Formerly VMIC)” in the xPC Target I/O Reference.

Support for Counters and Incremental Encoders for National Instruments M Series Boards

Pulse generation, pulse width measurement, and incremental encoder blocks have been added for the following National Instruments boards:

• National Instruments PCI-6221

• National Instruments PCI-6229

• National Instruments PCI-6251

• National Instruments PCI-6259

• National Instruments PCI-6280

• National Instruments PCI-6281

• National Instruments PCI-6289

Enhanced Floating-Point Performance

The SSE2 (Intel Streaming SIMD Extensions 2) is now supported. It provides enhanced performance for floating-point operations.

xPC Target™ Release Notes

xPC Target Demos

This release con

tains the following new demos:

• Distributed Cl

PCI-5565 Board models commun

• J1939 I/O Usin

reception of J in a single ta

• AudioToneCo

control aud

xPC Target C

The xPC Tar 2008 SP1 an

The xPC Ta C/C++ 200

osed-Loop Control with GE

s — Demonstrates closed-loop control using two xPC Target

icating over shared memory.

g Transport Protocol — Demonstrates the transmission and

1939 data through a loopback connection of two CAN ports

rget PC.

ntrol Using General Standards Boards — Demonstrates tone

io processing using General S tan dards I/O boards.

ompiler Support

get software now supports the Microsoft Visual Studio C/C++

d Express Editi on compilers.

rget software no longer supports the Microsoft Visual Studio

5 Express Edition compiler.

Compatibility Considerations

For a com

http:/

plete list of the xPC Target supported and compatible compilers, se e:

/www.mathworks.com/support/compilers/current_release/

Fanuc Embedded Systems

CANdb B

The CA

n on a block, has the string

butto

g indicates that the blocks might be removed from a future release.

strin

his release, you can continue to use the CANdb blocks as usual. In

For t

tion, existing models will continue to work as expected.

addi

ou type

If y

ears. This string indicates that the CAN Message blocks might be removed

app

m a future release. xPC Target users can ignore this warning and continue

fro

use the CANdb blocks as usual.

locks

Ndb message block documentation, accessible by clicking the Help

Obsolete in the reference page titles. This

xpclib in the MATLAB Command Window, the following message

Version 4.1 (R2009a) xPC Target™

Warning: The CAN Message blocks are obsolete and may be removed from the product at a future date. If your model uses t hese blocks, refer to the CAN blocks transition page and update your model accordingly.

Save complete SimState in final state Check Box

The Simulink product now supports the ability to save complete model simulation state (see “Saving and Restoring the Complete SimState” in the Simulink Release Notes). This capability is not supported when simulating a Simulink m odel that contains xPC Target blocks. Doing so might generate warning or error messages. To prevent these messages, clear the Save

complete SimState in final state check box in the Configuration Parameters Data Import/Export nodeforyourmodel.

Recreate Target Boot Disk and Rebuild Applications

Compatibility Considerations

If you upgrade your xPC Target software from a previous version, you must recreate the target boot disk andyoumustrebuildyourxPCTarget applications. See “Booting Target PCs from Boot Floppy Disk” in the xPC Target Getting Started Guide.

xPC Target™ Release Notes

Version 4.0 (R2008b) xPC Target

This table summarizes what’s new in Version 4.0 (R2008b):

New Features and Changes

Yes Details belo

Version Compatibility Consideratio

Yes—Details labeled as Compatibility Considerations, below. See also Summary

New featur

• “Enhanced

on page 23

• “Support

• “Change

• “Config

• “Autom

• “CPU Ov

• “Enha

• “Expo

page 2

es and changes introduced in this version are

Support for Booting Target PCs Within Dedicated Network”

for Booting from CDs” on page 23

s to xpcbootdisk Function” on page 23

uration Parameter Dialog Box Update” on page 24

atic IRQ Selection” on page 24

erload Management” on page 24

nced Scopes” on page 24

rting Data from Scopes of Type File to MATLAB Workspace” on

Fixed Bugs and Known Problems

Bug Reports Includes fix

Related Documentation at Web Site

• “Sup

• “Enh

• “Sup

• “I/

• “Ch

• “T

• “x

port for Model-Based Ethernet Communications” on page 25

ancements to xPC Target C API” on page 25

port for Serial ATA (SATA) Drives ” on page 25

O Driver Support” on page 26

anges to xPC Target Library” on page 26

argetPCMonitorUpdate”onpage26

PC Target Demos” on page 26

Version 4.0 (R2008b) xPC Target™

• “Compilers” on page 27

• “Functions, Properties, and Arguments Being Removed” on page 27

• “Recreate Target Boot Disk and Rebuild Applications” on page 28

Enhanced Support for Booting Target PCs Within Dedicated Network

The ability to boot target PCs within dedicated networks has been enhanced in this release. These enhancements include:

• Full integration into the xPC Target Explorer environment.

• Multitarget support in a dedicated network environment with network

booting.

In the p rev ious release, you manually started the network boot server process, and the capability was limited to one target PC within the dedicated network group. In this release, the xPC Target Explorer environment now fully integrates this feature and supports multiple target PCs.

See “Booting Target PCs Within a Dedicated Network” in the “Installation and Configuration” chapter of the xPC Target Getting Started Gui de .Youcan continue to use the manual procedure as described in xPC Target Version 3.4, or use the method integrated into xPC Target Explorer.

Support for Booting from CDs

The xPC Target software now supports targetbootCDs.See“BootingTarget PCs from CD or DVD” in the “Installation and Configuration” chapter o f the xPC Target Getting Started Guide.

Changes to xpcbootdisk Function

The xpcboot disk function has been updated to allow for the creation of CD boot images. As a result, this function can now create 3.5-inch boot disks, CD boot images, and DOSLoader files. In previous releases, this function could create 3.5-inch boot disks and DOSLoader files.

xPC Target™ Release Notes

Configuration Parameter Dialog B ox Update

The Configuration Parameters dialog box has the following change for xPC Target models. In the Execution options section of the xPC Target options node, the PCI slot/ISA base address parameter has been change d to PCI slot (-1: autosearch) or ISA base address. Its purpose and use remains the same.

Automatic IRQ Selection

The Configuration Parameters dialog box has the following change for xPC Target models. In the Execution options section of the xPC Target options node, the Real-time interrupt source parameter now has an

Auto (PCI only) option. This option enables the xPC Target software to

automatically determine and use the IRQ number that the BIOS assigned. In previous releases, you had to manually choose an IRQ number for the real-time interrupt source. See “xPC Target Options” in the “Basic Tutorial” chapter of the xPC Target Getting Started Guide.

CPU Overload Management

The x PC Target software now supports the management of CPU overloads. See “Allow CPU Overloads” in the xPC Target User’s Guide.

Enhanced Scopes

The following enhancements have been made for scopes.

• Number of scopes of type host is now infinite.

• Number of signals that scopes of type host and file can log is now infinite.

Note, the number of allowed scopes of type target and the number of signals that scopes of type target can log re main 10. The number of scopes of type file remains eight.

Version 4.0 (R2008b) xPC Target™

Exporting Data from Scopes of Type File to MATLAB Workspace

From xPC Target Explorer, you can now export data from target PC files to the MAT LAB workspace. In previous releases, you had to use the file system objects to transfer data from the target PC to the host PC.

Support for Model-Based Ethernet Communications

Support for model-based Ethernet communications. See “Model-Based Ethernet Communications Support” in the xPC Target I/O Reference.

Enhancements to xPC Target C API

The follow ing enhancements have been made to the xPC Target C API:

• xPC Target C API is now threadsafe.

• The following functions and structures are new:

- fileinfo

- xPCGetNumSco pes

- xPCScGetNumS igna ls

- xPCGetScopeL ist

- xPCScGetSign alLi st

- xPCGetSessio nTim e

- xPCFSFileInf o

See “Functions, Properties, and Arguments Being Removed” on page 27 for additional notes.

Support for Serial ATA (SATA) Drives

Target PCs with serial ATA (SATA) drives are now supported. In previous releases, only IDE or parallel ATA (PATA) drives were supported. Your target PC must have a PATA or SATA drive to log data to the target PC file system. See “Working with Targ et PC Files and File Systems” in the xPC Target User’s Guide.

xPC Target™ Release Notes

I/O Driver Suppo

Support for the f boards. See “Nat

• National Instr

• National Inst

• National Ins

• National In

Changes to

When you do the MATLA In previo displaye

us releases, double-clicking this block opened a sublibrary that

d a list of xPC Targ et driver demos.

Target P

The tar slot nu commun addres

get PC monitor display has bee n updated to reflect the PCI bus and

mber of the Ethernet card in the target PC used for host PC-target PC

ications. In previous rele ases, the display showed the memory base

s and IRQ of the Ethernet card.

ollowing National Instruments M series data acquisition

ional Instruments” in the xPC Target I/O Reference.

uments PCI-6221

ruments PCI-6229

ruments PCI-6251

truments PCI-6259

truments PCI-6280

struments PCI-6281

struments PCI-6289

xPC Target Library

uble-click the xPC Target Driver Demos block, the Demos ta b in

B Help Navigator now opens, displaying the xPC Target demos.

C Monitor Update

xPC Ta

This

• Data

type

• Rea

per

• Fil

rget Demos

release contains the following new demos:

Logging With a File Scope — Illustrates data logging to scopes of

file.

l-Time Transmit and Receive over Ethernet — Demonstrates h ow to

form real-time communications over the Ethernet protocol.

tering on MAC Address — Demonstrates how to filter Ethernet packets

sed on MAC addresses.

Version 4.0 (R2008b) xPC Target™

• Filtering on EtherType — Demonstrates how to filter Ethernet packets

based on EtherTypes.

• IO Test with Diamond Systems MM-32-AT Board — Demonstrates a

simple analog and digital I/O loopback test using the Diamond Systems MM-32-AT (PC/104) board.

• IO Test with General Standards PMC-ADADIO Board — Demonstrates a

simple analog I/O loopback test using the General Standards PMC-ADADIO board.

• IO Test with National Instruments PCI-6070E Board — Demonstrates a

simple analog and digital I/O loopback test using the National Instruments PCI-6070E (E Series) board.

• IO Test with National Instruments PCI-6289 Board — Demonstrates a

simple analog and digital I/O loopback test using the National Instruments PCI-6289 (M Series) board.

• Master/Slave Synchronization with the GE Fanuc Embedded Systems

PCI-5565 — Demonstrates how to synchronize two xPC Target models with shared memory interrupts.

Compilers

The xPC Target product now supports the following additional compilers:

• Microsoft Visual C/C++ compiler Version 9.0

• Open Watcom C/C++ compiler Version 1.7

Compatibility Considerations

The xPC Target product no longer supports the Open Watcom C/C++ compiler Version 1.3.

Functions, Properties, and Arguments Being Removed

The following changes affect the xPC Target C API.

For more information about the process of removing functions, see “About Functionality Being Removed” in “What Is in the Release Notes” on page 3.

xPC Target™ Release Notes

Function Name

What Happens

UseThisInstead Compatibility

Considerations When you use Function

xPCGetScopes

Still runs

xPCGetScopeList

The xPCGetScopes

function continues to

run. However, use

xPCGetScopeList

instead.

xPCScGetSignals

Still runs

xPCScGetSignalList

The

xPCScGetSignals

function continues to

run. However, use

xPCScGetSignalList

instead.

Recreate Target Boot Disk and Rebuild Applications

Compatibility Considerations

Version 3.4 (R2008a) xPC Target

This table summarizes what’s new in Version 3.4 (R2008a):

Version 3.4 (R2008a) xPC Target™

New Features and Changes

Yes Details belo

Version Compatibility Consideratio

Yes—Details labeled as Compatibility Considerations, below. See also Summary

New featur

• “xPC Targ

Network”

• “xPC Targ

• “Change

• “xPC Tar

• “xPC Ta

on page

• “xPC Ta

• “Chan

es and changes introduced in this version are

et Now Supports Booting Target PCs Within a Dedicated

on page 30

et Explorer Enhancements” on pag e 30

s in xPC Target Configuration Parameters” on page 31

get Software Support for Vector CANape TCP Layer” on page 31

rget Now Supports Multidimensional Signals and Parameters”

rget Driver Authoring Tool” on page 31

ges to Simulink External Mode” on page 32

Fixed Bugs and Known Problems

Bug Reports Includes fix

Related Documentation at Web Site

• “Arbi

• “get

• “Int

• “xP

• “I/

• “x

trarily Sized Target Application (DLM) Files” on page 32

xpcpci Function Has New verbose Option” on page 32

el Visual Fortran 9.1 Support” on page 32

C Targ et Product Does Not Support Open Watcom 1.7” on page 33

CTargetMouse”onpage33

OBlocks”onpage33

PC Target Demos” on page 34

PC Target Device Drivers Guide” on page 35

xPC Target™ Release Notes

• “Recreate Target Boot Disk and Rebuild Applications” on page 35

• ““What’s T his?” Context-Sensitive Help Available for Simulink

Configuration Parameters Dialog” on page 35

xPC Target Now Suppor ts Booting Target PCs Within a Dedicated Network

You can now boot a target PC from a host PC within a dedicated network. In previous releases, y ou could only boot a target PC with a target boot disk. See “xPC Target Boot Options” in the xPC Target Getting Started Guide.

Associated with this feature, the function creates the xPC Target kernel to boot target PC over dedicated network.

xpcnetboot function was added. This

xPC Target Explorer Enhancements

xPC Target Explorer has the following enhancements:

• You can now drag a prebuilt target application, DLM, to a target PC icon.

If a connection does not already exist, xPC Target Explorer prompts you to create a connection to that target PC. See “Downloading and Running Target Applications on a Target PC” in the xPC Target Getting Started Guide.

• You can now start xPC Target Explorer from the Simulink model window

(Tools > Real-Time Workshop > xPC Target Explorer).

• If a scope does not exist, you can now drag a signal to a Host Scope, Target

Scope,orFileScopeicontocreateascopeofthattypeinxPCTarget Explorer. See “Adding Signals to Scopes” in the xPC Target User’s Guide.

• You can no w change the refresh rate of xPC Target Explorer. See “Menu

Bar and Toolbar Contents and Shortcut Keys” in the xPC Target Getting Started Guide.

• The xPC Target Explorer PCI Devices node now displays the subsystem

vendor and device IDs. In previous releases, this node displayed only system vendor and device IDs.

Version 3.4 (R2008a) xPC Target™

Changes in xPC Target Configuration Parameters

ThefollowingarechangestothexPCTargetoptionspaneoftheSimulink Configuration Parameters dialog box.

• New check box, Use default communication timeout,andanew

associated text entry field, Specify the communication timeout in

seconds. See “xPC Target Options” in the xPC Target Getting Started Guide.

• New IRQ options 3 and 4 available for the Real-time interrupt source

parameter.

xPC Target Software Support for Vector CANape TCP Layer

The interface between the x PC Target software and Vector CANape®software has been enhanced to support the Vector CANape TCP communication layer. This enhancement enables xPC Target to acquire signal data at the base sample rate of the model. If you have existing models that use earlier Vector CANape solutions, they should continue to be valid. See in the xPC Target I/O Reference.

xPC Target Now Supports Multidimensional Signals and Parameters

xPC Target now supports the logging and monitoring of multidimensional signals and the tuning of multidimensional parameters. In previous releases, the xPC Target software ignored multidimensional signals and parameters. If a target application contains a multidimensional signal or parameter:

The xPC Target Explorer Model Hierarchy now displays signals and parameters in column-major format. See “Signals and Parameters” in the xPC Target User’s Guide.

xPC Target Driver Authoring Tool

The xPC Target Driver Authoring Tool has been added to help with the creation of custom x PC Target device drivers. See “Creating Custom Drivers Using the xPC Target Driver Authoring Tool” in the xPC Target Device Drivers Guide.

xPC Target™ Release Notes

Changes to Simul

The following li

• You can now add s

you could add sc data to Simuli

• xPC Target can

previous rele

• Each Simulin

from the targ only the fir

Arbitraril

Arbitrari BootFlopp setting.

For Stand

ly-sized target application (DLM) files can now be loaded in

getxpcp

The getx base ad is usef

dress register information in the PCI device display. This information

ul if you to want to use a PCI-based parallel port.

mitations n o longer apply to Simulink external mode:

opes of only type target or file to the system when updating

nk external mode.

nowuploaddatatomorethan10Simulinkscopes. In

ases, xPC Target could upload up to 10 Simulink scopes.

k scope can now upload more than the first 10 input signals

et PC. In previous releases, each Simulink scope could upload

st 10 input signals from the target PC.

y Sized Target Application (DLM) Files

y a nd DOSLoader modes. These modes ignore the

Alone mode, you still must specify the target application size.

ci Function Has New verbose Option

pcpci

function has a new verbose option. This option includes the

ink External Mode

copes of type host to the system. In previous releases,

MaxModelSize

Intel

The xP for th Fort

Guid

Visual Fortran 9.1 Support

C Target product now supports the Intel Visual Fortran 9.1 compiler

e incorporation of F ortran code into Simulink models. See “Incorporating

ran Code into the xPC Target Environment” in the xPC Target User’s

e for details.

Compatibility Considerations

xPC Target product no longer supports the Intel Visual Fortran 9.0 and

The Com

paq

Visual Fortran Compiler Version 6.5 or later compilers.

Version 3.4 (R2008a) xPC Target™

xPC Target Produ

ct Does Not Support Open Watcom

1.7

xPC Target produ continues to be

xPC Target Mou

The xPC Target PC. The Targe

Appearance C

ct does not support O pen Watcom 1.7. Open Watcom 1.3

supported.

software no longer supports the use of a mouse on the target

tmousefield has been removed from the xP C Target Explorer

omponent pane.

I/O Blocks

Updated Condor Engineering ARINC blocks

The block m Condor Eng

• Condor En

• Condor D

Compati

these bl to the w

ask and documentation have been updated for the following

ineering ARINC blocks:

code ARINC 429 Words for Send

ecode ARINC 429 Words from Receive

bility Considerations. If you have existing models that contain

ocks, you should reev aluate the configuration parameters with regard

ay the blocks work with binary data.

New ASCII Decode Block for Serial Communication

The AS impro Decod

CII Decode V2 block has been added to the RS232 library to provide

ved performance over the ASCII Decode block. The original ASCII

e block will continue to be available.

Changes to the RS232 Library

PC Target RS232 library has been reorganized as follows:

The x

• The

drivers in

Obsolete category.

the

Conventional drivers (Obsolete) have been moved to

xPC Target™ Release Notes

• The drivers in V1.0 compatible have been moved to the Obsolete V 1.0

category.

Obsolete I/O Blocks

Compatibility Considerations. xPC Target has obsoleted the counter

blocks for the following boards. The xPC Target block library continues to support the noncounter blocks for these boards.

• Diamond Quartz-MM-5

• Diamond Quartz-MM-10

• Measurement Computing CIO-CTR05

• Measurement Computing PCI-CTR05

• National Instruments PC-TIO-10

• Real Time Devices DM6804

You can still access these d riverblocksbytypingthecommand

xpcobsoletelib at the MATLAB Command Window. Existing models that

use these drivers will still work. However, their support is not guaranteed for future releases. Do not use these driver blocks in new models. Instead, consider the following alte rna t iv e boards:

• National Instruments PCI-6601

• National Instruments PCI/PXI-6602

• MPL PATI

xPC Target Demos

Thefollowingdemoswereupdatedinthisreleasetouseparallelports,instead of Measurem ent Computing P CI-C TR05 boards, as interrupt sources.

•

xpcasynctrans

• xpcasyncbuffer

The following demos were u pd ated in this release to improve clarity:

Version 3.4 (R2008a) xPC Target™

• xpcserialbaseboardbinarysplit

• xpcserialbaseboardbinarytest

• xpcserialbinarysplit

• xpcserialbinarytest

xPCTargetDeviceDriversGuide

The xPC Target Device Drivers Guide is now part of the xPC Target documentation set in the MATLAB Help browser.

Recreate Target Boot Disk and Rebuild Applications

Compatibility Considerations

“What’s This?” Context-Sensitive Help Available for Simulink Configuration Parameters Dialog

R2008a introduces “What’s This?” context-sensitive help for parameters that appear in the Simulink Configuration Parameters dialog. This feature provides quick access to a detailed description of the parameters, saving you the time it would take to find the information in the Help browser.

To use the "What’s This?" help, do the following:

1 Placeyourcursoroverthelabelofaparameter.

2 Right-click. A What’s This? context menu appears.

For example, the following figure shows the What’s This? context menu appearing after a right-click on the Start time parameter in the Solver pane.

xPC Target™ Release Notes

3 Click What’s This? A context-sensitive help window appears showing a

description of the parameter.

Version 3.3 (R2007b) xPC Target

This table summarizes what’s new in Version 3.3 (R2007b):

Version 3.3 (R2007b) xPC Target™

New Features and Changes

Yes Details belo

Version Compatibility Consideratio

Yes—Details labeled as Compatibility Considerations, below. See also Summary

New featur

• “J1939 Sup

• “Shared I

• “I/O Driv

• “Commun

page 38

• “Suppo

• “DOSLo

• “CANd

• “xPC T

es and changes introduced in this version are

port” on page 37

nterrupts” on page 38

er Support” on page 38

ication Timeout Applies to all xPC Target API F unctions” on

rt for Working with Referenced Model Signals” on page 38

ader Mode” on page 38

b Enhancements” on page 39

argetDemos”onpage39

Fixed Bugs and Known Problems

Bug Reports Includes fix

Related Documentation at Web Site

• “Link

• “Rec

J19

To s blo

and Target Products Regrouped in New Start, Help, and Demos

gory” on page 39

Cate

reate Target Boot Disk and Rebuild Applications” on page 40

39 Support

upport SAE J1939, an automotive CAN protocol, xPC Target provides the

cks described in “SA E J1939” in the xPC Target I/O Reference.

xPC Target™ Release Notes

Shared Interrup

xPC Target now su the same interru Started Guide.

pt num b ers. See “xPC Target Options” in xPC Target Getting

I/O Driver Sup

xPC Target 3.3 boards:

• General Stan

Input)

• General Sta

Analog Outp

Both are de

Communic API Funct

The comm

xPCGetL

target P applie

oadTimeOut

C a nd the host PC. In previous releases, the communication timeout

d only to the initialization and loading of applications.

has new driver blocks, including support for the following

dards 24DSI12 (see General Standards 24DSI12 Analog

ndards PMC66-16AO16 (see General Standards 16AO16

ut)

scribed in the xPC Target I/O Reference.

ation Timeout Applies to all xPC Target

ions

unication timeout of the

pports shared interrupts to allow multiple boards to have

port

xPCSetLoadTimeOut and

functions now apply to all communications between the

Suppor

xPC Ta refer

xPC Ta

DOSL

You n

“Booting from a DOS Device” and “Embedded Option” in the xPC Target

See

r’s Guide.

Use

t for Working with Referenced Model Signals

rget now supports the monitoring and logging of signals from

enced models. See “Monitoring Signals from Referenced Models” in the

rget User’s G uide.

oader Mode

o longer need xPC Target Embedded Option™ to use DOSLoader Mode.

Version 3.3 (R2007b) xPC Target™

Compatibility Considerations

In prev io us releases, xPC TargetBox®, which uses xPC Target software, was able to use StandAlone Mode without xPC Target Embedded Option. Starting with this release, this is no longer possible. xPC T argetBox users must have xPC Target Embedded Option to use StandAlone Mode.

CANdb Enhancements

TheFIFOModeCANMessageandObjectModeCANMessageblockscapture the data received by the xPC Targe t CAN receive blocks for translation into CANdb format (see “Accessing CANdb DBC Format Databases from the xPC Target Environment” in the xPC Target I/O Reference).

xPC Target Demos

This release contains the following new demos:

•

xpccandb — Illustrates how to access CANdb DBC format databases from

xPC Target.

•

j1939example — Illustrates how to access use the J1939 blocks from xPC

Target.

Link and Target Products Regrouped in New Start, Help, and Demos Categor y

A new product category, Links and Targets, now contains all MathWorks software products that link, target, or cosimulate code.

Compatibility Considerations

This change impacts you in the following ways:

• Finding and viewing these products through the MATLAB Desktop Start

button a nd in the Help browser Contents and Demos panes.

• Using the

For more about this new product category, see “Demos and Help Browser Contents Now Include New Category for Links and Targets”, in the MATLAB Release Notes.

demo command to access the product demos.

xPC Target™ Release Notes

Recreate Target

Boot Disk and Rebuild Applications

Compatibility Considerations

If you upgrade y must recreate applications

Getting Start

our xPC Target software from a previous version, you

the target boot disk and you must rebuild your xPC Target

. See “Booting Target PCs from Boot Floppy Disk” in xPC Target

ed Guide.

Version 3.2 (R2007a) xPC Target

This table summarizes what’s new in Version 3.2 (R2007a):

Version 3.2 (R2007a) xPC Target™

New Features and Changes

Yes Details belo

Version Compatibility Consideratio

Yes Summary

New features and changes introduced in this version are

• “CANdb Blocks” on page 41

• “Selecting Signals Using Signal Labels Now Supported” on page 42

• “Folder Contents Display” on page 43

• “From xPC Target Block Now Accepts Cell Array of Signals” on page 43

• “Target Application Versions Now Checked” on page 43

• “Discrete States Logging Now Supported” on page 4 4

• “Microsoft

on page 44

• “Parallel Ports Now Supported” on page 44

• “I/O Driver Support” on page 44

• “Writing Device Drivers for xPC Target” on page 45

Visual C++ 2005 Express Edition Compiler Now Supported”

Fixed Bugs an d Known Problems

Bug Reports Includes fix

Related Documentation at Web Site

• “Recreate Target Boot Disk and Rebuild Applications” on page 45

CANdb Blocks

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 a nd 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.

xPC Target™ Release Notes

The new xpccandbcfifo model illustrates how to read the CANdb messages contained in

matlabroot\toolbox\rtw\targets\xpc\xpcdemos\demo.dbc.

Selecting Signals Using Signal Labels Now Supported

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.

Target Application Object Methods

xPC Target has the following new target application o bj ect functions:

•

getsignallabel

• getsignalidsfromlabel

API

xPC Target has the following new C API functions:

•

xPCGetSigIdxfromLabel

• xPCGetSigLabelWidth

• xPCGetSignalLabel

xPC Target has the following new COM API functions:

•

xPCTarget.GetSignalidsfromLabel

• xPCTarget.GetSignalLabel

xPC Target Explorer

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 by their block paths, right-click the Model Hierarchy node and select

All Signals

block path or signal label, respectively. For details, see “Signal Monitoring with xPC Targe t Explorer” in the xPC Target User’s Guide.

. Hovering over the signal label or block path displays the signal

View Only Labeled Signals. To view signals

View

Version 3.2 (R2007a) xPC Target™

Folder Contents

xPC Target has ne afolder.

The new C API str

•

xPCFSDirItem

• xPCFSDirStru

• xPCFSDirSiz

The new COM A API functio

•

xPCFileSy

• xPCFileSy

ns are:

From xPC T

w A PI functions and structures to display the contents of

ucture is

ctSize

PI structures are

stem.DirList

stem.GetDiskInfo

arget Block Now Accepts Cell Array of

Signals

The From of signa names, t can impr parame

xPC Target block now allows you to manually enter a cell array

ls (Signal nam e parameter) to read. Using a cell array of signal

he From xPC Target block will output a vector of signal values. This

ove the performance of the application. In previous releases, this

ter accepted only one signal.

Display

dirStruct. The new C API functions are:

FSDir and FSDiskInfo.ThenewCOM

Targe

You ca versi to do targ

In p the

t Application Versions Now Checked

nnot download a target application that was built from a different on of xPC Target than the xPC Target kernel on the target PC. Attempts wnload such a target application generates an error message on the

et PC monitor:

Mismatch between model an d kernel versions

revious releases, downloading a mismatched target application causes target PC to crash.

xPC Target™ Release Notes

Discrete States

xPC Target now su model. In previo “Signal Loggin

Microsoft Vis

pports the logging and monitoring of discrete states in a

us releases, you could not log and monitor discrete states (see

g” in the xPC Target User’s Guide).

ual C++ 2005 Express Edition Compiler

Now Supported

xPC T arget no compiler. Se Guide for det

Note If you u not suppor

Parallel

xPC Targe Ports” in generat

e interrupts using parallel ports.

I/O Dri

xPC Tar boards

w supports the Microsoft

e“HostPCRequirements”inthexPC Target Getting Started

ails.

se Microsoft Visual C++ 2005 Express Edition, xPC Target does

t the generation of COM objects from the xPC Target model.

Ports Now Supported

t n ow supports the parallel ports ofyourtargetPC(see“Parallel

the xPC Target I/O Reference). Thisfeaturealsoenablesyouto

ver Support

get 3.2 has new driver blocks, including support for the following

Logging Now Supported

Visual C++®2005 Express Edition

• Commt

422/4

• Meas

Meas PCI-

• Quan

• Nat

xPC

ech Fastcom 422/2-PCI-335 board (see “xPC Target RS-232 and

85 D riv ers (Composite)” in the xPC Target I/O Reference)

urement Computing™ PCI-DAS1002andPCI-DAC6703(see urement Computing PCI-DAS1002 and Measurement Computing

DAC6703 in the xPC Target I/O Reference)

ser Q4 (see Quanser Q4 in the xPC Target I/O Reference)

ional Instruments PCI-6528 (see National Instruments PCI-6528 in the

Target I/O Reference)

Version 3.2 (R2007a) xPC Target™

Writing Device Drivers for xPC Target

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.

Recreate Target Boot Disk and Rebuild Applications

Compatibility Considerations

If you upgrade your xPC Target software from a previous version, you must recreate the target boot disk andyoumustrebuildyourxPCTarget applications.

xPC Target™ Release Notes

Version 3.1 (R2006b) xPC Target

This table summarizes what’s new in Version 3.1 (R2006b):

New Features and Changes

Yes Details belo

Version Compatibility Consideratio

Yes Summary

New featur

• “Ethernet

• “xpctarg

• “Simulin

• “Micros

• “I/O Dri

• “Obsol

• “xPC Ta

• “Recr

Ether

In add supp

es and changes introduced in this version are

et.targets Enhancement” on page 46

k External Mode” on page 47

oft

ver Support” on page 47

ete Driver Blocks” on page 47

rget Demos” on page 47

eate Target Boot Disk and Rebuild Applications ” on page 48

net Chip Support

ition to the existing list of Ethernet chip families, xPC Target now also

orts the Intel I8254X fast Gigabit Ethernet chip family.

Chip Support” on page 46

Visual C++ Compiler Version 8.0” on page 47

Fixed Bugs an d Known Problems

Bug Reports Includes fix

Related Documentation at Web Site

Printable Release Notes: PDF

Current product documentation

arget.targets Enhancement

xpct

xpctarget.targets has a new property, FloppyDrive. This property

The

ows you to set the 3.5-inch drive letter to the one designated by your target

all

for example a: or b:.

PC,

Version 3.1 (R2006b) xPC Target™

Simulink Extern

The xPC Target Si previous releas access this fea

Microsoft Vis

xPC Target now

8.0.

I/O Driver S

xPC Target h EVM with Tar xPC Target This appli EVM throug communic

To access Command

Obsolet

application to a target PC that contains a DM642 EVM board.

cation can then communicate and exchange data with the DM642

ationwithxPCTarget.

these blocks, type

Window.

eDriverBlocks

mulink external mode is now enabled by default. In

es, you needed to type the

ture.

ual C++ Compiler Version 8.0

supports Microso ft Visual C++ Professional Edition Version

upport

as new driver blocks to support the Texas Instruments™ DM642

get for TI C6000™. This enables you to build and download an

h an Target for TI C6000 model that contains blocks that enable

al Mode

xpcextmodeenable command to

xpctexasinstrumentslib at the MATLAB

Compatibility Considerations

xPC Tar can st at the will s Do no

xPC T

The (

for (

get has obsoleted the driver blocks for the Sensoray 626 board. You

ill access these driver blocksbytypingthecommand

MATLAB Command Window. Existing models that use thes e drivers

till work. However, their presence is not guaranteed for future releases.

t use these driver blocks in new models.

xpcobsoletelib

arget Demos

xPC Target demo, Exchanging Data with the TI DM642 EVM

dm642xPC

TI C6000 counterpart, Using the PCI Bus to Exchange Data with xPC

000pcixpc

e DM642 EVM through an Target for TI C6000 model.

), has been added to the xpcdemos folder. With its Target

), this demo illustrates how xPC Target can exchang e data with

xPC Target™ Release Notes

Recreate Target

Boot Disk and Rebuild Applications

Compatibility Considerations

If you upgrade y must recreate applications

our xPC Target software from a previous version, you

the target boot disk and you must rebuild your xPC Target

Version 3.0 (R2006a+) xPC Target

This table summarizes what’s new in Version 3.0 (R2006a+):

Version 3.0 (R2006a+) xPC Target™

New Features and Changes

Yes Details belo

Version Compatibility Consideratio

Yes Summary

New features and changes introduced in this version are

• “EthernetCardSupport”onpage49

• “Intel Visual F ortran 9.0 Support” on page 50

• “To/From Blocks and Target PCs” on page 50

• “xpctarget.fs Method Enhancements” on page 50

• “Numerical Formats for xPC Target Scope Blocks” on page 51

• “Simulink External Mode and Tuning Parameters” on page 51

• “xPC Target Explorer” on page 51

• “I/O Device Driver Support” on page 51

• “xPC Target Mouse” on page 53

• “xPC Target Demos” on page 54

• “Recreate Target Boot Disk and Rebuild Applications” on page 54

Fixed Bugs an d Known Problems

Bug Reports Includes fix

Related Documentation at Web Site

Ethernet Card Support

In addition to the existing l ist of Ethernet cards, xPC Target now also supports

• National Semiconductor DP83815

• 3Com 3C90x

xPC Target™ Release Notes

Note xPC Target does not support the 3C905-TX board (PCI device ID 0x9050).

• Realtek RTL8139, RTL8139C, RTL8139C+ (tested and verified for Zonet

ZEN3200 and AOpen AON-325)

Intel Visual Fortran 9.0 Support

xPC Target now supports the Intel Visual Fortran 9.0 compiler for the incorporation of Fortran code into Simulink models. See “Incorporating Fortran Code into the xPC Target Environment” in the xPC Target User’s Guide for details.

To/From Blocks and Target PCs

The To/From xPC Target blocks n ow support multiple target PCs with the following additional parameters:

• Use default target PC

Selecting this o p t io n directs the To xPC Target block to communicate to the default target PC.

• Specify target name

If you deselect the Use default target PC check box, this field is displayed. Enter the name of the configured target PC.

Compatibility Considerations

In earlier releases, to run a model that contained From or To xPC Target blocks in a multiple target PC environment, you had to configure your model with the Simulation > Configuration Parameters menu (see “To xPC Target and From x PC Target Blocks” on page 82). You can now configure the blocks directly for this behavior; younolongerhavetoconfigurethemodel that contains these blocks.

xpctarget.fs Method Enhancements

The xpctarget.fs fopen method now supports the following operations:

Version 3.0 (R2006a+) xPC Target™

Option Description

'a'

'r+'

'w+'

'a+'

Openthefileforappendingtothefile.

Openthefileforreadingandwriting.

Openthefileforreadingandappendingtothefile.

Numerical Formats for xPC Target Scope Blocks

In previous releases, the format string for numerical format entries of scopes of type target had a limit of 100 characters for all the signals combined. You can now have 100 characters per signal in a format string (see “Entering Parameters for an xPC Target Scope B lock” in the xPC Target Getting Started Guide).

Simulink External Mode and Tuning Parameters

In previous releases, the act of tuning target application parameters in Simulink external mode displayed messages on the target PC monitor. These messages are no longer displayed when you tune parameters in Simulink external mode.

xPC Target Explorer

xPC Target Explorer has a new check box in the Settings node, Target PC is a 386/486. You must select this check box if your target P C has a

386 or 486 compatible processor. If your target PC has a hig her version of the Pentium chip or compatible processor, selecting this check box will slow the performance of your target PC.

I/O Device Driver Support

New Board Support

xPC Target 3.0 has new driver blocks, including support for the following boards:

• SBS

xPC Target™ Release Notes

- SBS IP-UD-IHV-16I80

- SBS IP-UD-IHV-8I160

- SBS PCI-40B

• MPL PATI (PowerPC

controlled Analog and Timing I/O Intelligence)

- MPL PATI Digital Input

- MPL PATI Digital Output

- MPL PATI Incremental Encoder

- MPL PATI Timebase Setup

Compatibility Considerations. The previous xPC Target release introduced

the MPL PATI PWM measure and MPL PATI PWM generate blocks. The time base for these blocks was hard coded to 20 MHz.

In xPC Target V ersion 3.0, yo u must u se the ne w MPL PATI Timebase S etup block with these blocks to select the 20 MHz frequency for the time base. If youdonotusetheMPLPATITimebaseSetupblockwiththeMPLPATI PWM measure or MPL PATI PWM generate blocks, the TCR1 time base defaults to 1.25 MHz.

Manufacturer

MPL

National Instruments

Updated Driver Support

The drivers for the following blocks have been added or updated:

Change

• The MPL PATI PWM generate block has been updated to support

armed input.

The following blocks were added:

• National Instruments PCI/PXI-6711 Pulse Generation

• National Instruments PCI/PXI-6711 Pulse Width/Period

Measurement

• National Instruments PCI/PXI-6713 Pulse Generation

• National Instruments PCI/PXI-6713 Pulse Width/Period

Measurement

Version 3.0 (R2006a+) xPC Target™

Manufacturer

Change

• National Instruments PCI/PXI-6731 Pulse Generation

• National Instruments PCI/PXI-6731 Pulse Width/Period

Measurement

• National Instruments PCI/PXI-6733 Pulse Generation

• National Instruments PCI/PXI-6733 Pulse Width/Period

Measurement

Utilities Library

The xPC Target library has a new sublibrary, Utilities. It contains blocks that provide generic functions. The following blocks were added to the Utilities sublibrary.

• Byte Packing

• Byte Unpacking

• Bit Packing

• Bit Unpacking

Miscellaneous Library

The following blocks were added to the Miscellaneous library. These blocks provide counter and delta blocks for the Pentium chip.

• Pentium Time Stamp Counter

• Time Stamp Delta

xPC Target Mouse

Limitation

The mouse does not work on the target PC. Setting Target mouse to any setting on the xPC Target Explorer Configuration > Appearance node has no affect.

xPC Target™ Release Notes

xPC Target Demos

The VMIC5565 .md illustrates sen

demo has been added to the xpcdemos folder. This demo

ding and receiving data over the VMIC shared memory.

Recreate Targ

et Boot Disk and Rebuild Applications

Compatibility Considerations

If you upgrad must recreat applicatio

e your xPC Target softw are from a previous version, you

e the target boot disk and you must rebuild your xPC Target

ns.

Version 2.9 (R2006a) xPC Target

This table summarizes what’s new in Version 2.9 (R2006a):

Version 2.9 (R2006a) xPC Target™

New Features and Changes

Yes Details belo

Version Compatibility Consideratio

Yes Summary

New features and changes introduced in this version are

• “xPC Target Explorer” on page 55

• “xPC Target Options Pane” on page 56

• “Simulink External Mode” on page 56

• “MATLAB Compiler Support” on page 56

• “Open Watcom Compiler Support” on page 56

• “xPC Target C API” on page 56

• “Support for Model Referencing” on page 57

• “I/O Device Driver Support” on page 57

• “Recreate Target Boot Disk and Rebuild Applications” on page 58

Fixed Bugs an d Known Problems

Bug Reports Includes fix

Related Documentation at Web Site

xPC Target Explorer

xPC Target Explorer has the following enhancements:

• The ability to save an xPC Target application session, including scope

and target PC settings, to a s tandard MATLAB MAT-file on the host PC (see “Saving and Reloading xPC Target Application Sessions” in the xPC Target User’s Guide)

• The ability to copy (with drag and drop) a signal from one scope to another

• The ability to remember resized and relocated xPC Target Explorer

windows

• Enhanced file system support manipulation

xPC Target™ Release Notes

xPC Target Options Pane

ThexPCTargetOptionspane(see“xPCTargetOptions”inthexPC Target Getting Started Guide) has a new check box, Include model hierarchy

on the target application. Selecting this check box includes the model hierarchy as part of the target application.

Simulink External Mode

xPC Target support for Simulink externalmodehasthefollowing enhancement and change:

• xPC Target now supports uploading real-time data to Simulink scopes

when using Simulink external mode (see “Signal Tracing with Simulink External Mode” in the xPC Target User’s Guide).

• xPC Target now supports Simulink external mode for all target PCs, not

just the default one.

MATLAB Compiler Support

xPC Target now supports the MATLAB Compiler. With this capability, youcanusetheMATLABCompilertotakeM-filesasinputandgenerate redistributable, stand-alone applications that include xPC Target functionality.

Open Watcom Compiler Support

xPC Target now supports Open Watcom C/C++ Version 1.3. It no longer supports Watcom compiler C/C++ Version 11.0.

xPC Target C API

To better support target PC file systems, the xPC Target C API has been enhanced:

• The

diskinfo data structure was added. It contains information, such as

FAT type and number of clusters, for target PC file system disks.

xPCFSDiskInfo function was added. It returns information, such as

FAT type and number of clusters, for target PC file system disks.

Version 2.9 (R2006a) xPC Target™

Support for Model Referencing

If you download a target application to a target PC, and that target application was built from a model that contains referenced models, you can now tune the parameters of the top level of the model. The referenced models themselves must have Inline Parameters on, as in previous releases.

I/O Device Driver Support

New Board Support

xPC Target 2.9 has new driver blocks, including support for the following boards:

• Contec

- PIO-32/32F(PCI)

- PIO- 32/32L(PCI)H

- PI-64L(PCI)H

- PO-64L(PCI)H

- CNT32-8M(PCI)

• MPL PATI (PowerPC controlled Analog and Timing I/O Intelligence)

Updated Driver Support

The drivers for the following have been updated:

Manufacturer

Diamond Systems

National Instruments

Change

• The Diamond Prometheus driver has been updated

to also support the Diamond Athena board.

• The Emerald-MM block now lists the baud rates

with an contains the high-speed crystal option.

The PCI-MIO-16XE-50 blocks have been renamed to PCI-6911E.

HS labeltoindicatetherateiftheboard

xPC Target™ Release Notes

Manufacturer

United Electronic Industries (UEI)

Change

The PD2-MF and PDX1-MF 12-bit series blocks have been enhanced to support 3 MHz in addition to 1.25 MHz.

Utility Sublibraries

xPC Target has added the following utility sublibraries:

Sublibrary

Digital Input/Utilities, Digital Output/Utilities

Incremental Encoder/Utilities/Rollover

Description

Contains the following new blocks:

• Digital IO bit-packing — Constructs data

frames for digi t al I/O blocks

• Digital IO bit-unpacking — Extracts data

frames for digi t al I/O blocks

Contains the following new blocks:

• Rollover Counter — Sample rollover counter

block

• Extended Counter — Sample extended

counter block

Recreate Target Boot Disk and Rebuild Applications

Compatibility Considerations

If you upgrade your xPC Target software from a previous version, you must recreate the target boot disk andyoumustrebuildyourxPCTarget applications.

Version 2.8 (R14SP3) xPC Target

This table summarizes what’s new in Version 2.8 (R14SP3):

Version 2.8 (R14SP3) xPC Target™

New Features and Changes

Yes Details belo

Version Compatibility Consideratio

Yes Summary

New features and changes introduced in this version are

• “xPC Target Explorer” on page 59

• “Fixed-Point Support” on page 59

• “Target PC Environments” on page 60

• “New Supplied Ethernet Card” on page 60

• “I/O Device Driver Support” on page 60

• “Recreate Target Boot Disk and Rebuild Applications” on page 60

Fixed Bugs an d Known Problems

Bug Reports Includes fix

Related Documentation at Web Site

xPC Target Explorer

The xPC Target Explorer has the following enhancements:

• Apply and Revert buttons have been added to the bottom of many panes.

- Apply — Click this button to apply changes.

- Revert —UsetheRevert buttontoretrieveoldvalues.

• Target PC nodes now have a PCI D evices node. This lists all PCI device s

detected on the target PC.

Fixed-Point Support

xPC Target now supports Simulink fixed-point data. This enables you to

• Monitor and log signals of fixed-point data types

• Tune parameters of fixed-point data types

xPC Target™ Release Notes

Target PC Environments

This release now allows you to set up multiple target PCs from the command line. Se e the “Working with Target PC Environments” in the xPC Target User’s Guide for details.

New Supplied Ethernet Card

xPC Target now ships with the Intel PRO/100 M card.

I/O Device Driver Support

xPC Target 2.8 has new driver blocks, including support for the following boards:

• Condor

databus protocol

• National Instruments

QPCI/PCI-1553 to support the MIL-STD-1553 military avionics

- PCI/PXI-6731, PCI/PXI-6711

- PCI/PXI-6733, PCI/PXI-6713

Compatibility Considerations

The xPC Target MIL-STD-1553 drivers have the following limitations:

• Condor PCI/QPCI-1553 RT Initialize block — You cannot change the values

of the following parameters at run-time:

- Initial status

- Initial BIT word

- Inhibit terminal flag

Recreate Target Boot Disk and Rebuild Applications

Compatibility Considerations

If you upgrade your xPC Target software from a previous version, you must recreate the target boot disk andyoumustrebuildyourxPCTarget applications.

Version 2.7.2 (R14SP2) xPC Target

This table summarizes what’s new in Version 2.7.2 (R14SP2):

Version 2.7.2 (R14SP2) xPC Target™

New Features and Changes

Yes Details belo

Version Compatibility Consideratio

Yes Summary

New features and changes introduced in this version are

• “xPC Target Explorer” on page 61

• “I/O Device Driver Support” on page 61

• “Recreate Target Boot Disk and Rebuild Applications” on page 62

Fixed Bugs an d Known Problems

Bug Reports Includes fix

Related Documentation at Web Site

xPC Target Explorer

xPC Target Explorer has been enhanced and now fully supports the following:

• Inlined parameters

• Monitoring of test-pointed Stateflow

states

I/O Device Driver Support

xPC Target 2.7.2 has new driver blocks, including support for the following board:

Manufacturer Board

onal Instruments

Nati

The drivers for the following boards have been updated:

Manufacturer Board

Contec Contec DA12-16(PCI)

Measurement Computing CIO-DAS16JR/16

PXI-6052E

xPC Target™ Release Notes

Recreate Target

Boot Disk and Rebuild Applications

Compatibility Considerations

If you upgrade y must recreate applications

our xPC Target software from a previous version, you

the target boot disk and you must rebuild your xPC Target

Version 2 .7 (R14SP1+) xPC Target

This table summarizes what’s new in Version 2.7 (R14SP1+):

Version 2.7 (R14SP1+) xPC Target™

New Features and Changes

Yes Details belo

Version Compatibility Consideratio

Yes Summary

New features and changes introduced in this version are

• “xPC Target Explorer” on page 63

• “Default Target PC” on page 64

• “To/From Blocks and Default Target PCs” on page 64

• “Stateflow State Test Points” on page 65

• “xPC Target COM API” on page 65

• “I/O Device Driver Support” on page 66

• “xPC Target Demos” on page 66

• “Recreate Target Boot Disk and Rebuild Applications” on page 67

Fixed Bugs an d Known Problems

Fixed Bugs

Related Documentation at Web Site

xPC Target Explorer

xPC Target Explorer has been enhanced and now fully supports the following:

• Scopes of type file

• Access to target PC file systems

• Ability to e xport 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.

xPC Target™ Release Notes

Compatibility Considerations

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.

Default Target PC

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 b uild process. External mode is supporte d only with the default target PC. See the xPC Target G etting Started Guide for details.

To/From Blocks and Default Target PCs

In previous releases, you could build models that contained From/To xPC Target blocks without setting the Real-Time Workshop system target file to 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 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.

xpctarget.tlc. To accommodate the use of multiple

xpctarget.tlc. You access this dialog from

parameter RTW

Version 2.7 (R14SP1+) xPC Target™

Compatibility Considerations

To use existing models with these blocks, you must set the Real-Time Workshop parameter RTW system target file to running them. Note that the

xpcsliface command behavior does not change.

xpctarget.tlc before

Stateflow State Test Points

xPC Target now supports the monitoring of test-pointed Stateflow states. ThisisavailableonlythroughtheMATLABcommand-lineinterface. Itisnot yet supported by xPC Target Explorer or xPC Target Scope blocks.

xPC Target COM API

To support target PC file systems, the xPC Target COM API has been enhanced to support a new object, the following methods were added:

•

• CloseFile

xPCFileSystem. To support this object,

• GetFileSize

• Init

• MKDIR

• OpenFile

• PWD

• ReadFile

• RemoveFile

• RMDIR

• ScGetFileName

• ScGetWriteMode

• ScGetWriteSize

• ScSetFileName

• ScSetWriteMode

xPC Target™ Release Notes

• ScSetWriteSize

• WriteFile

I/O Device Driver Support

xPC Target 2.7 has new driver blocks, including support for the following boards:

Manufacturer Board

National Instruments

Adlink 6208A

Commtech Fastcom 422/2-PCI

UEI

Quatech

The drivers for the following boards have been updated:

Manufacturer Boards

General Standards ADADIO

Measurement Computing PCI-DAS1602/12 D/A

Sensoray

In addition, the RS-232 sublibrary has changed:

• FIFO read and write blocks have been added to support all RS-232

sublibrary composite drivers.

PCI/PXI-6602

PD2-DIO-64 series, PDL-DIO-64 series, PDXI-DIO-64 series

DSCP-200/300

626

xPC Target Demos

The following demos have bee n added to the xpcdemos folder:

•

udphost.mdl

• udphostpost.mdl

• udpsendreceiveA.mdl

Version 2.7 (R14SP1+) xPC Target™

• udpsendreceiveB.mdl

• udptarget.mdl

• udpxpctargetsteam.m

• xpcserialasciisplit.mdl

• xpcserialasciitest.mdl

• xpcserialbinarysplit.mdl

• xpcserialbinarytest.mdl

Recreate Target Boot Disk and Rebuild Applications

Compatibility Considerations

If you upgrade your xPC Target software from a previous version, you must recreate the target boot disk andyoumustrebuildyourxPCTarget applications.

xPC Target™ Release Notes

Version 2.6.1 (R14SP1) xPC Target

This table summarizes what’s new in Version 2.6.1 (R14SP1):

New Features and Changes

Yes Details belo

Version Compatibility Consideratio

Yes Summary

New features and changes introduced in this version are

• “xPC Target Explorer” on page 68

• “File Systems and Multiple Targets” on page 69

• “xPC Target Support for Vector CANape (Beta)” on page 69

• “Changed Source Dialog Box Behavior” on page 69

• “Dials & Gauges Blockset” on page 70

• “Watcom C/C++ Version 10.6 Compiler” on page 70

• “Recreate Target Boot Disk and Rebuild Applications” on page 70

Fixed Bugs an d Known Problems

Fixed Bugs

Related Documentation at Web Site

xPC Target Explorer

This release includes the first officially supported version of the xPC Target Explorer. It is a graphical user interface for xPC Target. It provides a single pointofcontactforalmostallxPCTargetinteractions,including

• Configure the host PC for xPC Target

• Add and configure target PCs for xPC Target

• Create boot disks for particular target PCs

• Connect the target PCs for your xPC Target system to the host PC

• Download a prebuilt target application,

• Build a target application for a specific target PC

• Start and stop the application that has been downloaded to the target

.dlm,toatargetPC

Version 2.6.1 (R14SP1) xPC Target™

• Add scopes of type host, target, and file to the downloaded target application

• Monitor signals

• Add and remove signals to the xPC Target scopes

• Start and stop scopes

• Adjust parameter values for the signals while the target application is

running

The xPC Target Explorer GUI runs on your xPC Target h ost machine.

Use xPC Target Explorer to perform xPC Target activities. This tool encompasses the functionality of

xpctgscope. Note that in a future release, xpcrctool, xpcscope,and xpctgscope will be obsoleted.

See the xPC Target Getting Started Guide and the xPC Target User’s Guide for details on xPC Target Explorer.

xpcsetup, xpcrctool, xpcscope,and

File Systems and Multiple Targets

The xPC Target file system and FTP feature now support the concept of multiple targets. You can now specify which target PC to work with when using the file s ystem or file object. In support of this, the

xpctarget.ftp constructors have changed to support an interface similar to

that used by the

xpctarget.xpc constructor.

xpctarget.fs and

xPC Target Support for Vector CANape (Beta)

xPC Target now enables your target application data to be accessed by a Vector CANape system, Version 5.00.20 and 5.00.30. See the Vector CANape chapter in the xPC Target I/O Reference for further details.

This release is a B eta version of this support. The MathWorks encourages you to use this new feature and provide feedback.

Changed Source Dialog Box Behavior

The behavior of source block dialog boxes has changed.

xPC Target™ Release Notes

Compatibility Considerations

The behavior of source block dialog boxes has changed as follows.

• Opening a dialog box for a source block causes Simulink to pause. W hile

Simulink is paused, you can edit the parameter values. You must close the dialog b ox to h av e the changes take effect and allow Simulink to continue.

In particular, hardware input blocks in the xPC Target library (blocks that acquire data from hardware) are affected by this changed.

• The xPC Target Explorer no longer supports changing tunable source block

parameters while a simulation is running. You will find all such parameter fields disabled while a simulation is running.

Dials & Gauges Blockset

References to the Dials & Gauges Blockset have been removed from the xPC Target documentation. As a result, the xPC Target documentation no longer describes the use of the Dials & Gauges Blockset. In particular, the “Graphical U ser Interfaces” chapter of the xPC T arget User’s G uide no longer describes this blockset.

Additionally, relevant xPC Target demos now use only the Gauges Blockset™.

Watcom C/C++ Version 10.6 Compiler

Compatibility Considerations

xPC Target no longer supports the Watcom C/C++ Version 10.6 compiler. xPC Target only supports Watcom C/C++ Version 11.0 and M icrosoft compilers.

Recreate Target Boot Disk and Rebuild Applications

Compatibility Considerations

If you upgrade your xPC Target software from a previous version, you must recreate the target boot disk andyoumustrebuildyourxPCTarget applications.

Version 2.6 (R14+) xPC Target

This table summarizes what’s new in Version 2.6 (R14+):

Version 2.6 (R14+) xPC Target™

New Features and Changes

Yes Details belo

Version Compatibility Consideratio

Yes Summary

New features and changes introduced in this version are

• “xPC Target Explorer (Beta)” on page 71

• “Real-Time Workshop

• “CAN Library Link Change” on page 72

• “xPCGetSignals API Function” on page 72

• “I/O Device Driver Support” on page 73

• “xPC Target Support for Vector CANape (Beta)” on page 73

• “Recreate Target Boot Disk and Rebuild Applications” on page 74

Fixed Bugs an d Known Problems

Fixed Bugs

Embedded Coder Support” on page 72

Related Documentation at Web Site

xPC Target Explorer ( Beta)

This release includes a Beta version of the xPC Target Explorer. It is a graphical user interface for xPC Target. It provides a single point of contact for almost all xPC Target interactions, including

• Configure the host PC for xPC Target

• Add and configure target PCs for xPC Target

• Create boot disks for particular target PCs

• Connect the target PCs for your xPC Target system to the host PC

• Download a prebuilt target application,

• Build a target application for a specific target PC

• Start and stop the application that has been downloaded to the target

.dlm,toatargetPC

xPC Target™ Release Notes

• Add scopes of type host, target, and file to the downloaded target application

• Add and remove signals to the xPC Target scopes

• Start and stop scopes

• Adjust parameter values for the signals while the target application is

running

The xPC Target Explorer GUI runs on your xPC Target h ost machine.

Use xPC Target Explorer to perform xPC Target activities. This tool encompasses the functionality of both Beta release of the xPC Target Explorer. The MathWorks encourages you to use this new interface and provide feedback.

See the xPC Target Getting Started Guide and xPC Target User’s G uide for details on xPC Target Explorer.

xpcsetup and xpcrctool. Thisisthe

Real-Time Workshop Embedded Coder Suppor t

xPC Target now supports the Real-Time Workshop®Embedded Coder™. This feature requires the Real-Time Workshop Embedded Coder.

Compatibility Considerations

xPC Target only supports Real-Time Workshop Embedded Coder for M icrosoft compilers. It does not support Real-Time Workshop Embedded Coder for Watcom compilers.

CAN Library Link Change

The mechanism used to link the external CAN libraries has changed. It is no longer necessary to select a CAN library via a list in be able to use CAN blocks in a model. Instead the link is set up automatically. xPC Target will ignore user-defined settings.

xpcsetup or xpcexplr to

xPCGetSignals API Function

The xPCGetSignals API function can now return the values of a vector of up to 1000 signals as fast as it can acquire them. This was previously limited to 10 signals.

Version 2.6 (R14+) xPC Target™

I/O Device Drive

xPC Target 2.6 ha boards:

• Condor Enginee

- CEI-520, CEI-

Contact your M for the board

• Contec

s new driver blocks, including support for the following

ring (for the aerospace industry)

520A

athWorks repres entative if you are interested in support

s C EI-620, CEI-820, and CEI-820TX.

- ADI12-16

• National In

- PCI-6601 A

- PCI/PXI-6

• Sensoray

- Sensoray

The foll

• Measure

owing drivers have been updated:

struments

rmed Pulse Generation

602 Armed Pulse Generation

626

ment Computing PCI-CTR05

rSupport

• Sensor

• Diamon

ay 526 Encoder Input block

d Systems MM-32-AT Frame Analog Input block

Compatibility Considerations

You ca Engi

xPC T

xPC Vec cha

nnot use the Watcom compiler for models that contain Condor neering blocks. Use a M icrosoft compiler instead.

arget Support for Vector CANape (Beta)

Target now enables your target application data to be accessed by a

tor CANape system, V ersion 5.00.20 and 5.00.30. See the Vector CANape

pter in the xPC Target I/O Reference for further details.

xPC Target™ Release Notes

Recreate Target

Boot Disk and Rebuild Applications

Compatibility Considerations

If you upgrade y must recreate applications

our xPC Target software from a previous version, you

the target boot disk and you must rebuild your xPC Target

Version 2.5 (R14) xPC Target

This table summarizes what’s new in Version 2.5 (R14):

Version 2.5 (R14) xPC Target™

New Features and Changes

Yes Details belo

Version Compatibility Consideratio

Yes Summary

New feature

• “xPC Targe

• “Multiple

• “Real-Ti

• “Numeric

• “C and CO

• “Suppor

• “Run-Ti

• “Inlin

• “Confi

• “RS-2

• “Numb

s a nd changes introduced in this version are

me Data Acquisition to Files on Target PC” on page 77

t for Model Referencing” on page 79

me Parameters” on page 79

ed Parameters” o n page 80

guration Parameters xPC TargetOptionsDialog”onpage80

32, RS-422, and RS-485 Add-on Board Drivers” on page 80

er of Available UDP Bloc ks Increase” on page 80

Fixed Bugs an d Known Problems

Fixed Bugs Open Bugs

t Explorer (Beta)” on page 76

Targets” on page 77

Precision in Host/Target Communications” on page 78

MAPI”onpage78

Related Documentation at Web Site

• “xPC

• “To x

• “xP

• “I/

• “R

Target Methods and Parameters” on page 80

Target Scopes” on page 81

PC Target and From xPC Target Blocks” on page 82

C Target From File Block” on page 82

O Device Driver Support” on page 82

ecreate Target Boot Disk and Rebuild Applications” on page 86

xPC Target™ Release Notes

xPC Target Explo

This release inc graphical user i for almost all x

• Configure the

• Add and config

• Create boot d

• Connect the t

• Download a p

• Build a targ

• Start and s

• Add scopes

• Add and re

• Start and

• Adjust p

running

The xPC T

ludes a Beta version of the xPC Target Explorer. It is a nterface for xPC Target. It provides a single point of contact

PC Target interactions, including

host PC for xPC Target

ure target PCs for xPC Target

isks for particular target PCs

arget PCs for your xPC Target system to the host PC

rebuilttargetapplication,

et application for a specific target PC

top the application that has been downloaded to the target

of type host, target, and file to the downloaded target application

move signals to the xPC Target scopes

stop scopes

arameter values for the signals while the target application is

arget E xp lo rer GUI runs on your xPC Target host machine.

rer (Beta)

.dlm,toatargetPC

You can perfor Explo provi

See th

use xPC Target Explorer or your usual xPC Target interfaces to

m xPC Target activities. This is the Beta release of the xPC Target

rer. The MathWorks encourages you to use this new interface and

de feedback.

e xPC Target U ser’s Guide for details on xPC Target Explorer.

Registering Active X Controls

ciated with the xPC Target Explorer is a new script,

Asso

ou are running MATLAB remotely (accessing MATLAB over the network),

If y

this script to register Active X controls before you start xPC Target

run

lorer.

Exp

xpc_register_ocx.

Version 2.5 (R14) xPC Target™

Multiple Target

xPC Target now su single host. In c accept the diff

Target User’s G

pports concurrent use of more than one target from a

onjunction with this, the

erent communication type s (

uide for detai ls.

Real-Time Dat

xPC Target su you to acquir Using the new to the h ost t to have a tar target PC fi

To support

• Afilesys

• FTP and fi

PC file sy

• Basic fi

pports a new scope type of

esignaldatainrealtimeandstoreittoafileonthetargetPC.

file objects and methods, you can then retrieve the file data

o plot or otherwise analyze the signal data. You do not need

get application loaded on the target PC before accessing the

le system.

this new capability, xPC Target now also provides

tem on the target PC

le system objects that enable you to work with files on the target

stem

le transfer methods

le system methods

xpc method has been updated to

'RS232' or 'TCPIP'). See the xPC

a Acquisition to Files on Target PC

file. This new scope type enables

• File sy

This fu

See th

• xPC Ta

Sign and F

• xPC T

• xPC

stem API

nctionality is limited to file systems of type FAT-12, FAT-16, or FAT-32.

e following chapters of the xPC Target documentation:

rget User’s Guide: Targets and Scopes in the MATLAB Interface;

als and Parameters; Working with Target PC Files and File Systems;

unction Reference.

arget Getting Started Guide: “Basic Tutorial”.

Target API Guide: API Function and Method Reference.

xPC Target™ Release Notes

Numeric Precisi

To improve numer messaging has be the f ull binary signal monitor

image of data values during xPC Target interactions such as

ing and parameter tuning.

on in Host/Target Communications

ic precision, the format of xPC Target host PC to target PC

en converted to binary mode. This implies the transfer of

CandCOMAPI

You no longer stand-alone

xPC Target AP

and methods

To deploy a G licensed c you do not h your GUI ap

In suppor in the

C:\

ate how to use the xPC Target COM API to create custom stand-alone

illustr GUI appl

•

VBNET\S

Visual is a fun own cus

need to purchase xPC Target Embedded Option to create

GUI applications with the xPC Target C or COM API. See the

IGuidefor reference pages for the C and COM API functions

UI application to other host PC systems that do not have your

opy o f xPC Target, you need the xPC Target Embedded Option. If

ave the xPC Target Embedded Option and would like to deploy

plication, contact your MathWorks representative.

t of this new feature, xPC Target provides the following new demos

matlabroot\toolbox\rtw\targets\xpc\api

folder. These demos

ications.

igsAndParamsDemo\Demo.sln

Basic

.NET files to run the windows form application. This demo

— Contains all the Microsoft

ctional application that you can use as a template to create your

tom GUIs.

•

lBasic\Models\sf_car_xpc

Visua

r_xpc

sf_ca

the mo

emo is written.

the d

tclt

xPC T

Tk.

Tcl/

demo, including the Microsoft Visual Basic project files and

del file (

sf_car_xpc.mdl)andDLMfile(sf_car_xpc.dlm)forwhich

— Contains Tcl/Tk demo scripts that illustrate how to directly access

arget COM API functions through a command-line interpreter like

— Contains all the relevant files for the

COM API GetParam Syntax Change

GetParam method now returns the correct size of elements returned. In

The

rlier versions, this method required you to provide an element size.

Version 2.5 (R14) xPC Target™

Support for Model Referencing

xPC Target now supports the new Model block from Simulink. This block allows one model to include another model as if it were a block. This feature , called model reference, works by generating code for included models that the parent model executes from a binary library file. See the Real-Time Workshop Release Notes for further information. When using model referencing with xPC Target, note the following Configuration Parameter parameter setting requirements:

• In the Real-Time Workshop node, ensure that the RTW system target

file parameter for both the top and referenced models is xpctarget.tlc.

• In the Solver node, ensure that the Solver settings for both the top and

referenced models match.

Compatibility Considerations

If you download a target application to a target PC, and that target application was built from a model that contains referenced models, you cannot tune the parameters on any of the models. This is a limitation of Real-Time Workshop.

Run-Time Parameters

xPC Target provides the following target object methods to enable you to save run-time parameters for your target application. These parameters are those you would like to save for reuse, such as those for parameter tuning. See the xPC Target User’s Guide for details:

•

saveparamset

• loadparamset

In conjunction, the following API functions enable the same feature. See the xPC Targe t API Guide for details:

•

xPCSaveParamSet

• xPCLoadParamSet

xPC Target™ Release Notes

Inlined Paramet

xPC Target now su Workshop.

Configuratio

In previous re contained the now containe tree. The fun

RS-232, RS-

New drivers

• RS-232 — QS

• RS-422, RS

• RS-232, R

boards fr respect

xPC Targ Serial C the new

S-422, RS-485 — Emerald-MM and Emerald-MM-8 PC/104

om Diam ond Systems. These boards provide 4 and 8 serial ports,

ively. These boards are jumper-configurable for the protocols.

et provides a set of functionally similar drivers for these boards. See

ommunication of the xPC Target I/O Reference for a description of

driver blocks.

pports the use of inlined parameters from Real-Time

n Parameters xPC Target Options Dialog

leases, the Simulink model Configuration Parameters dialog

xPC Target options in two panes. The xPC Target options are

d in one pane, available as a node in the Real-Time Workshop

ctionality of the dialog is otherwise identical.

422, and RS-485 Add-on Board Drivers

have been added for serial communication support:

C-100 and ESC-100 PCI boards from Quatech

-485 — QSC-200/300 boards from Quatech

ers

Number

The nu now ha and Re

xPC T

ollowing enhancements have been made to xPC Target methods and

The f

ameters:

par

ameters are no longer target object properties. You can no longer use

• Par

setparamid function to set parameter IDs, nor can you use the set or

of Available UDP Blocks Increase

mber of available UDP blocks per model has been increased. Y ou can

ve up to 32 UDP blocks in any given model (any combination of Send

ceive blocks).

arget Methods and Parameters

Version 2.5 (R14) xPC Target™

get function to get or set parameter values. For example, commands like

the following no longer work:

tg.P1 tg.P1=5

Instead, use the new methods, getparam and setparam.

• Signals are no longer targ et object properties. You can no longer u se

the

get function to get signal values. For example, a command like the

following no longer works:

tg.S1

Instead, use the new method, getsignal.

• After setting new parameters with

back to preceding ones with the

• The target method,

xpc, now allows you to establish communication with

setparam, you can now revert values

parIndexVec structure.

multiple target PCs.

These changes require you to update any xPC Target scripts or M-files that refer to these methods, parameters, or properties. Your existing scripts and M-files will no longer run on xPC Target otherwise.

See the xPC Target User’s Guide for details.

xPC Target Scopes

The following enhancements have been made to xPC Target scopes:

• xPC Target now supports 10 scopes of each scope ty pe for a maximum of 30

scopes. In prior releases, xPC Target supported a total of 10 scopes.

• Scopes created by xPC Target Scope blocks now acquire data according

to Simulink sample time rules. In previous releases, scopes created by xPC Target Scope blocks acquired data at the base sample rate of the model, regardless of the sample time of their input signal. T hi s includes non-regular e xecution, such as if the scope is in an enabled or triggered subsystem. Note that scopes created dynamically (from the MATLAB Command Window or the API) behave as before, sampling at the base rate, irrespectiveofthesampletimeoftheirsignals.

xPC Target™ Release Notes

To xPC Target and

The behavior whe blocks has chang block that has b the b lock refer block has not y In previous re Parameters di

To edit the bl blocks, righ

xPC Target F

xPC Target the target time. As th that data

PC hard disk and d istributes that data in chunks every sample

e xPC Target kernel on the target PC reads the file d ata, it write s

into a software buffer whose size is user-defined.

I/O Devic

xPC Targ boards:

et 2.5 has new driver blocks, including support for the fo llowing

n you double-click the To xPC Target and From xPC Target

ed. If you double-click a To xPC Target or From xPC Target

een properly configured, the target parameter or signal that

s to is highlighted. If the To xPC Target or From xPC Target

et been configured, double-clicking the block has no affect.

leases, double-clicking on these blocks displayed the Block

alog for the block.

ock parameters for the To xPC Target or From xPC Target

t-clickontheblockandselectMask parameters.

rom File Block

has a new block, From File. T his block reads data from a file on

eDriverSupport

From xPC Target Blocks

• Adlink

- PCI-81

• Conte

- CNT24

• Diamo

- Garn

- Diam

- Dia

- Eme

- On

-4D

et-MM

ond-MM-16

mond-32-AT Frame A/D

rald-MM

rald-MM-8

yx-MM-DIO

- Prometheus

• National Instruments

- PXI-6071E

- PCI-6601

- PCI-6602

- PCI/PXI-6711

- PCI/PXI-6713

• North Atlantic Industries

- PCI-76CS1

- PCI-76CL1

- PCI-76LD1

- 73SD3

• Quanser

Version 2.5 (R14) xPC Target™

- Q8

• Quatech

- QSC-100

- ESC-100

- QSC-200/300

• Real Time Devices

- DM6816

• Sensoray

- Sensoray526

• VMIC

- VMIC VMICPCI-5565 (previously released as part of the xPC Target

Release 2.0.2 library update)

Some xPC Target 2.5 drive r blocks have been updated, in cluding

xPC Target™ Release Notes

• The SBS and Systran®shared memory blocks have been updated to better

coincide with the VMIC shared memory blocks.

• All Diamond-MM blocks have been re named to MM. If you have existing

models with blocks named Diamond-MM, replace those blocks with the renamed equivalents.

• Diamond-MM A/D,D/A, DI, and DO blocks have parameter changes.

• The General Standards PCM-ADADIO block has been updated.

• Support for the following National Instruments boards has been enhanced:

- PCI-6023E

- PCI-6024E

- PCI-6025E

- PCI-6031E

- PCI-6052E

- PCI-6071E

- PCI-MIO-16E-1

- PCI-MIO-16E-4

- PCI-MIO-16XE-10

- PCI-6040E

- PXI-6070E

• Support for the following UEI boards has been enhanced:

- PD2-MF

- PD2-MFS

- PDXI-MF

- PDXI-MFS

- PD2-AO

• The following National Instruments drivers have been renamed:

- PCI-MIO- 16 E-10 , renamed to PCI-6030E

- PCI-MIO-16E-4, renamed to PCI-PCI-6040E

Version 2.5 (R14) xPC Target™

- PCI-MIO- 16 E-1, renamed to PCI-6070E

• The CIO-QUAD02, CIO-QUAD04, and PCI-QUAD04 Incremental Encoders

now have a Filter prescale factor, which helps eliminate high frequency noise.

• The Softing board drivers have been updated.

Obsolete Device Drivers

Compatibility Considerations. xPC Target has obsoleted the drivers for

the following manufacturers:

• Burr-Brown

• Gespac™

You can still access these d riverblocksbytypingthecommand

xpcobsoletelib at the MATLAB Command Window. Existing models that

use these drivers will still work. However, their presence is not guaranteed for future releases. Do not use these driver blocks in new models.

In addition, in the xPC Target library ( following Measurement Computing Incremental Encoder drivers. Use the new version of these drivers.

• CIO-QUAD02

• CIO-QUAD04

• PCI-QUAD04

To access the previous versions of these drivers, use the command. The presence of the obsoleted versions of these drivers is not guaranteed for future releases.

xpclib), the re are new versions of the

xpcobsoletelib

xPC Target™ Release Notes

Recreate Target

Boot Disk and Rebuild Applications

Compatibility Considerations

If you upgrade y must recreate applications

our xPC Target software from a previous version, you

the target boot disk and you must rebuild your xPC Target

Version 2.0.3 (R13SP2)

This table summarizes what’s new in Version 2.0.3 (R13SP2):

Version 2.0.3 (R13SP2)

New Features and Changes

No No No

Version Compatibility Consideratio

Fixed Bugs an d Known Problems

Related Documentation at Web Site

Printable Release Notes: PDF

V2.0.3 pr od uct documentation

xPC Target™ Release Notes

Version 2 (R13) xPC Target

This table summarizes what’s new in Version 2 (R13):

New Features and Changes

Yes Details belo

Version Compatibility Consideratio

Yes Summary.

New features and changes introduced in this version are

• “xPC Target API” on page 89

• “Enhanced Data Logging and Tracing” on page 89

• “New Host PC GUI” on page 89

• “Additional I/O Support” on page 90

• “Additional Async Events Support” on page 90

• “Fortran Support” on page 90

• “Polling Mode” on page 90

• “RS-232 Binary Drivers” on page 90

• “From/To xPC Target Blocks” on page 91

• “Data Logging/Scope Data Upload Is Faster” on page 91

• “Scope Data Is Uploadable When S tate Is Interrupted” on page 91

Fixed Bugs an d Known Problems

Fixed Bugs

Related Documentation at Web Site

• “Support For I82559ER-Based Ethernet Cards” on page 91

• “Scope Data/Data Logging Buffers Accessible Through WWW Interface”

on page 91

• “Scope ID Autoincrement” on page 91

• “Recreate Target Boot Disk and Rebuild Applications” on page 92

xPC Target API

The xPC Target AP operating syste to integrate wi tools to develo Target applic

ation.

I is an open environment designed for a Windo ws

m. It provides all of the information and accessibility you need

th various development tools. You can use these development

pandprogramaGUIapplicationthatconnectswithanxPC

Version 2 (R13) xPC Target™

The x PC Target

• xpcapi.dll —

application time.

• xpcapiCOM.

objects. Yo atargetap

A generate paramete

Check the on this f

rs and signals in your target application.

eature.

Enhance

You can target scope p

now upload continuous data, without missing samples, while the

application is running. Use two or more host scopes with the new

roperty

New Ho

ctool

xpcr

ing on the host PC. This GUI allows you to remotely connect from

runn

AB on a host PC to a target application on a target PC, tune

MATL

meters, trace signals, and log data.

para

API is distributed in two different libraries:

DLL w ritten in C with the necessary functions for your GUI

to link to at run time rather than link to statically at compile

dll — Component Object Model DLL consisting of COM

u use these COM objects with your GU I application to control

plication.

d model specific COM DLL allows you to easy access preselected

xPC Target Product News Page at for updated documentation

dDataLoggingandTracing

sc.TriggerSample.

st PC GUI

(Remote Ccontrol Tool) is a graphical user interface (GUI)

s GUI includes a new signal viewer for adding and removing signals from

Thi

PC Target Scope.

an x

xPC Target™ Release Notes

Additional I/O S

The following I/

• Standard IP mod

• CONTEC boards

• Increased NI b

• National Inst

• UEI drivers

• SBS shared m

Additional

xPC Target the board a

Fortran S

xPC Targe

Check th on this f

e xPC Target Product News Page at for updated documentation

eature.

O support has been added:

ules

and drivers

oard support

ruments counter boards

emory

Async Events Support

now supports the Real Time Devices DM6804 board. You can use

n interrupt source for generating an asynchronous event.

upport

t now supports Fortran for using S-functions in Simulink.

upport

Pollin

A n ew ex kerne unles commu signa

RS-2

New d rec

g Mode

ecution mode (Polling Mode) has been introduced in the xPC Target

l that enables smaller execution times. You should not use this mode

s absolutely necessary, because it will cause you to lose all host-target

nication during model execution. Consequently, parameter tuning,

l monitoring, etc., capabilities are lost in this mode.

32 Binary Drivers

rivers have been added for RS-232 I/O that enable you to send and

eive arbitrary binary data.

Version 2 (R13) xPC Target™

From/To xPC Targ

It is now possibl xPC Target block Target applica From/To xPC Tar

Data Logging/

Uploading lo faster than i

Scope Data I

If an xPC Tar whole buff uploaded d the data wa

Support F

Some (mo on the I8 support

stly in embedded form factors) PCs have Ethernet controllers based

2559ER Ethernet controller from Intel. These controllers are now

ed.

e to automatically generate From xPC Target blocks and To

s from an existing Simulink model representing your xPC

tion. This is done by tagging the blocks you want to use the

get blocks with.

Scope Data Upload Is Faster

gged data or data from an xPC Target scope (of typ e host) is now

t was in xPC Target 1.2.

s Uploadable W hen State Is Interrupted

get scope of type host is interrupted before it can acquire a

er of data, it is now possible to upload the data it has acquired. The

ata will still be of the entire buffer size; the last few samples where

s not acquired will be set to zero.

or I82559ER-Based Ethernet Cards

et Blocks

Scope D WWW Int

Data f

face,aswellasthedatalogged(states, outputs, TET) during application

inter execu can b

Scop

Target scopes have to have a unique identifier. This identifier had to

xPC

ntered manually in case you had two or more xPC Target scope blocks.

be e

s has been changed so that the scope ID is automatically incremented to

Thi

ppropriate value.

an a

ata/Data Logging Buffers Accessible Through

erface

rom x PC Target scopes of type host are uploadable through the WWW

tion. This data is in Comma Separated Variable (CSV) format, which

e read by most spreadsheet programs and also by MATLAB.

eIDAutoincrement

xPC Target™ Release Notes

Recreate Target

Boot Disk and Rebuild Applications

Compatibility Considerations

If you upgrade y must recreate applications

our xPC Target software from a previous version, you

the target boot disk and you must rebuild your xPC Target

Version 1.2 (R12.1) xPC Target

This table summarizes what’s new in Version 1.2 (R12.1):

Version 1.2 (R12.1) xPC Target™

New Features and Changes

Yes Details belo

Version Compatibility Consideratio

Yes Summary

New features and changes introduced in this version are

• “C API” on page 93

• “UDP Driver Support” on page 94

• “Asynchronous Event (Interrupt) Support” on page 94

• “CAN FIFO Support” on page 94

• “100 Mbit/Second Ethernet Support” on page 94

• “Fixed-Point Kernel Support” on page 94

• “Increased Data Upload Speed” on page 9 5

• “I/O Device Driver Support” on page 95

• “Recreate Target Boot Disk and Rebuild Applications” on page 95

Fixed Bugs an d Known Problems

No bug fixes

Related Documentation at Web Site

CAPI

A beta version of the xPC Target C API is available from the Product News page at http://www.mathworks.com/support/product/XP/productnews/productnews.html.

Use the C API to create stand-alone graphical user interfaces (GUIs) or console applications to interact with a real-time target application. xPC Target includes examples for Microsoft Visual C++ and Microsoft Visual B asic.

xPC Target™ Release Notes

UDP Driver Support

Communicate with another computer using User Datagram Protocol (UDP) packets. Add UDP driver blocks to your Simulink model and configure them for sending and receiving messages from another system.

The UDP driver blocks are not included on the R12.1 CD. Check the Product News page at http://www.mathworks.com/support/product/XP/productnews/productnews.html for the drivers when they become available.

Asynchronous Event (Interrupt) Support

Create subsystems that execute asynchronously when an event (interrupt) occurs.

These subsystems can communicate and be part of a larger model that executes with a monotonic step size.

We expect to further enhance the Asynchronous Event drivers currently available on the R12.1 CD. Check the Product News page at http://www.mathworks.com/support/product/XP/productnews/productnews.html for the enhanced version.

CAN FIFO Support

Use CAN FIFO model I/O drivers to either monitor an entire CAN network, or to minimize driver latency for certain applications.

100 Mbit/Se cond Ethernet Support

Use 10 or 100 megabit/second communication betw een the host and target computers for downloading real-time application and uploading signal data. The communication uses the TCP/IP protocol with an Ethernet card in both the host and target computers.

Fixed-Point Kernel Support

The xPC Target kernel runs on PCs (CPUs) that do not have a hardware floating-point unit. If needed, xPC Target uses a software floating-point emulator.

Version 1.2 (R12.1) xPC Target™

IncreasedDataU

Upload log data a three times fast

bout five times faster or better. Upload scope data about

er.

I/O Device Dri

xPC Target 1.2

• New blocks to

• Blocks to sup

controller

• Blocks to su

Recreate T

includes new device drivers blocks :

support additional I/O boards

port a GPIB field bus using a National Instruments GPIB

and an RS232 connection to the target PC

pport CAN and CAN FIFO networks

arget Boot Disk an d Rebuild Applications

pload Speed

ver Support

Compatibility Considerations

If you upg must recr applica

rade your xPC Target software from a previous version, you

eate the target boot disk and you must rebuild your xPC Target

tions.

xPC Target™ Release Notes

Version 1.1 (R12) xPC Target

This table summarizes what’s new in Version 1.1 (R12):

New Features and Changes

Yes Details belo

Version Compatibility Consideratio

Yes Summary

New features and changes introduced in this version are

• “xPC Target and xPC Target Embedded Option” on page 96

• “Web Browser Interface” on page 97

• “Target PC Command-Line Interface” on page 97

• “MATLAB Command-Line Interface” on page 97

• “Signal Monitoring” on page 98

• “I/O Device Driver Support” on page 98

• “Recreate Target Boot Disk and Rebuild Applications” on page 98

Fixed Bugs an d Known Problems

No bug fixes

Related Documentation at Web Site

xPC Target and xPC Target Embedded Option

The xPC Target and xPC Target Embedded Option products were introduced as MathWorks products in Release 11.1.

Note xPC Target 1.1 extends the functionality of the Real-Time Workshop. The xPC Target Embedded Option 1.1 in turn extends the functionality of the xPC Target and requires an additional licence from The MathWorks.

Target

xPC

xPC Target is a host-target PC solution for prototyping, testing, and deploying real-time systems. It is an environment where the host and target computers are different computers.

Mathworks XPC TARGET RELEASE NOTES

Specifications and Main Features

Frequently Asked Questions

User Manual