@gloomyandy

also i am try to simulate same Gcode with RRF 3.5.0 rc4 in that only one gcode give the bad command error (2 time simulated and giving two different error which is attached in image)

also attached Gcode SS

Hey,

I am using Duet 2 wifi with RRF 3.5.0 rc3.

sudden change in jerk and acceleration after resume APF, it's set random value which is not in config and not in gcode.

gcode in which jerk is 300 mm/sec & acceleration 500 mm/s2, when i run the power failure sequence and after resume the print there is sudden vibration in X Y axis, so i am rum M204 to check it's acceleration and the result of it is 50000 mm/s2 and jerk is 600mm/s but gcode generated on jerk 300mm/s and acceleration 500 mm/s2.

so give me solution what should i do?
@dc42 @Phaedrux

Hey,
I am trying to disable wifi of Duet2 Wifi by following below on YAT terminal.
M552
M552 S-1
M552
M552 S0

But it's not stop and whenever power up it display Error: Wifi module reported: network scan failed.

Any Suggestions.

When I am printing anything I found 12V under-voltage event (9.5V)after 1 layer complete.
Error comes up when 2nd layer start printing.
This error repeat every time while printing.
If I left machine ON with extruder heater and bed heater ON, then I didn't get any error.

I am using Duet Main Board 6HC with 24V Meanwell SMPS and it's output is 24V I have verified.
Changed my extruder heater.
Checked all wiring and no lose connection.

Can you please give me advice how can I find root cause for this under voltage event?
@dc42 @Phaedrux @T3P3Tony Is there any way to troubleshoot this problem?

@dc42 hey,

After upgrading to the latest firmware version 3.5.0rc4, we observed improvement in print acceleration settings. However, the travel acceleration is taking random value: while print acceleration seems to be functioning correctly, travel acceleration values are fluctuating unexpectedly.

@droftarts Thanks Yesterday i am trying using paneldue but missed M588 s"*" so it's not working. Thank you once again.

@droftarts
David seems to be absolutely right. Thank you both of you!
When I set skew factor 0, this problem doesn't appear.

now my question is , if skew is enabled , after some printing or moves, Y position changes. On HOMEY, I see Y position as -0.6 or so. How do I set it to 0 on Yhome?

Ideally, on Homing, position should be 0, right? Please revert on this.
(note: atimes this negative value is -0.0, -0.6, -1.9 etc, on homing Y)

Thanks & Regards,
R006

@jay_s_uk
i am waiting for your reply

@droftarts, I am waiting for your response.

Please check my config.g file:

M558 K0 P11 C"100.i2c.ldc1612" F36000 T36000    ; configure SZP as probe 1, type 11, on CAN address 120
M308 A"SZP coil" S10 Y"thermistor" P"100.temp0" ; thermistor on SZP coil
G31 P500 K0 Z3 Y-17 H10                                 ; define probe 1 offsets and trigger height
M558.2 K0 S23 R164530
M558.1 K0 S2

Let me know if I am doing something wrong.

At some points, I get trigger heights like 3.00, -2.55, or -2.99.

In DWC, my Z-probe value is not steady; it fluctuates between 0, 9097, and 999999.

Additionally, I am using a proximity sensor for homing the Z-axis.

provide me solution for that.

Thank you @droftarts

There's an extra full stop after the M558.1 line in your config.g. Probably not that important:
M558.1 K0 S1.7.

it's typing mistake.

In my setup, I am using only the SZP. When I run G30 K0 S-1, it gives me the error "Probe already triggered at start of probing move."

Can I use G30 K0 S-1 to measure the height from the bed to the SZP?

I have mounted the SZP 4mm above the bed, and at X0 Y0 Z0, the calibration data is:
"Scanning probe coefficients [4.546e-1, -3.829e-4, -8.222e-10, 1.247e-15]"

Where should I set this calibration data?
@droftarts @dc42 @Phaedrux

@droftarts @dc42
hey, sorry for the late reply.

I have attached an image of the wiring for the SZP with the Duet3 and its configuration.

SZP configuration in config.g

M558 K0 P11 C"120.i2c.ldc1612" F36000 T36000    ; Configure SZP as probe 1, type 11, on CAN address 120
M308 A"SZP coil" S10 Y"thermistor" P"120.temp0" ; Thermistor on SZP coil
G31 K0 Z2 Y-17                                  ; Define probe 1 offsets and trigger height
M558.1 K0 S1.7.
M558.2 K0 S15 R101133                           ; Set drive current and reading offset

