@Esteban
Problem solved!
It really wasn't a big deal, I just had two probes to configure and my Z axis end stop was one of them (I had left the basic Reprap configuration). And when probing, each probe could be individually triggered and mislead the probing by scanning the bed.
So I'm giving you the corrected configuration for those who have this problem.
Hello everyone,
I have some little problems with my motherboard, a 3 mini 5+ Ethernet.
My very first problem came this morning. I had already launched last night, a long print, which worked very well, but this morning my printer was switched on, except that it was in its initiation state, with no print status, all the heating elements were cold, and no gcode line backup... (After checking, no power failure at home)
I restarted another print. After a few hours, the printer stopped and also without any backup (although it was well configured in config.g and in any case there was no power failure whatsoever).
On the spot, I tried to execute a "resurrection" but my Y axis vibrated instead of moving, even though the nozzle wasn't blocked by the print.
I took a closer look at my power supply, but it turned out to be stable and functional.
I restarted my machine again with a Y axis that reversed direction...
Another attempt, and again vibrations, with no movement of the Y axis.
I have a mini 2 extension card, and I was able to try the same motor on other drivers. It worked perfectly.
Now for some additional information: on cura as on others, I've set a motion resolution of 0.05mm at a speed of 60mm/s. Can these interruptions be due to processor overload? Could these interruptions be due to processor overload? With an even lower resolution I had jerky movements but no lag whatsoever and a functional impression.
Then, on my mini 2 card, none of the drivers are working now. Should I buy another one, or will the problem come from the main card?
Second question:
When I scan with the SZP on my last scan line, I get an error telling me that the points have been skipped, and of course telling me the coordinates. Having scanned 400 points, I tried to reduce the mesh size by using a 25 mm square spacing. I tried to reduce the scanning speed to a very slow speed, but still obtained the same error. However, the scan on the rest of the board works fine with your correct data. I've tried to update everything again, but without success. What could be the cause?
Thank you in advance for any answers you may be able to give me.
Translated with deepl.
Hello everyone,
I'm having a problem with my homing. I have a switch to set the Z0 (in locurence at home, it triggers when the nozzle is about 1.5 mm from my platen, see homeall.g). Now, when my machine knows the position of its axis, it should be perfectly normal to send a G1 Z0 to bring the nozzle into contact with the platen... However, this is not possible.
My machine refuses to lower the axis below 0.6 mm. Finally, when I start printing, the nozzle remains +/- 0.6 mm from my platen, even when I adjust the ‘baby steps’ from the control screen. (My machine sends me an error message saying that this point is out of bounds).
However, my probe does its calibration and a scan of the plate before each print with levelling for the double Z axis, and everything goes very well (apart from an error message from my console telling me that quite a few points could not be reached: see photo). I'm also curious to know what went wrong (same error with much slower speeds).
So I'm sending you my configuration files here:
bed.g
config.g
config-override.g
homeall.g
homez.g
Thanks you
Hello everyone,
I could really use some help reconfiguring my SZP probe. Currently, when I mesh the bed, I only get heights of 0, i.e. a perfectly flat plate.
I'm making my configuration files available to you.
bed.g
config.g
homeall.g
homez.g
My probe is 12.7 mm from the base of my nozzle (Z) and 35 mm in Y (the values are already configured).
What's more, I don't have a second Z probe; the homing is done with a limit switch on the Z axis. When it's triggered, the nozzle is 1.45 mm from the bed.
Similarly, the M558.2 control also has the right values.
Thank you for any help you can give me.
@droftarts No, they're not... Which is something I'm going to do very soon.
Thank you for your feedback, I will contact support 
@dc42
Here's the answer:
M308 S10
Sensor 10 (Bobine SPZ) type Thermistor using pin (120.temp0,coiltemp), last error ok, reading 244.1, T:10000.0 B:3425.0 C:1.68e-7 R:2200.0 L:0 H:0
What's more, I've tried it on a second identical motherboard and the problem is identical.
Could it be the CAN port termination resistor ?
Hello to everyone on the forum.
I have a big problem with my SZP probe. I received it a few days ago and have been testing it. It has worked very well so far. Strangely enough, I've just switched my machine back on this morning and I can see on the Duet Web Control that my sensor is at over 200°C. (the nozzle was cold, it was the first switch on of the day).
I very quickly switched it off (you never know if it could be a short circuit or a real temperature reached) and used a laser thermometer to check if the coil or the board could be hot, but nothing.
I checked all the cables. Whether it was the CAN, the 5V power supply, and of course the FFC ribbon cable. All were OK and I did conductivity tests with my electronic tester and there again everything was fine.
So I turned my machine back on. It still showed me very high temperatures. I then looked at the values that my coil could send me and they were correct ~8000. (when I lower and raise the assembly I have values that change with consistency).
So I thought it might still work and tried a mesh...
And here's the result:
So either I've got a particularly flat chainring and axle alignment, and I'm very lucky! Or I have another problem to which I don't have the answer.
I've taken the time to review my configuration files and update all my various components to the same version. But the result is still the same.
So I'm asking for a little help ...
I'm attaching my configuration files:
bed.g
config.g
heightmap.csv
M122.txt
When I communicating with my SZP probe, it detects well and displays a very probable value, both on the Panel Duet and on the web.
I would also like to point out that when I first started using my machine, it took a few probe readings by itself, with movement on the Z axes. Unfortunately it no longer does this.
My red indicator LED works and does not flicker, but my green LED no longer lights up either at rest or when I try to communicate with the SZP.
Thank you in advance for your feedback.
@Esteban
Problem solved!
It really wasn't a big deal, I just had two probes to configure and my Z axis end stop was one of them (I had left the basic Reprap configuration). And when probing, each probe could be individually triggered and mislead the probing by scanning the bed.
So I'm giving you the corrected configuration for those who have this problem.
Bonjour tous le monde.
J'ai un petit problème avec ma sonde SZP ou du moins avec ma configuration général.
J'ai un interrupteur qui me sert de butée Z et mon SZP pour le balayage. Quand je lance mon balayage malheureusement l'interrupteur ce déclenche ce qui interrompt le processus. (l'axe touche physiquement l'interrupteur mais j'aurai aimé que la carte mère ne le prenne pas en compte)
Alors je n'arrive pas déterminer si je doit descendre mon interrupteur ou modifier mon ficher de configuration.
Je vous met donc a disposition mon fichier de configuration et mon fichier pour le mesh bed ainsi que ceux du homing.
(/assets/uploads/files/1725372078045-bed.g)[bed.g]
(/assets/uploads/files/1725372078473-config.g) [config.g]
(/assets/uploads/files/1725372177466-homeall.g) [homeall.g]
(/assets/uploads/files/1725372177489-homex.g) [homex.g]
(/assets/uploads/files/1725372177507-homey.g) [homey.g]
(/assets/uploads/files/1725372177527-homez.g) [homez.g]
Sur mon fichier de configuration mon interrupteur est K0 et j'ai un très léger offset, cela est tout a fait normal ne vous inquiétez pas les axes ne force pas dessus.
Merci de toutes l'aide que vous serrez en mesure de m'apporter.
Translated:
Hello everyone.
I have a little problem with my SZP probe or at least with my general configuration.
I have a switch that serves as a stop for me and my SZP for scanning. When I throw my swipe (start a SZP scan) unfortunately the switch this triggers what interrupts the process. (the axis physically touches the switch but I wish the motherboard wouldn't be taken into account)
So I can't figure out if I have to go down my switch or change my configuration plug.
So I'm making it available to you my configuration file and my file for the mesh bed as well as the homing files.
bed.g
config.g
homeall.g
homex.g
homey.g
homez.g
On my configuration file my switch is K0 and I have a very light offset, this is all normal don't worry about the axes don't force on it.
Thank you for all the help you can give me.
OK, thanks for your help anyway