@adammhaile said in M584 Driver does not exist with 3.4rc2:

@dc42 Oh excellent! Thanks!
Sorry if I added to the noise - didn't see any resolution on that other post about it, so thought maybe it was still up in the air. Forum pushed me to create a new thread instead of adding to an old one.

No problem at all. Thanks for posting.

@phaedrux okay

@dc42 That fixed it! Thanks. I guess we missed the RC2+2 announcement. We just updated our test machine and are vetting it now.

@chrishamm I grabbed the wrong error from the console - sorry. That was when I tried uploading a file from within a zip file which rightfully threw an error.

Better information on the issue: When uploading an individual file into a filament's folder, the file is not uploaded into the selected filament's folder - instead it is uploaded into the root filament folder.

@chrishamm tried your fix --> some of the dial buttons are not functional all the time!

After homing Z the nozle is positioned at 5mm and the move down Z-0.05 works one time only and then the Z-0.05, Z-0.5, Z-5 are not working but Z-25 works

--> my bed to have a nice mark now!

@owend thanks for confirming.

Closing this due to lack of response.

@vali3d closing this because it has been fixed in 3.4.0rc2.

@madeinta1wan yes it can

@phaedrux I guess mesh is still active after the print, but the maximum deviations on this printer is -0.090 / 0.090 mm.. no where near the .93mm that is "missing" from z-max. No other offset has been applied. On M999, the printer moves to 310mm without issue until after a print job completes. Then it's limited to 309.07mm.

I can confirm this behaviour on all 3 of my boards (2 Gloomy, 1 Duet). Tested with all internal and external plugins disabled just to be sure.

It's repeatable by hitting refresh on the tab and immediately switching tabs and waiting a couple of seconds, then tabbing back to a grey screen. I should also note that if the page is even partially rendered before tabbing off, the issue does not manifest.

I can not replicate this on firefox - only chromium based browsers (running on windows).

Notionally it seems to be influenced by the blue "connecting" dialog - if you go back to the duet tab before it closes the "connecting" dialog, the problem does not seem to manifest - but this could just be a red herring.

@chrishamm Ah, I see. Yes, good plan.

@theolodian please test using 3.4.0rc2.

Please can anyone else having issues with 3.4.0rc2 start a new thread to describe the problem.

@dc42 Thank you very much for this rocket-fast answer!

@phaedrux Thanks very much! Fixed.

@resam It was a shorthand version to ignore double (or even triple) slashes which are also permitted by FatFs, see http://elm-chan.org/fsw/ff/doc/filename.html But I suppose having /?/? instead of /* would also work.

@chrishamm https://1drv.ms/u/s!AplCFrF2DU0lh65DthnWsLuKB8b10w?e=oE297V

@dc42

I am happy to confirm that on RRF 3.4 rc1+3 +SBC and Duet Web Control 3.4.0-rc2pre the issue with M291 seems to be resolved.

Thanks! 😃 👍
-Max