Convert 6040z mks4-v controller to AXBB-E any help ?

[gurusonwheels]

exception was caused by not running the program as administrator .
once i choose to run as administrator error went away .

[gurusonwheels]

added the 20 ms to debounce .. but does not make since i had no debounce configured in mach3
with same hardware and wiring other than the axbb-e .

very strange ...

im thinking that it has something to do with
setting up the spindle with spindle relay output enabled and not setting up pins for the pwm ...
as when i got the machine this was instructions for setup spindle .
maybe im wrong just seems like the top section of uccnc spindle should be configured with something
instead of relay .

before my machine would run at 700rpm . now 700 is barely turning and you can stop with finger .

[gurusonwheels]

ok exception kept coming back . even running as admin . so i tried plugins ... it was a plugin . but not the one you thought .

the plugin causing the problem is :
ProbeIt (for UCCNC)

guess ill have to contact eric for that problem .

i fixed the spindle speed problem it was the jumper inside the axbb-e ...
changed it to 10v and speed is ok .

still have to have the 20ms debounce never used before adding axbb-e ?

what is the negative of using the 20ms ?
are there a way to get rid of ?

looks like we are almost cutting . thanks for all the help !

[cncdrive]

The inputs debounce is a digital low pass filter, it just makes the input to act slower than how fast it acts without the filter.
The AXBB-E has very fast input optocouplers with 10 MHz cut frequency, this means that it can throughput even 10 Million pulses per second.
This is useful when using fast signals like incremental encoders which requires relatively high frequency.
But because the inputs are fast they are more sensitive to noise, because even very short noise spikes gets through the optocoupler.

The only disadvantage of using the debounce filter is that the input will act slower.
With a few milliseconds to a few tens of milliseconds of debounce it will acts only as slow as inputs on a cheap Chinese breakout board with cheap slow optocouplers.

How you could get rid of using the inputs debounce is if you could reduce/elliminate the EMI noise in your system.
But again it should be not a problem to use a few to a few tens of milliseconds of debounce, it will just change the inputs to slower acting mode, the same slow as how they are in an avarage cheap BOB using cheap slow optocouplers.

[gurusonwheels]

Thanks a ton . I put 20ms in boxes and it seems to work
Just moving around manually and all . But would you go
Higher to prevent any thing random while actually cutting?

[cncdrive]

It depends on how much noise are there in your system.
Usually 20-30msec is far more than enough.
And the only downside if the value is too high is that your axis will overrun the limit switch, because the limit function will only trigger after the limit is active for the set amount of time, e.g. for 20msec.
You should take this into account, you know the max possible velocity of your axis, so you can calculate the travel distance with that speed, it is the worst case scenario for overtravel, when the axis is traveling with the maximum setup speed.
If the limit switch is placed with possible overtravel then it is usually not a problem if it overtravels a few millimeters.
But if the switch is placed in a way that overtravel hits the switch (it is bad design though) then it can be a problem, because your axis might hit the switch before it triggers the limit function and stops the axis.
So, too high debounce setting might be bad because of the possible overtravel.

[gurusonwheels]

thank you guys !

got it running with your help !