VMIVME-7698 VMIVME-7698-140 350-017698-140 A power component board

Connector Function:
P3:COM1/COM2
J3:Video Connector
J1:Ethernet Connector

Category: SKU: VMIVME-7698-140 Tag:
Whatsapp:+86 13313705507
WeChat:+86 13313705507
E-mail:geabbdcs@gmail.com
Contacts:KEN HE

Description

Introduction

VMIC’s VMIVME-7698 is a complete IBM PC/AT-compatible Celeron processor-based computer with the additional benefits of single Eurocard construction and full compatibility with the VMEbus Specification Rev. C.1. The VMIVME-7698, with advanced VMEbus interface and RAM that is dual-ported to the VMEbus, is ideal for multiprocessor applications.

The single CPU board functions as a standard PC/AT, executing a PC/AT-type power-on self-test, then boots up MS-DOS, Windows 95, Windows NT, or any other PC/AT-compatible operating system. The PC/AT mode of the VMIVME-7698 is discussed in Chapter 3 of this manual.

The VMIVME-7698 also operates as a VMEbus controller and interacts with other VMEbus modules via the on-board PCI-to-VMEbus bridge and the Endian conversion hardware.

The VMIVME-7698 may be accessed as a VMEbus slave board. The VMEbus functions are available by programming the VMIVME-7698’s PCI-to-VMEbus bridge according to the references defined in this volume and/or in the second volume dedicated to the optional PCI-to-VMEbus interface board titled: VMIVME-7698 Tundra Universe II™-Based VMEbus Interface Product Manual (document No. 500-007698-001 Rev. A).

The VMIVME-7698 programmer may quickly and easily control all the VMEbus functions simply by linking to a library of VMEbus interrupt and control functions. This library is available with VMIC’s VMISFT-9420 IOWorks Access software for Windows NT users.

The VMIVME-7698 also provides capabilities beyond the features of a typical PC/AT-compatible CPU including general-purpose timers, a programmable watchdog timer, a bootable flash disk system, and nonvolatile, battery-backed SRAM. These features make the unit ideal for embedded applications. These nonstandard PC/AT functions are discussed in Chapter 4 of this manual.

 

Fault situation of DCS during production process
Each manufacturer’s DCS has its own characteristics, so the analysis and handling of its faults are not the same. However, in summary, the obstacles caused by DCS in the second or above categories of the unit can be divided into three categories:

(1) The system itself has issues, including design and installation defects, software and hardware failures, etc.

(2) Faults caused by human factors, including personnel caused misoperations, incomplete management systems, and implementation of execution links.

(3) DCS malfunction caused by external environmental issues in the system. Abnormal conditions are caused by factors such as high or low ambient temperature, humidity, dust, vibration, and small animals.

 

Examples of problems and faults with DCS itself
This type of fault is common in the production process, mainly including system design and installation defects, controller (DPU or CPU) crashes, network disconnection and other faults, operator station black screen, network communication blockage, software defects, low system configuration, and problems with interfaces with other systems and equipment.