Solved Issues after prime

[dc42]

@heartleander81 I can see a jolt in the movement when the G1 E-0.6 line is kept as-is, but not if I change the E value to -0.5 or -0.8. This ties in with a report from another user.

I've just run the same file under the latest 3.4beta firmware, and the jolt is gone. So it's possible that the bug is already fixed. The scheduling code has change since release 3.3 but I need to check whether there has been a change that could fix this issue.

If you want to try the latest 3.4beta series firmware, you can find it at https://www.dropbox.com/sh/cq7q3g8coymo9s3/AABtPYEzV1_unETpKEMPInSia?dl=0. Use it with caution as I have only tested it briefly. It will work with the version 3.3 tool board firmware.

[Heartleander81]

@dc42

OK. I only need the .bin file? Will test it with caution.

[dc42]

@heartleander81 yes, just the .bin file for the MB6HC.

[Heartleander81]

@dc42 Unfortunately the bug is still there.

[dc42]

@heartleander81 thanks for testing it!

[Heartleander81]

@dc42 With pleasure. I like to help when I can

[Heartleander81]

@dc42 I think the board is not on Firmware 3.4 I must Look why

[dc42]

@heartleander81 said in Issues after prime:

@dc42 I think the board is not on Firmware 3.4 I must Look why

It may be that you need to upload the IAP file from the 3.3 release, to get a copy of it in the /firmware folder of the SD card, then run M997. https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet3_SDiap32_MB6HC.bin

[Heartleander81]

@dc42
I hadn't uploaded the firmware to the board via upload, but only tried using drag & drop. That was not possible so he installed the 3.3 again. I have now loaded the 3.4 via upload and install it. But it's taking an unusually long time.

[dc42]

@heartleander81 the firmware binary should install in about 30 seconds.

[Heartleander81]

I had the whole duet2 and duet3 firmware in the firmware folder.

Ok, that's been taking a lot longer. If necessary, I have to do it again via Bossa

[Heartleander81]

@dc42
I first flashed back 3.3 again.
Will make a backup of the SD card tomorrow.
Then I test the update to 3.4 Beta again.

[Heartleander81]

This post is deleted!

[dc42]

@heartleander81 if you are running with SBC then you will need to upgrade to the official 3.4beta2 release from the unstable feed of the package server first, so that you have a compatible version of DCS on your SBC.

[Heartleander81]

I forget who I must at Pi config the change stabil to unstabel.

Have anyone a link for me?

[Edit] I have found it.

[Heartleander81]

@dc42

Hello good news. The error is gone with the update to 3.4Beta2 that I got from you yesterday evening. Switching from M400 to T0 did not change anything. I will make test prints today if everything is going as usual.

[dc42]

@heartleander81, thanks for your feedback.

[Heartleander81]

This post is deleted!

[Heartleander81]

@dc42
I could still see something. The message for the G32 bed compensation now comes directly after the bed has been measured. In the past, the message came between the start code and the print. Using the example of the last code, not directly after the G32 but before the M400 / T0

[Heartleander81]

The first Print is done. 20x20 Cube with 1mm high.