I think the many users of the Duet who have had complete success, are very happy with their purchase, and who enjoy the assistance given on this forum would disagree with you.

It seems clear from your posts that English is not your first language, so you may have misunderstood some of the Wiki instructions. For the same reason you may also not realize how rude your posts appear to an English speaker. David, Tony, and the other frequent posters here are the most helpful I’ve found on just about any forum. If you would work with them rather than arguing I’m sure you would get things worked out.

1001 is a 1k resistor. (100 x 10^1)

Thanks David. No, I don’t have a config-override.g file, but changing diagonal rod length still makes no difference. I have no idea why.

However - M579 worked perfectly! I had thought from the RepRap code help page that it only worked with cartesian printers, and not with delta, but all is good. Thank you.

I'm a little confused about the diagonal rod length set in M665 and how this interacts with G30

In config.g I have this

M665 R143.71 L290.8 B130 H375 X0.30 Y0.07 Z0.00	; set delta radius, diagonal rod length, printable radius and homed height

```(I have no config-override.g file)

and then, in bed.g, I run a 13 point 6 factor leveling ending with this:

G30 P12 X0 Y0 Z-99999 S6

My prints are all a little large in the x,y directions so I tried increasing the diagonal rod length:

M665 R143.71 L294 B130 H375 X0.30 Y0.07 Z0.00 ; set delta radius, diagonal rod length, printable radius and homed height

However, this change made no difference at all to the size of the part! Is this because the M665 is overridden by the G30? If so, how do I adjust x,y scaling?

It’s very quick so you are probably right that it’s the max Z speed. I’ll try changing that.

Is there a way to adjust the z speed that is used to move the head away from the bed when using grid auto leveling G31? I know you can set the probe speed, and the travel speed, but I’d also like to adjust the speed that the head moves away from the bed before it moves to the next point. Why? Well it just happens to hit a resonance on my printer so that short move is very noisy. I can’t work out what speed it is using.

David,

1. Are there any significant changes from the final RC to the release version?

2. Can you update using the web system from RC to release version?

Thanks!

Shen - ran another test today. Your app predicted a print time of 2 hours and 10 seconds. Actual time taken was 2 hours and 14 seconds. Pretty darn good!

@Shen:

The problem is this line in your gcode:
"G1 S1 X50 Y50 F5000: FRONT LEFT TO HEAT UP"
You used a colon instead of a semi colon. It's a part of your starting gcode that's why none of your file works. I should have used some kind of gcode error handling, but I haven't got a change to work on it yet.

Well, so I did. Doh! Thank you for spotting that. Page works as expected now. (As you knew it would. :- ) )

@Shen:

Can you provide the gcode files? I have been updating the JavaScript files, if your browser caches the javascript files and one of the JavaScript file is not up to date, you might see that error.

I cleared the browser caches, and even tried a completely different browser (Opera this time) but still always get the same error I'm afraid. Line 509 and line 420 of the js look to be recursive in some way: [c]calculateTimeByAcceleration(gcode.nextMovementGcode);[/c]

Here's a sample gcode file https://www.dropbox.com/s/1eyzuovyeoioe0f/ipadmount.gcode?dl=0