Posts made by pinkmaro

That works like a charm Thank you!
1 more question: Can I use a heated print bed without a temperature sensor? If yes, how can I set it manually? I can't do it through the RRF Config Tool.

Hi, need some help here. I'm using my old delta printer and changing out the board to Duet. I have updated to all the latest firmware.
Motion of the axes is fine already, and now I'm testing the heaters.

In the RRF Config Tool:

Trying to set it up now and I'm facing this issue:

So basically, I can't manually turn on heater for Tool 0.
Also, on the DWC, Heater shows as n/a

I did try Output: e0heat (inverted) and the heater works. It heats up immediately, and the Temperature Chart reflects the temperature increasing. But heater is still "n/a".

Am I missing something here?

Not sure if this is needed but I've included config.g here:

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu May 21 2020 18:55:31 GMT+0800 (Singapore Standard Time)

; General preferences
G90                                           ; send absolute coordinates...
M83                                           ; ...but relative extruder moves
M550 P"Qubea"                                 ; set printer name
M665 R125 L250 B100 H397                      ; 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 S0                                    ; disable 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 X80.00 Y80.00 Z80.00 E663.00              ; set steps per mm
M566 X1200.00 Y1200.00 Z1200.00 E1200.00      ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z18000.00 E1200.00   ; set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z1000.00 E1000.00      ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800 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 active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop"                           ; configure active-high endstop for high end on Y via pin ystop
M574 Z2 S1 P"zstop"                           ; configure active-high endstop for high end on Z via pin zstop

; Z-Probe
M558 P0 H5 F120 T6000                         ; disable Z probe but set dive height, probe speed and travel speed
M557 R85 S20                                  ; define mesh grid

; Heaters
M140 H-1                                      ; disable heated bed (overrides default heater mapping)
M308 S0 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin e0temp
M950 H0 C"e0heat" T0                          ; create nozzle heater output on e0heat and map it to sensor 0
M143 H0 S280                                  ; set temperature limit for heater 0 to 280C
M307 H0 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 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 S0.5 H T50                            ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 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

; Custom settings are not defined

; Miscellaneous
M501                                          ; load saved parameters from non-volatile memory
T0                                            ; select first tool

Thanks in advance!

Am I right to say that the drive will be disabled right after homing? If yes, how can I disable this function of disabling the drive?

Your post always enlightens me on something new! I didn't know about M208!! Thank you! will go and change my code ^^ cheers

Sorry if i was being confusing.
It was 2 separate issues.

First issue:
I have set up for 1 Z-probe and initially it was working fine (i.e. Z-probe was set as P1 in config.g).
I did change other stuff in the configurator tool but I didn't change anything about the Z-Probe but starting from some point, the Z-probe was generated as P2 instead of P1.
The code in config.g was:
; Z-Probe
M558 P2 H5 F120 T6000 ; Set Z probe type to modulated and the dive height + speeds
G31 P500 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height
M557 X0:1050 Y-1040:0 S20 ; Define mesh grid

Second issue: I have defined my Z-axis homing with a limit switch to the "High End" but consistently my homez.g was as follow:
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v2 on Fri Feb 22 2019 13:32:37 GMT+0800 (Singapore Standard Time)
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
G1 S1 Z1062.35 F1800 ; move Z up until the endstop is triggered
G92 Z1 ; set Z position to axis minimum (you may want to adjust this)

; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 S2 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning

Initially I was really fresh to this whole 3D printing, Duet, Reprap and all these G-codes. But now I'm starting to understand better and so I know where to check for problems, and I can make the adjustments, so no big issue.

Hope this clarifies my confusing post earlier.! ^^

uhh, it's ok! I figured. in Config.g it should have been M558 P1 but the configurator generated it as M558 P2
Been having quite a bit of issues with the codes generated by the configurator actually. For example, homing my Z axis to the high end, it moves the Z towards the high end but sets the Z position to minimum after homing.

On the DWC, under Z-Probe, previously it was just "0". Suddenly it has become "0 (0)" and when I put something near the sensor, the reading becomes "0 (535)", and my Z-probe doesn't stop.

Any hints?

After checking back with my dad, he wants to do it such that we will connect the bed to an endstop. We will then manually switch on the heaters and when the temperature has been achieved, we will trigger with an "on/off" to the endstop. Is there a specific Mcode/Gcode that I can use in my gcode to detect this signal on the endstop and inform the duet to start print job?

We are getting lost steps when we move at higher speed. So we are wondering if fixing the pulse width can overcome the issue of lost steps.

Is there any way to set pulse width from the DuetWifi?

M588 S"NETWORKNAME" actually works wonder! Thanks so so much^^ and I've upgraded all my firmware~

@phaedrux thank you for the reply! I'm on Windows 10. I will try out M588 in config file and see how it goes
Im on 2.01 for now.. Found it a bit of a chore to upgrade firmware so I didn't do so. I shall get to the upgrading after I fix the network problem

Hi I've previously had a network set on my duetwifi and now that I have moved the card onto the system, it is very weak on this network and so I tried to connect it on another network.
I have done M588 S"*" through YAT and Pronterface (I have no idea how all these stuff works so I'm just trying all possibilities.) and set up the new network.
Now I can connect to the new network but the old network is still lurking around. When I upload config file and restart the board, sometimes it connects to the old network, sometimes it connects to the new network. At times I can get into the Web control, and get connection to the board, at times the Web control totally doesn't load. At times the Web control loads, but status is "Disconnected"

Another qn, can I change the config file directly through the duet Web control? I am trying to change the max speed on my Y axis and I tried editing the config file. Then it had an error message and a config backup file was generated. subsequently it seemed to become corrupted and I couldn't connect anymore.

Please help this very very lost sheep here.

Yes, I think it does, thank you!!! ^^ Looks I have a lot of reading to do to understand all the things about 3d printing. Will try out and come back if I have more questions.

Sorry if this is a really silly question, if I follow to use SSR, will the duet automatically know when my bed has reached the required temperature?
If no, how do I notify the duet?
I will be using K type thermocouple.

I'm not good at all technically, and my question might sound really odd. But thank you all for being patient and responsive!

@deckingman we have a 2400W external heater

I feel embarrassed telling you this... but I actually placed the board on top of my power supply (now you can tell how much of a complete electrical noob I am)
So I actually have no idea what has/have shorted.

I would like to use external heaters to heat up the print bed, then when the required temperature is reached, a signal will be sent to Duet Wifi to start print job.
Where should I send this "signal" to?
How should I modify the config or any other files to accommodate for that?

I think it is the big squarish IC (that's the CPU right?) anyway, I do think I have accidentally short circuit the board probably that explains why. maybe a nice insulated case will be a good add on
thanks for replying me though! always appreciate it!

One more thing: the now faulty board heats up quite a bit