Duet 2 wifi + FLSUN Q5 problems with probe
-
Howdy,
I've had my FLSUN Q5 on a shelf since I moved and had kinda forgotten about it. Today I tried to get it running. It was running a really old version of firmware, 2.0.5. I upgraded from that to 3.0, then to 3.3, then to 3.4.6. I'm guessing something changed since then because I'm now having issues with my probe. It is saying that the probe is already triggered whenever I try to run a probe. I don't know enough to be able to determine what is causing this. Any assistance would be appreciated!
4/7/2024, 5:43:35 PM m115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.6 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2023-07-21 14:08:28Here is my config.g file:
; Configuration file for Duet WiFi (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.4.1 on Sun Apr 07 2024 16:47:41 GMT-0500 (Central Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Q5Delta" ; set printer name M665 R104.3 L215 B104 H220 ; Set delta radius, diagonal rod length, printable radius and homed height M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S1 ; enable FTP M586 P2 S1 ; enable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S1 ; physical drive 3 goes forwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.02 Y79.94 Z80.07 E392.00 ; set steps per mm M566 X1200.00 Y1200.00 Z1200.00 E6000.00 ; set maximum instantaneous speed changes (mm/min) M203 X18000.00 Y18000.00 Z18000.00 E6000.00 ; set maximum speeds (mm/min) M201 X2000.00 Y2000.00 Z2000.00 E2000.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 Z0 S1 ; set minimum Z ; Endstops M574 X2 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin xstop M574 Y2 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ystop M574 Z2 S1 P"zstop" ; configure switch-type (e.g. microswitch) endstop for high end on Z via pin null ; Z-Probe M558 P5 C"zprobe.in+zprobe.mod" H5 I1 F600 T9000 ; set Z probe type to switch and the dive height + speeds G31 P25 X-2 Y-2 Z20 ; set Z probe trigger value, offset and trigger height M557 R100 S40 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp M950 H2 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H2 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 S0 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 S1 H1 T38 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"fan1" Q500 ; create fan 2 on pin fan1 and set its frequency M106 P2 S1 H1:0 T38 ; set fan 2 value. Thermostatic control is turned on ; Tools M563 P0 D0 H2 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 ; M591 D0 C3 P2 E6.0 ;This is the command for filament monitoring using an optical on/off switch M579 X1.012 Y0.9871 ; Miscellaneous M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss -
What type of probe is it?
M558 P5 C"zprobe.in+zprobe.mod" H5 I1 F600 T9000 ; set Z probe type to switch and the dive height + speedsThe
I1parameter is no longer used in RRF3. To invert the signal you'd need to invert the pin by adding a ! to the pin name.Can you send M98 P"config.g" and report any errors?
-
@Phaedrux Howdy, thank you for the reply.
It's a switch-type probe but it's weird because it's not always on the effector - you attach it just for probing and then remove it when you're done.
4/8/2024, 3:50:23 PM M98 P"config.g" HTTP is enabled on port 80 FTP is enabled on port 21 TELNET is enabled on port 23 Error: Pin 'fan1' is not free Error: Fan number 2 not foundWould the ! go in front of the zstop in the m574 line or in front of the zprobe.in+zprobe.mod part?
I'm not sure what's going on with the fans either - Everything was working in firmware version 2.0.5 but I left it sitting around for a couple of years and I didn't test it before updating the firmware the other day, so I'm not sure if the issues I'm having strictly come from the firmware change or if something happened while it was just sitting around. I'm guessing it's firmware but since I failed to test it before upgrading I can't say that for sure. Once again, thank you for the help, I really appreciate it!
-
@Phaedrux said in Duet 2 wifi + FLSUN Q5 problems with probe:
M558 P5 C"zprobe.in+zprobe.mod"
If it's just a simple switch type than the probe type configured here is not correct.
What pin is the switch actually connected to? Zstop or zprobein?
M558 P8 C"zprobe.in" is more likely.
-
@Phaedrux It's currently wired to e0_stop. It's a 3 pin connector like a normal endstop so it won't go into zprobein and there is a separate endstop plugged into zstop. I don't remember setting it up the first time but my guess is that this is the issue - when I generated the rrf 3.0 config, I used my old config.json because I couldn't remember all the things I had to change initially. The probe came up as 'null' so I tried to fix it using generic google search which is where the incorrect type line came from. I am sorry that I can't remember how I initially got it working with it plugged into e0_stop - it's just been a while. Is there a way to get it working with the current config or do I need to make physical changes?
-
Please try
M558 P8 C"e0_stop" H5 F600 T9000Test carefully by hand that the trigger works to halt motion. See here for safe testing instructions: https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_testing
If you get an error at the start og homing saying it's already triggered, then you need to invert the pin by adding a ! to the pin name, like this:
M558 P8 C"!e0_stop" -
@Phaedrux said in Duet 2 wifi + FLSUN Q5 problems with probe:
: M558 P8 C"!e0_stop"
M558 P8 C"!e0_stop" did the trick. The probe isn't giving an already triggered error anymore, however, it did expose a mechanical issue I'm having where it probes the first two points, but then when going to probe the third point, it jerks and pulls the effector up and stops triggering the probe. I am fairly sure this is some issue with one of the axis' arms but it looks like once I get that solved, it'll work fine. I really appreciate the assistance! You are awesome!
-
undefined Phaedrux marked this topic as a question
-
undefined Phaedrux has marked this topic as solved