I am doing the following steps using DWC. Please check this. However, when I run G30 K0 S-1, it gives the following error:
G30 K0 S-1
Error: M300: Probe already triggered at start of probing move

DWC Commands & it's output:

G30 K0 S-1
Error: M300: Probe already triggered at start of probing move
M558.1 K0
Scanning probe coefficients [-4.805e+0, -3.410e+0, 0.000e+0, 0.000e+0]
Scanning probe coefficients [-4.805e+0, -3.410e+0, 0.000e+0, 0.000e+0], reading at trigger height 9050, RMS error 4.143mm
M558.2 K0 S-1
Calibration successful, sensor drive current is 15, offset is 135750
M558.2 K0
Sensor drive current is 15, offset is 101133
M558
Z Probe 0: type 11, input pin 120.i2c.ldc1612, min interval 2ms, dive heights 5.0,5.0mm, probe speeds 36000,36000,36000mm/min, travel speed 36000mm/min, recovery time 0.00 sec, heaters normal, max taps 1, max diff 0.03

I have some questions:

1. Is it necessary to connect the BL-Touch the first time to calibrate the Z height?
2. I am doing tabletop testing. Is this the correct way to calibrate the SZP, or should it be done on the machine?
3. Please check my configuration and wiring of the SZP. Is it correct?
4. Could you please explain a simpler way to calibrate it? I have read the documentation, but it is quite difficult to understand.

@dc42 10:30:33 I have tried building both firmware and both are giving the same error.

