Made in USA
The Embedded Solutions Experts


PCIe3IP

PCIe adapter for 3 IP Modules with independent overlapped accesses to each IP. 8, 16, 32, 64 bit accesses supported

Order This Item


Quantity

PCIe3IP Description

  • Windows® , Linux, VxWorks driver included with purchase
  • Single PCIe lane operation ↣ can be installed in any PCIe slot.
  • 3 IndustryPack Module positions w/ 8⇆32 MHz. operation
  • Independent IP control buses with overlapped instruction execution
  • Fused, FIltered 5V, +12V, -12V supplied to IP´s
  • Multi-word accesses supported including 64, 32, 16, 8 bit and larger payload handling to IP´s
  • Full memory space supplied to each position
  • 1/2 length PCIe card
  • Ribbon Cable Bezel Cutout
  • 1 year warranty standard. Extended warranty available.
  • Extended [Industrial] Temperature standard.
  • ROHS and Standard processing available
IndustryPack® Modules are an important part of solutions for Embedded situations. Rugged, small, light .. just right for many applications. IndustryPack® Modules require a "carrier" in most cases to adapt them to the system. Dynamic Engineering has carrier solutions for a variety of formats. PCIe3IP is designed to support PC computer based solutions. Solutions available for PC104p, cPCI, and PCI and planned for cPCIexpress, VPX, PC104express.

PCIe3IP is part of the IP Compatible family of modular I/O components. PCIe3IP provides three IndustryPack® module sites in one PCIe slot. PCIe3IP acts as an adapter, converter, carrier, and bridge between the PCIe bus and your IndustryPack® hardware. PCIe3IP is a half size, single lane PCIe card compatible with the smallest chassis and all PCIe slots.

PCIe3IP is supported with Windows® compliant WDF drivers for Win7 etc. as well as Linux and VxWorks support. The drivers come with a generic IP driver to allow use with "unknown" IP´s <=> IP´s that do not have a driver designed yet. For example, third party IP´s.

IndustryPacks are 16 bit devices, and the PCIe bus supports larger payloads. PCIe3IP accepts up to 128 byte payloads, and converts to word accesses. Most modern CPU´s can generate 8, 16, 32 and 64 bit instructions. The IP accesses can be auto-incremented or static address accesses. With the static access option the intended word can be accessed multiple times. With auto-incremented addresses multiple addresses are accessed. The strength of the PCIe bus is in handling larger payloads. PCIe3IP provides the capability of handling larger payloads to reduce the average execution time. By changing from 16 bit accesses to 32 the overhead is cut in half and by going to quad instructions the over head is cut in 4 leading to much higher bandwidth. For payloads larger than 64 bits DMA is needed to create the packets. The current PCIe3IP implementation includes the larger payload capabilty using external DMA. We are working on FPGA supported DMA to make CPU independent.

With Gen1 it takes about 2.5 uS to read a 16 bit value from a target device. With reads the data from the IP must be accessed, and a return payload constructed, and transferred to the host before the host can proceed to the next instruction. The access time for the IP Module is only 94 nS at 32 MHz with 1 wait state. The response time is dominated by the over head. This is based on a loop of 1000 accesses to a 32 MHz IP with 1 wait state in the memory space. (2.451 uS was the tight loop average). The same loop with 32 bit accesses took an average of 2.556 uS or 1.278 uS per 16 bit read. The 64 bit loop provided 2.741 uS or .685 uS per 16 bit read. Larger payloads will approach the actual read time of the IP HW.

With writes the time is much lower due to the ability to auto respond before the write is completed, and the FIFO´s allowing storage of multiple commands per IP module. With the same parameters as the above and a write loop, the average for 16 bit access is .548 uS, for 32 bit .301us/word and for 64 bit .205uS/word. With larger transfers the access time will approach the IP access time on an average per word basis.

The Dynamic Engineering implementation does not require any special features on your IP module. Larger transfer sizes are especially useful for repetitive data transfers - loading or reading from RAM or FIFO´s faster will reduce the overhead on your CPU leading to more available time to process the data leading to lower cost or more capable systems.

Each position has a separate clock controller for 8 and 32 MHz operation. The frequency to be changed on the fly. The state-machine within the bridge design automatically locks to the IP Slot frequency as programmed.

Each PCIe transaction is pre-decoded and forwarded to separate IP Module handling logic. Each Module has separate memory and control interfaces to allow for overlapped IP operation. For example IP 0 can be executing a read or write in parallel with IP 1 and IP 2. Multiple commands can be stored for execution by each IP. Synchronization between the IP´s is available to provide multi IP sequenced programming should that be necessary.

