We are quite busy working on the plugins and have little time to check the forums - our official support is only through emails at the moment.

We will check the issue with the decimals. Since the translation from floating point numbers to integers is done on PC (either in Mach3 or plugin), I am hopeful that this can be solved.

We have now fixed the problem with the decimals - up to 3 decimals are now allowed. Download the update 3.1.52b for the new plugin.
The plugin constantly monitors the motion parameters of Mach3 and compares them to those in PoKeys device. If parameters differ, they are updated. Specifying step value in decimals caused the plugin to constantly detect the change (due to rounding error) and was updating the parameters in device constantly, blocking the motion as the result.

I’m back, after been away for Songkhran (Thai New Year) holiday for several weeks.

I tested plugin version 3.1.53, the decimal point problem is gone. However, Fast Encoder problem still there, counter is not correct when compare to Ultra Fast Encoder . even I perform slow jog.

Originally, encoders support was designed for use with simple encoder switches (without a numeric dial). The fast encoders were later added for use with MPGs and not for providing position feedback of the stepper (ultra fast encoder can be used for this purpose).

Hi,

From my opinion speed of fast encoder (hardware interrupt, but not dedicated one) should be able to handle this, we can notice from the pace of counting and few error of counting.
There should be a bug need to be addressed. I know that finding this mysterious bug is not easy.

I'm sure you guys can do it, It's just a matter of time.

Thank you for your work,

As I noted earlier, these encoders were not designed for such job. Even interrupt events are a limited resource and a lot of other functionality can affect the performance of fast encoders (Pulse engine operation, PoIL core operation, communication, etc.).