Page 1 of 1

Ver 1.2110. Spindle relay + MPG: fail

PostPosted: Tue May 21, 2019 11:23 am
by Fagge
Controller AXBB-E
M3/M4 Spindle Relay: Connected to Port1 Pin 2+3

The problem: The spindle relay switching off, when i switching between the X / Y / Z buttons in the MPG / JOG menu.
But the Spindle icon in RUN menu still lights up green & indicates Spindle ON.
This wrong event always happens to me in this version "1.2110"

Re: Ver 1.2110. Spindle relay + MPG: fail

PostPosted: Tue May 21, 2019 1:32 pm
by cncdrive
Post your profile file.

Re: Ver 1.2110. Spindle relay + MPG: fail

PostPosted: Mon May 27, 2019 6:32 am
by Fagge
Here comes the Profile.
This was no problem in the previous version.
And when I installed this latest version, I didn't save any files from before. All configurations were re-made.

Re: Ver 1.2110. Spindle relay + MPG: fail

PostPosted: Mon May 27, 2019 9:37 am
by dezsoe
Do you switch the MPG axis with the external buttons or on the jog screen? (You have also some interesting input configuration on port 2.)

inp.png

Re: Ver 1.2110. Spindle relay + MPG: fail

PostPosted: Mon May 27, 2019 10:17 am
by Fagge
It doesn't matter if I press via external buttons or via the mouse in the jog screen. The spindle stops, but indicates ON.

I tried to combine Cyclestart and Pause via the same button. I will try to remove this combo...
Yes I share the Home switches with an inverted probe on the same input, when only one function is used at same time.

Re: Ver 1.2110. Spindle relay + MPG: fail

PostPosted: Mon May 27, 2019 10:24 am
by dezsoe
OK, thanks, I'll check it later today. (Now I don't have an AXBB with me.)

Re: Ver 1.2110. Spindle relay + MPG: fail

PostPosted: Wed May 29, 2019 8:09 am
by dezsoe
Sorry, I could test it only now. The issue exists.

Re: Ver 1.2110. Spindle relay + MPG: fail

PostPosted: Fri May 31, 2019 8:26 am
by Fagge
Okay.
Good to get it confirmed. Then we wait for a future update :)

Re: Ver 1.2110. Spindle relay + MPG: fail

PostPosted: Mon Jun 17, 2019 2:59 pm
by cncdrive
We could reproduce this issue and fixed it, it will be OK in the next release.