PCIe3IP asks for MSI interrupts during enumeration. If provided by the system, MSI interrupts will be available for operation. Legacy interrupts are provided when MSI interrupts are not programmed by the system.

Each IP position has "self healing" fused, filtered power. Each IP Module has separate bulk and bypass capacitance.

Industry standard 50 pin [ribbon cable] headers are used with the IO connectors. Vertical connectors are provided in the rear two positions. The connector at the bezel is a right angle model and is mounted through the bezel. The bezel connector is outfit with ejectors. An ordering option for ejectors to be mounted to the rear vertical headers is available. This is not the default option due to PCIe height restrictions. A recommended upgrade if your system has the room. "-EJ"

The bezel has a cut-out to allow the ribbon cables to be brought outside of the chassis without requiring an extra slot in the chassis. The blank bezel is available by adding "-BB" to the part number.

Ribbon cable or discrete wire cables can be interfaced directly with the PCIe3IP. Alternatively the HDRterm50 can be used to create a terminal block interface.

The IP´s can be reset from the control register within the FPGA via the software interface. In addition at power-up the IP´s are provided the 200 mS reset as required by specification.

LED´s are provided to each of the three IP slots for activity indicators. When each slot is accessed the LED is flashed. The FPGA provides a "one shot" circuit to stretch the "on" time to make it visible. Power indicator LED´s are provided using voltage monitors. An additional eight user LED´s are available for debugging or other purposes.

A surface mount "dip switch" is available for configuration control or debugging purposes. The switch values are available to be read via the PCIe bus. The switch is used for deterministic control by the driver. When multiple carriers are used in the same system the switch is used to allow the driver and application software to "know" which carrier maps to which handle. Further the slot information for a particular IP is stored to create a "vector" pointing to a specific slot on a specific carrier. Deterministic control of specific interfaces is easily achieved with this system without hardwiring system data into your software. The application software will be more portable and not break when new assets are added to the system (and your PCIe addresses change).

IP accesses are protected by a watch-dog timer. The timer is started at the beginning of each IP access. If the timer expires before the IP being accessed responds, a bus error internal to the PCIe3IP is created. The PCIe3IP responds normally to the host, not creating an errror on the PCIe bus, and provides status and an optional interrupt to alert the host to the problem with the IP. The Bus Error timer is useful in situations where the software may want to cause a bus error to find out what is installed or where a hung system would have consequences.

Connector positioning is compatible with IP-Debug-Bus will allow the user to isolate and debug the control interface of an IP. The IP-Debug-IO can be used in conjunction with the PCIe3IP and IP-Debug-Bus to provide test-points on the IO signals and loop-back capability for the IP.

PCIe3IP has an alternate "mini-map" option available. The standard design provides the full address space to the IP Memory space. The mini-map provides a minimized memory space equal to the ID, IO, and INT spaces with 128 bytes. The total PCIe memory space is reduced to 2K with this option. Please download the alternate manual to get the address map and other details. Please order with the -MM option for the mini-map.

PCIe3IP is an extended temperature board. The extended or "Industrial Temp" version has components rated for -40C to +85C minimum. This temperature range will need to be derated based on your chassis thermal situation.


PCIe3IP Features

Size
Half size PCIe card.
IP compatible slots
3 independent positions.
Clocks
Each position has independent selection of 8 and 32 MHz operation. Clock selection can be changed on-the-fly with glitch free operation.
Access Width
Each position can be accessed as byte, word, or multiple word payload [x32, x64]. Multiple word accesses can be static or auto- incrementing to the IP slot.
Bus Error
The Watch-Dog timer protects against PCIe bus hangs by responding when the IP is not installed or has a failure.
Cable interface
Industry standard 50 pin box header connectors. Right angle through the bezel and vertical mount for the remaining 2 positions. Special bezel with cable slot for IO egress through the bezel. Bezel has an "arm" :rotate out of the way when installing the cable(s) and then lock back into place to secure.
Software Interface
Control registers are read-writeable. IO, ID, MEM, INT spaces supported. Windows® , Linux and VxWorks Drivers available
Interrupts
Each IP has 2 potential interrupts. All are handled as MSI or Legacy types on the PCIe bus. Control registers are provided to enable amd tailor the pace at which interrupts are sent to the host and Status registers are provided to determine the source of the interrupt.
Power Requirement
+5V, +12V, -12V current determined by IP´s installed. 3.3V used by FPGA. +12V used to create +5, -12V for IP´s, local DC:DC power supplies for efficient power conversion. Full IP spec power available to each position.
DIP switch
An 8 position switch is available to allow for configuration control, or to facilitate debugging, and to provide a positive ID of each PCIe3IP in your system
Volatility
Statement of Volatility
LED´s
monitored +1.2V, +3.3V, +5V, +12V, -12V, activity LED´s. 8 user LED´s also included.
Reliability
estimated 1.3 million hours. Bellcore. GB 25c

