DESIGNERCOUNCIL Archives

1996

DesignerCouncil@IPC.ORG

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Received:
by ipc.org (Smail3.1.28.1 #2) id m0ualIA-0000EcC; Mon, 1 Jul 96 10:53 CDT
Old-Return-Path:
Date:
Mon, 1 Jul 96 11:01:09 CDT
Precedence:
list
Resent-From:
Resent-Sender:
DesignerCouncil-request [log in to unmask]
Mailer:
Elm [revision: 70.85]
Status:
O
X-Mailing-List:
<[log in to unmask]> archive/latest/1812
TO:
Return-Path:
<DesignerCouncil-request>
X-Status:
Resent-Message-ID:
<"dAUf-.0.ZcB.1I_rn"@ipc>
Subject:
From:
Jack Holm <[log in to unmask]>
X-Loop:
From [log in to unmask] Wed Jul 3 09:
09:27 1996
Cc:
Message-Id:
Parts/Attachments:
text/plain (30 lines)


We are starting up a project that the customer requires us to put our
CCAs on VME buss configuration.

Can any of you give me an idea if there is something special we would
have to do to comply??

It is my understanding that the VME constraint just defines board size,
and connector information.

I don't think it drives any special layout requirements, but that is why 
I am asking for you opinions.

Please be gentle.

                    thanks

                                   '''
                                  (O O)
  ============================oOO==(_)==OOo=========================
  Jack Holm                    \_/     \_/     
  PC Design "System Weenie"     /  jah  \     Phone (219) 487-6199
  ITT Aerospace/Communications (_________)    Fax   (219) 487-6033
  1919 W. Cook Road             \   _   /     E-Mail [log in to unmask]
  Fort Wayne IN. 46801           \ / \ /
  ===============================(_)=(_)============================



ATOM RSS1 RSS2