-
Match the complete marking
Include MVME172-333 and every visible revision or serial identity in your enquiry. Keep the same complete reference on the quotation. -
Check the offered item before ordering
Request available label and connector photos. Have your maintenance team compare the offered MVME172-333 with the installed equipment and applicable Motorola documentation.
Technical specifications for MVME172-333
-
Manufacturer:Motorola
-
Product Category:General Automation
-
Spare Part Number:MVME172-333
-
Weight:0.6 kg
-
Tariff Code:8537101190
-
Processor:60 MHz MC68060
-
Main memory:8 MB ECC DRAM
-
Storage interface:SCSI fitted for -333 assembly
-
Network interface:Ethernet fitted for -333 assembly
-
Controller family:MVME172LX
-
VME connection:P1/P2 VME interface
-
Boot monitor:172Bug firmware platform
-
Memory expansion:Configuration depends on fitted mezzanine
-
Serial configuration:Verify port type and transition connection in installed system
Information
- An MVME172LX controller provides a 68060 host for a VME installation that also uses SCSI and Ethernet.
Boot record: preserve 172Bug variables
Rear route: label storage and network leads
Acceptance: confirm memory and field traffic
The MVME172LX family uses VME host connections and a configurable boot environment. Rear transition wiring, serial access and peripheral attachments must be compared with the original slot and system drawings; an identical processor family does not prove connector equivalence.
At commissioning, inspect 172Bug startup messages and memory detection before testing storage and network traffic. Preserve boot parameters and application image from the operating unit, then validate real field communication through the installed system.
-
Motorola MVME172-333 technical reference
Original Motorola pages - PDF, 4 pages. Motorola MVME172LX VME Embedded Controller Installation and Use, MVME172-2xx/3xx assembly list. -
Motorola MVME172-333 installation guide
Prepared by Apter Power - PDF, 3 pages. Model-specific installation, electrical checks and commissioning review.
Interface scope: The -333 assembly includes SCSI and Ethernet; peripheral function still depends on the attached devices, transition hardware and installed application.
-
VME system processing
Run the established 68060 application with its original VME address and interrupt map. -
SCSI storage path
Keep boot-device ID, termination and transition-module route aligned with the existing storage chain. -
Ethernet host link
Restore network configuration and test the intended service endpoint after board startup. -
Service and diagnostics
Use 172Bug and the installed serial console path to isolate boot, memory and interface problems.
Isolate the VME supply and handle the board using ESD protection.
Inspect fitted memory hardware and compare the recorded 8 MB ECC configuration before startup.
Label SCSI, Ethernet and serial leads by actual connector and port, not by nearby board position.
Record 172Bug environment variables and storage selection before removing the current controller.
Check VME controller and interrupt settings against the chassis system map.
Prove memory diagnostics, boot device, Ethernet communication and application I/O after replacement.
Alternative Names
Technical notes
Variant boundary: The -333 ordering row has 8 MB ECC DRAM and is not the 32 MB Petra II PA-652SE configuration.
System handover: Keep the original 172Bug environment and boot-device map with the machine record before exchanging the board.
Technical reference: Motorola MVME172LX VME Embedded Controller Installation and Use. Its assembly table explicitly identifies MVME172-333.
FAQ View All FAQ
-
Which assembly facts distinguish MVME172-333 from nearby MVME172 variants?Motorola identifies -333 with a 60 MHz MC68060, 8 MB ECC DRAM, SCSI and Ethernet. Use all four attributes when screening a spare.
-
How should ECC memory be checked after installing MVME172-333?Compare detected memory with the 8 MB assembly and review 172Bug memory diagnostics before loading the application image.
-
What can prevent MVME172-333 from finding its SCSI boot device?Check the physical transition path, target ID, bus termination and saved firmware boot setting before replacing storage hardware.
-
How should Ethernet service be proved on MVME172-333?Verify physical link, configured interface parameters and successful traffic to the intended host; also test the plant application endpoint.
-
Why is the 172Bug record important when changing MVME172-333?The monitor controls board initialization and boot selection. Saved environment values help distinguish a configuration mismatch from a faulty replacement.
-
Can MVME172-333 use a MVME172PA-652SE software image without review?Do not assume so: the two boards have different documented memory architectures and platform implementations. Validate the board support package and peripheral map first.
-
What should be compared on the VME backplane for MVME172-333?Match slot function, P1/P2 seating, controller role and rear I/O wiring to the installed chassis drawing.
-
What is a meaningful completion test for MVME172-333?Pass firmware and memory checks, boot from the expected SCSI path, prove Ethernet communication and run the application I/O acceptance sequence.
Supporting new and legacy automation
-
Please try to be as accurate as possible with your search.
-
We can quote you on 1000s of specialist parts, even if they are not listed on our website.
-
We can't find any results for “”.
Related cases and sourcing guidance
View all case studiesYou May Also Like
Product Browsing History
-
Whatsapp: +86 18030235313
Send us a message. -
sales13@apterpower.com
Complete our online form. -
+86 18030235313
Speak to our team in your native language.



