Posts made by Lorclonil

Would you do that the same way you do the h values in bed.g? For each point measured, calculate the difference from the center measurement and add/subtract it to the height map point?

I'm curious about a couple things with mesh bed leveling.

Does it move the head up and down to account for bumps or is it just a plane correction?

If you have a slight effector tilt (that is compensated for via H adjustments in the bed.g), how does the G29 command adjust for this (if at all?)

Thanks!!

Thanks for the incredibly fast response!

Setup of DuetWifi has been a breeze for the most part because of these forums and the wiki. I'm incredibly glad I decided to switch to it (and will probably end up getting a 2nd PanelDue & Duet combo for the other printer I'm working on.)

When running the Reprapfirmware configurator using version 1.17 and selecting the E3D thermistor (4719 K for the beta value and 3.166739e-6 for the C value) for the heater results in this line in config.g:

1. M305 P1 T100000 B-6788 C3.166739e-6 R4700 ; Set thermistor + ADC parameters for heater 1

E3D recommends using 4719 K for beta and 7.08e-8 for C so I manually change the C in the RepRapFirmware configurator and end up with this line in config.g:

2. M305 P1 T100000 B-6788 C7.080000e-8 R4700 ; Set thermistor + ADC parameters for heater 1

In both of these cases the configurator correctly shows 4719 K as the beta value and 3.166739e-6 and 7.08e-8 respectively in the C value column before I output the configuration files.

These don't work. The temperature reading starts to drop when you try to heat it up. I then manually changed the config.g B value to 4719 to have this line in config.g:

3. M305 P1 T100000 B4719 C7.080000e-8 R4700 ; Set thermistor + ADC parameters for heater 1

My question is: Did I do the right thing in changing the B value to 4719 (and thus is the 3rd M305 line I listed correct?)

Fantastic! I was wondering if there was a way to include both fan positions on one M563 line (glad to see there is!) Nice and elegant solution.

That's easy enough. I was just trying to keep everything going 1-1 (easier in the long run to make changes to the configuration of fans, hotends, probes, etc.) Thanks!

I was just wondering if it'd be possible to assign 2 part cooling fans (attached to Fan0 and Fan1) to one tool so that when an M106 command is sent it turns on both? (I have my hotend cooling fan connected to always on.)