This is not a problem, but more of a kudo's!
I had just recently purchased the Magnetic Filament sensor for one of my extruders and was working on calibration. I had a fairly long (12 hour) print going. During the print, the sensor kept telling me the extrusion amount was low. At first, I thought it was something I was doing. I kept checking the sensor and the machine. Finally, I ran a print where it wasn't extruding anything. It appears my extruder motor was going out slowly. Every time I looked it was working, but when I walked away it stopped.

I replaced the motor and everything was running smoothly again! So glad I purchased this, will be getting more in the future!

I just went ahead and updated to 3.0 (2020-01-03b3) and everything is working so far. Probably just a bug or bad update, because it was working before and after the 2.05.1 update.

@Danal
I'm not saying there is anything wrong with the release. Just noting what I had to go through to get things working. Its my belief that removing the additional firmware (which would be for your board) is what resolved my problem, though it could have just been the final upgrade to the v3 RC12.

As a side note, I'm still not getting "filaments" to work. The config.g for those doesn't execute. Though they did before all my recent updates... have to rely on my slicer for most things still.

Okay, so I made some success on getting this to work this weekend, purely on accident. I was upgrading to the new web console and had an issue where the Bed was no longer being displayed in the tools of the web console after updating to Duet Web Control 2.1.7.
I updated the firmware to 3.01-RC12 (2020-05-06b1), but still no change.

Prior to finding the solution to my Bed heater problem, I removed config.json and any file "duet3" in the name. I don't know why, but this appears to have resolved the problem with my G10 offset not working. Now when I select the tools in the PanelDue the Z offset changes immediately as expected. I suspect these files were included from my original upgrade to v3.0 as they were included in the Duet2and3Firmware-3.0.zip.

Ultimately I found the problem of my Bed not showing up being related to an additional "M140 H0" command being needed after defining it in the config.g.

So I upgraded the firmware and ran the tests again. Even adding 0.2 to the Z didn't make a change. I made the change while the printer was going just to make sure.

Board: Duet WiFi 1.02 or later + DueX5
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.01-RC6 (2020-04-03b3)
Duet WiFi Server Version: 1.23

Went from:

G10 P1 R0 S0 X17.6 Y-12.8 Z0.2

To:

G10 P1 R0 S0 X17.6 Y-12.8 Z0.4

No change. Doing baby-stepping does change the height.

Yeah, this seems to be a constant battle of funky workings with each code update. I updated to this version to battle a problem I was having with the last upgrade. Each time something different. Maybe I just need to re-reflash.

Only my tpost0.g has anything:

M116 P0

Getting things at the exact same Z-Height is a challenge and have always been able to utilize this feature to fix the issue.

Since I'm tired of chasing the next fix, I'll probably just adjust this in the slicer onToolChange script for now, since that's essentially doing the same thing as using the BabyStepping.

Does anyone have any ideas? I was looking through my G-Code output and not seeing anything that would silently set the offset. It was working in the last version of 2.x I was running, but this is the first time since upgrading to the 3.x that I've tried printing with both heads simultaneous.

I could try dialing the heads in more, but that hadn't been necessary before.

Do those parts have a lot of single extrusions? I found this exasperated this issue. Slowing down the print, re-slicing to reduce/remove the single extrusions helped, but obviously not a total solution.

So I have two tools defined in my config.g and up until recently had only been utilizing one of the tools. Now that I'm attempting to use the other tool and can't get the Z-offset to align. I have tried to change the Z offset in both directions and shows no change in the height of the second tool offset from the first tool.

Board: Duet WiFi 1.02 or later + DueX5
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.0 (2020-01-03b3)
Duet WiFi Server Version: 1.23

;;;;;;;;;;;;;;;;;
;;;   Tools   ;;;
;;;;;;;;;;;;;;;;;
;; Tool 0 - Extruder 0 - Chimera Head 1 - Mounted on Petsfang Chimera with custom TronXY Offset.
M563 P0 D0 H1 F0                          ; Define tool 0 -> Heater 1 -> Fan 0
G10 P0 R0 S0 X0 Y-13 Z0                         ; Set tool 0 axis offsets

;; Tool 1 - Extruder 1 - Chimera Head 2 - Mounted on Petsfang Chimera with custom TronXY Offset.
M563 P1 D1 H2 F0                           ; Define tool 1 -> Heater 2 - Fan 0
G10 P1 R0 S0 X17.6 Y-12.8 Z0.2                  ; Set tool 1 axis offsets

T0                                        ; Select the first tool.

Any suggestions? Anyone else having this problem?

I just went ahead and updated to 3.0 (2020-01-03b3) and everything is working so far. Probably just a bug or bad update, because it was working before and after the 2.05.1 update.

@TC said in Filament type assignment:

"state.currentTool

Thanks! I'll look into that. Actually I think after my update to 2.05.1 my filament config.g macros aren't even working. Going to check into that.

This is not a problem, but more of a kudo's!
I had just recently purchased the Magnetic Filament sensor for one of my extruders and was working on calibration. I had a fairly long (12 hour) print going. During the print, the sensor kept telling me the extrusion amount was low. At first, I thought it was something I was doing. I kept checking the sensor and the machine. Finally, I ran a print where it wasn't extruding anything. It appears my extruder motor was going out slowly. Every time I looked it was working, but when I walked away it stopped.

I replaced the motor and everything was running smoothly again! So glad I purchased this, will be getting more in the future!