top variability – multi-protocol support – future-oriented

The FlexCard PMC II is a bus interface device for automotive bus systems in PMC design. Four physical layer (FlexTiny II) slots allow several configurations of bus Communication Controllers. Every FlexTiny II module supports two same physical layer drivers. Configurations of up to 4 FlexRay (channel A and B) or up to 8 CAN Communication Controllers are possible. A free and future-oriented field of application is guaranteed.

A variable combination of paired bus interfaces saves the use of multiple devices and slots in the system. Using different monitoring modes, the card can be used as pure monitoring tool and as real communication node. The multi-protocol support of the FlexCard PMC II is especially suitable for multi-bus applications. A consistent API for all FlexCard products reduces the device integration in user applications. The PMC design allows a simple integration in nearly all PCI systems.

Features

• 4 FlexTiny II slots allow configurations up to 4 FlexRay (A+B) or up to 8 CAN Communication Controllers
• Support of LIN, MOST, Ethernet, RS232 in scheduling
• Configurable bus termination
• 2 Trigger connectors configurable as in- or output
• 2 MB onboard memory; 1 MB for data buffering
• State display with LEDs
• Extensive driver software for several operating systems
• Chronological correlation of bus messages with one timestamp base
• Firmware update with user PC

Fields of application

• End-of-Line Tests
• Hardware in the Loop systems (HiL)
• Network simulation 
• Measurement equipment with PMC or PCI systems
• Prototype development
• Automotive test insert
• ECU quality tests

Functional range CAN

• Receive and transmit of CAN frames (data and remote frames)
• Silent mode useable for listening without bus interference
• Filtering with suitable buffer configuration possible
• Signal of error states forwarded directly to user application

Functional range FlexRay

• Receive and transmit of FlexRay frames
• Asynchronous listening (e.q. logging of start-up)
• Receive of null frames configurable
• Transmit acknowledge
• Receive and transmit of FlexRay symbols and wake-up pattern
• Immediately signalization of network synchronization (with timestamp)
• Signal of error states (e.q. bus-/syntax error) forwarded directly to user application
• Triggering on the precise slot, cycle and on various error states
• Configuration of a second start-up/sync frame possible (with firmware versions of only one sync Communication Controller), to use not start-up/syncable FlexRay nodes in a virtual FlexRay cluster