Thanks What i ended up just trying was changing from the thermistor 2 port to the thermistor 3 port and setting the new pin number in the config no other changes to the config.
and it's working correct temp now, so looks like the input on 2 for the thermistor is bad.
it there a easy way to fix it, or just forget it and go with what i have running now, I don't picture ever needing a 3rd thermistor...
Gary
I will have to get the config file later but i have not changed anything in the config and it was working fine last time i used this printer..
it's a maestro board
i did have the thermistor disconnected when taking the readings.
I placed a 2 pin connector on the thermistor pin's with wires inserted and tested across the 2 wires .
I also tested the two thermistor's while disconnected across the 2 wire's, I forget at the moment what the reading was but they were the same for both thermistor's.
Thanks gary
I have my bed thermistor hooked to the duet thermistor 1 input , and i am getting a -90 reading
I tried 2 different thermistor's and i am fairly sure both are good..
I connected a multi meter to the pin on the board and with power off i was reading around 6.5 K ohm
power on it was 28 K ohm.. on thermistor 1 pins..
I connected to thermistor 2 input and was getting 76k ohm power off and 253k ohm power on.
So there is a big difference between the two doe's it sound like input 1 is bad ? or do i need to test in a different way? and is it a easy repair if needed..
Thanks gary
@t3p3tony
I have my config setup for the piezo would that setup work for a test of will need to modify it..
Thanks gary
Here is a few pic's of a mount i just made, and would like some advice of if it looks doable, i haven't connected or used the smart effector as of yet, but came up with this mount. to use the direct drive..
I seem to have enough clearance for the rods and, the mount isn't hitting any of the solder pads..
and i think it should still have enough flex to trigger probe, but not sure..?
Any thoughts
Gary
When i print a angled part all the way up it looks like steps instead of a smooth angle..
Like in the pic.
its a delta printer petg and .6 nozzle layer height .53 speeds are fairly slow.
It prints ok if i lay it on the side, but i have slots in the bottom and didn't want to use supports..
Any suggestions
Thanks gary
M307 H0 B0 A113.8 C611.3 D0.4 V23.0
I have gone ahead and installed 3.3RC3 and that has seemed to fix it, I tuned the hotend again and it tuned with no errors, used the m307 it suggested and when cooled down i heated it to 240c and no fault error now.
Still a little trouble with the bed tuning gives me a waring message every time and a suggested a m307 value
i enter that in the config and it heats up fine.. so guess i won't worry about it to much..
Thanks gary
Seeing the subject has been brought up again..
I have just change out my hotend and heater and tried auto tune, always finishes but seems to have errors and gives me the values for the 307 in config, after entering the new values and i turn on the heater to 210 i always get a heater fault not rising fast enough. but from watching the DWC the temp seems to be going up fast.
So returned and this time no error and a new pid value so i enter that and got the same heater fault
If i put just use the default m307 values with no pid values it heats up fine no errors..
also have a pt100 with the duet pt100 board and it a diet2 wifi
this is with firmware 3.2.2 release
Thanks gary
Thanks i have tested from P720 to P800 was getting the same results.
I have added the G31 P{sensors.probes[0].value[0] + 8} to my homedelta and that is working fine.
The G32 was done with the bed at 60C and the hotend at 220C
I did the G32 and heightmap looks ok I guess
![alt text]
(image url)
So Should i do a G32 every time before a print,?
And should I do a G29 once and load the map or do that before each print also.?
Thanks
Thanks I will try adding in the homeall and see how that go's..
I think that is correct i think it changes the sensitivity level, but not sure and for me right now it's the only way the probe will work, without DWC thinking it is already triggered
When i first load DWC it shows red color in the probe value dro, when i run the macro it changes color and works..
Thanks
I'm not much of a programmer, so not real sure why the code is needed but the piezo will not work without the macro being run before a probe move.
The probe is set in analog mode.
If i don't run the macro before any probe moves the probe shows as always being triggered.
I am just looking to see if there is a way to have, G31 P{sensors.probes[0].value[0] + 8}, run at startup, like in config file or something along that approach. I think it will only need to be run once endless a reboot or estop happens..
make any more sense?
Thanks
Thanks a stupid mistake going blind in old age works now..
Have another question, is there anyway to put this code in the config. file
I have tried but doesn't seem to work.
G31 P{sensors.probes[0].value[0] + 8}
i have it in a macro but would like not to have to run the macro if possible, if for some change i forget to run the macro and run the g30 i always get the message probe
already triggered..
Thanks
Problem with G30 S1..
I home first then jog down to 5mm to 10mm above bed and in the web console i enter a G30 S1
It seems to probe 3 times and retract every time.
The probe doesn't stop at trigged height so i can't seem to get the correct Z offset value
the z after retract always seems to end up at around 7mm above bed
Its a delta printer and a precision piezo probe..
seems to be triggering ok seems it hit and retract fine, no crashing into the bed...
just doesn't stop at the trigged height..
this is my Z probe form config file
; Z-Probe
M558 P3 C"zprobe.in" R2 H5 F1200:800 T3000 A3 S0.03 K0
G31 X0 Y0 Z2 P720
M557 R85 S20
my firmware installed
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3RC2 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-05-11 14:55:01
Is the hotend assembled correctly? There should be a gap between the block and the heatsink.
Yep been using as is for a couple months no problem, as i stated in the first message it was fine with the pt100 thern but the wire broke and only thing i had on hand was the therm that came with ed3 v6 hotend so till i can get a replacement pt100 thats what i'm tring to get working..
Do you have a silicone nozzle sock on the block? They can help a lot with keeping a stable temp.
no sock been printing with PETG and find it was to sticky and messy for the sock.
Does the cooling fan kick on at layer 6? Does it blow on the block more than it should?
No I have found at least for me the PETG sticks and prints better with no fan.
Did you start tuning from room temp, or was it already warm?
start at room temp.
Did you do the tuning with the part cooling fan on at an average level like you'd have on during a print? That can help it keep up during a print.
No cooling fan during tuning, i have the fan running that's cooling the heat sink only..
I did make a new wire and hooked it up, did another tune and added the new values to config.g
let cool down to room temp and the set the temp to 240C, it overshot by around 2%C
and about 20 or 30 seconds seemed to stabilize at 240C was running 239.5 to 240,5.
Will try another test print tomorrow and see how that go's.
that's were i will find out if i get the fault, at least that's were i am now, no fault errors when tuning and none setting the temp in DWC..
my D is set to 7.6 how high can that go, or should i bother with only about 1% oscillation?
Thanks gary
Didn't go so good during print, the layers that were printed look fine, but print made it to layer 6 and then message heater fault, though i had captured the screen also but for some reason didn't get saved... haven't tried a new wire but looks like its next.. guess i go put one together..
Thanks gary
ran tune again got some different values, entered them into the config.g
and this is what i have now for a screen shot at 245C.. looks better, seems to be holding from 243.8 to 246.2 hits 246 drops to 243 then back to 246 keeps repeating that..
but ran 3 times after cooling and no heater fault.. will try a print later and see how that go's.
not as good as the pt100 but i guess not bad or is it?.
Thanks gary
ran m307 h1 and the values are there..
also tried heatint to 245 a second time and now i get the heater fault it was at 40C.
I tried a third time and got same results, and this time i had my multi meter connected in the temp setting and that read 40C also so seems like the temp is close at least at low temps if i can get it go past 40 again i will see what the meter says at the higher temps..
thanks for the interpolation tip so you think i should drop down from x32 to x16 ok i will give it a shot when i get the heater working...
may try a new wire, don't know where to go from here..
Thanks gary
Here is a pic of the heat chart, i got to heat this time to run with no fault, i set the temp to 245C
and as you can see it is jumping around it over shoots to 251 and then drops to 239 and back up and back down..
unrelated. whats your reasoning for not wanting to run interpolation?
never though about it would i be better off using?.
Thanks gary
Have some issues with the heater E0 faulting..
I have tuned the heater 4 or 5 time to 240c and it never errors it finishes and i get the tuned values and enter them in the config.g ...
but when i try to run a print and set the heater to 240 it faults before it reaches 50 to 70C
i re tune the heated it go's right up to 240C i enter the values again into config.g
let it cool down and try setting the heater to 240C and it faults again
i get the message not heating fast enough
It was working good with a pt100 therm, but wire broke and i had to replace with the standard ed3 therm, only thing i had on hand... changed all the config.g settings for the correct therm..
duet2 and firmware 3.1.1
any suggestions
heres my config.g and i put the autotune values at the top just to show what it came up with
code_text
heater tune
9/14/2020, 9:48:15 AM M307 H1
Heater 1 model: gain 426.3, time constant 274.4, dead time 0.7, max PWM 1.00, calibration voltage 23.0, mode PID
Computed PID parameters for setpoint change: P157.8, I11.161, D80.4
Computed PID parameters for load change: P157.8, I43.139, D80.4
end tune
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Sun Jul 19 2020 16:48:57 GMT-0400 (Eastern Daylight Time)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"My Printer" ; set printer name
M665 R176.402 L288 B85 H317.498 X0.000 Y0.000 Z0.000 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X-0.06 Y0.07 Z-0.01 ; put your endstop adjustments here, or let auto calibration find them
; Network
M551 P"gorf" ; set password
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 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X32 Y32 Z32 E32 I0 ; configure microstepping without interpolation
M92 X200.00 Y200.00 Z200.00 E173.5 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E800.00 ; set maximum instantaneous speed changes (mm/min)
M203 X4000.00 Y4000.00 Z4000.00 E1200.00 ; set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z1000.00 E500.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 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 P8 R0.6 C"!^zprobe.in" H2.5 A10 F400 T4000 ; set Z probe type to effector and the dive height + speeds
;G31 P250 X0 Y0 Z-0.306 ; set Z probe trigger value, offset and trigger height
M558 P0 C"!zprobe.in" R2 H6 F2800 4000 A4
G31 X0 Y0 Z-0.306 P492
M557 R65 S20 ; define mesh grid
; Heaters
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 A113.8 C611.3 D0.4 V23.0 ; Disable bang-bang mode for the bed heater and set PWM
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermocouple via CS pin spi.cs1
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 A426.3 C274.4 D0.7 V23.0 ; 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.25 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q35 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H-1 ; set fan 1 value. Thermostatic control is turned off
; 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
; Custom settings are not defined
Thanks gary