Motorola MVME147‑011 VMEbus Single‑Board Computer (SBC)

Product Description

MVME147‑011 is a double‑height 6U VMEbus single‑board computer developed by Motorola, built around MC68030 25 MHz 32‑bit microprocessor with MC68882 floating‑point coprocessor and 4 MB parity‑enabled DRAM. It integrates abundant onboard peripherals including battery‑backed NVRAM and real‑time clock, four EIA‑232‑D serial ports, SCSI controller with DMA, Centronics‑compatible parallel printer port, Ethernet interface, watchdog timer and multi‑purpose timer channels. It acts as VMEbus master/slave and system controller, supporting A32/D32 VME bus access mode. Equipped with MVME147Bug onboard debug firmware and front‑panel status LED indicators, this discontinued legacy CPU board is widely deployed in long‑life industrial embedded VME systems, requiring anti‑static handling during installation and maintenance.

Product Features

• MC68030 CPU at 25 MHz, MC68882 floating‑point coprocessor, 4 MB parity‑check DRAM memory
• VMEbus A32/D32 master‑slave interface with full system‑controller functionality for VME backplane management
• On‑board peripherals: four EIA‑232‑D serial channels, SCSI‑DMA interface, parallel printer port, Ethernet transceiver interface
• Battery‑backed 4KB SRAM and time‑of‑day real‑time clock for persistent configuration and timestamp recording
• Four ROM / EPROM / EEPROM sockets for booting firmware and application program storage
• Hardware watchdog timer, dual 16‑bit tick timers, multi‑level VME interrupt handling capability
• Embedded MVME147Bug debug monitor firmware for board initialization, diagnosis and low‑level debugging
• Front‑panel LED status indicators: SCON, DUAL, FAIL and STATUS plus hardware Reset / Abort push‑buttons
• Double‑height 6U VME form‑factor, plug‑in installation for standard VME chassis, supports hot‑swap under proper system design
• Designed for continuous long‑term operation in industrial cabinet environment, compliant with VME bus specification

Application Scenarios

• Legacy VME‑based industrial control systems for power‑plant turbine and boiler auxiliary control racks
• Defense, aerospace and railway embedded computing platforms using VME bus architecture
• Industrial test‑and‑measurement equipment, data acquisition systems and real‑time process controllers
• Telecommunication infrastructure equipment requiring high‑reliability single‑board computing
• Retrofit and spare‑part replacement for existing installed MVME147 series legacy VME systems
• Real‑time embedded application running VxWorks or other 68K‑family real‑time operating systems

Common Problems & Troubleshooting

• FAIL LED lit, board fails boot‑up: Check VME chassis power supply voltage; re‑seat MVME147‑011 module; inspect backplane P1/P2 connector gold‑finger contamination; verify onboard battery status; run MVME147Bug diagnostic firmware for hardware check.
• Loss of configuration and clock time drift: Replace onboard backup battery; battery aging causes NVRAM and RTC data corruption after power‑cycle; avoid discharging battery during storage.
• Serial port communication abnormal: Verify EIA‑232‑D wiring, baud‑rate, parity and handshaking configuration; check transceiver chip damage caused by ESD surge; test with MVME147Bug terminal command.
• VME bus access error, cannot communicate with other VME modules: Confirm system‑controller mode setting; check VME bus arbitration and interrupt level configuration; inspect P2 backplane connection integrity.
• SCSI or Ethernet interface cannot work: Check termination resistor setting for SCSI bus; inspect external transceiver module; verify driver and firmware initialization sequence in operating‑system.
• Watchdog timer unexpected system reset: Review application software watchdog refresh logic; check CPU over‑temperature caused by cabinet poor ventilation; inspect unstable VME power rail.
• Spare‑part replacement mismatch risk: Use exact model MVME147‑011; distinguish from MVME147‑012,‑021 variants with different memory and CPU speed; strictly execute anti‑static operation during handling; firmware may need re‑download after replacement.