@tecno said in Motors move wrong way:

@dougal1957

So M584 line has to be X0 Y1 Z2 and E4 or E5 or just E4 no x/y/z?

I am just about to go out but I will get you a copy of my Config.g

; General preferences M575 P1 S1 B57600 ; enable support for PanelDue G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Delta" ; set printer name M665 R239.403 L450.7 B175 H401 ; 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 ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S1 ; enable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S1 ; physical drive 3 goes forwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X200.00 Y200.00 Z200.00 E2500.00 ; set steps per mm M566 X54000.00 Y54000.00 Z54000.00 E2400.00 ; set maximum instantaneous speed changes (mm/min) M203 X1080000.00 Y1080000.00 Z1080000.00 E144000.00 ; set maximum speeds (mm/min) M201 X1000.00 Y1000.00 Z1000.00 E120.00 ; set accelerations (mm/s^2) M906 X1000 Y1000 Z1000 E500 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 Z0 S1 ; set minimum Z ; Endstops M574 X2 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin xstop M574 Y2 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ystop M574 Z2 S1 P"zstop" ; configure switch-type (e.g. microswitch) endstop for high end on Z via pin zstop ; Z-Probe M558 P5 R0.4 C"zprobe.in+zprobe.mod" H5 F1200 T6000 ; set Z probe type to effector and the dive height + speeds G31 P500 X0 Y0 Z0.1 ; set Z probe trigger value, offset and trigger height M557 R85 S20 ; define mesh grid ; Heaters M308 S0 P"spi.cs2" Y"rtd-max31865" F50 ;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 S75 ; set temperature limit for heater 0 to 75C M308 S1 P"spi.cs1" Y"rtd-max31865" F50 ;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 M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"fan2" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; 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 F2 ; 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 ; Custom settings are not defined ; Miscellaneous M501 ; load saved parameters from non-volatile memory T0 ; select first tool

i have a 3d printer i designed and build myself , but IRL i run and setup cnc lathe and milling for a living !

@owend

Dohhh, missed to select tool 😞

Just for prosperity if others come across this thread in the future, I finally got around to updating to RRF 3.4.x and the implemented change works great. I can now correctly define the servo with the needed PWM frequency like so:

M950 S0 C”duex.pwm5” Q333

And then move it with the servo commands like so:

M280 P0 S45 ; set servo position to 45 degrees

And it moves a sensible amount as expected.

BTW, the current measurement method I use is I = sqrt(I1^2 + I2^2).

It's agnostic to microstep position, it estimates the per coil peak current, is independent of run vs stop states, and it determines the overall stepper power/heat: P = R * I^2, where R is coil resistance. Very handy.

I think I replicates the internal values that the stepper motor uses before applying the sine/cosine functions for the two coils.

@mattyo not yet, please feel free to ask Aurarum to stock them!

@yaron

Hi
I got everything to work (in Version 3.4)

Here is the config file if someone is interested :

; executed by the firmware on start-up
;https://duet3d.dozuki.com/Wiki/Using_external_stepper_motor_drivers -- reassining the motors for use
; Drives
M584 X10 Y11 E3:4:0:1 ; # X10 ( lcd 10 ) , Y11 ( LCD 11) , reassign 3-> e0 ( as was), 4-> e1 ( as was) , old X -> e2 old Y -> e4.NEED TO BE FIRST INSTRUCSION IN FILE
M584 P3 ; Number of visible axes, defaults to the total number of axes configured.
M569 P10 S0 ; reverse the direction of the motor attached to driver P10 ->X
M569 P11 S0 ; reverse the direction of the motor attached to driver P11 -> Y
M569 P2 S1 ; Drive 2 goes forwards -> z
M569 P3 S1 ; Extruder (driver 3) goes fo rwards

; General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves

; Network
M550 PENDER3 ; Set machine name
M552 S0 ; disable the network
M587 S"MyNet" P"LLLL" ; set passwword for the network
M552 S1 ; Enable network
;*** Access point is configured manually via M587
M586 P0 S1 ; Enable HTTP
M586 P1 S1 ; Enable FTP
M586 P2 S1 ; Enable Telnet

M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X1600.00 Y1600.00 Z416 E400 ; Set steps per mm
M566 X1000 Y1000 Z100 E30000 ; Set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z500 E1500 ; Set maximum speeds (mm/min)
M201 X300 Y300 Z100 E5000 ; Set accelerations (mm/s^2) was 500 you changed it to 300 for stall guard
M906 X500 Y500 Z500 E1000 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S300 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X235 Y235 Z260 S0 ; Set axis maxima

; Endstops
M574 X1 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"exp.heater7" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F200 T2000 ; set Z probe type to bltouch and the dive height + speeds
G31 P25 X-31 Y0 Z2.060 ; set Z probe trigger value, offset and trigger height
M557 X30:205 Y20:220 S20 ; Define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; 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 R0.25 ; 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 150C
M308 S1 P"e0temp" Y"thermistor" T100000 B4092 ; 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
M143 H1 S275 ; set temperature limit for heater 1 to 275C

; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; 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
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 S1 H1:0 T45 ; set fan 2 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
T0 ; Select tool 0

; Heaters
;M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
;143 H0 S120 ; Set temperature limit for heater 0 to 120C
;M305 P1 X150 T"K" ; Set THERMOCOUPLE parameters for heater 1 X150 is the right channel (terminal block) on the daughterboard. X151 is the right channel.
;M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1 - set E0 thermistor parameters
;M143 H1 S280 ; Set temperature limit for heater 1 to 260C

; Fans
;M106 P0 S0 I0 B0.5 F250 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
;M106 P1 S1 I0 B0.5 F500 L255 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Minimum Speed is 1/3 aka 87 Thermostatic control is turned on triggered at nozzle temp 45;
;M106 P2 S0 I0 B0.5 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Tools
;M563 P0 D0 H1 ; Define tool P0 to be D0 ( EXTRUDER E0 in gcode commands )
;G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
;G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

; Automatic power saving
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss

;filament monitor
M591 D0 P1 C3 S1 ; filament monitor connected to E0_stop (C3) On Extruder 0 (D0) S1 - simple sensor (high signal when filament present)

@cromker said in Print Just stopping and disconnecting from Web Control:

The Super extruders, installed them and they wouldn't work, what I discovered was that the firmware is set up to run PT1000 thermistors with the Super, however, the purchased extruders came with standard E3D thermistors. The manufacturer suggested that because we don't run high temps, just run them using the regular Volcano set-up. Could this be the issue?

I don't think this is the cause of the driver overtemp, if that's what you mean.

As for the PT1000 versus a normal thermistor, that's an easy configuration change to make.

1200mA on an extruder isn't crazy, but on a long running print heat build up may be an issue. To test that theory gathering the info infiniteloop requests would be good. You can also try improving cooling by adding a fan or leaving the enclosure open. Without being able to see it I can't give any more specific recommendations.

@oliof said in Gcode lines per second?:

@mrob just to add, simulation is about 5 to 20 times faster than actual printing...

I find it about 60 times faster than actual printing. It depends on how fast you print.

Thanks for the help! It turns out changing M201 worked perfectly fine from the start. I expected to see a larger amount of ringing between accelerations but I was printing fast enough as I forgot to turn up perimeter under speed.

Thanks for the replies all!

@phaedrux that was it! Thank you very much. This condensed my macro down to this:

G91 ; relative positioning G1 Z50 F360 ; lift Z by 50mm M98 P"/macros/print_scripts/goto_front_middle.g" ; move to front for filament change M291 P"Change and purge filament. Resume when after complete." R"Mid-print Filament Change" S2; G0 Z-50 ; drop back down to printing height G90 ; absolute positioning

@droftarts Seems your tips may have worked. No problems so far. And I also ordered replacement pins for my bltouch.
Keep your fingers crossed,

Thank you all!

@t3p3tony Great thanks. Yes they have fault outputs.
Thanks to all of you for your answers.

@oliof @Blacksheep99

Autodesk printer? Powered by Duet

Yes that's correct, a collaboration between Autodesk, Warwick School of Engineering and Duet3D. I expect a lot more details will be published in the upcoming months. It has some very cool aspects: especially the bed and the print head.

@dc42 so do you think i can put my controller in CL by emulating quadrature so that board knows where axis is at any time? By the manual can you understand if the quadrature emulation would be ok for 1HCL board?

thanks in advance.

@57buick said in Failed to enable endstop configuring IR sensor:

Yea I just figured out changed the P1 to P8 made it show up in DWC now and manually putting a aluminum plate under it it changes from 1000 to zero when the led turns on so it is seeing it now. But it still shows homed after it homes the X and Y the Z also immeditately shows homed without actually going and probing the Z

The triggered state is the 1000.

So if you are seeing that when the sensor is NOT near the bed you need to invert the logic of the pin declaration you used for the Z probe.

Add a ! character before the io0.in:

M558 P1 C"121.io0.in" >= M558 P1 C"121.!io0.in"

The reason is reports homed with out actually homing is because the firmware is seeing the sensor activated when it is not. So it thinks the homing was completed.

Frederick

Whew! Figured it out - had to go to the plugins tab and start Motion Webcam Server. All working now.

I might eventually want to change over to using this camera for timelapses, but for now this will work.

Thanks for the help!

I was originally using buildtak sheets, printing the same item repeatedly in the same location on the bed, got about 20-30 parts. Each part takes 9 hrs to print.
I then switched to garalite G11 3mm sheet 16months ago and still haven’t had to touch up the G11 surface. Best money spent

@paboman Alternatively, notepad++ (which is free) will do what you want quickly and easily using "Search" - "Replace". Just remember that when you "save as" by default, it will add .txt to the end of the file so you need to remove that extension. Or you can associate .g files with notepad++ then it won't add the .txt extension.

@deckingman said in What's the difference...:

You are confusing machines with configurations.

Thanks for the clarification.

Frederick