Bitsetter Config Woe ("Probing Cycle Failed")

CNC Machines Shapeoko
1

Bitsetter installed, connected & configured according to the instructions along with HDZ… Connect to cutter, initialize/home, gantry moves to front centre, then prompts to probe… then fails… can’t understand why the process continues to fail at exactly the same point?

Touch probe also installed (grounding clip nowhere near the base), CM build 4.0.431. All physical controller connections checked/verified, Bitsetter reconfigured multiple times, and PC re-booted)

Note: after connecting the cutter, (but ~prior~ to initiating/homing) then checking the settings, under >Active Inputs< the “PROBE” is showing active… do I have a stuck switch, or is this a bug (several others have replied to the below question with the very same issue with HDZ & Bitsetter through the “Shapeoko & Nomad Users Group (Unofficial)” on FB (Hope the following URL works!)

2

Either a stuck switch, a faulty switch, or something miswired.

I would suggest removing both Probe and BitSetter, then adding them one at a time.

1 Like
3

one gotcha I had is that I had accidentally have the probe and its little clamp touch… which blocks the bitsetter from working at all.

1 Like
4

I did double-check that (and stole an idea from another user to wrap some tape around the touch probe cord to clip the alligator clip too… my touch probe has the red/green LED (green = open circuit, red = closed circuit)… the touch probe light remains green

5

If the Probe light remains green then the problem may be a matter of where you are grounding to — there’s an odd screw on the electronics enclosure which works for this, or you can use one of the screws at a corner of the electronics — if that’s not it, contact us at support@carbide3d.com if you haven’t already and we’ll do our best to work through this with you.

1 Like
6

Thanks William, yep - the Touchprobe seems to be responding as expected (I’ve grounded the alligator clip to the front left belt tensioning bolt). This morning I took the touchprobe and daughterboard out of the equation entirely, plugging the Bitsetter directly to the “Reserved” port on my V2.4 controller… exact same issue with cycle fail, exact same place in the process.

I took another video of this and posted it on the unofficial FB group this morning, and sent both videos (the one where it fails to the soundtrack of Top Gun! with both probes connected; and the second taken this morning where the touchprobe/daughterboard are removed) over to support@carbide3d.com this am… hopefully the guys there can help shed some insight into this :wink:

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.