Posts made by streamliner

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

Hey there @3dmntbighker -- I think we have spoke in the past. I of course won't utilize the Duet Forums for a 'Palette 2 vs Quadfusion' discussion, because it simply will just result in unfounded arguments.

I too was quite interested in the Palette 2; I thought.. surely this is the multi-material solution I've been envisioning. But, I think we can say.... well... it's not quite what most of us expected.

One of the great things about the direction that we've taken M3D is that we aren't tied to any particular closed tech, etc any longer... and when I look at the Palette 2, this is all I see.

We have went from a fairly closed company to our latest and future product lines utilizing:

• Open Hardware -- This time in the form of the Duet 2 Maestro.
• Open Software -- the dc42 Branch of RepRapFirmware(DuetFirmware)
• Total Transparency; our community is taking the plunge with us.

As for slicing, I'm glad you asked; the future is truly bright here. With the latest updates to Slic3r and Cura, color mix slicing has become simple. I am personally developing a slicer; our community has 2 separate slicers in development, KissSlicer is becoming one of the most amazing tools we have -- check it out ASAP!

Tons of additional work is being done in the realm of post-processing scripts; 3 or 4 of these exist in our community alone. We're even investigating the 3MF format and, believe it or not, MS 3d Builder. In addition to things like pre-processing face groups in MeshMixer, using 3MFs for model separation data.... I have generated 3 or 4 fully functional workflows for color slicing; this isn't just simple layer color changes... i'm talking about full on, same layer change, multi-color(CMYK mixed) color.

Keep in mind that our professional printer line, the ProMega, is a CoreXY bot driven by a Duet 2 Maestro with optional quad and compound heads... so, i'd say you don't have anything to worry about. If you'd like, get with me and I'll provide you with some methods to begin experimenting with in terms of color slicing.

Thanks

David@M3D

@dc42 The replacement LCD that was being rushed to me is here now; and I've got a fully built out set of Menu entries. I will be testing in the next few minutes.

Thanks!

David@M3D

@antlestxp Would you mind sharing your config and describe the kinematics/overall nature of your printer? I would love to create suitable Spreadcycle settings for the Crane/Promega printer lines.

Thanks!

DavidH

@bass4aj I think one of the things @dc42 is indicating here is that when currents are properly tuned, spreadcycle results in better overall prints. Also, when the appropriate current is supplied the noise level is GREATLY reduced as to what testing we've done thus far.

We should look into dialing in our settings correctly for spreadcycle on the maestro.

~DavidH

@crussty Most certainly I am just trying to determine where the 'fracture' ocurred right now... this is not fun. I think I may just pick up on the most complete version of what @dc42 has and just update it inline.

@dc42: Speaking of, what branch of your dev firmware is currently the most similar to the feature branch: https://github.com/PrintM3D/RepRapFirmware/tree/v2-feature/morecomplete12864? I see what happened at this point...he was going to implement the feature branch, had to stop, and somewhere in between would have been an update.. i'm trying to construct a timeline to understand where to go back to.

Thanks,

David

@deckingman Yep! How are you doing Ian? We've been insanely busy preparing for the Crane launch... it has pulled me away from the Quad for a bit unfortunately, but, it will soon be back in focus. Things are going really well otherwise. We had a very, very interesting brainstorming session on active mixing last night... I will have to email the details to you.

I have the community refocused a bit to pick up on the 3MF standard, as it seems AMF has splintered and come nearly non-existent. On the other hand, the 3MF standard has been picked up by some very large companies that have put some very big promises behind it. I have to say in this occasion, in order to move past STL we do need some type of consortium/entity to truly take this to the next level.

Cheers

David@M3D

@dotorg Interesting -- I simply watched the Palette 2 promotional video and it seemed to give me a different impression. I am actually curating the Crane Line of 3d Printers from M3D, including the Crane Quad; it utilizes our QuadFusion Mixing Head and we offer a variety of color patched CMYK(process color) filaments. We've been able to produce around 55,000 colors so far... this is driven by a Duet Maestro with a 2-stepper expansion. That said, I have a particular interest in mixing... but from what you've said, and from the prints I've seen... now it just seems like the Palette 2 is a more sleek version of the Prusa MMU.

Cheers,

David

@dc42 In Fact -- I believe he followed it exactly, and as you say the only thing that I can't find is the Splash Image -- that's no problem. It seems nearly complete.

Now, I tried simply merging over his changes to the menu and associated files, but still ran into an error. I am actually getting my macos devmachine up again so I can use xcode... Eclipse is killing me. I use this machine for a lot of MCU prototyping and I think I am just getting a lot of conflicts because of this.

I'm restoring my mac workstation tonight and will establish n proper project tomorrow. I may have a few more questions for you; soon this will all be a lot smoother.

Thanks you for your time!

Cheers!

David

Thanks @dc42 -- I think I am getting close to determine what happened here... I plan to take on as much Maestro-specific stuff as I can. As far as getting us back on even footing... do you have any suggestions on going forward? Right now i'm doing a full folder diff between the v2-dev branch and the v2-12864nearcomplete branch on our side.

He has added a very substantial amount of Menu Items.. I am attempting to abstract them now. If you have any suggestions for how we can abstract this, I'm all ears... otherwise, I'll finish up here soon enough.

Also -- I'm still fairly new to the FreeRTOS concept, do you think the Maestro would benefit from a FreeRTOS build(or is that the public build?).

Thanks

David

@dc42 I'm going through commit history to determine what has happened.. it looks like at some point the project file for the 'v2-almostcomplete' build was removed from gitignore and became part of their ongoing updates to the m3d Repo... I'm trying to determine teh best way to unravel this.... is there anything I could do to simply assist with the merge?