PCIe3IP Benefits

Speed
With the direct PCIe to IP Bridge design featured in PCIe3IP the access to your hardware happens faster than in competing designs. The 32 bit access capabilities and overlapped IP access further extends the lead in speed. Compatible with mult-processor systems without sacrificing access times for single CPU systems. Multiple threads with accesses to different IP´s are supported.
Price
System level cost is best when reasonably priced reliable hardware is used and NRE minimized. With PCIe3IP, driver support for the carrier and IP level, reference software, history of reliable operation, and fantastic client support your cost per unit and overall costs are attractive. Please check the current per item pricing with the storefront lower on this page. Orders can be placed via the on-line ordering system or via phone / email PO order systems.
Ease of Use
PCIe3IP is easy to use. A point and shoot user interface to the IP sites. Please download the manuals and see for yourself. Reference software is provided in source form to get you started. The generic IP interface allows the driver to be used with IP´s without a driver specific to that design.
Availability
We work to keep PCIe3IP in stock. Send in your order and in most cases have your hardware the next day. We can ship with FedEx pick-up everyday, and other carriers as requested.
IP Specification Compatibility
PCIe3IP is IP compliant per the VITA 4 - 1995 specification. All Dynamic Engineering IP Modules are compatible with the PCIe3IP. All other IP Modules which are compliant with the VITA specification can be expected to work. ID, IO, INT, and Memory spaces are supported in all 3 positions.
PCIe Compatibility
PCIe3IP is a PCIe compliant device. PCIe3IP can be expected to work in any PCIe compliant backplane.

Part Number: PCIe3IP
Ordering Options

  • PCIe3IP Standard board - with 3 IP positions, Industrial temperature components.
  • -EJ Add Ejector Style Header connectors for the 2 non-bezel positions.
  • -ROHS Use ROHS processing. Standard processing is ""leaded"
  • -BB Option to have a blank bezel without a cut-out. The Ribbon Cable Bezel is standard and includes a cutout to facilitate cable egress from the IP Modules. Note: -BB also causes bezel position to have a vertical box header connector.
  • -VC Option to have vertical box header in bezel position while retaining the standard Ribbon Cable Bezel.
  • -CC Option to add Conformal Coating

PCIe3IP Drivers

Software Support for PCIe3IP includes: Windows® 7, VxWorks, and Linux compliant drivers
Please see the Driver manuals for the specifics of each type.

PCIe3IP-7 Windows®7 or Linux drivers for PCIe3IP. The drivers are designed to be overlayed with individual IP Module(s) driver(s). IP drivers are auto installed for each instance detected. Please see the Driver manual for the specifics of writing your board interface. Please contact Dynamic Engineering if you would like us to produce one for your IP or a third party design. Our Windows drivers come with IP-Generic which is automatically installed when a specific driver is not found for a particular IP Module. IP-Generic can be used to control your IP including handling interrupts, and accesses to all 4 space types.

Linux
The PCIe3IP Linux driver is a bus driver capable of supporting multiple (up to 64) Industry Pack buses/carrier cards. This driver interfaces with the ipack-core Open Source code to support Industry Pack devices. This Open Source code has been slightly modified, and is included with the tar-ball for this driver.

A generic IPACK driver (ipack_gen) and user library (libipack) has been developed by Dynamic Engineering. This driver and library may be sufficient for developing user space drivers for a device depending upon the complexity of that device. Other device specific user libraries and kernel drivers are available for Dynamic Engineering Industry Pack modules. The diagram below illustrates possible layering of Industry Pack components:



Integration support is available. Please contact Dynamic Engineering for this option or download the Technical Support Description from the Company button.


PCIe3IP Manuals

Click on the link to Download selected manuals in PDF format.
Download the PCIe3IP Hardware Manual
Download the IP Carrier Windows®7 manual. For PCIe and PCI based carriers
Download the Win7 Generic IP Driver Manual in PDF format.
Download the IP Carrier Linux Manual
Download the Linux IP Module Manual