Question on Z-Offset and Start Script, Also Nozzle Adjustment.

Phaedrux

Can you run an M122 in the console and post resulting diagnostic?

I notice in your config that you have 2 extruders specified. Are they the same? Some of the values differ.

M350 X16 Y16 Z16 E16:16 I1                   ; Configure microstepping with interpolation
M92 X100 Y100 Z400 E624:582                    ; Set steps per mm
M566 X1200 Y1200 Z18 E300:300                ; Set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z180 E1200:1200             ; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z100 E5000:5000             ; Set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E1000:1600 I30        ; Set motor currents (mA) and motor idle factor in per cent

Phaedrux

Do you have other filament to test with? Perhaps your PLA has gone stale.
Or perhaps the hotend is not getting as hot as you expect it to? That could explain the poor adhesion.
Can you verify the temperature of the hotend with a thermocouple?
Are the temps stable?
Have you run a PID tune on the hotends yet?
Are you sure your thermistor values in config.g are correct?

Sorry for the shotgun blast of ideas.

justinds89

I only have one extruder so I'm not sure why it shows two or how exactly to fix that.

As for extruding into free air. It appears to do this just fine (have extruded several hundred mms this way).

justinds89

I can try with other filament yes even though before the build I was using this filament.

I am using a PT1000 sensor and it shows the temp at room temperature is accurate. I'm not sure how to very if it is accurate when heated up though.

The temps do remain stable.

Here is the diagnostic.
M122
=== Diagnostics ===
Used output buffers: 4 of 32 (10 max)
=== Platform ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later
Board ID: 08DGM-956GU-DJMSN-6J1FA-3SN6P-TUNZF
Static ram used: 16152
Dynamic ram used: 100448
Recycled dynamic ram: 2184
Stack ram used: 1224 current, 4512 maximum
Never used ram: 7776
Last reset 00:00:22 ago, cause: software
Last software reset at 2018-08-01 18:15, reason: User, spinning module GCodes, available RAM 7776 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x04417000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 27.0, current 27.5, max 28.4
Supply voltage: min 24.3, current 24.4, max 24.6, under voltage events: 0, over voltage events: 0
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: 2018-08-01 18:16:13
Slowest main loop (seconds): 0.014056; fastest: 0.000046
=== Move ===
MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== 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 ===
Responder states: HTTP(1) 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.21RC4(08b3)
WiFi MAC address 00:00:00:00:00:00
WiFi Vcc 3.34, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 17088
WiFi IP address 0.0.0.0
WiFi signal strength -39dBm, reconnections 0, sleep mode modem
Socket states: 2 0 0 0 0 0 0 0
=== Expansion ===

justinds89

That is fine. I appreciate the help as I'm stuck on what to do.

I am fairly certain I have the thermistor values correct in config.g.

I have not PID tuned them and I'm not really familiar with the process.

Phaedrux

According to this: https://duet3d.dozuki.com/Wiki/Connecting_thermistors_or_PT1000_temperature_sensors#Section_PT1000_sensors
I don't think you have your PT1000 configured correctly.

You currently have

M305 P1 T100000 B4138 C0 R4700               ; Set thermistor + ADC parameters for heater 1

but should have

M305 P1 X501 R4700

That could explain your actual temperature being different from what's reported.

Phaedrux

Here is the wiki for tuning the heaters.

https://duet3d.dozuki.com/Wiki/Tuning_the_heater_temperature_control

Getting the temps correct will be first step.

justinds89

Okay, I will check this out and report back. Thanks!

I can confirm it does the same thing with different filament.

justinds89

@phaedrux

I looked at the config and everything as far as the heaters go looks correct. This is the settings.

; Heaters
M307 H0 B0 S1.00 ; Disable bang-bang mode for the bed heater and set PWM limit
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 X200 ; Configure thermocouple for heater 1
M143 H1 S280

justinds89

Heater 0 is the bed.
Heater 1 is the hotend for extruder 1.

justinds89

Wow, I upped the temp by 20 degrees and it is now printing fine.

I guess it was grinding filament because it wasn't hot enough to melt it properly.

Looks like I will be PID tuning it when I figure out how.

Thanks for the help man!

dc42

@justinds89 said in Question on Z-Offset and Start Script, Also Nozzle Adjustment.:

Wow, I upped the temp by 20 degrees and it is now printing fine.
I guess it was grinding filament because it wasn't hot enough to melt it properly.

Your slicer may be configured to reduce the extrusion temperature after the first layer. Also, if your print cooling fan is directing too much air at the heater block and the nozzle instead of at the print, the nozzle temperature may drop a little when the print cooling fan turns on, which is usually at the start of the second layer.

justinds89

@dc42

That makes sense, but when monitoring what the temperature shows in the web interface it shows that the temperature is what is set and steady.

I'm using 200 for PLA which is what I've always used in the past. Now though I had to up it to 220 to get a successful print.

I still have no clue on how to PID tune things if that is the route I need to go after reading the wiki.

I can confirm my Slicer isn't dropping the temperature after the first layer.

justinds89

@dc42

I will try to check again and make sure the temperature doesn't drop when the fan kicks on.

Phaedrux

Did you correct the PT1000 configuration for heater 1 as mentioned above? That could easily explain why you're 20 degrees off expected.

justinds89

@phaedrux

I didn't change anything as my configuration has this set for heater 1:

M305 P1 X200 ; Configure thermocouple for heater 1
M143 H1 S280

I thought this was correct?

justinds89

@phaedrux

I should note I have a PT100 connected to the daughterboard.

Phaedrux

Ah I see. Earlier you had said pt1000. Easy typo to make. I wish they had slightly different names.

The link I posted earlier for PID tuning has a lot of information but basically start from a cold machine and run the M303 command with the parameters for the heater you want to tune.

https://duet3d.dozuki.com/Wiki/Gcode#Section_M303_Run_heater_tuning

M303 H1 S220 ; tune hot end to 220c
M303 H0 S60 ; tune bed to 60c

After they are finished you can send M500 to save the values to config-overide so they are loaded at startup, or ~~send m303 again with no parameters~~ Send M307 H1 and it will report the PID values it found for heater 1 which can manually be entered into config.g. it's easier to just use m500 and then copy and paste the values over if you wish. M307 H0 will give the results for the heated bed.

justinds89

@phaedrux

Sorry for the confusion.

As I understand I need to just run the M303 command? I don't need to plug in specific values?

Appreciate all the help. Getting closer to having this up and running!

Phaedrux

M303 H1 S220 The H1 tells it to tune heater 1 which is the hotend, and to target 220c as the temperature. The tuning will give some messages about what it's doing in the console. It will heat up and cool down the hotend which can take 10 or more minutes. When it's done you can send M307 H1 and it will tell you the values it came up with for heater 1. Then send M500 to save the values.