Hey @dc42 -- nice to chat with you guys as per usual. I am actually going through and uncovering some of that particular aspect of the 12684 branch from the M3D side now. We have a few things spread out since Matt's departure, and we just found a MAJOR portion of work we had thought was lost. I'll be putting it up on the m3d repo soon.

Thanks,

David Hargrove
PrintM3D

@sparkymark79 glad that was it man.. lol, between the fb groups, forums, and github repos I regular... I have probably seen people with this problem close to a hundred times at this point.. I still have the manual with the incorrect(but seemingly correct-looking) layout.

@dc42 You don't have QF head yet? Did @T3P3Tony steal it from you? You gotta watch that guy... I'll see if I can get Mike to bring one to TCT for you.

~David@M3D

You and me both. lol... I went with the Graph Paper -> Binary -> Hex, then wrote it all into a hex editor. I know that somewhere in my head there's a better way to do this, but I can't seem to locate it.

The bmp2c-escher3d application that is used to create PanelDue checks the color depths of the bitmap before proceeding -- in the case of a 1-bit bitmap, it returns a warning stating that this has not yet been implemented. I'm unsure if the source of this application is available, I've only been able to find the executable. This could be a good place to start.

@mudcruzr Excellent. I just applied your menu files to one of my test printers and it looks great. Really good use of real estate on the main menu. I wasn't sure about the format of the image file in this case. I actually created the few i'm working with byte-by-byte -- do you have a different conversion method you'd be willing to share?

Thanks,

David

Very Nice! I am doing an extensive update to the Crane Series menus at the time. It's really great to see someone else's take on this. I feel like I've been the only person on earth doing this lately.

I've been so incredibly tied up with the launch of the Crane and QuadFusion head that I've been focused entirely on customer issues and improvements. Now that we are off the ground well I will be turning my attention back to active development.

If you're interested, I have created a number of icons for things like the hotend, heatbed, etc. I can provide them here but they will be making their way to the Crane github today. I'll post a few pics also. For now, I am going to check your menu files out.

Cheers!

David Hargrove
M3D

Good luck @dc42 and I hope everything goes well.

If anyone has Maestro specific Issues, I should be able to help you out! I will be watching the forums a bit more than usual.

Thanks,

David@M3D

Actually yes -- I have problems particular associated with the messenger and the forum post dialog that scrolls up from the bottom of the page. I've been using Chrome lately without any issues, but I haven't really tested... i'll run it through the machine gauntlet today and see if I get any issues.

~David@M3D

@SplatHammer I am glad you worked that out! I have been chasing issues down on a product for some time now, and it's amazing how a seemingly complex problem can turn out to be one of the most simple. now, let's see what you can do with that board!! Curious: Do you have some pics available of your build? I would really like to see it.

I also want to underscore what Ian said -- thank you for acknowledging you had made a mistake. We all can get very hot headed/upset with 3d printing, it's just the nature of the beast.... what separates the men from the boys, per se, is owning up to your problems and carrying on without getting hung up on the details, insulting someone, etc... This is another reason why I love the Duet community... we tend to have a lot of people with these qualities, and that fosters even more to follow their lead.

I am preparing to do a similar build that I will be utilizing as a test bed; it will be modeled very similarly to the design E3D has been using to show their toolchanger... the idea will be: solid, high-quality build with easy access to all components for the purposes of testing out various configurations quickly.

Thanks,

David@M3D

@deckingman You got my attention. We should talk about this. What's your schedule in the next 10 hours?

--David

@SplatHammer I have thoroughly reviewed this thread I don't see how these problems are related to the firmware at all.

Can you please post your config.g and config-override.g file as they exist currently on your duet SD Card?

To be quite frank, your assumption that you have a unique hardware issue related to the design of the board is totally unfounded. Is it possible that your board itself is flawed? Possibly, but even this is rare.

Allow me to offer some further words of advice; if you are using expensive hardware like legitimate hi-win rails, Olson Ruby Nozzles, that sort of thing.... you should develop an appropriate testing procedure in order to minimize damage to that hardware... I would not possibly just 'give it a go' on a design that I am not already vastly familiar with in terms of how it functions with Duet. The Duet Developers and Community are an AMAZING source of assistance, but we all must take ownership to some degree for our own projects.

If you wouldn't mind posting your config.g and config-override.g, which @Danal suggested you do but was seemingly ignored. Please, let us help you by verifying the content of the files.

Thanks!

David@PrintM3D

@deckingman Hey Ian, I hope you're well! I've had to go a bit dark on the forums and email lately due to our multiple impending launches. Just skimmed over this and I wanted to indicate one thing about logging. Logging, similar to the way most software systems/operating systems handle it, is done at prescribed 'levels' on the duet.

If you send an M111 you'll get a list of modules; On a Duet Maestro, this is what I am provided:

M111
Debugging enabled for modules: none(15)
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) WiFi(14)

While enabling all of the modules will most certainly fill your sdcard quickly, my recent troubleshooting has really only utilized Platform and Move; and with intense testing my Log file is only a few kb in size. I personally will likely keep my 'Platform' logging set to on no matter what.

I don't suppose your schedule is open today for a bit of a chat, is it? I wanted to discuss some firmware retract stuff with you, as well as some recent slicing milestones.

Thanks,

David@M3D

@dc42 You don't have QF head yet? Did @T3P3Tony steal it from you? You gotta watch that guy... I'll see if I can get Mike to bring one to TCT for you.

~David@M3D