开云体育

Art,

Could you tell me why my pulse frequency went from 23Khz to 25Khz
after running the OCX test?

For weeks my frequency was a rock solid 25Khz (plus some small
amout) then I installed RC11 and it went to 23Khz. I unistalled the
driver - re-installed the driver multiple times no change. So last
night I ran the OCX test and it jumped back to 25KZ and has stayed
there. Have I missed some process along the way?

Jeff E.

Jeff:

The ocx test is a very bad way to measure your pulse frequency. It
uses a method where it says to the system, start counting, wait one
second and then stop counting. What is the total?
The problem here is it asks the APPLICATION system to time the one
second. One second in the app system can vary a wide margin depending
on system load and several other factors.

In the program , on the diags page, the DRIVER is told to measure
one second via the number of clock cycles send to the CPU chip, so if
your running a 700Mhz system, the driver will count the number of
interrupt cycles which occur over the period of 700,000,000 clock
cycles. This is much more accurate and is the best indicator of
actual pulse timing. The OCX test , while a good quick test, has no
meaning in the context of your pulse speed. (Remember, it was written
before Mach2 was, so its technology is somewhat behind.)

Thanks,
Art

Art,
My point was that there is some sort of interaction between Mach2 and
the OCX. I was stating that before I ran the ocx my frequecy as
measured by Mach2 was 23KHZ. After running the OCX the frequecy
measured by Mach2 is now 25KHZ.??

Jeff E.
--- In mach1mach2cnc@..., "Art Fenerty" <fenerty@a...>
wrote:

Jeff:

The ocx test is a very bad way to measure your pulse frequency. It
uses a method where it says to the system, start counting, wait one
second and then stop counting. What is the total?
The problem here is it asks the APPLICATION system to time the

one

second. One second in the app system can vary a wide margin

depending

on system load and several other factors.

In the program , on the diags page, the DRIVER is told to measure
one second via the number of clock cycles send to the CPU chip, so

if

your running a 700Mhz system, the driver will count the number of
interrupt cycles which occur over the period of 700,000,000 clock
cycles. This is much more accurate and is the best indicator of
actual pulse timing. The OCX test , while a good quick test, has no
meaning in the context of your pulse speed. (Remember, it was

written

before Mach2 was, so its technology is somewhat behind.)

Thanks,
Art

Jeff:

Hmm, I could understand if it was reverse of that, but for MAch2 to read
23 then 25 is a bit strange...

Art
www.artofcnc.ca