|
In the remote chance
that EBEs speed creates a problem with time-sensitive programs;
you have some choices on how to alleviate the problem:
Since EBE provides line-by-line speed
control of program execution, you can choose to:
-
Slow down the line-by-line
execution of all programs on the respective PE3000 from within
the " .ini " file
-
Slow down the line-by-line
execution of a program from within the program.
-
Slow down the line-by-line
execution of a portion of a program from within
the program.
Consequently, if it
is truly required, you may significantly slow the line-by-line
execution of program instructions down to MV200 or CP100 Plus speed,
or even to CP80 speed!
The following is a
comparison of times required to execute a test (no I/O) on 4
different CPUs.
PE3000 = 14 seconds
( 261 times CP80 speed )
MV200 = 915 seconds
( 4 times CP80 speed )
CP100
= 1,220 seconds ( 3 times CP80 speed )
CP80 = 3,660
seconds (Reference)
As this test
indicates, the MV200 CPU execution time can be adjusted to run at
CP80 speed or up to 4 times that speed. The PE3000 can run at CP80
speed, but also can run at any one of 261 multiples of that speed,
any of which can be assigned to the CPU or a specific program or a
specific portion of a program.
While throughput is
restricted to some degree by I/O time requirements, it is still
greatly and favorably affected by the extremely fast computing time
of the PE3000; which directly increases Test Floor efficiency and
profits.
|