Topics created by DR8

That's right dc42. I have a CoreXY and defenetly it's a problem on DWC latest release. I did the downgrade and now it's working fine. Thanks

@dr8 Glad it was an easy fix.

For anyone else seeing this the M911 S voltage level needs to be met for resume to work.

@dr8 Thanks for your report. Its good to know the reason and no doubt this will help others!

Oh, ok. Thanks alot.

The belt is tight and I retighten all the screws, pulleys and so on. I have changed the values for X=220 and Y=230 just to see what's happening. I'll post the result.

@burtoogle:

I think you should be posting this on the Cura forum (https://community.ultimaker.com/), not here, as the problem is more likely to be a slicer setting rather than a problem with the Duet config.

Sorry, you're right. I'm gonna post there.

I don't know anything about your setup but maybe your extruder can't keep up. The product of line width * layer height * print speed must be below the max value that your extruder can hack. As for infill pattern type, I almost always use zigzag which is fast to print and adheres well to the walls.

I wish you good luck, I wouldn't dream of trying to print anything at 120mm/s but, then again, my priority is quality rather than speed.

Yes they work at extremely low PWM frequencies at some PWm values, but not smoothly because of the low PWM frequency. I think the reason is that they don't start up until power has been applied for a certain length of time.

It's built in C++. See https://github.com/dc42/PanelDueFirmware/blob/master/BuildInstructions.md.

Thank you for the tool, David. It is very useful and confirmed my previous calculations were correct.

In order to move it at the back I think I must choose user specified. I also tried with sharpest corner but did not had effect.

@dc42:

the next PanelDue firmware revision.

next meaning 1.18 or later I guess - on version 1.17 the M291 command does not work.

I had an M291 P"message" S3 command in a macro and this has a disastrous effect on functionality.
As soon as I execute the macro, the status line at the top of the display shows "busy" and from that moment on I cannot access the SD1 card from the PanelDue anymore.

Any idea on a release date for a new firmware revision supporting this?

I just configured some macros to deploy and retract a probe; this requires some manual intervention on my machine so I use the M291 command - works great from the web interface.

Rob

Interesting, did you have a PanelDue plugged in?

Ok, so the problem was

; Tell the firmware where we are
G92 Z2.5

this line of gcode from homeall.g .I have disabled it and now it's working great. I can't believe, such a thiny detail… But now I understand the point.

Now, how can I make to have the ressurect.g file to be saved automatically to SD Card?

Support could be added to PanelDue and DWC to accept gcodes passed to it through messages.

So the message would include the prompt to the user, then some syntax that provides a button (or series of buttons) that the user can press that executes gcode.

Obviously, this only works well if the message is presented at the end of a gcode file, and gives the user options to initiate other gcode macros.

The power outage protection works faster in firmware 1.20beta4 so I suggest you upgrade to that version first. Read the upgrade notes, in particular the parameters to the M911 command have changed.

The only reasons I can think of why the Y motor direction would change are:

1. Firmware - as noted above, I made a change between 1.18 and 1.19, to bring RRF in line with other firmwares.

2. A change to the M569 commands in config.g, or an M569 command in some other file that is getting executed. [But AFAIK, no slicers generate M569.]

3. Reversing the Y motor connector, or swapping the wires of one of the phases in the Y motor connector. This could happen if you changed the Y motor cable.

I'm sorry, you appear to have received a faulty Duet. My guess is that there is a bad soldered joint on the SPI data output from driver 0. Either that, or the driver chip itself has a fault on that pin. Please ask for your Duet to be replaced under warranty.