Posts made by Phaedrux

@fcwilt Same place. You're right though. -Y should move the nozzle to the front.

@fcwilt said in Not homing in correct direction.:

Y+ is to the back

I guess we should be specific about what is moving where. On a cartesian it can be confusing, because the bed moves back, but the nozzle is moving to the front.

@BattleDroid said in Not homing in correct direction.:

"heater 0 fault: temperature rising much more slowly than the expected 1.7 C/sec".

You'll need to PID tune your heaters.

M303 H0 S60
When it's done, send M500 to save the results.
And then add M501 to the end of your config.g

In RRF 3.2 you can tune the tool heater with M303 T0 S200 and then M500 to save it as well.

@BattleDroid said in Not homing in correct direction.:

Where I am stuck is when I home X or Y they go in the wrong direction.

Homing moves are defined in the homeall.g homex.g homey.g homez.g macros.

As long as the axis are moving in the right direction

@BattleDroid said in Not homing in correct direction.:

( X+ to the right, y- to the back, z+ up)

As you have described. and the endstops are defined at the right location. Either high end of the axis (m574 X2) or low end of the axis (M574 X1).

Then the homing moves in the homing files should move towards the endstop. + or - direction.

@bearer But then I can't pretend they are tiny floppy disks...

Can you post the results of M122?

Standalone or SBC?

SD card speed?

Give it some time for @chrishamm to see.

Here's an example using io3

https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+3+Mini+5++Guide+Part+1:+Wiring/87#s336

https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Mini+5++Guide+Part+2:+Configuration/88#s268

Is there an SD card in the Duet by chance?

Is your wiring all good? Ribbon cable?

Can you try and capture some extra data on the pi?

https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Monitoring_optional

Don't do that, it will overload the CPU. Use x16 and interpolation instead.

@Proschi78 said in Duet2 WiFi Firmware on Raise 3d E2 ?:

What should I enter?

M350 X16 Y16 Z16 E16:16 I1

Make sure your steps per mm in M92 is correct for x16.

@matt3o said in 1LC and BLTouch:

@BlueDust you can always put some solder on the tips (ONLY on low currents like those)

I'd say that's not a good idea. The solder tin doesn't compress at all like the wire strands would, so you might be get very good pressure. Back to same problem as using the bootlace ferrules.

Give the bare wires a twist with your fingers to keep them tidy and then screw them down.

Did you see the note on the release page?

https://github.com/Duet3D/RepRapFirmware/releases/tag/3.2

Users running an unstable firmware version (for example, any 3.2beta or 3.2RC version) on Duet + SBC, run sudo apt-get update followed by sudo apt-get upgrade duetsoftwareframework=3.2.0 duetcontrolserver=3.2.0 duetwebserver=3.2.0 duettools=3.2.0 duetruntime=3.2.0 duetsd=1.1.0 duetwebcontrol=3.2.0 reprapfirmware=3.2.0-1

For me, in the long run I use a separate SD card entirely for testing beta releases. Just a work around, I know, but probably best practice to keep test environment separate anyway.

https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M25_Pause_SD_print

M25 wasn't going to work.

Do not use this code to pause the print in the currently printing G-code file, use M226 instead. M226 is intended for use in the GCode file being printed, for example to pause after a particular layer has completed. So it waits until all the moves in the queue have been completed. M25 is intended for use from a different source of GCodes than the current print from SD card (like the web interface console, PanelDue or Macro).

Did you have a filament_change.g present?

Can you post the results of M122?

Can you show the heightmap on a more oblique angle? Dead on makes it hard to see the surface relief.

@Enpixa said in massive overextrusion, E-Steps are calibrated:

Filament also came out of my hotendblock.

Like out the heat break side? I think you might need to re-visit the hotend assembly.

fw 3.2 is available now. Probably a good idea to update. Not likely to solve your problems I don't think, but lots of fixes regardless.

Upload to your system tab. https://github.com/Duet3D/RepRapFirmware/releases/download/3.2/Duet2and3Firmware-3.2.zip

https://github.com/Duet3D/RepRapFirmware/releases/tag/3.2

M350 X16:16 Y16 Z16:16:16:16 E16 I1                                   ; configure microstepping with interpolation
M92 X80.00:80.00 Y80.00 Z1600.00:1600.00:1600.00:1600.00 E420.00         ; set steps per mm
M566 X900.00:900.00 Y900.00 Z60.00:60.00:60.00:60.00 E120.00          ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00:6000.00 Y6000.00 Z180.00:180.00:180.00:180.00 E1200.00   ; set maximum speeds (mm/min)
M201 X500.00:500.00 Y500.00 Z20.00:20.00:20.00:20.00 E250.00              ; set accelerations (mm/s^2)
M906 X800:800 Y800 Z900:900:900:900 E800                               ; set motor currents (mA)

should be

M350 X16 Y16 Z16 E16 I1                                   ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z1600.00 E420.00         ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00          ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00   ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00              ; set accelerations (mm/s^2)
M906 X800 Y800 Z900 E800                               ; set motor currents (mA)

Only the extruders need to be independently defined for each motor because each extruder is an independent axis. Multiple motors on an axis only get the values per axis.

@OsherHachm said in help setting z axis 4 motors and endstop and one probe:

The new problem I'm having is when I homing the X axis it's run slowly and the Z axis as well at the same time(hapooening only for the X axis).

I'm not really sure what you mean by this.

@OsherHachm said in help setting z axis 4 motors and endstop and one probe:

I'm leveling the nuzzle from the low end ( z min is close to the bed) so I decided for every axis will be one end stop.

I'm not sure what you mean by this either. Your endstops are configured at the high end of the Z axis. Are they actually located at the low end?

If you're using the probe to level, does your bed.g work correctly?

Also, if it's an IR probe, you don't need M401 and M402 in your bed.g

Do you use mesh compensation? Do you have an example heightmap image? Does it show a tilt?

@deckingman said in Error - Homing failed after upgrade to RRF3.2:

Edit. Those lines which contain {1} are just blank lines in notepad++. I have no idea why they show up as {1} when I copy and paste into this forum. Could that be clue?

The forum software seems to insert them sometimes. Not sure what kind of blank space character it's picking up, but sometimes it happens and others not.

Also, 3.2 final is out, no need for the RC2.

https://github.com/Duet3D/RepRapFirmware/releases/tag/3.2

Can you post the commands or macros you are using the create the heightmap? Does a simple g29 work to create heightmap.csv?

Setting m558 P0 and then using g29 as normal will ask you to manually jog the nozzle to touch the bed at each point.

Can you post the results of m122 please?

Try removing the z move from your command to see if it saves correctly then. Perhaps the z move is draining too much power and preventing it from writing.

There are some threads in the forum discussing adding capacitors to allow for a bit more reserve.

6-way barrier strip: two pins for main VIN and GND; two pins for the VIN and GND supply for the OUT_0 terminals; and positive and negative OUT_0 terminals. OUT_0 is intended to drive a bed heater. The ground side of OUT_0 is switched by the mosfet and the positive side is protected by a 15A fuse.