Solved Pinda prob config
-
Hi,
Just finished to install and config new super pinda prob on my duet 3 board,
It works ok when homing X Y Z , but right after I get " Error ; Faild to enable endstops"
Any idea what Im doing wrong?Attached : config g , config homez , config homeall
config (3).g
homez.g
homeall.gThanks
-
Do you have a Z endstop? Or just the probe. Your config isn't clear.
; Endstops M574 X1 S1 P"io3.in" ; configure active-high endstop for low end on X via pin io3.in M574 Y1 S1 P"io4.in" ; configure active-high endstop for low end on Y via pin io4.in M574 Z1 S2 P"io7.in" ; Set endstops controlled by probe ; Z-Probe M950 S0 C"io7.out" ; create servo pin io7 for PINDA M558 P5 C"^io7.in" H5 F300 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X50 Y50 Z0.05 ; set Z probe trigger value, offset and trigger height M557 X15:400 Y15:400 S100
This would indicate you have a probe for Z.
; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Jul 27 2021 22:03:56 GMT+0300 (שעון ישראל (קיץ)) G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-905 Y-905 F1800 ; move quickly to X and Y axis endstops and stop there (first pass) G1 H2 X5 Y5 F6000 ; go back a few mm G1 H1 X-905 Y-905 F360 ; move slowly to X and Y axis endstops once more (second pass) G1 H1 Z-350 G90 ; absolute positioning G92 Z0 ; set Z position to axis minimum (you may want to adjust this) ; Uncomment the following lines to lift Z after probing G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G90 ; absolute positioning G1 H2 X0 Y0 F6000 ; go to first probe point G30 ; home Z by probing the bed
This shows trying to home Z with an endstop move before then doing a probe with G30.
If you don't have a Z endstop, remove these lines
G1 H1 Z-350 G90 ; absolute positioning G92 Z0 ; set Z position to axis minimum (you may want to adjust this)
Also you're over-using the G1 H2 command. You only need to use those when you want to move an axis before it's been homed. Like when lifting the Z axis for XY clearance. Don't use it any other time (unless you're using a delta or corexy and want to move a single motor independently).
-
Thank you so very much!
I removed that lines and its work now,
I also removed most of G1 H2 lines ,hope I did it right (attached config homeall.g)
from some reason when I upload the config.g it gives me - "error; invalid use of p parameter" -
You've removed too much. TRy this instead.
; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Jul 27 2021 22:03:56 GMT+0300 (שעון ישראל (קיץ)) G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-905 Y-905 F1800 ; move quickly to X and Y axis endstops and stop there (first pass) G1 X5 Y5 F6000 ; go back a few mm G1 H1 X-905 Y-905 F360 ; move slowly to X and Y axis endstops once more (second pass) G90 ; absolute positioning G1 X150 Y150 F6000 ; move probe to center of bed G30 ; home Z by probing the bed
@danny777 said in Pinda prob config:
when I upload the config.g it gives me - "error; invalid use of p parameter"
Can you send M98 P"config.g" in the gcode console and report what it returns?
-
Thank you for your response,
this what returns,
-
I don't think you sent the correct command. Use the gcode console tab so you can see the full result.
M98 P"config.g"
-
Like this?
-
Yes. Did you press enter? Or the send button?
-
Yes, I did
-
"error; invalid use of p parameter"
Where do you see that?
-
it showes on duet panel (led screen) when i do config.g save
-
On the gcode console tab and you send M122 and M98 P"config.g" again?
-
This is what i get
-
Have you power cycled your board recently? I can't really tell what's going on from your screen shot as it doesn't appear to be updating the text.
-
Yes I work with the machine ,
-
It looks like lots of details thet i run throough the dwc showes on the console,
for exemple , when I run mesh compensation i get this -
Are you using a raspberry pi with your Duet?
If you look at the general tab in DWC and the machine specific tab what versions are listed for the Duet and DWC?
-
Im not using a raspberry pi
version - Duet Web Control 3.1.1 -
Ok, if DWC is on 3.1.1 then I wonder what your firmware version is. Something isn't matched up.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
Upload this zip file as it is to the system tab in DWC, don't extract it first. After it is finished update the firmware and reboot. Then send M122 again and see what it reports.
-
Did it! look better but still "error; invalid use of p parameter"
03ce6d49-eec4-4e3f-a336-bdd208f1043a-image.png