Due to my set of 12864 menu files being ever-evolving, I've put them up on github to give me some degree of code management:

https://github.com/mudcruzr/Duet-Maestro-12864-Menu-Files

As I've never used github before, I'd appreciate if someone could download or clone the repo and let me know if it's successful and if I've done it correctly or not.

cheers

0_1547829464630_Maestro_Menu_v1.1.zip.txt

Above please find v1.1 of my maestro menu files, as before I had to append the .txt to the end of the filename to allow the upload. Remove the .txt and unzip it, then upload the contents to your Display folder (/menu).

The changes are:
COOLDOWN added to the PREHEAT menu page and a poor attempt at the D3D logo on the main/info page.

enjoy

Can I ask which version you upgraded from?

If it was earlier than v2.2, I think you may need to add a M918 line into your config.g to initialise the 12864 display (minimally M918 P1). See https://duet3d.dozuki.com/Wiki/Gcode#Section_M918_Configure_direct_connect_display

and

https://duet3d.dozuki.com/Wiki/Duet_2_Maestro_12864_display_menu_system

and

https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md - Read the release notes for v2.02

I've updated a couple of the 12864 menu files to cope with the changes in 2.03RC1

As usual they are in https://github.com/mudcruzr/Duet-Maestro-12864-Menu-Files

2 Files required updates to cope with the changes in 2.03RC1

The new files are main_for_203RC1 and heat_for_203RC1

Upload the 2 new files, rename the existing heat and main to something like heat_backup and main_backup then rename the 2 new files to heat and main respectively.

Note these files are ONLY for using with 2.03RC1

Me too, I need to refresh the page as I get the "File not found" message if I press the refresh button.

info
About
Duet Web Control 2.0.0-RC3

Electronics: Duet Maestro 1.0
Firmware: RepRapFirmware for Duet 2 Maestro 2.03beta1 (2019-02-03b3)

I've updated a couple of the 12864 menu files to cope with the changes in 2.03RC1

As usual they are in https://github.com/mudcruzr/Duet-Maestro-12864-Menu-Files

2 Files required updates to cope with the changes in 2.03RC1

The new files are main_for_203RC1 and heat_for_203RC1

Upload the 2 new files, rename the existing heat and main to something like heat_backup and main_backup then rename the 2 new files to heat and main respectively.

Note these files are ONLY for using with 2.03RC1

Yes, you need to give negative coordinates see the wiki:
https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors

and the example config.g on that page.

Please post your config.g and your homing files (homeall.g, homex.g, homey.g and homez.g)

@phaedrux My only answer to that is: I have two genuine Maestros at the full £111.85 each lol.

@3dmntbighker Ask and Ye shall receive.... (Wow! talk about service)

2 files: A new version of main to replace your current one and a new image baby.img for the B/S (Babystep) graphic. You know the routine by now - delete the .txt, unzip and upload to the /menu directory.

BTW I've made the babysteps field alterable so you can tune Z from the main screen if you want.

0_1547845613823_babysteps.zip.txt

@bugsysiegals I can't see why not, but I'm on holiday now until July, but (if I remember) I'll look at it when I get back. If you don't hear from me by say the 5th or 6th of July, I've forgotten - send me a reminder, lol.

@mudcruzr said in duetbackup - CLI tool to backup your Duet SD Card:

@wilriker said in duetbackup - CLI tool to backup your Duet SD Card:

Release 1.1.0

I just released v1.1.0 and I think this will make @mudcruzr quite happy - as well as I hope that other users will also be happy with the new feature. Release notes below.

LOL

Happy? Happy? I'm absolutely ecstatic mate! Seriously, many thanks for a very useful tool.

Ah! not so happy now even with the exclude flag it's still including all the gcode files.

Command line:

./duetbackup -domain "192.168.0.52" -outDir "Feynman" -dirToBackup "0:/" -exclude "0:/gcodes"

(Sorry!)

@wilriker said in duetbackup - CLI tool to backup your Duet SD Card:

Release 1.1.0

I just released v1.1.0 and I think this will make @mudcruzr quite happy - as well as I hope that other users will also be happy with the new feature. Release notes below.

LOL

Happy? Happy? I'm absolutely ecstatic mate! Seriously, many thanks for a very useful tool.

Maybe I'm missing something here but why not simply plug the printer in via the smartplug and use your smartphone or even better Alexa to turn the printer on & off. That's what I do, before I go to my workshop I say "Alexa, turn on workshop" and everything that's plugged in via a smartplug switches on. Of course I can control each smartplug individually too.
Another advantage is that I can leave the workshop with the printers finished printing but with the hotend fan still running while the printers cool down and turn everything off later. Previously I'd wait, twiddling my thumbs, until the hotend had cooled down before switching off for the night.

@wilriker said in duetbackup - CLI tool to backup your Duet SD Card:

Release 1.0.2

I just released version v1.0.2.

• This release should fix the time zone issue @mudcruzr described.
• Also starting from this release the (callable) filename for all target platforms now is duetbackup - for this the files are package as either tar.gz or zip depending on target

Works for me, many thanks! (Windows 10)

I have a suggestion (only semi-seriously), if it's not too cheeky: an exclude switch, e.g.

./duetbackup -dirToBackup "0:/" -excludeDir "0:/gcodes" -domain "192.168.0.53" -outDir "./bkup"

(I didn't realise how many files I had accumulated in my gcodes directory, lol)

Under windows 10 I run:

.\duetbackup.exe -domain "192.168.0.53" -outDir ".\bkup"

(Tried it with & without the quotes and using ./bkup and .\bkup all with same error.)

and it errors with the following:
2019/06/01 20:15:32 Fetching filelist for 0:/sys
panic: time: missing Location in call to Time.In

The whole error message is here 0_1559416600853_Duetbackup_errors.txt

@dc42 Many thanks David

Is there any chance of a new build with these changes in (for those of us without the wherewithall to compile) please?

That'd work.

@bearer said in RepRapFirmware 3.0:

Should you not be able to use M401 instead of M280 to keep the menu files the same? I thought M401 called M98 P"deployprobe.g" which then can ve version specific?

I guess I could, but I expect RRF2 and RRF3 to diverge more and more as RRF3 develops and trying to include new RRF3 functionality while maintaining backwards compatibility with RRF2 seems a bit like making a rod for my own back. I fully expect the whole lot to be rewritten & redesigned more than once.