| Version 1.1 (R12) xPC Target™ Release Notes | |
This table summarizes what's new in Version 1.1 (R12):
New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems | Related Documentation at Web Site |
|---|---|---|---|
Yes | Yes | No bug fixes | No |
New features and changes introduced in this version are
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. |
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.
In this environment you use your desktop PC as a host computer with MATLAB®, Simulink®, and Stateflow® (optional) to create models using Simulink blocks and Stateflow diagrams. After creating a model, you can run simulations in nonreal-time.
You can than use your host computer with Real-Time Workshop, Stateflow® Coder™ (optional) and a C compiler to create executable code. After creating the executable code, you can run your target application in real time on a second PC compatible system.
The xPC Target Embedded Option requires an additional license from The MathWorks.
This option allows you to boot the target PC from a device other than a floppy disk drive such as a hard disk drive or flash memory. It also allows you to create stand-alone applications on the target PC independent from the host PC.
If the target PC is connected to a network, you can use a Web browser to interact with the target application from any computer connected to a network. Currently, this feature is limited to one browser connection at a time. xPC Target supports Netscape Navigator® 4.5, Microsoft® Internet Explorer® 4.0 and later versions.
You can interact with the xPC Target environment through the target PC command window. Enter most of the xPC Target commands in the command window on the target PC. This interface is useful with stand-alone applications that are not connected to your host PC.
The behavior for the commands getparamid and getsignalid has been changed. The default behavior is to return the parameter or signal name (P0, P1 . . . or S0, S1, . . .), and you can also return the parameter or signal index (0, 1, 2 . . .) by setting an argument flag.
The behavior for the command getsignalid in xPC Target 1.1 is different from xPC Target 1.0 and may break scripts that use this command. The default behavior for the command getsignalid with Version 1.0 was to return the signal index.
This is the process for acquiring signal data without time information. The advantage of this process is that there is minimal CPU overhead for collecting the data.
xPC Target 1.1 includes new device drivers blocks:
New blocks to support additional I/O boards
Blocks to support a GPIB fieldbus using a National Instruments® GPIB controller and an RS232 connection to the target PC
If you upgrade your xPC Target software from a previous version, you must recreate the target boot disk and you must rebuild your xPC Target applications.
| Version 1.2 (R12.1) xPC Target™ | Compatibility Summary for xPC Target™ Software | |
| © 1984-2008- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |