Posts made by ianborg

also of note, after having "heater issues" with my revo, i purchased a replacement heater and things seemed to be fine for a while. I had to some noise issues which was the result of a Y bearing rod rubbing. i fixed that and tried to print again and that's where these issues started. so i figured I need to re-calibrate everything, and ended up with this issue I posted about. after thinking it was fixed, i tried some more prints tonight and it really has smelled up my office. i chalked it up to the filament and threw on a known good roll. as I began to extrude 100mm, it was nearly falling out of the nozzle. I then saw the temp jump to 240 c and got a heater fault.. hmm as i touched the wires, yep the temps start moving all over the place.
so I have an issue with the heater, thermistor or wiring. the smell probably was because the filament was being heated way to hot and the temp readings were false. and that also of course explains, why things seemed fine and now all of a sudden all kinds of PID tuning issues.
so i posted this incase anyone finds it helpful in the future.

@deckingman no - nothing was in config-override.g file
interesting result tuning just the heater worked and gives no error when printing now.
it also only took a few minutes where the other way was taking 30-60 minutes.
so i guess i'm good now. thanks for the replies.

11/7/2022, 8:31:13 PM	Auto tuning heater 1 completed after 3 idle and 5 tuning cycles in 572 seconds. This heater needs the following M307 command:
 M307 H1 R0.741 K0.195:0.000 D5.31 E1.35 S1.00 B0 V24.6
Edit the M307 H1 command in config.g to match this. Omit the V parameter if the heater is not powered from VIN.
11/7/2022, 8:27:44 PM	Auto tune starting phase 3, measuring
11/7/2022, 8:24:20 PM	Auto tune starting phase 2, settling
11/7/2022, 8:21:46 PM	Auto tune starting phase 1, heating up
11/7/2022, 8:21:41 PM	m303 p1 s200 h1
Auto tuning heater 1 using target temperature 200.0°C and PWM 1.00 - do not leave printer unattended

@gloomyandy I will get some screen shots posted asap
thanks!

@deckingman Yes I put it in config.g
I have tried tuning with the bed close and far away, same results
I will try just the heater and post results.
also running latest firmware 3.4.4 (duet 2 wifi)

sorry if this turns out to be a double post, but I was editing the original to make it more readable and then it said it was being marked as spam. so not sure if it will be auto removed or not

I switched over to the E3d Revo hot end.
on their support site it indicates the following config changes are needed to use the correct thermistor.

M308 S1 P"e0_temp" Y"thermistor" T100000 B4725 C7.060000e-8

my PID auto tunes take over 30 min and always seem to give warnings, is there something else I need to do?
thanks!

11/6/2022, 9:37:21 PM	Warning: heater behaviour was not consistent during tuning
Auto tuning heater 1 completed after 3 idle and 50 tuning cycles in 2030 seconds. This heater needs the following M307 command:
 M307 H1 R1.456 K0.224:0.291 D2.50 E1.35 S1.00 B0 V24.6
Edit the M307 H1 command in config.g to match this. Omit the V parameter if the heater is not powered from VIN.
11/6/2022, 9:18:28 PM	Warning: heater behaviour was not consistent during tuning
Auto tune starting phase 4, measuring with fan on
11/6/2022, 9:06:44 PM	Auto tune starting phase 3, measuring
11/6/2022, 9:04:59 PM	Auto tune starting phase 2, settling
11/6/2022, 9:03:35 PM	Auto tune starting phase 1, heating up
11/6/2022, 9:03:30 PM	M303 T0 S205

when i try to print i then get this

Heater 1 fault: temperature rising too slowly: expected 0.40°C/sec measured -0.40°C/sec

I switched over to the E3d Revo hot end.
on their support site it indicates the following config changes are needed to use the correct thermistor.
M308 S1 P"e0_temp" Y"thermistor" T100000 B4725 C7.060000e-8

my PID auto tunes take over 30 min and always seem to give warnings, is there something else I need to do?
thanks!

11/6/2022, 9:37:21 PM	Warning: heater behaviour was not consistent during tuning
Auto tuning heater 1 completed after 3 idle and 50 tuning cycles in 2030 seconds. This heater needs the following M307 command:
 M307 H1 R1.456 K0.224:0.291 D2.50 E1.35 S1.00 B0 V24.6
Edit the M307 H1 command in config.g to match this. Omit the V parameter if the heater is not powered from VIN.
11/6/2022, 9:18:28 PM	Warning: heater behaviour was not consistent during tuning
Auto tune starting phase 4, measuring with fan on
11/6/2022, 9:06:44 PM	Auto tune starting phase 3, measuring
11/6/2022, 9:04:59 PM	Auto tune starting phase 2, settling
11/6/2022, 9:03:35 PM	Auto tune starting phase 1, heating up
11/6/2022, 9:03:30 PM	M303 T0 S205

when i try to print i then get this

Heater 1 fault: temperature rising too slowly: expected 0.40°C/sec measured -0.40°C/sec

code_text

@droftarts Yeah I don't know how they got their either.
nodedfs was about 8k firmware folder was about 8mb
when i crafted the new card, I only added the folders that should be there and used a new webcontrol zip.
the only thing had to transfer over was the xml file.

@droftarts sorry missed the rest of the questions. currently running latest firmware.
hard to say on what versions I have installed over the last few years. I rarely stay on the bleeding edge, more of an every once in a while I'll check and see if something new is out. I also tend to updated firmware, web control. and panel due firmware at the same time.
size of the www folder was about 100mb it was only 128mb sd card.
now has a 32 GB card. so i'll likely never have storage space issues again
let me know if you have any other questions.
thx

@droftarts @chrishamm Actually yes i do. I won't post every screenshot unless you need me to. but this is 2 of them should show the issue. every folder is similar though.
years of them. I guess if i had a large sd card in there I may have never known about it.
I'm assuming due to the card being full, my PID setting never saved and thus i continued to get temp errors as the e3d revo used a different type of thermistor than what I had before. let me know if you need anything else related to that. thx for the reply

I wanted to post my recent experience with my duet3d wifi board. so the info is out there incase it is helpful to anyone.
i not so long ago switched to an e3d revo. everything seemed okay, then i started having temp errors
I've only printed a few times, so surely my new e3d revo couldn't have gone bad yet.

I started looking into it and trying to PID auto tune, it never seemed to work.
i started looking into newer firmwares. etc. still no luck.
as of tonight, I could no longer upload any files at all. moved on to the sd card troubleshooting.
it mounted and unmounted, but no luck there. so i finally had to remove the sd card and put it in my pc.
I found a few things. 1) it was very small old sd card. 2) it was full and 3) what filled it up was years of the duet3d web control files in the www folder.
it doesn't appear those files ever get cleaned out????? I had some files going back to 2020 at least

so lessons learned. IF you start having problem out of the blue like that and end up not being able to upload new files, check your card.

I put in a new formated 32gb card, put my files back on, reinstalled , re-tuned and am on my 2nd print of the night.

what would have been helpful, would be to have more access to the SD card directories in the web UI.
I am only able to access system and firmware. so thoughts for a future feature add.

@pkos @alankilian I'm on 3.2.2 which I believe is the latest. I don't seem to have access or the ability to get into the firmware folder from the WC. I ended up enabling FTP and saw the folder firmware was there, i FTP uploaded it and then it worked.
thanks for the reply and info.

I'm trying to update the firmware on my display.
I'm running duet2 wifi with firmware 3.3 beta 2
when i issue M997 S4 I receive the message.
0:/firmware/PanelDueFirmware.bin Not found
I was under the impressions the firmware was pulled from the sys folder?
any suggestions?

@bearer said in browser must be open to upload from s3d:

add a call to curl "http://192.168.x.xx/rr_connect" at the top?

@bearer Thanks.. that did the trick!

