Migrating from 2.05.1 to 3.0 and 3.4.5 ,BLTouch and Fan Issues
-
First Question: After the update It seems I also have all the Bin files of the other boards in my system folder. I thought they get deleted automatically when using the zip files for updating (42 files in total).
When you uploaded 3.4.5 on top of 3.0, all the binary files will have been uploaded to sys. If you upload 3.4.5 again, they'll go in the /firmware folder. You can clear the binary files out of /sys; it doesn't do it automatically, it just won't upload them there any more.
hotend fan does not start when the specified temperature is reached.
Currently you have
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H T45 ; set fan 1 value. Thermostatic control is turned onThe M106 line should refer to the heater that controls it, eg
M106 P1 S1 H1 T45Now my BLtouch deploys randomly when I use the fan control in DWC
I can't immediately see why this is happening. What is in deployprobe.g and retractprobe.g?
Also sendM98 P'config.g'to see if the config generates any errors.Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
@droftarts said in Migrating from 2.05.1 to 3.0 and 3.4.5 ,BLTouch and Fan Issues:
When you uploaded 3.4.5 on top of 3.0, all the binary files will have been uploaded to sys. If you upload 3.4.5 again, they'll go in the /firmware folder. You can clear the binary files out of /sys; it doesn't do it automatically, it just won't upload them there any more.
I had a look into the firmeware folder. There are also many different bin files (17) .I guess I only need "Duet2CombinedFirmware" ,"Duet2_SDiap32_WiFiEth","Duet WiFiServer" and may "DuetWiFiModule_32S3" , Right ?
@droftarts said in Migrating from 2.05.1 to 3.0 and 3.4.5 ,BLTouch and Fan Issues:
The M106 line should refer to the heater that controls it, eg M106 P1 S1 H1 T45
Fixed, Thanks!
@droftarts said in Migrating from 2.05.1 to 3.0 and 3.4.5 ,BLTouch and Fan Issues:
I can't immediately see why this is happening. What is in deployprobe.g and retractprobe.g?
Also send M98 P'config.g' to see if the config generates any errors.M98 P'config.g' ---> Warning: Macro file 'config.g' not found
2.5 Version: The Inverting was as far i know mandatory to work with my version of BLTouch
; deployprobe.g ; called to deploy a physical Z probe ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun Mar 22 2020 03:04:07 GMT+0100 (Mitteleuropäische Normalzeit) M280 P3 S10 I1 ; deploy BLTouch ; retractprobe.g ; called to retract a physical Z probe ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun Mar 22 2020 03:04:07 GMT+0100 (Mitteleuropäische Normalzeit) M280 P3 S90 I1 ; retract BLTouch3.4.5
; deployprobe.g ; called to deploy a physical Z probe ; ; generated by RepRapFirmware Configuration Tool v3.3.16 on Tue May 16 2023 18:36:49 GMT+0200 (Mitteleuropäische Sommerzeit) M280 P0 S10 ; deploy BLTouch ; retractprobe.g ; called to retract a physical Z probe ; ; generated by RepRapFirmware Configuration Tool v3.3.16 on Tue May 16 2023 18:36:49 GMT+0200 (Mitteleuropäische Sommerzeit) M280 P0 S90 ; retract BLTouchThanks!
Thomas -
@TAS_3D said in Migrating from 2.05.1 to 3.0 and 3.4.5 ,BLTouch and Fan Issues:
I had a look into the firmeware folder. There are also many different bin files (17) .I guess I only need "Duet2CombinedFirmware" ,"Duet2_SDiap32_WiFiEth","Duet WiFiServer" and may "DuetWiFiModule_32S3" , Right ?
Yes, that's correct. If you have any other files, they will just be ignored. Splitting firmware files off to the the firmware folder started with RRF v3.3, to make the sys folder easier to navigate. You'll rarely need to look in the firmware folder.
M98 P'config.g' ---> Warning: Macro file 'config.g' not found
Oops! That should be
M98 P"config.g"BLTouch: according to https://docs.duet3d.com/User_manual/Connecting_hardware/Z_probe_connecting#software-setup it looks like your BLTouch config is set up correctly. You used to have to invert in RRF2, but not in RRF3. Maybe try reflashing the firmware, and re-uploading the DWC zip file.
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
@droftarts said in Migrating from 2.05.1 to 3.0 and 3.4.5 ,BLTouch and Fan Issues:
Oops! That should be M98 P"config.g"
No Problems found
What would be the best way to reflashing within DWC , to be sure everthing is fresh without some old files which could mess something up.
Today, had some time to test my machine. In the morning everthing worked almost flawless. 5 hours later the same issue with random deploys triggered by fan happend again.
--> May I got some shorts/bad wires/ bad board exactly at the exactly at the same time as I did the update -
Update: Checked wires and connectors --> no issues found
When I switch on the cooling fan --> Bltouch goes crazy , sometimes it stops when switch the cooling off, sometimes the bltouch still randomly deploy.
After sending M208 P0 S10 and M208 P0S90 --> fan doesnt trigger bltouch anymore
All M208 codes work as they should. -
@TAS_3D I'd guess interference between the fan and the BLTouch control wire. Do they run next to each other? It could be the fan is producing a lot of interference, or that the fan's PWM frequency is just right to trigger the BLTouch - you can change the PWM frequency in the M950 command for the fan with the Q parameter. Otherwise, try shielded wire for one or both of them, or just more space between the wires.
Edit: It's possible 2.05 used a different PWM frequency for either, or both, the BLTouch control and the fan, which is why they only now start interfering. I don't remember what the defaults are in 2.05.
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
I reflashed the firmware and uploaded a new config from scratch. Did not solve the issue.
Since the problem was gone after sending manually M280 comands i guess it isn´t related to interfernce. Also the BLtouch sometimes doens´nt stop deploying after the fan speed is set to zero.
So my workaround was to place M280 comands at the end of the config.g file --> working fix; Z-Probe M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X0 Y-26 Z0.754 ; set Z probe trigger value, offset and trigger height M557 X15:195 Y15:175 S20 ; define mesh grid ; Heaters M308 S0 P"spi.cs2" Y"rtd-max31865" ; configure sensor 0 as PT100 on pin spi.cs2 M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S105 ; set temperature limit for heater 0 to 105C M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 P0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 P1 H1 T45 ; set fan 1 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 ; bugfix workaround M280 P0 S10 ; deploy BLTouch Fan M280 P0 S90 ; retract BLTouch ; MCU Temp Control M308 S3 Y"mcu-temp" A"MCU" ; defines sensor 3 as MCU temperature sensor M308 S4 Y"drivers" A"Duet stepper drivers" ; defines sensor 4 as stepper driver temperature sensor M912 P3 S-6.6 ; MCU Temp. Calibration M950 F2 C"fan2" Q500 ; create fan 2 on pin fan1 and set its frequency M106 P2 H3:4 T40 X1 ; MCU Fan Setpoint ;config-overide Settings M501 ;Read config-overideAdditionally, I set up a fan for board cooling and found out that the M106 command has some weird firmware madness going on. It is written in the Gcode dictionary that after Reprap 3.4 and newer the S parameter will be obsolete and ignored , which is not true. Actually the S parameter works as expected and is configured using the online tool and the X parameter bricks the fan control if used for the print cooling fan ( not shown in code)
M106 GCode dictionaryThomas
-
@TAS_3D S parameter is ignored on thermostatic fans only, because it is not needed. If you set X very low the fan may not turn. What setting did you use, and what was the effect?
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
@droftarts Hi, sorry for the late reply had no time for 3d-printing
I used different settings, mostly in the comand line. Result was that the S parameter works to set the fan to e.g. 70%. X-parameter did not work to set fan to e.g. 70%; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 P0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 P1 H1 T45 ; set fan 1 value. Thermostatic control is turned onThe current online config tool also uses P1 to set the fan.
Thomas
-
@TAS_3D thank you very much,the same problem here. I spent a few weeks on mine and as soon as I started to get things working I had to start work again. I'm going to spend some time with it today,thanks for the instructions.
