Ask our team:
  • Phone: +86 181 0690 9650
  • E-Mail sales1@apterpower.com
  • Lifecycle status

    Active / Available from OEM
    Apter Power offers exact-model quotations, technical documentation, sourcing support, and VME/ControlNet configuration guidance.

5136-CN-VME

/ 4.9
1001 reviews | Need a Specific Revision?
For a 6U VMEbus host, Molex Woodhead 5136-CN-VME connects ControlNet I/O and peer devices through a dedicated network interface card.
In Stock
Ships by Wednesday, October 28
Fast Shipping Available
Get a quick price for 5136-CN-VME
Quantity
*E-mail
Company
*Mobile
*Content
Upload (gif, jpg, jpeg, png, bmp, doc, docx, xls, xlsx, ppt, pdf, csv)

Technical specifications for 5136-CN-VME

  • Manufacturer:
    Molex Woodhead
  • Part Number:
    5136-CN-VME
  • Product Family:
    SST ControlNet VME Interface Cards
  • Product Type:
    ControlNet VME Interface Card
  • Stock:
    1
  • Host bus:
    IEEE 1014 VME, 6U, P1-compatible
  • Network protocol:
    ControlNet
  • Network connectors:
    Two BNC for redundant connections; standard ControlNet NAP port
  • Processor:
    Intel i960 32-bit RISC, 33 MHz
  • Typical current:
    400 mA at 5 V
  • Diagnostics:
    Three LEDs: two network status, one system status
  • Interrupt selection:
    IRQ 1–7 or none, selectable by DIP switch
  • Operating temperature:
    0 to +50 °C
  • Weight:
    0.28 kg
  • Estimated shipping dimensions:
    26.3 x 2.1 x 18.7 cm
  • Tariff Code:
    Please confirm the destination before shipping
  • Country of origin:
    USA
  • Place of shipment:
    Xiamen,Fujian,China
By purchasing this item, you agree to the Terms & Conditions, ApterPower is not an authorized distributor for listed manufacturers or tradenames and therefore the manufacturer's warranty does not apply. All our products come with ApterPower's 1-year warranty.

More Information

Overview Manuals VME Integration ControlNet Roles Network Service Product Applications

Features:

  • VME host format: the 6U P1-compatible interface is intended for an IEEE 1014 VMEbus computer.
  • Concurrent network roles: ControlNet messaging, scanner and adapter functions can operate together.
  • Service visibility: separate network and system LEDs help distinguish link conditions from card status.
The VME variant is the relevant choice when the existing host is a VMEbus computer; PCI, ISA and PC/104 versions have separate ordering numbers.

Its combined network roles let an application monitor field I/O while exchanging data with other ControlNet participants.

When an existing rack is serviced, the host software, available slot and network layout determine how the interface is returned to operation.

Apter Power supports Molex Woodhead 5136-CN-VME ControlNet VME Interface Card quotations, technical documentation and exact-model sourcing.
Molex Woodhead 5136-CN-VME ControlNet VME Interface Card Manuals,Datasheets,Link
Important Notice: The manufacturer datasheet covers the VME interface; host software and installed network configuration remain project-specific.
  • Bus fit: the IEEE 1014, 6U, P1-compatible card belongs in a matching VME host rather than a PCI or ISA slot.
  • Host power: the interface uses the VME 5 V supply; the documented ±12 V rails are not used by this card.
  • Software route: Woodhead provides an open memory-map interface and example C source for custom driver development.
  • I/O scanning: the VME host can scan ControlNet I/O for its own application.
  • Messaging: the interface supports exchange of data with PLCs and other ControlNet devices.
  • Concurrent operation: scanner, adapter and messaging functions can run at the same time.
  • Message capacity: the manufacturer lists 128 scheduled and 128 unscheduled message screeners.
  • Redundant media: two BNC connections support a redundant ControlNet network arrangement.
  • Maintenance access: the standard ControlNet NAP port provides a service connection at the card.
  • LED separation: two network-status LEDs and one system-status LED provide different first-line fault indications.
  • ControlNet I/O scanning: a VMEbus host can collect cyclic field data from a ControlNet installation.
  • PLC data exchange: the host application can communicate with PLCs and other ControlNet devices.
  • VME computer integration: existing VME applications can be connected to a ControlNet control or monitoring network.
Description
A VMEbus control computer can use 5136-CN-VME to exchange data with a ControlNet installation without replacing its host platform. Woodhead identifies this part number as the VME version of its ControlNet interface card, distinct from the PCI, ISA and PC/104 versions listed in the same ordering table.

During operation, 5136-CN-VME can scan ControlNet I/O, exchange messages with PLCs and devices, and serve scanner and adapter functions. Those roles allow one VME application to bring network data into its own monitoring or control workflow, subject to the host software and network design.

In an operating VME rack, replacing 5136-CN-VME affects both the physical card position and the host application's ControlNet data path. Retaining the accepted program and network configuration helps the engineer restore the intended exchange after an exact-model replacement.
Alternative Names
SST 5136-CN-VME BradCommunications 5136-CN-VME Woodhead 5136-CN-VME Molex Woodhead 5136-CN-VME 5136 CN VME 5136CNVME 5136-CN VME 5136 CN-VME
Technical notes
The 5136-CN-VME occupies selectable VME memory, register and interrupt resources. An address or IRQ conflict can keep the host from recognizing the card even with a sound ControlNet link. Its documented memory map and DIP-selected interrupt level therefore belong in the host integration plan before network troubleshooting begins.
Exceptional Service

Our Mission

  • 100% Satisfaction

    We believe expertise is priceless. With over 20 years of experience, and top engineers on staff, we can help you solve or avoid problems that threaten your business.
  • Trust Guaranteed

    Not only do we have a vast inventory, our team makes sure every piece of equipment is in working condition. Your purchases are also backed by our Warranty.
  • Expertise

    Time is money, especially when your equipment is down. We work quickly to get your equipment on its way so you can get it back up and running.

FAQS

The following is a list of questions commonly asked by our customers. Please contact us if you have a question about our process that is not answered below.
Will 5136-CN-VME fit a PCI host used for a ControlNet upgrade?
A PCI host needs a different interface: Woodhead lists this as the 6U VME card and gives the PCI version a separate 5136-CN-PCI ordering number. The host bus determines the correct card family.
A VME application sends messages through 5136-CN-VME; will that alone scan remote ControlNet I/O?
Messaging alone does not establish an I/O scan. Woodhead provides a configuration tool for scanner applications, so the intended I/O connections must also be configured for the VME host.
How can an engineer develop host software for 5136-CN-VME when no packaged driver matches the VME computer?
Woodhead provides an open, documented memory-map interface with example C source for custom driver development. The site software team should map the card resources into its actual VME operating environment.
What should be checked when one ControlNet leg fails but 5136-CN-VME remains visible to the VME host?
The card has two network-status indicators and redundant BNC connections. Compare each indicator with its own network leg and cable path; a healthy host interface does not prove both media paths are healthy.
Can 5136-CN-VME be installed in a VME rack whose 5 V supply has no spare current margin?
It should not be added without capacity review. The interface draws a typical 400 mA from 5 V and does not use the ±12 V rails, so available 5 V capacity is the relevant host-power decision.
If I/O scanning still works but peer messaging fails through 5136-CN-VME, does the VME card necessarily need replacement?
A messaging failure alone does not establish a failed card. Woodhead documents distinct scanner and messaging functions running together, so review the host application messaging configuration and card status before replacing healthy I/O hardware.

Product Browsing History