@T3P3Tony Hi, I did calculate them initially on the reprap configurator, but Y was slightly out of whack (possibly due to belt or build).
An adjustment of -10 steps per mm seems to have worked perfectly, though I admit I know far less about this stuff than almost everyone here 
@Phaedrux Embarrassingly, I didnt realise that my previous M303 hadn't been stored, so the heaters weren't actually configured! 
Unfortunately, my cubes are printing with a backwards lean, so have raised another question to see if anyone can help.
The best thing is that this is all in preparation for transitioning from a prusa clone to a hypercube evolution, so I can imagine I will have a lot more questions to ask again once I start using the new build!
Hey - thanks for the responses!
I am attaching a few different images of the most recent cube to show the lean:
As you can see, it seems to start off straight and develop the lean after about 1/5th of the print.
I shall check angles on the frame and hardware (I only have spirit levels and an inclinometer) and see if I can spot anything.
Could this be anything to do with my config?
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.1 on Wed Jun 03 2020 22:59:46 GMT+0100 (British Summer Time)
; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
;Network
M552 S1 ; enable network
M550 P"###" ; set printer name
M551 P"###" ; set password
M552 P192.168.1.13 ; set IP address and enable network
M554 P192.168.1.1 ; Gateway (not used yet)
M553 P255.255.255.0 ; Netmask
M586 P0 S1 ; enable HTTP
M586 P1 S1 ; enable FTP
M586 P2 S0 ; disable Telnet
;PanelDue
M575 P1 B57600 S1 ; Set auxiliary serial port baud rate and require checksum (for PanelDue)
; Drives
M564 H0 ; allow axis movement without homing
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S0 ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X160.00 Y150.00 Z800.00 E837.00 ; set steps per mm
M566 X500.00 Y500.00 Z12.00 E100.00 ; set maximum instantaneous speed changes (mm/min)
M203 X1500.00 Y1500.00 Z400.00 E300 ; set maximum speeds (mm/min)
M201 X800.00 Y800.00 Z240.00 E300.00 ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E1000 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
; Axis Limits
M208 X6 Y0 Z0 S1 ; set axis minimum/maximum
M208 X190 Y200 Z180 S0 ; set axis maximum
; Endstops
M574 X1 S1 P"xstop" ; configure active-low endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-low endstop for low end on Y via pin ystop
M574 Z1 S1 P"zstop" ; configure active-low endstop for low end on Z via pin zstop
; Z-Probe
M558 P0 H3 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
;M557 X0:200 Y0:200 S20 ; define mesh grid
; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H1 T35 ; set fan 0 value. Thermostatic control is turned on
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S0.5 H-1 ; set fan 1 value. Thermostatic control is turned off
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 S1 H-1 ; set fan 2 value. Thermostatic control is turned off
; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
; Misc
M501 ; read stored parameters
; Custom settings are not defined
Hi all,
Bit of a strange one for me here. I have finally managed to get to the point where I can actually print (it's a big deal for me! ).
I have started with calibration cubes, but though I have gradually managed to improve the overall quality, my prints are leaning backwards.
It started off quite severe until I slightly reduced Y steps per mm (160 to 150), but I'm concerned that if I reduce much further I will screw my whole print geometry. The lean is reduced now, but definitely still there.
I have gone to great lengths to ensure my bed is as level as possible - does anyone have any other advice?
Can't get photos or files right now, but will upload later if needed.
@JoergS5 I managed to fix it and am currently printing a calibration cube - will let you know how it goes but looking good so far...
Thanks so much for your help - it has been a long journey to get here!
@JoergS5 Afraid not - both of my heaters are now giving me faults (heating more slowly than expected). This happened yesterday too, but seemed to be fixed after I ran M303.
I am destined never to print with this board!
@JoergS5 said in Endstops not stopping motors:
@Harrynice you should also check the following chapter:
in https://duet3d.dozuki.com/Wiki/Gcode#Section_M574_RepRapFirmware_Num_3
"Endstop type S0 (active low switch) is no longer supported in M574 commands. Instead, use type S1 and invert the input by prefixing the pin name with '!'. Ex: M574 X1 S1 P"!xstop". Invert the input when using an NPN output inductive or capacitive sensor, or using a NO switch (not recommended, use a NC switch instead)."
You said you have active low endstops, so you may need the ! parameter.
I tried this again just to double check; once the '!' was added and the board rebooted, when i pressed home for any of the axes, z moved up as expected and then the other axes moved about 5mm or so in the wrong direction.
So, I removed the '!', rebooted and tried again and now all of the axes are homing properly!
I am REALLY confused now - that is the only change I made other than correcting the stop naming mistake you spotted earlier. I dont know what happened here but it looks (for the moment at least) like it is fixed!
Thank you so much for your help!
@JoergS5 said in Endstops not stopping motors:
@Harrynice What do you mean by stopping: it says immediately that endstops activated, or do you mean something else?
Sorry - not sure what you are referring to here...
@JoergS5 I do - have attached it to this post
@JoergS5 I have actually tried this; as soon as I add '!' to any of the stops, WiFi stops working...
@JoergS5 well spotted - I probably did this while troubleshooting today. Will correct it.
Hi all,
I am having a really strange issue with my endstops not working correctly. For some reason, when I attempt to home either Y or Z, they continue to move even though the endstops have been triggered. X was like this for a while but now seems to be working OK
So, to start with some basic information:
I am using a Duet 2 WiFi, firmware version 3.1.1. I have 3 standard microswitch endstops, all at low end, all active low. The board LEDs all switch off when the switches are triggered, and I can see the endstop states changing in Machine Specific settings when they are pressed.
Running M119 shows the correct endstop states, as well as 'Z-Probe: at min stop' (though I have no probe attached at the moment and I assumed it would be disabled by my M558 entry below).
I feel so close to actually starting to print now (first thing will be a mount for my probe), but so far away every time I experience an issue like this. I would really appreciate if someone could point me in the right direction please!
My config.g is below (I have attached homeall, homex, homey and homez):
; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
;Network
M552 S1 ; enable network
M550 P"#####" ; set printer name
M551 P"#####" ; set password
M552 P192.168.1.13 ; set IP address and enable network
M554 P192.168.1.1 ; Gateway (not used yet)
M553 P255.255.255.0 ; Netmask
M586 P0 S1 ; enable HTTP
M586 P1 S1 ; enable FTP
M586 P2 S0 ; disable Telnet
;PanelDue
M575 P1 B57600 S1 ; Set auxiliary serial port baud rate and require checksum (for PanelDue)
; Drives
M564 H0 ; allow axis movement without homing
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S0 ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X160.00 Y160.00 Z800.00 E837.00 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X1000.00 Y1000.00 Z250.00 E1000 ; set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z240.00 E1000.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minimum
M208 X200 Y200 Z180 S0 ; set axis maximum
; Endstops
M574 X1 S1 P"xstop" ; configure active-low endstop for low end on X via pin xstop
M574 Y1 S1 P"zstop" ; configure active-low endstop for low end on Y via pin ystop
M574 Z1 S1 P"ystop" ; configure active-low endstop for low end on Z via pin zstop
; Z-Probe
M558 P0 H3 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
;M557 X0:200 Y0:200 S20 ; define mesh grid
; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H1 T45 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on
; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
; Misc
M501 ; read stored parameters
Thanks all, I shall set it to 24v.
This is the bed I am using at the moment, but I am about to start building a hypercube evolution so will need a 300x300mm bed soon.
Anyone have any recommendations for a good one?
Hi all - wanted to ask for a quick bit of advice about my heated bed.
I am (for the moment) using a Geeetech superplate which can be set for either 12v/24v with a quick solder job. I have a 24v mean well sp-320-24 power supply.
I need to know whether to set the heatbed for 12 or 24v
I have read through 'choosing a bed heater' on the wiki, but I don't understand it all very well and have not come to any conclusions.
Can someone please advise which voltage I should set on the bed please?
@deckingman not to worry - managed to resolve the issue
@deckingman OK - I know that I have both 20 tooth pulleys and idlers, so used your calculation and have set 200 steps per mm for X & Y. The Z axes use 300mm threaded rods/leadscrews with an 8mm pitch, which via the configurator states steps per mm of 800.
So, I set these values and what do you know? My endstops have stopped working :). For some reason I am now getting a G28 X error (failed to enable endstops). Perhaps I will meet you all in my next question post?
However, testing using M564 H0 shows that my axes are now all moving the distances I was expecting them to, and so I thank you all once again!
@deckingman yes, I started with this issue not realising the difference, but have since set the configuration for 0.9 degrees. Problem is I am not entirely sure what the other settings should be - I am using 6mm (is that the belt pitch?) gates powergrip gt2 belts, the motor spindle is 5mm, but I don't know how many teeth to specify!
@zapta hi, yes that's the model. Will post up my config.g as soon as I can get to it. Thanks!
#edit - added config.g - hopefully you will be able to spot where I am going wrong?config.g
Hi all, I am hoping someone can provide me with some advice/guidance.
I have managed to get my Duet 2 WiFi working fairly consistently now, despite my lack of understanding causing various problems. However, I am really struggling to understand how I can configure it to work correctly with my current bed dimensions.
I am using the frame from my original printer (Geeetech prusa i3 pro b) but despite trying different options in the configurator or adjusting my config.g file, I cant seem to work out what I need to do to get the dimensions right.
My print area should be 200x200x180mm, but using these values doesnt seem to work. When I move axes I often get strange results (moving X to 200 takes it only halfway across the bed for example). When I send an axis to the extent of its printable area, the coordinates shown in web control do not correspond with what I was expecting (for example again, X maxima is about 335 of whatever units web control is showing me, rather than the 200 I am expecting)
I am sure this is all to do with me not understanding how to set the correct steps per mm (I am using e3d high torque motors for X, Y and both Z axes - have tried to calculate steps per mm but I am not sure if they are correct), and not understanding how microstepping affects everything, but I am baffled and could really use some help
Is anyone able to explain (in terms a simple man like me can understand) how to correctly set this up?
Amazing! It is now working again! Thank you so much for pointing this out - I could have sworn I did the upgrade to 3.0.0 first, but apparently not!
Looks like PEBKAC and issue now appears to be solved, so please accept a virtual beer from me :).