Delta Data Systems PMAC PCI, Справочник по аппаратуре

Страница: 66 / 80

PMAC-PCI Hardware Reference
56 Software Setup
SOFTWARE SETUP
Communications
Delta Tau provides communication tools that take advantage of the PCI bus Plug and Play feature of 32-
bits Windows
©
based computers. Starting with MOTIONEXE.EXE version 10.32.00, which is included
in Pewin32 version 2.32 and newer, a PMAC2 PCI board plugged in a PCI bus slot will be recognized by
the operating system when the computer is boot up. The available PCI address, dual-ported RAM address
and Interrupt lines are set automatically by the operating system and can be checked (but not modified) in
the MOTIONEXE.EXE application or the resources page of the device manager.
PMAC I-Variables
PMAC has a large set of Initialization parameters (I-variables) that determine the personality of the card
for a specific application. Many of these are used to configure a motor properly. Once set up, these
variables may be stored in non-volatile EAROM memory (using the
SAVE
command) so the card is
always configured properly (PMAC loads the EAROM I-variable values into RAM on power-up).
The easiest way to program, setup and troubleshoot PMAC is by using the PMAC Executive Program
Pewin and its related add-on packages P1Setup and PMAC Plot. These software packages are available
from Delta Tau, ordered through Acc-9WN.
The programming features and configuration variables for the PMAC PCI are fully described in the
PMAC User and Software manuals.
Operation of the Non-Turbo CPU
When used as a non-Turbo CPU, the Flex CPU board operates in a manner that is fundamentally
compatible with older CPU designs. However, there are a few issues to note:

The Flex CPU requires the use of V1.17 or newer firmware. There are few differences between
the previous V1.16H firmware and the V1.17 firmware other than the addition of internal support
for the Flex CPU design.

Due to more advanced processor logic and the internal integration of all memory, the Flex CPU
will operate significantly faster than older non-Turbo CPU designs,
even for equivalent CPU
frequencies . The Flex CPU in a non-Turbo configuration will generally operate more than twice
as fast as older non-Turbo CPUs running at the same frequency.
This will result in significantly faster cycle times for background tasks such as PLC programs
(the frequency of interrupt-driven foreground tasks is not affected, although the increased
computational speeds permit higher frequencies for these tasks). Generally, this will not be a
problem, but if existing programs controlled timing by computational delay (e.g. number of loops
waiting), operational differences may occur.

The operational frequency of the CPU can now be set in software by new variable I46. If this
variable is set to 0, PMAC firmware looks at the jumpers (E48 on a PMAC(1), E2 and E4 on a
PMAC2) to set the operational frequency, retaining backward compatibility for 40, 60, and 80
MHz operation.. If I46 is set to a value greater than 0, the operational frequency is set to 10MHz
* (I46 + 1), regardless of the jumper setting. If the desired operational frequency is higher than
the maximum rated frequency for that CPU, the operational frequency will be reduced to the rated
maximum. It is always possible to operate the Flex CPU board at a frequency below its rated
maximum.
On a Flex CPU board configured for Option 5AF with 40 MHz maximum frequency, I46 should
be set to 3 to operate the CPU at its maximum rated frequency.