Posts made by hmortensen

@t3p3tony It works now.

@t3p3tony It still looks like this for me even in a new browser.

@t3p3tony Did you change the fav icon also?
It looks quite bad now with inverted colors in the duet logo, and blue box around instead of transparent.

Have you tried copying the value from the object browser?
In the screenshot it seems to be capital letter I in gpIn and your echo command is all lower case.

That is hard to say, it is a beta afterall. But you can always downgrade again if things doesn't work for you.

M17 is implemented in 3.3 beta 1 according to the release notes:
https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-Beta-&-RC

Have you tried with:
http://192.168.1.27/capture

If it's the default ESP32-cam sketch, then this URL should work:
http://<IP OF ESP>/capture

@dc42 said in New heater tuning algorithm:

@hmortensen said in New heater tuning algorithm:

Is it possible to control the fan when tuning?

No.

I rarely use it at 100% when printing, but the tuning turns it fully on.

When printing, the heating algorithm takes account of using the fan at reduced PWM.

Can I see how many cycles it has run so far?

Only by counting the cycles on the temperature graph.

Would the result be usefull at all, if I let it finish, or should I just wait for the next algorithm update?

Yes it would be useful; however the next version is likely to be available 1 to 2 days from now, so you may prefer to wait.

Redid the tuning after updating to beta 4.1. This time it did finish after 45 min but with a warning.
Then I tried with S230 instead, and that took around 11 min and no warning.
Any guidelines to which temperature to tune at?

After saving with M500, it also rewrote the M307 for bed heater. I didn't retune bed heater yet. Is that normal?

@dc42 said in New heater tuning algorithm:

@hmortensen said in New heater tuning algorithm:

Hi

I've tried tuning my hotend heater after updating to 3.2b4, but this step "Auto tune starting phase 3, fan on" ran for 45 min without finishing, and then I turned it off.

Is something wrong, or should it take this long?

The tuning algorithm does two idle cycles and up to 30 tining cycles until the data becomes stable. Yout heater struggles to reach 250C, so each cycle is taking 2 minutes. Therefore it could take a little over an hour. You could try using a lower target temperature.

The next update uses a modified algorithm that often reduces the number of cycles needed in cases like yours.

Is it possible to control the fan when tuning? I rarely use it at 100% when printing, but the tuning turns it fully on.
Can I see how many cycles it has run so far?
Would the result be usefull at all, if I let it finish, or should I just wait for the next algorithm update?

Thank you, I used the M208 option like this:
M208 X0 Y-12 Z0 S1 ; set axis minima
M208 X235 Y235 Z250 S0 ; set axis maxima

Hi

I've tried tuning my hotend heater after updating to 3.2b4, but this step "Auto tune starting phase 3, fan on" ran for 45 min without finishing, and then I turned it off.

Is something wrong, or should it take this long?

Attached snip of temp chart and console log.

11/29/2020, 7:47:45 PM	M303
Heater 1 is being tuned, phase 5 of 5
11/29/2020, 7:37:59 PM	M303
Heater 1 is being tuned, phase 5 of 5
11/29/2020, 7:11:50 PM	M303
Heater 1 is being tuned, phase 5 of 5
11/29/2020, 7:07:56 PM	M303
Heater 1 is being tuned, phase 5 of 5
11/29/2020, 7:05:29 PM	Auto tune starting phase 3, fan on
11/29/2020, 7:04:57 PM	M303
Heater 1 is being tuned, phase 4 of 5
11/29/2020, 7:02:30 PM	M303
Auto tune starting phase 3, fan off
Heater 1 is being tuned, phase 4 of 5
11/29/2020, 7:01:05 PM	Auto tune starting phase 2, heater settling
11/29/2020, 7:01:03 PM	M303
Heater 1 is being tuned, phase 2 of 5
11/29/2020, 6:58:30 PM	M303
Heater 1 is being tuned, phase 2 of 5
11/29/2020, 6:58:05 PM	Auto tune starting phase 1, heater on
11/29/2020, 6:58:00 PM	M303 T0 S250
Auto tuning heater 1 using target temperature 250.0°C and PWM 1.00 - do not leave printer unattended
11/29/2020, 6:57:47 PM	Connection established
11/29/2020, 6:57:46 PM	Connection interrupted, attempting to reconnect...
HTTP request timed out
11/29/2020, 6:57:36 PM	Upload of config.g successful after 0s
11/29/2020, 6:56:36 PM	M303 T0 S250
Error: M303: heater 1 target temperature must be below the temperature limit for this heater (250.0C)
11/29/2020, 6:44:03 PM	M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2-beta4 running on Duet WiFi 1.02 or later
Board ID: 08DGM-917NK-F2MS4-7JTDJ-3SS6J-KWVNH
Used output buffers: 3 of 24 (15 max)
=== RTOS ===
Static ram: 24108
Dynamic ram: 104312 of which 40 recycled
Never used RAM 1588, free system stack 188 words
Tasks: NETWORK(ready,148) HEAT(blocked,294) MAIN(running,459) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:46:27 ago, cause: software
Last software reset details not available
Error status: 0x00
MCU temperature: min 28.1, current 28.9, max 29.4
Supply voltage: min 23.9, current 24.0, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2020-11-29 18:43:55
Cache data hit count 4294967295
Slowest loop: 259.02ms; fastest: 0.19ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 4.6ms, write time 39.8ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, StepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, StepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
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
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 1754.37ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.24
WiFi MAC address 60:01:94:2e:a5:fa
WiFi Vcc 3.40, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 23840
WiFi IP address 192.168.1.7
WiFi signal strength -64dBm, mode none, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
11/29/2020, 6:43:25 PM	M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.2-beta4 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-11-26
11/29/2020, 6:41:14 PM	Connected to 192.168.1.7

; 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

So I just change this G10 like this to move the Y axis?
G10 P0 X0 Y20 Z0

Hi

On my Ender 3, I've changed hotend, and now the print area is a bit off from the bed area.
Can I define an offset to the bed?

Can you supply a picture of it?
Have you checked that the browser window is zoomed?
Or the menu is visible taking up more space.

My lines for BLT using same wiring:
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"zprobe.in+zprobe.mod" H5 F600 T6000 ; set Z probe type to bltouch and the dive height + speeds

So I think you need to swap the two lines and use the pin ref as I'm using.

When testing homeing, raise your Z alot and just trigger the pin with your finger to avoid bed crashing. If it doesn't stop, then do powerdown.

It's just the first time after the application loads, it needs an extra click. After that it works as expected.

It's not a new bug, also mentioned here:
https://forum.duet3d.com/topic/16303/code-send-button-misbehavior

You have to describe the problem a bit better and post your config file.

@chrishamm Thank you, that did fix both problems.
Didn't work in first try, as when I created a macro file it had no extension and I tried calling it with '.g'.
Is it possible to force it into error state instead of just yielding a warning if the macro doesn't exist?

I went with the custom macro approach, as I guess the start.g macro would be called before the actual print file and then I would miss the option of setting temperature in the slicer.

I made a new directory prefixed with a dot and it had the expected effect of hidding it from the dashboard

Tried with the E infront of the comments, but no change. Still jumps directly to layer 2 when doing the purge, and total layer count is still one too low.