Ok - with RC7 actually installed it appears to be working fine. I've got 10 minutes into a print that was failing after 5.

Thank you for the awesome support as always and apologies for being a stupid user !

Keep safe.

(I'll close the issue on Github when I finish at work).

David

How weird. I didn't check that the update took before I posted - sorry- from the apt-get update on the console it looked like it had.... I was indeed still on RC6. I'll report back once I test it.

Hi @chrishamm - I'll report it on github when I get home but I just tested RC7 and confirm the same error.

Kind Regards,

David

"Error: Internal Error in Spin at ../src/Linux/LinuxInterface.cpp(54)"

As it says. Using a Duet 3 and expansion board. Latest RC is throwing that error generally about 5 minutes into a print.

Have tried a few prints that have never been an issue before so I assume it's an issue with the RC.

Any suggestions?

Keep safe all

David

This has been driving me crazy for months - can confirm console output is restored for G32 (and others for me) with with 2.1.1

Thank you.

I'm glad it's not just me. This started as soon as I moved to Duet 3 h/w. If I press the level button on the panel due - then I get the expected output in both console and web interface via the pop up.

If I run G32 via the web console then the printer does run the macro as expected but I don't get any output.

Did anyone find a solution to this?

So that worked very easily - thank you @dc42 - for anyone else wanting to do the same - I used this in config.g.

M584 X0.0 Y0.1 Z0.2:1.0:1.1:1.2 E0.3 ; set drive mapping with dummy driver on mainboard (0.2)
M906 X1400 Y1400 Z100 E800 I60 ; set to low power

M584 X0.0 Y0.1 Z1.0:1.1:1.2 E0.3 ; set drive mapping for the real z steppers
M906 X1400 Y1400 Z1000 E800 I60 ; set a sensible power level

M584 X0.0 Y0.1 Z0.2:1.0:1.1:1.2 E0.3 ; add the dummy drive (still at 100mA) back to the group.

This does break automatic bed leveling since RRF3 now thinks I have 4 independent z's and I'm only declaring 3 in bed.g - I don't think there is any easy solution for that but if anyone has a good suggestion...

Thanks !

@dc42 and that'll be what gets you the reputation you have in these parts !

Thank you for the quick reply. I am too tired to try it tonight but I will do so tomorrow and report back / mark resolved assuming it works !

I don't know if you want to rename the thread to make finding that answer easier.

I looked pretty carefully and it wasn't advice I found elsewhere.

Thanks again !

@deckingman thank you for that. I assume it's also true you can't run z probes on an expansion board (still).

It's not the end of the world I just have to extend the wiring for all three of my z steppers and move them to the main board.

I wonder if @dc42 could comment as to when either of the above will be solved (or indeed it they are solved in the current beta).

Just by way of additional information.

Moving the bltouch to the expansion board (1.io0) didn't work. It no longer seemed to work at all.

Moving it back to 0.io7 and it works again fine (responds to M401 / M402)

The obvious thing would be to move my z steppers to the main board but I have a cable length issue.