G32 Error:´´ Z probe was not triggered during probing move´´
-
@fcwilt
drives to the first probe point of mesh compension and --> g32 -->
Error: Z probe already triggered before probing move started -
only this message came
-
@barbarossa-cologne said in G32 Error:´´ Z probe was not triggered during probing move´´:
@fcwilt
drives to the first probe point of mesh compension and --> g32 -->
Error: Z probe already triggered before probing move startedAnd this was with bed.g only having the M291 command?
Frederick
-
@fcwilt yes
-
@barbarossa-cologne said in G32 Error:´´ Z probe was not triggered during probing move´´:
@fcwilt yes
And you didn't see the popup message about bed.g running?
Frederick
-
@fcwilt no. just the message you see on the screenshot.
-
@barbarossa-cologne
Hi,
Do you know how to enter commands directly into Duet Web Control using the Console page?
Frederick
-
@fcwilt yes
-
@barbarossa-cologne
Good.
Enter M98 P"bed.g" and let me know what happens.
Frederick
-
@fcwilt said in G32 Error:´´ Z probe was not triggered during probing move´´:
M98 P"bed.g"
-
@fcwilt
and bed hasn´t reached the pin of the BL. I think it goes back to the same high then the bed was before the comand started. -
@barbarossa-cologne
Well it seems the bed.g file you edited to enter the M291 command is not the bed.g file that G32 is executing.
Are you editing the bed.g file that is in the system directory - the directory where the config.g file is located?
Frederick
-
for your question:
-
@fcwilt something to do with this code in config.g?
; Z-Probe M558 P9 C"io4.in" H10 F200 T1800 ; set Z probe type to bltouch and the dive height + speeds M950 S0 C"io4.out" ; create servo pin 0 for BLTouch G31 P25 X-20 Y-20 Z2.5 ; set Z probe trigger value, offset and trigger height M557 X15:650 Y15:650 S200 ; define mesh grid
-
Hi,
Now we are getting somewhere I think.
Notice on the left hand side you have MACROS selected.
Is that correct?
If so the files there are not the system files the firmware is using.
Those file are in the SYSTEM directory - the item below the MACROS item.
Select the SYSTEM item and take a look and see what is there.
Frederick
-
@fcwilt
ahhhh I know what you mean.... at the systems page my bed.g is:; bed.g ; called to perform automatic bed compensation via G32 ; ; generated by RepRapFirmware Configuration Tool v3.1.3 on Tue Jun 23 2020 22:36:44 GMT+0200 (Mitteleuropäische Sommerzeit) M561 ; clear any bed transform G29 ; probe the bed and enable compensation
-
Hi,
Well there is the G29 that G32 has been invoking.
I think you have a problem with files being in the MACROS directory rather than the SYSTEM directory.
You are going to have to determine if the some or all files in the MACROS directory need to be moved to the SYSTEMS directory.
If the files in the SYSTEMS directory are the ones you want to keep you should delete the files in the MACROS directory that have the same name.
For example - you should have homeall.g in your SYSTEMS directory. You should NOT have homeall.g in your MACROS directory.
Think you can get this sorted out?
Frederick
-
yes.. I know. It was stupid....
Now I took every code into the systems page.
Now, I have the message ´´failed to enable endstops´´when I make a single z probe. -
; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.3 on Tue Jun 23 2020 22:36:44 GMT+0200 (Mitteleuropäische Sommerzeit) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Duet 3" ; set printer name ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S1 ; physical drive 0.2 goes forwards M569 P0.3 S1 ; physical drive 0.3 goes forwards M569 P0.4 S1 ; physical drive 0.4 goes forwards M569 P0.5 S1 ; physical drive 0.5 goes forwards M569 P1.0 S1 ; physical drive 1.0 goes forwards M569 P1.1 S1 ; physical drive 1.1 goes forwards M569 P1.2 S1 ; physical drive 1.2 goes forwards M584 X0.0 Y0.1 Z0.2:0.3:0.4:0.5 E1.0:1.1:1.2 ; set drive mapping M350 X16 Y16 Z16 E16:16:16:16:16:16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z1600.00 E1600.00:1600.00:1600.00:92.70:92.70:92.70 ; set steps per mm M566 X900.00 Y900.00 Z12.00 E120.00:120.00:120.00:120.00:120.00:120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00 E3600.00:3600.00:3600.00:1200.00:1200.00:1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z40.00 E250.00:250.00:250.00:250.00:250.00:250.00 ; set accelerations (mm/s^2) M906 X1200 Y1200 Z3000 E3000:3000:3000:1200:1200:1200 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X700 Y700 Z800 S0 ; set axis maxima ; Endstops M574 X2 S1 P"!io3.in" ; configure active-high endstop for high end on X via pin !io3.in M574 Y2 S1 P"!io0.in" ; configure active-high endstop for high end on Y via pin !io0.in ; Z-Probe M558 P9 C"io4.in" H10 F200 T1800 ; set Z probe type to bltouch and the dive height + speeds M950 S0 C"io4.out" ; create servo pin 0 for BLTouch G31 P25 X-20 Y-20 Z2.5 ; set Z probe trigger value, offset and trigger height M557 X15:650 Y15:650 S200 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H1 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S90 ; set temperature limit for heater 0 to 90C M308 S1 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; Fans M950 F0 C"out3" Q500 ; create fan 0 on pin out3 and set its frequency M106 P0 S0.8 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"out7" Q500 ; create fan 1 on pin out7 and set its frequency M106 P1 S1 H-1 ; set fan 1 value. Thermostatic control is turned off M950 F2 C"out8" Q500 ; create fan 2 on pin out8 and set its frequency M106 P2 S1 H T45 ; set fan 2 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings are not defined M671 X-12:92:92:-12 Y185:185:615:615 S2.5 ; Miscellaneous M501 ; load saved parameters from non-volatile memory M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power deploy---------------------------- ; deployprobe.g ; called to deploy a physical Z probe ; ; generated by RepRapFirmware Configuration Tool v3.1.3 on Tue Jun 23 2020 22:36:44 GMT+0200 (Mitteleuropäische Sommerzeit) M280 P0 S10 ; deploy BLTouch retract.g-------------------------------- ; retractprobe.g ; called to retract a physical Z probe ; ; generated by RepRapFirmware Configuration Tool v3.1.3 on Tue Jun 23 2020 22:36:44 GMT+0200 (Mitteleuropäische Sommerzeit) M280 P0 S90 ; retract BLTouch homez.g------------------------- ; homez.g ; called to home the Z axis ; ; generated by RepRapFirmware Configuration Tool v3.1.3 on Thu Jun 25 2020 00:21:12 GMT+0200 (Mitteleuropäische Sommerzeit) G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G90 ; absolute positioning G1 X15 Y15 F6000 ; go to first probe point G30 ; home Z by probing the bed
-
@barbarossa-cologne
Did you overwrite any files already in the SYSTEMS directory that were the correct ones?
For example if you moved a file config.g and overwrote the config.g file already in the SYSTEMS directory the file you moved may not be correct.
Frederick