**** Build of configuration Release-5.0i-7.0i for project PanelDueFirmware ****
make -j8 all
/bin/sh: -c: line 1: syntax error near unexpected token (' /bin/sh: -c: line 1: /c/Program Files (x86)/GNU Arm Embedded Toolchain/10 2021.10/bin/make --no-print-directory main-build && /c/Program Files (x86)/GNU Arm Embedded Toolchain/10 2021.10/bin/make --no-print-directory post-build'
make: *** [makefile:82: all] Error 2
"make -j8 all" terminated with exit code 2. Build might be incomplete.

10:30:34 Build Failed. 1 errors, 0 warnings. (took 901ms)

10:31:11 **** Build of configuration Duet3_MB6HC for project RepRapFirmware ****
make -j8 all
/bin/sh: -c: line 1: syntax error near unexpected token (' /bin/sh: -c: line 1: /c/Program Files (x86)/GNU Arm Embedded Toolchain/10 2021.10/bin/make --no-print-directory main-build && /c/Program Files (x86)/GNU Arm Embedded Toolchain/10 2021.10/bin/make --no-print-directory post-build'
make: *** [makefile:105: all] Error 2
"make -j8 all" terminated with exit code 2. Build might be incomplete.

10:31:12 Build Failed. 1 errors, 0 warnings. (took 701ms)

How to resolve this problem?

@dc42, I’ve reinstalled everything and tried to build the firmware, but I’m encountering the following error:
14:18:51 **** Build of configuration Duet3_MB6HC for project RepRapFirmware ****
make -j8 all
/bin/sh: -c: line 1: syntax error near unexpected token (' /bin/sh: -c: line 1: /c/Program Files (x86)/GNU Arm Embedded Toolchain/10 2021.10/bin/make --no-print-directory main-build && /c/Program Files (x86)/GNU Arm Embedded Toolchain/10 2021.10/bin/make --no-print-directory post-build'
make: *** [makefile:105: all] Error 2
"make -j8 all" terminated with exit code 2. Build might be incomplete.

14:18:51 Build Failed. 1 errors, 0 warnings. (took 566ms)

@Phaedrux
Homeall.g

G91                                         
G1 H2 Z2 F100                            
G1 H1 X-300 Y-300 F600                   
G1 H2 X5 Y5 F1000                          
G1 H1 X-300 Y-300 F200                   
G1 H2 Z-5 F100
G1 H1 Z304.1 F300                             
G1 H2 Z-2 F100                            
G1 H1 Z304.1 F100
G92 X0 Y0
G90                                        
G92 Z304.1 

homex.g

G91             
G1 H2 Z2 F100  
G1 H1 X-300 F600 
G1 H2 X5 F600 
G1 H1 X-300 F200 
G1 H2 Z-2 F100
G92 X0
G90   

homey.g

G91             
G1 H2 Z2 F100   
G1 H1 Y-300 F600
G1 H2 Y5 F600 
G1 H1 Y-300 F200 
G1 H2 Z-2 F100
G92 Y0
G90              

homez.g

G91              
G1 H2 Z2 F300  
G1 H1 Z304.1 F360 
G1 H2 Z-5 F240
G1 H1 Z304.1 F200
G90
G92 Z304.1         

config.g

M552 S1                                                                                          
;M552 S-1
M586 P0 S1                                           
M586 P1 S0                                          
M586 P2 S0                                           

; Drives
M569 P0 S1                                           
M569 P1 S1                                           
M569 P2 S1                                           
M569 P3 S1 
M569 P4 S1 
M569 P5 S1   
M584 X0 Y1 Z2:3:4 E5                                    
M350 X32 Y32 I0                                        
M350 Z16 E16 I1                                      
M92 X160.0 Y160.0 Z2133.33 E932.00  
;change as per machine                   
M566 X720.00 Y720.00 Z300.00 E600.00                       
M203 X8400.00 Y8400.00 Z420.00 E8400.00          
M201 X3000.00 Y3000.00 Z30.00 E250.00                
;M-curr 
M906 X1600 Y1600 Z1600 E800 I50                      
M84 S30                                              

; Axis Limits
M208 X0 Y0 Z0 S1                                     
M208 X300 Y300 Z304.1 S0                               

; filament Sensor                           
M591 D0 P7 C"exp.e3stop" R15:300 L7 E17 S1            

; Endstops
M574 X1 S1 P"xstop"                                 
M574 Y1 S1 P"ystop"                                
M574 Z1 S1 P"zstop+e0_stop+e1_stop"                                 

; Z-Probe
M950 S0 C"exp.heater3"                               
M558 P9 C"^zprobe.in" H5 F120 T6000  
                   
G31 P500 X0 Y0 Z1.038

; Auto level, coordinates as per motor order in M584 
M671 X-17.66:297.34:140.00 Y-5.00:-5.00:327.61 S5.0 F1.2  
; define mesh grid                           
M557 X30:300 Y30:300 S20   
M376 H5                        
		
; End Limits 
M950 J1 C"exp.e4stop"  				   	 
M581 P1 T2 R0 S1                                     			     
M582 T2							     
M581 P-1 T2	                                         				     
M581 P1 T0 R0 S1                                    

;PA
M572 D0 S0.045		                             

; Bed Heater
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138       
M950 H0 C"bedheat" T0                                
M307 H0 B0 S1.00                                     
M140 H0                                             
M143 H0 S105                                         

; Extuder Heater
M308 S1 P"e0temp" Y"pt1000"                          
M950 H1 C"e0heat" T1                                 
M307 H1 B0 S1.00                                      
M143 H1 S320                                         

; cooling Fans
M950 F0 C"fan0" Q500                                 
M106 P0 S0 H-1                                       
M950 F1 C"fan1" Q500                                 
M106 P1 S0 H-1                                       

; Tools
M563 P0 D0 H1 F0                                    
G10 P0 X0 Y0 Z0                                      
G10 P0 R0 S0  
M575 P1 S1 B57600                                   
M501                                                
M911 S21 R22.5 P"M913 X0 Y0 G91 M83 G1 Z5 E-5 F1000"   
M929 S3 P"/macros/SERVICE/log/STPL_DEBUG.txt" 

Hello,

I am using a Duet 2 WiFi with RRF 3.5.2rc1.

My setup includes three Z motors connected to the Z, E1, and E2 connectors, with the X and Y motors connected to their respective axes. The motor current is configured at 1600mA for all motors, while their rated capacity is 2500mA.

;M-curr 
M906 X1600 Y1600 Z1600 E800 I50                      
M84 S30   

I have observed that when the axes are at their home positions, the motor connectors heat up significantly, which appears unusual. However, after homing, if I jog the axes, the connectors cool down to a normal temperature. Additionally, there is a fan installed that blows air directly onto the board.

What could be the cause of the connectors heating up?
Occasionally, the drivers also overheat. What might be causing this issue, and how can it be resolved?

Looking forward to your guidance. @dc42 @Phaedrux

@dc42 okay, where i need to add MSYS2 path.

@dc42
I am using the PanelDue firmware from the master branch.
However, despite following the instructions as per the duet docs I am still facing an error.

Hello,
I’m encountering an issue while trying to build the PanelDueFirmware. The error message is as follows:
**14:53:49 **** Build of configuration Release-5.0i-7.0i for project PanelDueFirmware ****
make -j8 all
make: /bin/sh: No such file or directory
make: *** [makefile:79: all] Error 127
"make -j8 all" terminated with exit code 2. Build might be incomplete.

14:53:49 Build Failed. 1 errors, 0 warnings. (took 301ms)**

Could you please provide guidance on how to resolve this issue? @dc42 @Phaedrux