Topics created by danzaywer

@martinv I'm on 2.1beta4, after turned FTP off the problem not occurred yet but I restart printer for other reasons. I have the impression that the problem arises after a long period of activity .

@jay_s_uk
Thank you!
It worked

@dc42
Ok, I can try, even if I've never put my hand to the Reprap firmware I think I can do it. But I try to make another request: is it possible to insert the retraction in the special movements managed by M201.1? also would it be possible to include in the special movements also the return to position between the two probes if, for example, 2 passes are used with the Bltouch?

@danzaywer said in Manual Bed Leveling with COREXZ:

This kinematics does not support auto-calibration

Looking at the source code, it seems like CoreXZ does not allow for manual bed leveling assistant to be setup because it only is active for kinematics derived from ZLeadscrewKinematics with 2 or more leadscrews (and kinematics with their own Auto-Calibration like linear delta).

@dc42 this seems to be a suboptimal limitation on Core Kinematics/belted z designs because it also seems to block usage of manual bed leveling. Should we lodge a feature request for v3.5 to get a way to allow for more kinematics to go through manual bed leveling assistant?

@danzaywer I haven't tried virtual axes so I can't say.

I think that you can do M584 and M92 anytime, just do an M400 first to make sure that all moves have stopped? Hopefully someone can confirm?

@chrishamm
Yes, is a surface pro 7

@danzaywer I would rather have the slicer tell then firmware what sort of movements are coming up, e.g. outer perimeter, other perimeter, infill, bridging. Then the firmware could select the correct fan speeds, print speeds etc. ignoring the ones passed by the slicer. This would allow me to run exactly the same GCode on all my printers, as long as they all have the same nozzle size.

@dc42 Thank you very much! worked perfectly

@t3p3tony said in sensors.endstops[4].triggered not set until macro exit:

I understand, my point is when you go through the while loop its unlikely to actually ever match the condition during the brief point that the stall occurs

Thanks! at this point, checking the position seems to be the only way to verify that the stall has occurred

rc10 comes with it too so you don't need the one from 3.0

Normally you upload that one first and then the Duet2CombinedFirmware.bin and the dwc will ask if you want to flash it. But for some reason I cannot upload the IAP file ?!?! DWC fails somehow, so I rename IAP file to xxx.xxx upload it (it uploads normally that way) then use DWC to rename it (right click/rename) in to original name directly on the duet, then upload Duet2CombinedFirmware.bin dwc will ask if you wanna flash, you click yes and voila you are upgraded

@Danal
thanks! it worked perfectly.

@dc42

M115 FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.01-RC2 ELECTRONICS: Duet WiFi 1.02 or later + DueX5 FIRMWARE_DATE: 2020-02-18b1

The problem persist.