I'm using curl commands to send a sliced filed from s3d to my printer. however, it only ever works if i've first opened the web interface to the duet in my browser.
anyone know why that is and what i can do to upload without the browser having to be open first?

here are my commands if it helps
curl --data-binary "@[output_filepath]" "http://192.168.x.xx/rr_upload?name=gcodes/[output_filename].gcode&time=YYY"
curl "http://192.168.x.xx/rr_gcode?gcode=M32[output_filename].gcode"
curl "http://192.168.x.xx/rr_disconnect"

@Phaedrux no worries. okay so sorta the same problem
I confirmed if i set the z0 and do a trigger height, i get like 1.1, if i do nothing but reboot, i'll get a trigger height 1.1 each time.
if i go into my config and change the config from 1.0 to 1.1, and reboot, i now get a trigger height of 1.2x
change the config, put it 1.2 (no rezero of Z) i now get a trigger of 1.3

so that leads me back to the the problem of the 1st layer, i'm always having to baby step to get a good first layer and i'm wondering if the above problem is why.

is there a way to add a +0.5 Z (or whatever number) to my config on top of what i have so i don't have to baby step each print?

@Phaedrux said in trigger height always changes:

@ianborg said in trigger height always changes:

G31 X37 Y0 Z0.98

Your G31 is missing the P value. Add P25. Not sure what the default is, or if this would make a difference, just something I noticed.

I'd also try reducing your Z max feed rate. Try 500 and see if it makes an improvement.

Also check your BLTouch mount to ensure that it's stable and fully vertical. Also the base of the probe should be ~2mm above the nozzle tip for best results.

that may have actually helped I rebooted 3 times and got 1.1x trigger heights each time. which is what i would have expected and wasn't seeing. so i'm going to adjust and try it all again.
1 question, my bltouch is set to be 8.3 mm above. most of my google searching says that's the number. i printed a 8.3mm jig and used that to set the height. is there something specific with the duet that it has to be 2mm??
appreciate the help!

@Phaedrux said in trigger height always changes:

you loading the heightmap automatically at boot?
Are you clearing any bed transform before measuring?
What exactly are you sending to measure the trigger height?

sorry it's a little messy. but here are my files.
I'm using a macro that has 2 lines to measure
G1 Z10 F1000
G30 S-1
just to be sure it wasn't me. i changed my trigger height, saved, config and all i did was restart and it was different, i didn't re-calibrate z0 and it's still different after every reboot
I'm using M561 to clear the bed before i measure.

config

; General preferences
G90                                     ; send absolute coordinates...
M83                                     ; ...but relative extruder moves
M550 P"FT5-R1 Custom"                   ; set printer name

; 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 forwards
M569 P1 S0                              ; physical drive 1 goes forwards
M569 P2 S0                              ; physical drive 2 goes forwards
M569 P3 S0                              ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3                        ; set drive mapping
M350 X16 Y16 Z16 E16 I1                 ; configure microstepping without interpolation
M92 X80.80 Y80.80 Z401.00 E435.00       ; set steps per mm
M566 X600 Y600 Z50 E600			; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z1000.00 E6000.00 ; set maximum speeds (mm/min)
M201 X1000 Y1000 Z300 E2000		; set accelerations (mm/s^2)
M906 X850 Y900 Z950 E850 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 minima
M208 X300 Y300 Z345 S0                  ; set axis maxima

; Endstops
M574 X1 S1 P"!xstop"                            ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"!ystop"  
; M950 H4 C"nil"
M950 P2 C"^exp.heater4" Q50
M950 P3 C"^exp.heater5" Q50
M950 P4 C"^exp.heater6" Q50
M950 P5 C"^exp.heater7" Q50
; Z-Probe
M574 Z1 S2                              ; set endstops controlled by probe
; M307 H3 A-1 C-1 D-1                     ; disable heater on PWM channel for BLTouch
M950 S0 C"exp.heater3" ; create servo/gpio 0 on heater 3 pin on expansion connector
M558 P9 C"^zprobe.in" H5 F100 T4000 A5 R0.3 S0.005 B1  ; BLTouch connected to Z probe IN pin
G31 X37 Y0 Z0.98                   	; set Z probe trigger value, offset and trigger height
M557 X40:280 Y15:280 P5                ; define mesh grid

