2 bugs that need to be fixed

punamenon

Bug #1
In the new Duet Web Control 2.0.7 when updating configuration changes made in the "RRF Config Tool" the user clicks the "upload system files" button, and then selects the config.zip folder which was downloaded. The files are uploaded to the Duet board, but a restart is not performed. This means that changes do not take effect until the User manually restarts the board. The board should restart automatically so that all changes may take effect. Otherwise the user will be confused why there is no change to the behavior of their printer.

Bug#2
When setting up a Delta Printer: In the "compensation tab of the "RRF Config Tool" the "Bed Probing for Delta Calibration" point matrix generation is doubly compensating for the probe offset. Those coordinates are the points where the probe itself touches the bed, not where the nozzle touches the bed as the points are being measured. This is correct and it is the only probe offset compensation needed. It is unnecessary to make the points asymmetrical in order to avoid having the probe measuring off the edge of the bed. As you can see, the points which are generated currently are asymmetrical. All that is needed to fix this issue is to remove probe offset compensation when generating the point matrix.

Danal

@punamenon said in 2 bugs that need to be fixed:

The board should restart automatically so that all changes may take effect

You should be prompted with Yes/No option to restart. Is this not happening?

Danal

@punamenon said in 2 bugs that need to be fixed:

When setting up a Delta Printer: In the "compensation tab of the "RRF Config Tool" the "Bed Probing for Delta Calibration" point matrix generation is doubly compensating for the probe offset.

Very interesting. There seems to be some confusion about this spread across other threads. I just did some physical experiments, and for the moment, I agree that the calculator below appears to be wrong!!

https://configtool.reprapfirmware.org/

@dc42 In the log below, the printer physically moved when the G30 command was executed. This seems correct, because the G1 moved the nozzle over the 100,100 spot, and the G30 should move the probe over the 100,100 spot, then probe.

All good so far.

However... The calculator reprap online config tool (linked above) changes the coordinates in bed.g and provides a G30 with offsets when offsets are specified on the data entry forms. This does seem to be "double counting".

3/30/2020, 5:02:41 PM	G30 P0 X100 Y100 Z-99999
3/30/2020, 5:01:31 PM	G31
Current reading 0, threshold 500, trigger height 0.000, offsets X35.0 Y-55.0
3/30/2020, 5:01:21 PM	G90 X100 Y100 Z5

punamenon

@Danal I am receiving no Yes/No restart option. I don't know if it matters, but I'm running a pretty old Duet2 PCB. I just updated from firmware version 1.2

Phaedrux

@punamenon said in 2 bugs that need to be fixed:

I just updated from firmware version 1.2

What did you update to? 2.05?

If you upload the config.g on it's own does it prompt to restart?

Sounds like an issue for @chrishamm

punamenon

@Phaedrux Yes. 2.05 because 3.0 does not yet support BLTouch functionality. At least it is not an option in the online configurator.

Phaedrux

@punamenon said in 2 bugs that need to be fixed:

3.0 does not yet support BLTouch functionality.

It certainly does.

In the configurator you just need to tell it which pins you've chosen to use. It should then be an option in the probe tab.

That said, 2.05 is probably the right choice for most people for the near term which RRF3 is maturing.

chrishamm

@punamenon Thanks for reporting these issues, I've already fixed #1 in the upcoming DWC 2.1.0. I'll have a look at #2 later this week.

HenryDara

Trying to understand what is what here.... 2.0.7 that came in the last release (3.01-RC5) is the same as 2.0.7 from before? (No change?)

Should we expect anything to be fixed in the latest 2.0.7?

Should we not expect fixes until 2.1.0 is released?

I have been hoping for this one to get fixed for a while...thanks

https://forum.duet3d.com/topic/14743/heater-numbers-incorrect-in-dwc-2-0-7

droftarts

@HenryDara said in 2 bugs that need to be fixed:

Trying to understand what is what here.... 2.0.7 that came in the last release (3.01-RC5) is the same as 2.0.7 from before? (No change?)

Yes, that's right, it hasn't changed.

Should we expect anything to be fixed in the latest 2.0.7?

No, there's been no new release, or it would have a different version number.

Should we not expect fixes until 2.1.0 is released?

@chrishamm has said that these issues should be fixed in 2.1.0.

I have been hoping for this one to get fixed for a while...thanks

Me too!

Ian