Features:
- Runs Mark VI application code from a single VME controller slot.
- Links the controller to the Unit Data Highway through Ethernet.
- Moves simplex or voted process data across the VME backplane.
IS215UCVEM08B combines the processing and nonvolatile storage resources required to operate a Mark VI control application.
COM1 provides the low-level setup path, while the second RS-232C port supports an additional serial connection.
The controller works with the rack communication board so network traffic and process I/O follow separate defined paths.
The General Electric IS215UCVEM08B Mark VI UCVE VME Controller Board may still be available for purchase and support from Apter Power beyond End-Of-Life (EOL) by the manufacturer (OEM).
General Electric IS215UCVEM08B Mark VI UCVE VME Controller Board Manuals, Datasheets, Links
Important Notice: Other accessories, manuals, cables, calibration data, software, etc. are not included with this equipment unless listed in the above stock item description. All prices are shown in USD.
Processing Resources
- Processor Core: Executes the controller application
- Working Memory: DRAM supports runtime operation
- Nonvolatile Storage: Flash retains the file system
- Backplane Role: VME transfers external system data
Controller Access Points
- Ethernet: Connects IS215UCVEM08B to the Unit Data Highway
- COM1: Supports initial setup and low-level diagnostics
- COM2: Provides a serial communications channel
- VME Bus: Links the controller with VCMI data exchange
Mechanical and Loading Boundaries
- Slot: Install IS215UCVEM08B in rack position 2
- Backplane: Use a rack position without J3 and J4 connectors
- Flash Loading: Program the flash file system with the controller tool
- Network Setup: Assign the controller TCP/IP address before runtime loading
System Exchange Paths
- Simplex I/O: Process I/O reaches IS215UCVEM08B over VME
- TMR I/O: Voted I/O is presented through the same rack bus
- Network Traffic: UDH communication uses the Ethernet interface
- Application Data: Runtime and application code execute in controller memory