Voron 0.1, M5P, EBB36 - Random unable to parse errors

[Titus A Duxass]

I've just completed my V0.1 build and have ran through the Orca calibration steps - all went well.

I am now getting random "unable to parse move G1 E F2100 errors when printing.

I've tried several files that I downloaded from printables and it happens on them all. On the third attempt it printed without it happening.

Can someone point me in the right direction to fix this?

TIA

TAD

[mvdveer]

It may be in the slicer profile. Can you try a different profile and see if the problem persists.

[Titus A Duxass]

That also came into my head while I was watching the darts last night.

I use the same slicer for both my V2.4 and V0.1, the V2.4 does not have the same issues.

I'll give it a try.

[Methos]

On 2/8/2024 at 8:11 PM, Titus A Duxass said:

I've just completed my V0.1 build and have ran through the Orca calibration steps - all went well.

I am now getting random "unable to parse move G1 E F2100 errors when printing.

I've tried several files that I downloaded from printables and it happens on them all. On the third attempt it printed without it happening.

Can someone point me in the right direction to fix this?

TIA

TAD

This is the slicer; notice the E does not have a number after it.

I would copy V2.4 working profile and just edit the bed size.

I've had Orcaslicer give me very wrong E values before, like E-99999999.99999, which Klipper did not like.

Cheers

[Titus A Duxass]

On 2/15/2024 at 11:47 PM, Methos said:

This is the slicer; notice the E does not have a number after it.

I would copy V2.4 working profile and just edit the bed size.

I've had Orcaslicer give me very wrong E values before, like E-99999999.99999, which Klipper did not like.

Cheers

I haven't changed anything but it has stopped doing it now.