Store 
| Products & Services | Solutions | Academia | Support | User Community | Company |
 |
Download Product Updates | | |  |
Get Pricing | | | |
Trial Software |
| Documentation → xPC Target |
| Products & Services | Solutions | Academia | Support | User Community | Company |
|
Download Product Updates | | | |
Get Pricing | | | |
Trial Software |
| Documentation → xPC Target |
| Contents | Index |
| Learn more about xPC Target |
This table summarizes what's new in Version 4.2 (R2009b):
New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems | Related Documentation at Web Site |
|---|---|---|---|
Yes | Yes—Details labeled as Compatibility Considerations, below. See also Summary | Bug
Reports | Printable Release Notes: PDF |
You can use the new CAN Pack and CAN Unpack blocks that are available with your xPC Target™ license to perform message packing and message unpacking functions. Refer to the CAN Blocks Transition document for more information. These 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 handling capability of the xPC Target CAN block library has changed. These blocks 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 (including FIFO Write and Read blocks) 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.
If you have models that use old CANDBC blocks from the xPC Target block library (available by typing xpcobsoletelib), you will see an obsolescence 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 information 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 Target library of obsolete drivers:
CAN Message Packing
CAN Message Packing (CANdb)
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 driver blocks by typing the command 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.
In xPC Target Version 4.1 (R2009a), typing xpclib in the MATLAB Command Window caused a CAN_MESSAGE warning. This warning now appears only when you type .xpcobsoletelib.
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 Microsoft .NET Framework 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.
The UDP library has been enhanced to support variable length packets. The following blocks are updated:
The default behavior of these blocks remains the same as before. Your existing UDP models will continue to work without modification.
The J1939 library has been enhanced to support address claiming. See SAE J1939 in the xPC Target I/O Reference.
The following block is new:
The following blocks have changed to take into account the capabilities of the new J1939 Controller Application block:
J1939 Protocol Stack — See the reference for the updated block parameters. The following parameters have been removed: TX CAN Board, RX CAN Board, TX CAN Port, RX CAN Port, Transport Protocol Enabled, Transport Protocol Max Send (# of Fragments), Transport Protocol Max Receive (# of Fragments).
The following parameters are new: Max CAN Message Receive (Per Sample Time), Max CAN Message Transmit (Per Sample Time), Enable Transport Protocol, Maximum Concurrent Sessions, Enable Address Claiming.
J1939 Receive 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.
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.
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. You must then configure the J1939 Protocol Stack, J1939 Receive Message, and J1939 Transmit Message blocks to correctly reference the controller application.
xPC Target 4.2 now supports National Instruments PCI-6225 as part of its support for the National Instruments® M series data acquisition boards.
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 DynamicFileName, FileName, and MaxWriteFileSize properties in the set method.
See Acquiring Signal Data into Multiple, Dynamically Named Files on the Target PC in the xPC Target User's Guide.
The xPC Target software now enables you to load parameter sets from the target PC file system. The Configuration Parameters 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
File name
See xPC Target Options in the xPC Target Getting Started Guide.
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.
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 MATLAB 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. Other 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-time 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.
The xPC Target software now supports the Intel Visual Fortran 10.1 compiler.
The xPC Target software no longer supports the Intel Visual Fortran 9.1 compiler.
This release contains the following new demos:
UDP demos
Target to Host Transmission using UDP — Demonstrates how to use UDP blocks to send data from a target PC to a host PC.
Target to Target Transmission using UDP — Demonstrates how to use UDP blocks to send data between two target PCs.
CAN I/O and CAN I/O FIFO demos using CAN_MESSAGE data type
CAN I/O - Simple Use Case (with CAN_MESSAGE) — Demonstrates simple CAN I/O communication using the Softing® CAN-AC2-PCI board.
CAN I/O FIFO Mode - Simple Use Case (with CAN_MESSAGE) — Demonstrates CAN I/O communication using the First In First Out (FIFO) mode of the Softing CAN-AC2-PCI board.
CAN I/O FIFO Mode - Simple Use Case (with CAN_MESSAGE and Function Call Output) — Demonstrates CAN I/O communication using the First In First Out (FIFO) mode of the Softing CAN-AC2-PCI board. The FIFO Read block uses a function call output format.
If you upgrade your xPC Target software from a previous version, you must recreate the target PC boot image and you must rebuild your xPC Target applications. See xPC Target Boot Options in the xPC Target Getting Started Guide.
 | xPC Target Release Notes | Version 4.1 (R2009a) xPC Target |  |
Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
| © 1984-2009- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |
