Shapeoko 4 XXL running for about a week. Bit Setter has running flawlessly multiple dozen times until today. Failure mode. During initialization, I receive a Probing Cycle Failure. I hope you can see the failure in the video. Shapeoko 4 failure during bit setting - YouTube
Based on another post with a somewhat similar issue, I disabled bit runner and have been running without it and experiencing no other related issues.
Can you capture the log output when that happens?
If you have a bitzero, make sure it’s not being triggered.
Is the red dot illuminated on the bitsetter before it’s pressed? If so, you may have a defective bitsetter cable. I had this same problem, and carbide 3d replaced the parts. Haven’t had any issues with it since.
Thanks for the reply, I reenabled the bit setter and not getting the error. I am sure it fail again and will grab the logs and look at the indicator as well as it was also recommended.
Thanks for the reply. Failure cleared, which is unfortunate as I know it will come back. I will check the light when this happens.
Bitsetter failed again and was able to capture the logs. Although I cleared the logs and copied everything around the point of failure below. Not sure if you see something here that can tell what is occurring?
M56P0
ok
N0 M5
ok
N0G0Z-5.0000
ok
N0G0X-1.2500Y-863.7500Z-5.0000
ok
N0G0Z-15.0000
ok
N0G38.2Z-155.0000F800.0
ALARM:4
GRBL_RESET
ok
Grbl 1.1f [’$’ for help]
[MSG:’$H’|’$X’ to unlock]
$X
[MSG:Caution: Unlocked]
ok
N0 G4P0.005
ok
The issue occurred again, did not see the bitsetter light illuminate, but captured the logs.
Can you send a ? through the MDI and capture the response in the log?
Your BitSetter is most likely showing as triggered. This could be
You have another probe (BitZero) that is grounded
A faulty BitSetter or wiring
EMI
Thank you for the help and information.
? gave me a syntax error.
The bit setter is working again, so will wait for it to fail again to see if I can capture the issue again and I am going to read up on EMI and ground as I did get a disconnect during a run earlier. I was not thinking that they were “possibly” ESD related.
Spoke too soon, got the error again, this time, I send /? through MDI and got the following response:
M56P0
ok
N0 M5
ok
N0 G4P0.005
ok
N0 G4P0.005
ok
N0 G4P0.005
ok
$h
ok
N0 G4P0.005
ok
N0 G4P0.005
ok
M56P0
ok
N0 M5
ok
N0 G4P0.25
ok
N0G0Z-5.0000
ok
N0G0X-432.0000Y-834.0000
ok
N0 G4P0.005
ok
N0 G4P0.005
ok
M56P0
ok
N0 M5
ok
N0G0Z-5.0000
ok
N0G0X-1.2500Y-863.7500Z-5.0000
ok
N0G0Z-15.0000
ok
N0G38.2Z-155.0000F800.0
[PRB:-1.250,-863.750,-73.800:1]
ok
N0 G4P0.005
ok
N0G0Z-69.7300
ok
N0G38.2Z-224.7300F50.0
[PRB:-1.250,-863.750,-69.770:1]
ok
N0 G4P0.005
ok
N0G0Z-5.0000
ok
N0 G4P0.005
ok
N0G0X-432.0000
ok
N0 G4P0.005
ok
M56P0
ok
N0 M5
ok
M56P0
ok
N0 M5
ok
N0G0Z-5.0000
ok
N0G0X-1.2500Y-863.7500Z-5.0000
ok
N0G0Z-15.0000
ok
N0G38.2Z-155.0000F800.0
[PRB:-1.250,-863.750,-75.525:1]
ok
N0 G4P0.005
ok
N0G0Z-71.4650
ok
N0G38.2Z-226.4650F50.0
[PRB:-1.250,-863.750,-73.225:1]
ok
N0 G4P0.005
ok
N0G0Z-5.0000
ok
N0 G4P0.005
ok
M56P0
ok
ďż˝
N0 G4P0
ok
N0 G4P0.005
ok
M56P0
ok
N0 M5
ok
G92.1
ok
G54
ok
G10L2P1X0Y0Z0
ok
G21
ok
G49
ok
G90
ok
$G
[GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F50 S0]
ok
$#
[G54:0.000,0.000,0.000]
[G55:0.000,0.000,0.000]
[G56:0.000,0.000,0.000]
[G57:0.000,0.000,0.000]
[G58:0.000,0.000,0.000]
[G59:0.000,0.000,0.000]
[G28:0.000,0.000,0.000]
[G30:0.000,0.000,0.000]
[G92:0.000,0.000,0.000]
[TLO:0.000]
[PRB:-1.250,-863.750,-73.225:1]
ok
N0 G4P0.005
ok
$$
$0=10
$1=255
$2=0
$3=5
$4=0
$5=0
$6=0
$10=255
$11=0.020
$12=0.010
$13=0
$20=0
$21=0
$22=1
$23=0
$24=100.000
$25=2000.000
$26=25
$27=3.000
$30=1000
$31=0
$32=0
$100=40.000
$101=40.000
$102=200.000
$110=10000.000
$111=10000.000
$112=1000.000
$120=500.000
$121=500.000
$122=270.000
$130=845.000
$131=850.000
$132=95.000
ok
M56P0
ok
N0 M5
ok
M56P0
ok
N0 M5
ok
N0 G4P0.005
ok
M56P0
ok
N0 M5
ok
N0 G4P0.25
ok
N0G0Z-5.0000
ok
N0G0X-432.0000Y-834.0000
ok
N0 G4P0.005
ok
N0 G4P0.005
ok
M56P0
ok
N0 M5
ok
N0G0Z-5.0000
ok
N0G0X-1.2500Y-863.7500Z-5.0000
ok
N0G0Z-15.0000
ok
N0G38.2Z-155.0000F800.0
[PRB:-1.250,-863.750,-86.190:1]
ok
N0 G4P0.005
ok
N0G0Z-82.1300
ok
N0G38.2Z-237.1300F50.0
[PRB:-1.250,-863.750,-86.155:1]
ok
N0 G4P0.005
ok
N0G0Z-5.0000
ok
N0 G4P0.005
ok
N0G0X-432.0000
ok
N0 G4P0.005
ok
M56P0
ok
N0 M5
ok
M56P0
ok
N0 M5
ok
N0 G4P0.005
ok
M56P0
ok
N0 M5
ok
N0 G4P0.25
ok
N0G0Z-5.0000
ok
N0G0X-432.0000Y-834.0000
ok
N0 G4P0.005
ok
N0 G4P0.005
ok
M56P0
ok
N0 M5
ok
N0G0Z-5.0000
ok
N0G0X-1.2500Y-863.7500Z-5.0000
ok
N0G0Z-15.0000
ok
N0G38.2Z-155.0000F800.0
[PRB:-1.250,-863.750,-15.020:1]
ok
N0 G4P0.005
ok
N0G0Z-10.8000
ok
N0G38.2Z-165.8000F50.0
ALARM:4
GRBL_RESET
ok
Grbl 1.1f [’$’ for help]
[MSG:’$H’|’$X’ to unlock]
$X
[MSG:Caution: Unlocked]
ok
N0 G4P0.005
ok
G92.1
ok
G54
ok
G10L2P1X0Y0Z0
ok
G21
ok
G49
ok
G90
ok
$G
[GC:G0 G54 G17 G21 G90 G94 M5 M9 M56 T0 F0 S0]
ok
$#
[G54:0.000,0.000,0.000]
[G55:0.000,0.000,0.000]
[G56:0.000,0.000,0.000]
[G57:0.000,0.000,0.000]
[G58:0.000,0.000,0.000]
[G59:0.000,0.000,0.000]
[G28:0.000,0.000,0.000]
[G30:0.000,0.000,0.000]
[G92:0.000,0.000,0.000]
[TLO:0.000]
[PRB:0.000,0.000,0.000:0]
ok
N0 G4P0.005
ok
M56P0
ok
N0 M5
ok
G92.1
ok
G54
ok
G10L2P1X0Y0Z0
ok
G21
ok
G49
ok
G90
ok
$G
[GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]
ok
$#
[G54:0.000,0.000,0.000]
[G55:0.000,0.000,0.000]
[G56:0.000,0.000,0.000]
[G57:0.000,0.000,0.000]
[G58:0.000,0.000,0.000]
[G59:0.000,0.000,0.000]
[G28:0.000,0.000,0.000]
[G30:0.000,0.000,0.000]
[G92:0.000,0.000,0.000]
[TLO:0.000]
[PRB:0.000,0.000,0.000:0]
ok
N0 G4P0.005
ok
$$
$0=10
$1=255
$2=0
$3=5
$4=0
$5=0
$6=0
$10=255
$11=0.020
$12=0.010
$13=0
$20=0
$21=0
$22=1
$23=0
$24=100.000
$25=2000.000
$26=25
$27=3.000
$30=1000
$31=0
$32=0
$100=40.000
$101=40.000
$102=200.000
$110=10000.000
$111=10000.000
$112=1000.000
$120=500.000
$121=500.000
$122=270.000
$130=845.000
$131=850.000
$132=95.000
ok
?
ok
N0 G4P0.5
ok
$#
[G54:0.000,0.000,0.000]
[G55:0.000,0.000,0.000]
[G56:0.000,0.000,0.000]
[G57:0.000,0.000,0.000]
[G58:0.000,0.000,0.000]
[G59:0.000,0.000,0.000]
[G28:0.000,0.000,0.000]
[G30:0.000,0.000,0.000]
[G92:0.000,0.000,0.000]
[TLO:0.000]
[PRB:0.000,0.000,0.000:0]
ok
$G
[GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]
ok
Do you have a Bit Zero as well?
I do have one of those as well.
From what I’ve gathered from hangin out on this forum, the motion contoller board only uses one input for for both the bit setter, and bit zero. So if the magnet/ground of the bitzero comes inot contact of the bit zero, or even the machine itself, it will trigger the bit setter.
Interesting. Let me see if how I store the bit zero and if that has anything to do with it. Thank you. It might explain why it fails consistently at times and works fine at other times.
I am holding out hope that your comment about the bit zero storage was my issue. I had been keeping it under the frame with the magnet attached to the frame as well. If the bit zero is up against the frame, the light remained red and I would get the failure I was experiencing. It might explain why it would fail consistently for awhile, then I would have no issues. Only time will tell, but fingers crossed. I also grounded my X, Z and extractor hoses as it was also suggested. Thank you and all the others who have joined this discussion!
I wished that I had paid more attention to your comment about the bit zero, I was getting mixed up with the bit setter. That was most likely the cause as the way I was storing it (under the frame) and the magnet attached to same frame! Thank you for your time. Time will tell. I also grounded the X,Z and extraction hose as I was getting occasional disconnects.
It’s usually option #1.
Easy thing to have happen! Two probes with one signal is unexpected.
My bitzero is set up so the it’s always grounded to the spindle, so if I so much as touch it when the BitSetter is doing its thing it throws things off. As such I keep it in a mount on the inside of the enclosure to prevent exactly this.
This topic was automatically closed after 30 days. New replies are no longer allowed.