This cube has come out with no visual difference up the seam again. I had the following PA values at the respected layers:
Layer | PA Value
25 | 0.7
50 | 0
75 | 0.9
100 | 0
125 | 1.1
150 | 0
175 | 1.3
200 | 0
225 | 1.5
No change at all other than it stopped extruding a little for 6/7 layers during the 1.1 value set of layers (layers 125 to 150).
M122 for this print:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-956GU-DJMSN-6J1F4-3SJ6N-1BNBF
Used output buffers: 5 of 24 (18 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 94256 of which 308 recycled
Exception stack ram used: 492
Never used ram: 10336
Tasks: NETWORK(ready,524) HEAT(blocked,1236) DUEX(suspended,156) MAIN(running,1668) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 02:37:52 ago, cause: software
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 10312 bytes (slot 1)
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 54.2, current 54.3, max 57.1
Supply voltage: min 24.0, current 24.3, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/1023
Driver 1: standstill, SG min/max 0/243
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max 0/972
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max 9/249
Driver 6: standstill, SG min/max 14/254
Driver 7: standstill, SG min/max 0/255
Driver 8: standstill, SG min/max 0/259
Driver 9: standstill, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 100.31ms; fastest: 0.08ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 169, MinFreeDm: 159, MaxWait: 7ms
Bed compensation in use: mesh, 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
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Segments left: 0
Stack records: 4 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: 202.15ms; fastest: 0.08ms
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 3
WiFi firmware version 1.23
WiFi MAC address XXXXXXXXXXXXXX
WiFi Vcc 3.32, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24592
WiFi IP address XXXXXXXXXXXXXX
WiFi signal strength -56dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
How far before the seam point on each layer should PA start to kick in because its literally right on top of the seam that the extruder shows some movement for PA. It doesn't change at all for the corners, its one continuous extrusion from start of layer to the end of the layer. I'm not sure it should really be like that....