Posts made by Poul Erik

@o_lampe Thank you. This solved my problem.
Kind Regards
Poul Erik

@Phaedrux Thank yo for your reply.
I increased the "H" parameter in the Z-probe definition, as suggested by @o_lampe. This solved my problem.
Thank you again.
Kind Regards
Poul Erik

Hi forum
I could need help diagnosing a problem with probing.
I am running Duetwifi and the IR probe.
The printer has been running without problems till now, but recently a problem accured.
The probe is working on the first couple of probing positions, but as it moves to a new position it skips the probing and continues to the next position. There is a error message when a probing point is skipped "probe already triggered at start of probing move".
Any help would be greatly appreciated.
Kind Regards
Poul Erik

Thank you @achrn
Your time is much appreciated.
I will change the SSR and see if this solves my issue.
//pe

@zapta said in 230v heatbed thermal runaway:

Duet and the SSR, does the bed heats when you turn the printer on? If so, you may have shorted SSR.
Also, does your SSR have a led, indicating the control signal? I so, it will help you identify if the problem is on the duet/firmware side or the SSR.

Thank you @zapta
What might cause the SSR to short?

//pe

@gixxerfast said in 230v heatbed thermal runaway:

the input of the SSR, does the LED on the SSR (if there's one) light up ?

HI @gixxerfast The heatbed will turn on even if the bed is not marked as active.
There is no led on the SSR.

Thank you.
Poul Erik

@achrn
Thank you, much appreciated!

@t3p3tony
Thank you Tony, I really appreciate your time.
The wiring is pretty standard and worked until yesterday.

I suspect you are asking for somthing other than what the image is showing! But what?

Kind Regards
Poul Erik

@t3p3tony
i would have to take the printer apart to answer how the it is wired.

@t3p3tony
Yes, it starts heating rightaway.

@t3p3tony
m115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-02-09b1

@poul-erik

config.g:

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.1 on Sun Jun 07 2020 22:29:30 GMT+0200 (Centraleuropæisk sommertid)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"DuetWasp" ; set printer name
M665 R391.149 L613 B200 H748.863 X0.011 Y-0.286 Z0 ; Set delta radius, diagonal rod length, printable radius and homed height , X,Y,Z tower position correction
M666 X-0.05 Y0.54 Z-0.49 ; put your endstop adjustments here, or let auto calibration find themx

; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S0 ; physical drive 1 goes backwards
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, enabled
M92 X80.00 Y80.00 Z80.00 E400 ; set steps per mm
M566 X1200.00 Y1200.00 Z1200.00 E1200.00 ; set maximum instantaneous speed changes (mm/min)
M203 X1800.00 Y1800.00 Z1800.00 E1200.00 ; set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z1000.00 E1000.00 ; set accelerations (mm/s^2)
M906 X700 Y700 Z700 E900 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 null
; M574 E1 S0 P"fstop" ; configure active-high endstop for high end on filerment
;M574 U2 S1 ; active high endstop switches, XYZ at min, U at max
M581 E1 S1 T3 C0 ; filament out, 2=simple sensor (low signal when filament present) C1 when running this, C0 is only for testing

; Z-Probe
M558 P1 C"zprobe.in+zprobe.mod" H3 F5 T6000 ; set Z probe type to unmodulated and the dive height + speeds
;M558 H3 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
G31 P500 X3 Y3 Z 1.251 ; set Z probe trigger value, offset and trigger height
M557 R180 S20 ; define mesh grid

; Heaters ;Bed
M305 P0 T100000 B3977 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S110 ; set temperature limit for heater 0 to 110C
M307 H0 A190.4 C1871.8 D7.2 V16.6 B0 ;Pid tuning bed

;hotend

M305 P1 P"e0temp" Y"thermistor" T500000 B4217  ; configure sensor 1 as thermistor on pin e0temp
M307 H1 A338 C126.3 D3.3 V23.9 B0 ; Pid tuning heater
; MCU
M912 P0 S35.5 ; MCU temperature calibration

; Fans
M106 P0 S1.0 H-1 I0 ; set fan 0 value, H-1=PWM disabeled= Thermostatic control is turned off. Invert PWM (I1), disable fan (I-1), or normal mode (I0, default)
M106 P1 S255 F500 X0.2 H1 T45 B0.1 ; set fan 1 value. On. (F500 frequency.) Thermostatic control is turned on, start at 45dgr.
;(B0.1= Time for which the fan will be operated at full PWM when started from cold 0,1sec. (L0.05 X0.2 = Min power 0.5pct. Max power20pct)(H1 T45 Start at45 dgr)

; Tools
M563 S"Maby this will work"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

; Miscellaneous
M575 P1 S1 B57600 ; enable support for PanelDue

; Custom settings are not defined

Hi Duet Forum
I have a problem with thermal runaway on my heatbed.
The temperature will continue rising past the temperature I set in the Web interface, even if I push the emergency stop button.

Apparently I get the correct temp reading, but the board doesn´t shut down the bed heater.
What is going on? Can anyone suggest a solution ?

Thanks in advance.
Poul Erik

printer spec:
Deltaprinter
Duet Wifi
230v heatbed / SSR

@Veti
Thank you Veti
I´ll give that a try.
//pe

@Veti said in ”The last HTTP request has timed out.”:

on the heater via the web interface to the printing temperature?
Hi Veti
Yes it does. I think we are closing in on something.
Does it have to do with the extruder heater?

@Phaedrux
I checked again to see when the "blackout" happens.

1. Job sent to printer.
2. Bedheater starts 230v, and finish heating.
3. Duet shuts down as extruder starts heating.
4. Blackscreen for a second or so. There is a red light just above the Wifi module, that turns off for a second, all other lights on the board stay on.
5. Duet restarts in Idle state.

Any Ideas?
//pe

@Phaedrux
Thank you for the comment.
I get what you are saying. Is there a guide to trouble shooting the powersupply. As you may have guessed, I´m not an electrical engeneer!
This forum is just so helpfull!
Kind Regards
Poul Erik

@Phaedrux @dc42

Hi Forum

I thought that I found the reasen for the ustable internet, but unfortunately the instability has returned.
After updating the firmware to version 2.05 /WiFi firmware version 1.23, and still had the issue, I found that My ”Philips Hue” was using the same IP address as the printer. When I changed the IP address, the Wifi connection became stable.
Some days has passed and the trouble is back.
I can connect to the printer, but when I send a print command, or some other command, the Wifi connection turns of and immediately afterwards it connects up again.
I have tried to execute a print local on the printer, and the same thing happends, the screen goes black, then turns back on, and the printer is idle, no print is executed.
Can you help me? It would be much appreciated.
Kind Regards
Poul Erik

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet WiFi 1.02 or later
Board ID: 08DGM-956GU-DJ3S0-7J9FD-3SJ6K-KAGVF
Used output buffers: 1 of 24 (6 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93000 of which 0 recycled
Exception stack ram used: 312
Never used ram: 12048
Tasks: NETWORK(ready,764) HEAT(blocked,1176) MAIN(running,3736) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:00:41 ago, cause: power up
Last software reset at 2020-01-22 20:19, reason: User, spinning module GCodes, available RAM 11868 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 39.5, current 40.3, max 40.5
Supply voltage: min 24.6, current 24.7, max 24.9, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2020-01-26 12:08:44
Cache data hit count 104594956
Slowest loop: 1.34ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.51ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8

• WiFi -
  Network state is running
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.23
  WiFi MAC address 5c:cf:7f:76:64:25
  WiFi Vcc 3.37, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 24424
  WiFi IP address 192.168.38.101
  WiFi signal strength -53dBm, reconnections 0, sleep mode modem
  Socket states: 0 0 0 0 0 0 0 0
  === Filament sensors ===
  Extruder 0: pos 0.04, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0

Hi @Phaedrux
What is the preferred way to update the config file?
I am intimidated by the sheer amount of changes, and worried to overlook something!
Will I have to read through all changes from my previous firmware, as they are listed here?
https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md
Or is there a summary somewhere, with relevant changes for 3d printers or even for Delta printers?

Kind Regards
//Poul Erik

Thank you @Phaedrux
I have updated the printer and I am working on the config.
//pe