Duet Maestro users: can you share a set of menu files?
-
@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.
-
@mudcruzr said in Duet Maestro users: can you share a set of menu files?:
@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.
Dude
Looking at the main page it looks like you can't get another line in there at the bottom. I'm wondering if you may as well drop everything a bit and make the icons a bit larger? Just giving feedback since you are putting in the effort. Shame to waste that blank bit at the bottom.
-
@3dmntbighker That blank bit at the bottom is where M117 messages display. I may yet do away with it as the only messages I ever see are the ones I have in my slicer start G-code and end G-code: "Print started" and "Print finished" lol
-
@mudcruzr said in Duet Maestro users: can you share a set of menu files?:
@3dmntbighker That blank bit at the bottom is where M117 messages display. I may yet do away with it as the only messages I ever see are the ones I have in my slicer start G-code and end G-code: "Print started" and "Print finished" lol
Hmm, actually, that being the case I vote to keep that in place. #thumbsup
-
I'm a little late to the party but finally sharing a set of menu files for the 12864 type displays.
https://github.com/tinkerlifeprojects/DUET3D_12864LCD_MenuFiles
They design is loosely based on the "TinkerFirmware" for the ultimaker printers. It has two "Main" pages with shortcuts to common functions and then a set of menus for controlling more aspects of the printer.
Any suggestions or requests are welcome
-
@jottesman said in Duet Maestro users: can you share a set of menu files?:
I'm a little late to the party but finally sharing a set of menu files for the 12864 type displays.
https://github.com/tinkerlifeprojects/DUET3D_12864LCD_MenuFiles
They design is loosely based on the "TinkerFirmware" for the ultimaker printers. It has two "Main" pages with shortcuts to common functions and then a set of menus for controlling more aspects of the printer.
Any suggestions or requests are welcome
Nice menus, but your bed.img file is missing from the repo mate.
-
@mudcruzr Good spot. I've uploaded the "bed.img" file to the repository. I think it may actually be the one you uploaded (I liked it so much)
-
love the open source thing every one put is toutch for a great cause i just canot code anything i want to give my apreciation to all of you guy's!
-
@jottesman
WOW man, those are great. Have not chance to look into it deep but first impressions are WOW.
What have you used to convert bitmaps? -
@agniusm very glad you like them. I will continue to try and update them, especially if you find any bugs or have any requests etc. Just let me know.
My method of creating the images was far from streamlined. But because they were small images it didn't matter too much.
I started in paint3D (Any photo editor will do but paint 3D has a pixel brush and lets you zoom in far enough that a 10x10 grid is big enough to see properly.)
Moved to paint to convert to monochrome bitmap
uploaded file to this site to convert to hex
Then manually copied into a Online hex editor and added the width and height at the start. (Just be careful to write the width and height in hex, ie 10 is 0A)
If anyone has a more streamline method though I'd be eager to hear it.
-
i know this topic is pretty old, but hadn't find anything better around. The method sounds good only problem is the monocrome .bmp i get out of paint are way bigger than they shall be according to pixel dimension and byte rules in the begin of the thread... any help ?
