yasas

undefined

We are excited to announce that Duet3D Plugin Repository [beta] is finally live at https://plugins.duet3d.com/

Feel free to check it out

If you have already developed one or a few plugins, we would love to see them in our new Plugin Repository.

To list your plugins, follow the guide here: https://plugins.duet3d.com/guide/submission.html
(spoiler alert, the process is very simple).

As it's a beta release, things might not be perfect and it currently has features like

Plugin approval
Plugin removal
Plugin listing/searching

If you come across any problems, we'd appreciate it if you can let us know here in this thread.

PS. We'd also love to hear any feedback about how we can make the plugin approval process better.

Thanks!

undefined

@jay_s_uk
Currently, it only shows the compatible version for the latest release.
However, older releases can be downloaded from the sidebar of each plugin page. All releases can be seen there for a plugin.

We are working on listing the compatible version for each plugin as well. Thanks for raising it!

undefined

@stuartofmt Hi @stuartofmt I'm sorry to hear this I have missed the GH issues as for some reason they have been closed/wasn't notified. I will update the error messages in case someone else runs into the same issue.

undefined

@stuartofmt Hi @stuartofmt I'm sorry to hear this I have missed the GH issues as for some reason they have been closed/wasn't notified. I will update the error messages in case someone else runs into the same issue.

undefined

Hi @stuartofmt

Sorry I missed this.

No no that's totally fine. And I really appreciate it.

Take your time.
(And I know it's kind of a big ask given the calibration prints/printouts and everything. But it will definitely be helpful. Thank you.)

undefined

@stuartofmt
Yeah I agree. But having an estimate would be sufficient to support the calibration process.

So the test print we ask the users to print and take a timelapse of does actually contain markers so we can come up with a mapping between real-world and pixel coordinates.

Yeah you're right. It was also our initial though to use the calibration image and take images from different coordinates but then later we realised that it would potentially involve a lot of human errors. Hence, the test print(test_model.stl). But definitely it would be helpful to take different images of it from different coordinates as opposed to only taking from the timelapse coords.

For the time being, yes. The calibration print(test_model.stl) and its timelapse would allow us to determine the camera coordinates/perspective to some extent. It's not perfect but it gives an estimation that's within the tolerance levels we accept.

undefined

Hi @stuartofmt
Definitely. Appreciate the feedback. It allows me to think from many other perspectives which I didn't consider before. So thank you.

To address the points.

It's not a requirement. Step 2 in the instructions are so we can perform real world to image relation and find the perspective (elevation, azimuth, distance)
Mentioned it as moving the bed towards the camera because usually for bed slinger printers when timelapses are taken the bed is moved a bit forward for a clearer image of the print. Wanted to generalize a bit but seems I have done the exact opposite.
Yes, exactly. This information will be helpful in finding an offset per setup as we can make a more accurate connection using perspective data we determine/calculate from point 1 above.

Again, thanks very much for questions. Super helpful.. Will change the document appropriately

undefined

Hi @stuartofmt

Thanks for the questions/suggestions.

So in Step 1, what we're trying to do is to calculate intrinsic camera parameters so we can get rid of as much distortion as possible. It's in Step 2 that we're trying to determine the perspective.

I believe that in the event the camera is fixed, one workaround would be to print the grids on a smaller paper(or 1/2 of letter/A4) and fixing it on a board(ex: chopping board) using clips, so the paper would be flat, and capture an image from the camera.

About XYZ coordinates: As most of the time timelapses are taken by taking the extruder out of the way and moving the bed towards the camera, it would be helpful to know those coordinates. For example img, in this case roughly X=0, Y=180. Now if we assume X=0, Y=0 is in the center. In that case, for the above image roughly X=-0.5bedsize, Y=-0.5bedsize.
(And yes, Z should be disregarded)

I'll update the document/post. Thanks very much for raising these. Hadn't occurred to me earlier.

Cheers

undefined

Hi all,

I am Yasas, a software engineer working with Duet3D.

We are working on a part quality monitoring project (which is also my Master's research) and we need your help with a few things things.

A set of calibration images for your printer (step 1 of Instructions.pdf)
A calibration print (step 2 of Instructions.pdf)
Timelapses that you've been recording/will record as a collection of images and and the associated gcode that you printed.

Attachment - Instructions.pdf

For sharing, feel free to use Dropbox/WeTransfer or a similar tool.
I can also arrange a Google Drive link upon request.

PS:
- Make sure not to upload any prints with commercial sensitivity.
- Any images/emails/files you provide will be handled/stored/used safely.

Thanks very much!

undefined