Lost probe with 3.7.13 #1125

Attach a photo of your controller so I can see the wiring.

Send the ? command with the probe circuit inactive and active and show the response.

gpio 34 is now set to high, not low, but working in v3.7.10.

`

You had to change it to make it work in 3.7.10?

Yes, once I re-installed 3.7.10, the probe works fine. The added strange thing is that coolant is assigned to gpio 2 in config, but it’s connected to 25, my mistake. However, M8 activates gpio 25 on the board. That’s a head scratcher. I’m going to now change the gpio to 25 for coolant in config and see if M8 still works to trigger my relay.

This line
[MSG:WARN: Increasing stepping/pulse_us to the IS2 minimum value 4]

in conjunction with this line
pulse_us: 4

makes me wonder if you might not be using the config file that you think you are using.

“Yes, once I re-installed 3.7.10, the probe works fine.”

What does the “yes” refer to?

Ok, I just changed config.yaml to gpio 25 for coolant and m8 no longer works. There is most definitely something going on with pin mapping. 3.7.10 somehow has assigned hardware gpio 2 to 25 pinout?! That is according to the pinout sheet that I downloaded from the wiki.

I think you broke your config when you upgraded. You returned to the old firmware and things still did not work. You fixed some things in the config and now some stuff works.

“Yes” was in reference to your question, “you had to change to…”

Did you try fixing that in the new firmware?

Sorry, fixing what?

I was never able to get the probe to work in the new firmware, with the config.yaml I uploaded.

gpio 34 is now set to high, not low.

What was it in the new firmware?

Hi It seem’s I have the same problem since upgrading to 3.7.13 I have lost the probe.
I’m using the xPro V5 controller, the probe output is at 5v. Everything other is working fine.
I will provide the ? output tomorrow.
Regard’s
Claude

here the normal status :
< Idle MPos: -733.962,507.194,-1.003|FS:0,0|Pn:Py>
and went the probe is triggered :
‹ Idle MPos: -733-962,507.194, -1.003 55:8,0|Pn: PY|Ov: 100, 100,100>
Which is very surprising that the Override appears ! And I confirm whiteout triggering the probe I have no Ov in the status
Any Idea ?

The Ov field is issued on every tenth or every twentieth report depending on the state. It is unrelated to the probe trigger state. This behavior is inherited from classic Grbl.

Excerpt from the official Grbl documentation at https://github.com/gnea/grbl/blob/master/doc/markdown/interface.md :

 - **Override Values:**

      - `Ov:100,100,100` indicates current override values in percent of programmed values for feed, rapids, and spindle speed, respectively.

      - Override maximum, minimum, and increment sizes are all configurable within config.h. Assume that a user or OEM will alter these based on customized use-cases. Recommend not hard-coding these values into a GUI, but rather just show the actual override values and generic increment buttons.

      - Override values don't change often during a job once set and only requires intermittent refreshing. This data field appears:

        - After 10 or 20 (configurable 1-255) status reports, depending on is in a motion state or not.
        - If an override value has changed, this data field will appear immediately in the next report. However, if `WCO:` is present, this data field will be delayed one report.
        - In the second report after a reset/power-cycle.

The part about it being configurable is true only if you are willing to recompile the code.

Hello,

Ok for the override, but how can I debug/check the none working probe ?

Regard’s
Claude

Send $probe at the console, so you can show me the config.

client : Sprobe
/probe:
pin: gpio.22:low:pu
toolsetter _pin: NO_PIN check _node_start: false ok

The gpio.22 pin is used for the i2so section. You probably have errors in your startup messages about this. You can only use these pins as inputs.

After any change to your config file, check for errors in the messages.

I’m sorry, I’m not @massiveradiation 
I have not the same board and not the same configuration, maybe I should have open a new request ! Sorry for that.
As mentionned earlier I have a Xpro V5 board
Do you want me to open another request ?

This issue is getting confusing.

no problem, I open a new one.

I think this is resolved. Let us know on a new issue if the problem exists on the latest firmware.