CoreXY neither X nor Y moving

droftarts

Thinking about it, it may be due to heat dissipation. The assumption is that the the X and Y driver would work hardest, so having the most copper around them makes sense, so put them in the middle.

Ian

Nemesis1782

@droftarts Ah yeah that would actually make sense. In that case I might actually move the assignments back since my X and Y motors are NEMA23's which will run at 1500mA. Can anyone confirm this is the case?

dc42

@Nemesis1782 said in CoreXY neither X nor Y moving:

@droftarts Ah yeah that would actually make sense. In that case I might actually move the assignments back since my X and Y motors are NEMA23's which will run at 1500mA. Can anyone confirm this is the case?

At 1500mA you don't need to worry about stepper motor cooling on a Duet WiFi or Ethernet. So use whichever driver assignment is convenient.

I don't know the reason why the drivers were laid out in that order on the original Duet, but @T3P3Tony might.

Nemesis1782

@dc42 Thnx for the reply. The Duet is mounted vertically and will be fitted with a low RPM fan. (Is it possible to have the FAN be controlled by Duet and Driver temperatures?)

Phaedrux

@Nemesis1782 said in CoreXY neither X nor Y moving:

(Is it possible to have the FAN be controlled by Duet and Driver temperatures?)

Yes.

https://duet3d.dozuki.com/Wiki/Mounting_and_cooling_the_board#Section_Cooling

You can tie the fan speed to the MCU temperature as a proxy for the drivers, you can add a seperate thermistor to a driver chip and use that, you simply set a fixed fan speed in your slicer start gcode and then turn it off again in the end gcode, or you can tie it to the hotend/bed temp to turn on when printing.

Nemesis1782

@Phaedrux Thnx mate, The Start/Stop GCode is actually a good idea. However, the RRF3 example is exactly what I want!

It would be nice if you could set variable frequencies though, preferably a frequency curve. That way instead of the fans turning on at a high speed intermittently they would ramp up and down as needed and thus much less annoying.

deckingman

@Nemesis1782 said in CoreXY neither X nor Y moving:

It would be nice if you could set variable frequencies though, preferably a frequency curve. That way instead of the fans turning on at a high speed intermittently they would ramp up and down as needed and thus much less annoying.

That can be already be done. Instead of setting a fixed temperature you specify a range. For example, you could use something like M106 Pn Snnn T50:80 Hn. This would start the fan turning when the temperature reached 50 deg C, ramping up proportionally to full speed at 80 deg C. You may find that at temperatures close to 50, the fan might make an annoying "buzzing" sound when PWM is at a low value. If this is the case then you can use at "L" parameter to set a minimum speed. i.e you could have say M106 Pn Snnn L125 T50:80 Hn. In this example The fan would be completely off at below 50 deg C. At 50 deg it would start to run at half speed and would stay at half speed until the temperature reached mid way between 50 and 80 (so 65) and from 65 to 80 it would ramp up from half speed to full speed.

You can also use the "X" parameter to set the maximum speed, the "B" parameter to "blip" the fan. There isn't much that you can't do. https://duet3d.dozuki.com/Wiki/Gcode#Section_M106_Fan_On

Edit. But you can only do that when there is an actual temperature which can be read. The MCU and driver temperatures are simply digital "flags" set when a certain value is exceeded.

droftarts

@deckingman said in CoreXY neither X nor Y moving:

The MCU and driver temperatures are simply digital "flags" set when a certain value is exceeded.

True of the driver temperature: see note in https://duet3d.dozuki.com/Wiki/Gcode#Section_M305_Set_temperature_sensor_parameters

Channel 1001 represents the temperature warning and overheat flags on the TMC2660, TMC2224 or other smart drivers on the Duet main board. It reads 0C when there is no warning, 100C if any driver reports over-temperature warning , and 150C if any driver reports over temperature shutdown.

But the MCU is a proper temperature sensor. It may need calibrating, however; see https://duet3d.dozuki.com/Wiki/Gcode#Section_M912_Set_electronics_temperature_monitor_adjustment

Ian

Nemesis1782

Thnx for the help guys, I'll tinker around bit with thos settings. @Calibration needed if the temp is off a few degrees that isn't a problem I'll make sure to err on te side of caution.

deckingman

@droftarts said in CoreXY neither X nor Y moving:

........................ But the MCU is a proper temperature sensor. It may need calibrating, however; see https://duet3d.dozuki.com/Wiki/Gcode#Section_M912_Set_electronics_temperature_monitor_adjustment

Ian

Of course it is - my bad.

(What is even worse is that I used to use MCU temp with a fan to cool the board when I had Duet2 - my memory just keeps getting worse the older I get).