Due probing again... I havent been able to use my CNC for a while

Due probing again…

I havent been able to use my CNC for a while and after almost 2 weeks gave it a try today. I planned to mill a PCB, but got probing problems again. Nothing has changed in my setup.

While I was just re-trying, getting false probes in different locations every time, I suddenly came into a situation, that when I click ‘Run Test Probe’ in Chilipeppr the Z axis goes up, and not down. Homing, homing direction, axis direction all work OK. I wonder if this is still wiring issue or something else.

@Alden_Hart @Riley_Porter_ril3y I do not really know how is it possible to perform repetitive probing process with this setup, which is Arduino Due and gShield based. I am close to give up :frowning:

@raykholo Did you manage to start testing Due+gShield? I am very interested in your results/observations.

This is not an software issue as probing works for me. The difference my hardware / wiring. If it worked once and the software did not change then almost certainly this is a hardware issue. I can’t help at the moment but I will try shortly.

@Riley_Porter_ril3y ​​ Thanks a lot for your quick reply.

Few questions:
Could you post some details of your setup, whenever possible?
Do you have any filter/debouncing
Is the probe realised as normally opened circuit?
What are the connections e.g. GND on probe tool, Probe on PCB or opposite?
What is your probe tool (I am using the bit I am going to mill with)?
Is the tool mounted to a spindle directly or via a sort of adapter/mount and eventually what type of spindle do you use?

I will try to put the probe tool into 3d printed out plastic mount in order to electrically isolate it from the spindle and see if that helps.

I have added 100uF electrolytic capacitor between probe and GND, very close to the microcontroller and got successful probing.

@sszafran hi from Malta, can u make a photo from ur probe pin with complete Z-Axis. IMHO, I guess u fight with electric noise in ur setup.

I had a flaky GRBL shield on my machine. One axis would only move in one direction occasionally. Replacing that it worked fine. It was frustrating to debug. My guess is at that x position there is some strain on a cable and it might be pulling loose creating an energetic event.

Hi @sszafran , I just got my DUE and i am about to upgrade to G2+gshield following your steps. I have just seen that to load up the G2 onto the board the process is completely different, so I downloaded a binary loader called BOSSA, but is not directly working. Any ideas on that? Thanks!

@enricodina ​ You can program Arduino Due using http://chilipeppr.com programming feature for Bossa port and choosing appropriate board type. I am not at the computer right now, but there are two possible options for Due, Synthetos gShield Programming Port or Native USB Port, depending on what port you are using while programming. I don’t remember exact names, but you will find it nearly at the end of the list. The code available via http://chilipeppr.com didn’t work for me and I recompiled it to my needs. More details in my earlier posts. I will be available online some time later (in 2-3 hrs) so I can help you if needed.

I found the way to program board as you mentioned. Board was detected on spreading boards list, selected “Due Programming Port COM 7” as it showed up. Latest ULR, then the progress bar says it “Could not find board: arduino:sam:arduino_due_x undefined”
Its strange as board was autodetected. I tried almost all different boards available to choose and get same result with them all…

@enricodina ​ You should choose ‘Synthetos TinyG2 (Due+gShield)’.