Probe signal not working when CYD Pendant configured

[VIPer23]

Hi everybody,

im happy to be a part of the community and I searched already the forum for a solution.

I have an MPCNC Primo build very clean (technical and electrical background) As controller I Use the Jackpot 3 Controller.

So what’s the problem.

When I use the standard config from Releases · V1EngineeringInc/FluidNC_Configs · GitHub the Probe is working and it shows the status in the WEB UI. Currently im using v3.9.9 as suggested. I tried it also with 4.0.2 but the problem is every time the same.

As soon as I activate the CYD Pendant which is wired to the RJ11 the probe pin does not work anymore.

Fluid Touch works on both versions seamlessly.

Here is the probe config:

probe:

pin: gpio.36:low

toolsetter_pin: NO_PIN

check_mode_start: true

And here the Pendant config:

Pendant:

uart2:

txd_pin: gpio.15

rxd_pin: gpio.12

rts_pin: NO_PIN

cts_pin: NO_PIN

baud: 1000000

mode: 8N1

uart_channel2:

report_interval_ms: 75

uart_num: 2

I found also out that when I use this command in the Stepper Drivers config that this deactivates the probe as well:

stealthchop_threshold: 800 # mm/min

I tried now also to swap pin 25 and I tried it also with pin 32 in the config with the pin 36 from the probe with rewiring it changes nothing on the beheavier of not working probe. But the end stops work on every pin every time. With Fluid NC version 3.9.9 and with 4.0.2.

So the probe is technically definitely correctly wired because it works with the basic config without the CYD pendant.

Here is the config from me where probe works with just the parts commented out with # which stop the probe from working.

config.yaml.zip (2.1 KB)

I measured the probe also with my multimeter, I have 3.3 v between GND and the Signal pin 36 and when I close the contact from the probe it goes down to 0V which should be exactly what we need. I tried it also with a switch between the Signal Pin 36 and GND to be sure no mistake is made with the cables. But still the same problem when I activate the CYD pendant what stops the probe signal from working. In the Fluid Web installer is then also a ? mark shown under settings.

Here is the CYD Pendant version that I use.

So I really need your help on this. I need a workaround or a hint if it’s my config or maybe it’s something that can’t work together Pendant and probe because something is used double.

Tried to solve it with AI too. But no chance.

Im thankful for all your thoughts and solution on this.

Thanks a lot

Cheers Matt

[jeyeager (Jason Yeager)]

What is the $SS output? I’m guessing there’s something it doesn’t like in your config.yaml. I think comments need to be on their own line. You can’t put a comment on the same line after the value.

[VIPer23]

Hi that with the comment was an important thing.

I have Following

Pendant:

and I think it should be commented. I removed both ## and I think that causes the troubles.

This is how it should be I guess:

#Pendant:

I will check tomorrow when Im Back at home.

Thanks, I think that’s the problem and I will try this $$ thing. never done before….

[VIPer23]

@jeyeager

$SS output

How do i do this $SS output thing? Never done before sorry for asking….

[jeyeager (Jason Yeager)]

There is no pendant tag at all. Sounds like something AI made up.

You just enter $SS in the terminal in the WebUI.

[VIPer23]

Hi this is the screenshot from the config at FluidNC_Configs/MPCNC/Jackpot3/JP3_MPCNC at main · V1EngineeringInc/FluidNC_Configs · GitHub

Guess my mistake was that I removed both ## from pendant…. Now it make sense when you say it shouldn’t be there at all.

ill try that tomorrow

Thanks, for your quick replies, I appreciate that a lot.

[jeyeager (Jason Yeager)]

If there is a # at the start of the line, that line is commented out and has no effect.

[VIPer23]

Yep i understand that but I removed the # before Pendant completely. And so I guess this causes the issues. I let u know tomorrow if it worked.

[VIPer23]

Hi Jason,

it was the mistake that I removed the # before Pendant. now all is working perfectly.

I run now on fluid NC 4.0.3 and all good.

One little thing. I installed Fluid touch 1.0.5 dev and flickering is back… it was gone in 1.0.4.

But I love the end stop probe indicators a lot

BIG THANKS

[jeyeager (Jason Yeager)]

@VIPer23

One little thing. I installed Fluid touch 1.0.5 dev and flickering is back… it was gone in 1.0.4.

Ew. I haven’t seen that issue but I suppose it’s possible due to a change I was forced to make.