Weird M665 H/R issue
Posted by SolderSucker
|
Weird M665 H/R issue October 11, 2015 05:39AM |
Registered: 8 years ago Posts: 8 |
Hi all! I've got a strange problem with my mini kossel/duet machine when calibrating, and I wondered if anybody else had come across it.
When going through my setup and endstop calibration, as per DC42's instructions, I am able to get past the paper test and zero out all of the endstops. I then adjust the delta radius (from 105.6 to 105.47) again as per the instructions and test again. This gives me a reading of 0.05 on all three towers and the centre point, indicating that the plane is flat.
Now to my thinking, I should be able to just drop the hot end using M665 H by 0.05mm and the job should be done, right? However...ANY adjustment of height using M665 results in the hot end moving anything between 5 and 20mm above the bed when the software reading for Z is zero. For example, my z height in the firmware us set to 229.89 - if adjust to 229.95 it zeros 20mm above the bed. It I use 229.90 it's 5mm above the bed...
Thinking this might be a relative move issue, I have flashed the settings and power cycled the printer. This gave the same results.
This has got me completely stumped, so if anybody can tell me what's going on, I would be very grateful!
When going through my setup and endstop calibration, as per DC42's instructions, I am able to get past the paper test and zero out all of the endstops. I then adjust the delta radius (from 105.6 to 105.47) again as per the instructions and test again. This gives me a reading of 0.05 on all three towers and the centre point, indicating that the plane is flat.
Now to my thinking, I should be able to just drop the hot end using M665 H by 0.05mm and the job should be done, right? However...ANY adjustment of height using M665 results in the hot end moving anything between 5 and 20mm above the bed when the software reading for Z is zero. For example, my z height in the firmware us set to 229.89 - if adjust to 229.95 it zeros 20mm above the bed. It I use 229.90 it's 5mm above the bed...
Thinking this might be a relative move issue, I have flashed the settings and power cycled the printer. This gave the same results.
This has got me completely stumped, so if anybody can tell me what's going on, I would be very grateful!
|
Re: Weird M665 H/R issue October 11, 2015 06:30AM |
Registered: 9 years ago Posts: 445 |
Quote
SolderSucker
Hi all! I've got a strange problem with my mini kossel/duet machine when calibrating, and I wondered if anybody else had come across it.
Now to my thinking, I should be able to just drop the hot end using M665 H by 0.05mm and the job should be done, right? However...ANY adjustment of height using M665 results in the hot end moving anything between 5 and 20mm above the bed when the software reading for Z is zero. For example, my z height in the firmware us set to 229.89 - if adjust to 229.95 it zeros 20mm above the bed. It I use 229.90 it's 5mm above the bed...
Thinking this might be a relative move issue, I have flashed the settings and power cycled the printer. This gave the same results.
This has got me completely stumped, so if anybody can tell me what's going on, I would be very grateful!
I'm not sure I follow....
You have a duet but you set Z-height in the firmware?
All the configuration of the duet is done via a configuration file (config.g) on the SD-card.
Which looks something like this:
Quote
config.g
; Configuration file for Mini Kossel kit from Think3DPrint3D
; Communication and general
M111 S0 ; Debug off
M550 PMiniKossel ; Machine name and Netbios name (can be anything you like)
M551 Preprap ; Machine password (used for FTP)
M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED ; MAC Address
;*** Adjust the IP address and gateway in the following 2 lines to suit your network
M552 P0.0.0.0 ; IP address (0 = use DHCP)
M554 P192.168.1.1 ; Gateway
M553 P255.255.255.0 ; Netmask
M555 P2 ; Set output to look like Marlin
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
; Axis and motor configuration
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M569 P4 S1 ; Drive 4 goes forwards
M574 X2 Y2 Z2 S1 ; set endstop configuration (all endstops at high end, active high)
;*** The homed height is deliberately set too high in the following - you will adjust it during calibration
M665 R105.6 L215.0 B85 H240 ; set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them
M92 X80 Y80 Z80 ; Set axis steps/mm
M906 X1000 Y1000 Z1000 E500 ; Set motor currents (mA)
M201 X1000 Y1000 Z1000 E1000 ; Accelerations (mm/s^2)
M203 X20000 Y20000 Z20000 E3600 ; Maximum speeds (mm/min)
M566 X1200 Y1200 Z1200 E1200 ; Maximum instant speed changes mm/minute
; Thermistors
;*** If you have a Duet board stickered "4.7K", change R1000 to R4700 to the following M305 commands
M305 P0 T100000 B3950 R1000 H30 L0 ; Put your own H and/or L values here to set the bed thermistor ADC correction
M305 P1 T100000 B3974 R1000 H30 L0 ; Put your own H and/or L values here to set the first nozzle thermistor ADC correction
M305 P2 T100000 B3974 R1000 H30 L0 ; Put your own H and/or L values here to set the second nozzle thermistor ADC correction
M570 S180 ; Hot end may be a little slow to heat up so allow it 180 seconds
; Tool definitions
M563 P0 D0 H1 ; Define tool 0
G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures
;*** If you have a dual-nozzle build, un-comment the next 2 lines
;M563 P1 D1 H2 ; Define tool 1
;G10 P1 S0 R0 ; Set tool 1 operating and standby temperatures
M92 E663:663 ; Set extruder steps per mm
; Z probe and compensation definition
;*** If you have an IR zprobe instead of a switch, change P4 to P1 in the following M558 command
M558 P4 X0 Y0 Z0 ; Z probe is a switch and is not used for homing any axes
G31 X0 Y0 Z4.80 P500 ; Set the zprobe height and threshold (put your own values here)
;*** If you are using axis compensation, put the figures in the following command
M556 S78 X0 Y0 Z0 ; Axis compensation here
M208 S1 Z-0.2 ; set minimum Z
;
T0 ; select first hot end
This is where you should modify your M665 command to alter your Z-height, this file is read at each boot-up so the printer will always "default" to these settings.
Edited 2 time(s). Last edit at 10/11/2015 06:35AM by Koenig.
|
Re: Weird M665 H/R issue October 11, 2015 06:37AM |
Registered: 8 years ago Posts: 8 |
Hi, yes I am aware of that. I am making adjustments using the M665 command within the config.g file to make them permanent, but also manually entering the code using the Duets web interface while testing.
So to clarify, regardless of if I adjust the home height using the web interface or within config.g I am getting the same strange result of a small adjustment to M665 resulting in a relatively huge difference in the Z height vs the reading from the duet.
Edited 1 time(s). Last edit at 10/11/2015 06:46AM by SolderSucker.
So to clarify, regardless of if I adjust the home height using the web interface or within config.g I am getting the same strange result of a small adjustment to M665 resulting in a relatively huge difference in the Z height vs the reading from the duet.
Edited 1 time(s). Last edit at 10/11/2015 06:46AM by SolderSucker.
|
Re: Weird M665 H/R issue October 11, 2015 06:53AM |
Registered: 9 years ago Posts: 445 |
|
Re: Weird M665 H/R issue October 11, 2015 08:11AM |
Registered: 8 years ago Posts: 8 |
|
Re: Weird M665 H/R issue October 11, 2015 09:27AM |
Registered: 9 years ago Posts: 445 |
|
Re: Weird M665 H/R issue October 11, 2015 11:16AM |
Registered: 10 years ago Posts: 14,672 |
SolderSucker, that behaviour sounds odd to me. Please check which firmware version you are using and upgrade to 1.09k if it is older.
Most people use the fast auto calibration these days. I am wondering whether the endstop corrections are getting re-normalised at some point when you calibrate manually, which would affect the M665 H parameter by the average endstop correction. So please try this. With the printer in the state you describe (i.e. 0.05mm too high at all 4 points), run M665 and M666 without parameters to see the existing values. Then send a new M665 H command with the adjusted parameter. Then run M665 and M666 again to see whether the new values are as expected.
If you haven't already seen it, take a look at [reprap.org].
Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod
Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
Most people use the fast auto calibration these days. I am wondering whether the endstop corrections are getting re-normalised at some point when you calibrate manually, which would affect the M665 H parameter by the average endstop correction. So please try this. With the printer in the state you describe (i.e. 0.05mm too high at all 4 points), run M665 and M666 without parameters to see the existing values. Then send a new M665 H command with the adjusted parameter. Then run M665 and M666 again to see whether the new values are as expected.
If you haven't already seen it, take a look at [reprap.org].
Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod
Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
|
Re: Weird M665 H/R issue October 12, 2015 05:39AM |
Registered: 8 years ago Posts: 8 |
Hello all,
@koenig - the maximium speed is left at the default - I limit it in the slicing software I use (Slic3r). As for the e-steps - these are calculated based on test print measurements using the formula:
// NEMA 17 motor with T2 belt and 20-tooth pulley:
(200 * 16) / (2 * 20) = 80.0
new_e_steps = old_e_steps * (100 / distance_actually_moved) … or, old_e_steps * (100 / (120 - distance_to_mark))
'The M666 values look a bit odd as well, >5mm really much.'
I'm not sure why you think that's odd? I started M665/M666 calibration with a reference H of 235 to allow plenty of travel above an below the bed during calibration, so to me these sound about right. Admittedly my Z end stop seems to be a couple of mm higher than the X/Y end stops, but that shouldn't matter when adjusting with software to my thinking - do you have a different view?
'Which version of the firmware are you using?' - it's currently shown as:
Firmware Name: RepRapFirmware
Firmware Version: 1.09c-dc42 (2015-06-25)
Web Interface Version: HTML: 1.06, JS: 1.06
@DC42 - as above, I'm using the 1.09c version of your firmware fork currently. Running the tests you suggested, I get the following:
1. Checking existing M665/M666 values are reported as expected (and match what's in the config,g file)
2. Send M665 H230.00 via the web interface
3. Run M665 - value is reported as H230.00
4. Move the hot end Z down to the bed - reported height is 3.60...
Very strange and repeatable!
I'll flash 1.09k today and report back on results.
Thanks all!
@koenig - the maximium speed is left at the default - I limit it in the slicing software I use (Slic3r). As for the e-steps - these are calculated based on test print measurements using the formula:
// NEMA 17 motor with T2 belt and 20-tooth pulley:
(200 * 16) / (2 * 20) = 80.0
new_e_steps = old_e_steps * (100 / distance_actually_moved) … or, old_e_steps * (100 / (120 - distance_to_mark))
'The M666 values look a bit odd as well, >5mm really much.'
I'm not sure why you think that's odd? I started M665/M666 calibration with a reference H of 235 to allow plenty of travel above an below the bed during calibration, so to me these sound about right. Admittedly my Z end stop seems to be a couple of mm higher than the X/Y end stops, but that shouldn't matter when adjusting with software to my thinking - do you have a different view?
'Which version of the firmware are you using?' - it's currently shown as:
Firmware Name: RepRapFirmware
Firmware Version: 1.09c-dc42 (2015-06-25)
Web Interface Version: HTML: 1.06, JS: 1.06
@DC42 - as above, I'm using the 1.09c version of your firmware fork currently. Running the tests you suggested, I get the following:
1. Checking existing M665/M666 values are reported as expected (and match what's in the config,g file)
2. Send M665 H230.00 via the web interface
3. Run M665 - value is reported as H230.00
4. Move the hot end Z down to the bed - reported height is 3.60...
Very strange and repeatable!
I'll flash 1.09k today and report back on results.
Thanks all!
|
Re: Weird M665 H/R issue October 12, 2015 06:10AM |
Registered: 10 years ago Posts: 14,672 |
I am more interested in whether the M666 values changed at any of these steps, in case they got renormalised to average zero.
Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod
Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod
Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
|
Re: Weird M665 H/R issue October 12, 2015 08:12AM |
Registered: 8 years ago Posts: 8 |
Quote
dc42
I am more interested in whether the M666 values changed at any of these steps, in case they got renormalised to average zero.
sorry DC42, I forgot to include that above - M666 showed the same values as the config.g (M666 X-3.30 Y-3.90 Z-5.85) both before and after changing the H value in M665 to 230.00
|
Re: Weird M665 H/R issue October 12, 2015 10:29AM |
Registered: 8 years ago Posts: 8 |
OK, so I flashed to 1.09k, and here's my observations.
1. Immediately up on flashing, my hot end now hits the bed at...you guessed it...3.6mm reported height.
2. M665 reports R105.49 L215 B85 H229.89 matching config.g
3. M666 reports X-3.30 Y-3.90 Z-5.85 matching config.g
4. I heated the hot end and bed, and took a new reported reading of 3.50mm
5. Setting a new H of 226.39 using the web console worked fine, and I got a +0.05 reported reading with the hot end at the X/Y/Z/C points.
6. Increased M665 to H226.44 using the web console (left R105.49 L215 B85 as is) - all good on all X/Y/Z/C points.
7. Updated config.g to include M665 R105.49 L215 B85 H226.44, restarted printer.
This all now appears to be working as normal - I need to make a minor adjustment to the Y endstop measurement based on a test print, but the M665 command changes now seems to be responding as expected. I did try to send M665 H250, and then gradually reduce it to see if I could force the bug to be reproduced, but it didn't during my testing. My conclusion, and I'm interested to hear your view DC42, is that the particular combination of 1.09c and the final M665 R setting (from 105.6 to 105.49) combination caused some issue with its calculations, and that this issue is not present in the K version.
While I have you - where can I find release notes on changes to the PanelDue and Duet firmwares? I see on GitHub that there is a newer version of the PanelDue firmware - I'm currently running 1.09 and I'm wondering what 1.11 brings. Is there a mailing or notification list I can sign up for?
Thanks for suggesting the firmware upgrade - it seems to have solved my issue!
1. Immediately up on flashing, my hot end now hits the bed at...you guessed it...3.6mm reported height.
2. M665 reports R105.49 L215 B85 H229.89 matching config.g
3. M666 reports X-3.30 Y-3.90 Z-5.85 matching config.g
4. I heated the hot end and bed, and took a new reported reading of 3.50mm
5. Setting a new H of 226.39 using the web console worked fine, and I got a +0.05 reported reading with the hot end at the X/Y/Z/C points.
6. Increased M665 to H226.44 using the web console (left R105.49 L215 B85 as is) - all good on all X/Y/Z/C points.
7. Updated config.g to include M665 R105.49 L215 B85 H226.44, restarted printer.
This all now appears to be working as normal - I need to make a minor adjustment to the Y endstop measurement based on a test print, but the M665 command changes now seems to be responding as expected. I did try to send M665 H250, and then gradually reduce it to see if I could force the bug to be reproduced, but it didn't during my testing. My conclusion, and I'm interested to hear your view DC42, is that the particular combination of 1.09c and the final M665 R setting (from 105.6 to 105.49) combination caused some issue with its calculations, and that this issue is not present in the K version.
While I have you - where can I find release notes on changes to the PanelDue and Duet firmwares? I see on GitHub that there is a newer version of the PanelDue firmware - I'm currently running 1.09 and I'm wondering what 1.11 brings. Is there a mailing or notification list I can sign up for?
Thanks for suggesting the firmware upgrade - it seems to have solved my issue!
|
Re: Weird M665 H/R issue October 12, 2015 12:19PM |
Registered: 10 years ago Posts: 14,672 |
I'm glad the firmware update fixed it.
For the PanelDue firmware change list, see the commit history in my github repo. AFAIR the main change from 1.09 to 1.10 was to number the tools from 0 instead of 1. You need this change because you are defining the first head using M563 P0 in config.g which is the standard convention now. Version 1.11 changed the user interface style, fixed a bug with deleting SD card files, and added a button for delta calibration.
Btw cold extrusion prevention is broken in Duet firmware 1.09k but will be fixed in the next release.
Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod
Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
For the PanelDue firmware change list, see the commit history in my github repo. AFAIR the main change from 1.09 to 1.10 was to number the tools from 0 instead of 1. You need this change because you are defining the first head using M563 P0 in config.g which is the standard convention now. Version 1.11 changed the user interface style, fixed a bug with deleting SD card files, and added a button for delta calibration.
Btw cold extrusion prevention is broken in Duet firmware 1.09k but will be fixed in the next release.
Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod
Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
Sorry, only registered users may post in this forum.