; Heaters
M308 S0 P"bed_temp" Y"thermistor" T100000 B4138 R4700	; define bed temperature sensor
M143 H0 S120                            ; set temperature limit for heater 0 to 120C
M950 H0 C"bed_heat" T0 ; heater 0 uses the bed_heat pin, sensor 0
M308 S1 P"e0_temp" Y"thermistor" T100000 B4138 R4700	; define bed temperature sensor
M143 H1 S280                            ; set temperature limit for heater 1 to 280C
M950 H1 C"e0_heat" T1 ; heater 1 uses the e0_heat pin and sensor 1

; Fans
M950 F0 C"fan0" Q500                           ; create fan 0 on pin fan0 and set its frequency
M106 P1 S0 I0 F500 H-1                  ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M950 F1 C"fan1" Q500                           ; create fan 1 on pin fan1 and set its frequency
M106 P0 S1 I0 F500 H1 T45               ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on

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

; STARTUP TUNE
;
G4 S5 ; pause 5 seconds
M300 P200 S1975.53
G4 P201
M300 P200 S2217.46
G4 P201
M300 P200 S1975.53
G4 P201
M300 P200 S2793.83
G4 P201
M300 P200 S2489.02
G4 P201
M300 P200 S2217.46
G4 P201
M300 P200 S2489.02
G4 P201
M300 P200 S2959.96
G4 P201
M300 P300 S3520.00

home all

G91                     ; relative positioning
;G1 H2 Z5 F6000          ; lift Z relative to current position
G1 H1 X-305 Y-305 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000       ; go back a few mm
G1 H1 X-305 Y-305 F360  ; move slowly to X and Y axis endstops once more (second pass)
G90                     ; absolute positioning
G1 X15 Y15 F6000        ; go to first bed probe point and home Z
G30                     ; home Z by probing the bed

I'm trying to level my bed, but having issues with the trigger height always changing. (duet wifi, bltouch, latest firmware)
I follow the instruction and set z = 0 in the middle of my bed.
i perform a trigger height test and say i get consistent results of 1.232
i go into my config.g and change my G31 to G31 X37 Y0 Z1.23
when i save, it restarts my duet wifi, i go back and perform the same steps and this time my trigger height in the middle is different.
i put in the new number 0.9 in the config. save, reboot perform test again, trigger height is once again different.

I'm using mesh calibration, but struggle to get a good first layer, i always have to baby step up or else it grinds.

thoughts or suggestions about what may be my problem?
Thanks!
(note my bltouch is the newest version and set at the correct height)

@infiniteloop said in has anyone see this problem before (bltouch/bed):

didn’t find that in the specs. Is there any possibility of the 4 treaded rods coming out of sync, for either electrical or mechanical reasons?

The FT5 homes to the back right corner 0,0

Then, I think your mesh shows a look from the back, but anyway, that does’n matter.

my next step is to replace the bltouch and hope it has something to do with that?

Whatever BLtouch or other probe you take, you must make sure that it is trustworthy, so you should repeatedly probe a single point with G30 S-1 and look if the reported values are identical or at least very narrow.

originally it had 2 z motors wired in series? off of 1 z driver, but the R2 version used a single Z motor with bigger belt so allot of us that had R1 machines also converted over to a single Z.
to your other question, if i had the original melamine parts, then i would say yes possible, but that is why many people started getting the milled aluminum parts to replace. if you were curious check out 713maker.com that's the guy who makes all the aluminum conversion parts.

here is a photo to show you can see the bracket on the corner, i ground it away and the tile sits flush now.
photos.app.goo.gl/RRype9WyK23GTihd7