Topics created by sinned6915

@sinned6915 the only limit I have found in the code is the limit on the total size of the response to the FTP command. This is approximately 9kb on Duet 3 and 5.5kb on Duet 2. Does that account for what you are seeing?

@sinned6915 I just checked the code. The M401 command does not check whether the probe has been deployed already, it always runs deployprobe.g. It then sets the "deployed by user" flag so that G30, G29 etc. commands don't attempt to deploy/retract it. Similarly, M402 always runs retractprobe.g and clears the "deployed by user" flag.

So I suggest you avoid calling M401 in that while loop, or arrange to call it only the first time.

You can read the state of the deployedByUser flag from the object mode, under sensors.probes.

@droftarts THANK YOU!
I am glad I made and installed the little logic shifter in there.

@sinned6915 How fast would you expect the mechanism to stop if it triggered an endstop? Abrupt stops can cause all sorts of problems. OTOH, nothing is more abrupt than hitting a mechanical stop at the end of an axis.

More importantly, why is your printer missing steps? That really shouldn't happen under normal operating conditions. If it is, you have some mechanical and/or configuration problems that should be fixed.

Of course, bad things can happen- there's no accounting for stray fingers/cats, dropped tools, seized bearings, etc. , but with controlled access to the machine maybe such events are rare enough that they don't require active measures.

@sinned6915
Hello, I have the same issue on PanelDue7.0/V3 controller.
I can't recompile the firmware with the modified PanelDue.cpp file because I don't have the skills. Would it be possible to share the one you use? Thanks in advance

@sinned6915 related github issue:
https://github.com/Duet3D/RepRapFirmware/issues/622

T3P3 created this issue in Duet3D/RepRapFirmware open G30 improvements #622

@sinned6915 here are some possible causes:

Shorted heater, or short between heater +ve wire and ground Blown (short circuit) stepper driver Blown (short circuit) 5V regulator

I suggest you inspect the stepper drivers and the 5V regulator U3 for signs of damage. If there are none, then disconnect all heaters and stepper motors from the Duet, replace the 7.5A fuse, and apply power again. If the fuse fails again, the problem is on the board. If not, then it's probably a heater.

@sinned6915 assuming you are running in standalone mode, I don't think the web server supports the "Expect: 100-continue" header item. Can you amend the curl command so that it isn't used?

@droftarts THANK YOU! That will work.

I missed that feature in the description of changes. I will try that.

@dc42: i am sorry if i mis-spoke.

I wrote the echo comment to read

abort "deployprobe start value Probe already picked up. Manually return probe to the dock"

Bottom line, I can not determine why the system seems to loose track of the probe pickup token.

Do you have any ideas? Can you offer any help?

I have been fighitng this for weeks, months really if you go back to my other thread on trying to pick up the probe from the bed.

Here is an example summary of my probing results-
632d1cc0-88fe-4b32-ad17-4175388f87dc-image.png

@t3p3tony
can I also send variables with M118 or 'strings-only'?

Just a sidenote: I read about SD-card stuff yesterday and I thought 'all' relevant M-codes are M20-M32.
Now I see M929 is also related to SD-card, but there was no_word about it in the other M-codes. (playing hide and seek?)
OTOH, there are M33-M35 currently not used by RRF. Why not put the M929 function there?

@sinned6915 yes, you do. 3.2.2 for it. The object model also changes somewhat between 3.1.1 and 3.2.2 so I suggest upgrading anyway

@dc42 thank you for your response.

You can have different deploy and retract files for different Z probes. Name them deployprobe0.g for Z probe 0, deployprobe1.g for Z probe 1, and so on. Similarly for the retraction files. If the file that includes the Z probe number isn't found then it falls back to the regular deployprobe.g and retractprobe.g files.