Layer Shifts with Duet3

PCR

Dear Christian,

first of all. Love your work Greetings from Berlin

2nd. Can you post your M122?

And the output M98 P"config.g"?
And the output of M569 P1.0

What current rating does the nema 17 has?

Best

JoergS5

X is on the 3HC board, so the M122 B... is valuable also.

M350 uses U, but U is not defined. Same with Tool1 offset which uses U.

Veti

@CR3D said in Layer Shifts with Duet3:

M569 P1.1 S0 ; physical drive 1.0 goes forwards Y0
M569 P1.2 S1 ; physical drive 1.0 goes forwards Y1

you have enabled spreadcycle for other drivers but not y?

CR3D

@PCR thank you

Here is the M122:

I555
M115 B1
Status
Idle
Mode: FFF
Tool Position
X
0.0
Y
0.0
Z
0.00
Extruder Drives
Drive 0
0.0
Speeds
Requested Speed
0 mm/s
Top Speed
0 mm/s
Sensors
Vin
23.7 V
V12
12.2 V
MCU Temperature
34.8 C
Z-Probe
0
 Tools
 Extra
 Control All
Tool	Heater	Current	Active	Standby
Links
T0 - Load Filament	Heater 1
standby	210.0 C	
210
210
Bed	Heater 0
off	25.1 C	
0
0
Temperature Chart
m122
25.11.2020, 12:07:25	m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2-beta1 running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956L2-G43S4-6J9F0-3SD6S-9U56D
Used output buffers: 2 of 40 (12 max)
=== RTOS ===
Static ram: 154820
Dynamic ram: 165960 of which 236 recycled
Exception stack ram used: 320
Never used ram: 71880
Tasks: NETWORK(ready,142) ETHERNET(blocked,110) HEAT(blocked,278) CanReceiv(blocked,865) CanSender(blocked,372) CanClock(blocked,352) TMC(blocked,52) MAIN(running,1122) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 03:48:29 ago, cause: software
Last software reset at 2020-11-25 08:18, reason: User, GCodes spinning, available RAM 71688, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
Error status: 0x020
MCU temperature: min 33.7, current 34.8, max 36.0
Supply voltage: min 23.5, current 23.6, max 23.7, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, current 12.3, max 12.3, under voltage events: 0
Driver 0: position 0, standstill, reads 3319, writes 15 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 3319, writes 15 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 3320, writes 15 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 3324, writes 11 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 3321, writes 15 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 3325, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2020-11-25 12:07:23
Slowest loop: 10.79ms; fastest: 0.22ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.6ms, write time 2.8ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, 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  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 37.81ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0
=== CAN ===
Messages sent 54857, send timeouts 54857, longest wait 3ms for type 6024, free CAN buffers 48

@JoergS5

Here is the M122 B1

m122 B1
Diagnostics for board 1:
Board EXP3HC firmware 3.2beta (2020-09-14b1)
Never used RAM 150.1Kb, max stack 320b
HEAT 314 CanAsync 367 CanRecv 357 TMC 63 MAIN 294 AIN 258
Last reset 03:49:43 ago, cause: software
Last software reset data not available
Driver 0: position 0,  standstill, reads 7430, writes 15 timeouts 0, SG min/max 0/0
Driver 1: position 0,  standstill, reads 7433, writes 14 timeouts 0, SG min/max 0/0
Driver 2: position 0,  standstill, reads 7434, writes 14 timeouts 0, SG min/max 0/0
Moves scheduled 0, completed 0, in progress 0, hiccups 0
No step interrupt scheduled
VIN: 23.7V, V12: 12.2V
MCU temperature: min 42.4C, current 42.7C, max 42.9C
Ticks since heat task active 89, ADC conversions started 13783080, completed 13783080, timed out 0
Last sensors broadcast 00000000 found 0 93 ticks ago
Free CAN buffers: 36, messages lost 0, duplicates 0, oos 0
NVM user row de9a9239 aeecffb1 ffffffff ffffffff

@JoergS5 you are right with the U-Axis, because this was the main firmware of my idex machine... but I think this would not cause an layershift at X, or?

@Veti

Yes you are right, for the Y-Axis with the NEMA 23 I had no problems at the moment...but I can also change this...

I attached the datasheet of the NanoTec Motor here:

NanoTec_NEMA17_SCA5618X2804-A.pdf

I changed the motor current a few times... now it is a little bit higher...

Regards Christian

JoergS5

@CR3D said in Layer Shifts with Duet3:

I think this would not cause an layershift at X, or?

I am not sure, if you have tool changes somewhere and U is undefined. I just want to exclude possible reasons.

Veti

@CR3D said in Layer Shifts with Duet3:

Board EXP3HC firmware 3.2beta (2020-09-14b1)

can you update to the latest beta? just to rule out a problem with the beta firmware.

CR3D

Now I updatet the firmware of the main and expansion board to 3.2 beta 3.2

And get this error message:

Board 1 does not have input handle 1100

@dc42 do you know this issue?

dc42

@CR3D said in Layer Shifts with Duet3:

Board 1 does not have input handle 1100

@dc42 do you know this issue?

That can happen after you update tool or expansion board firmware if you do not reset the main board afterwards, so that config.g is run and sets up whatever heaters etc. you have configured on the expansion boards.

I've just released firmware 3.2beta4 at https://github.com/Duet3D/RepRapFirmware/releases/tag/3.2beta4 so please use that instead of 3.2beta3.2.

CR3D

@dc42

Ok you are right! Thank you!

Now I installed 3.2 beta 4 ...

Do you have any ideas about the layer shifts?

dc42

Do you still get the layer shifts with 3.2beta4?

Is the axis showing the layer shift controlled by a motor attached to the main board, or to the expansion board?

CR3D

The testprint with FW 3.2 Beta 4 is running now...till now it looks good...

But did you changes in this way?

The axis with problems was connected to the expansion board...

CR3D

So the test print runs without problems!

@dc42 did you made any changes in this direction?
I did not read something about a topic like this in the changelog...
Please let me know, because there are machines outside from us with the old firmware...

Regards Christian