Wow, awesome additions. Thank you!

Amazing work Mark! Thanks for your efforts !

That is bloody fantastic cant wait for it to be available

I think you did a fantastic job. Thank you for sharing.

Wow! This is awesome! Can't wait to do the calibrations on my machine. Thank you so much!!! I guess it eliminates the last small issues..

Good news! Thanks, Mark!

awesome work mark!

Very cool, can't wait until this is in the official release!

Awesome work! 👏🏻

Thank you for sharing your knowledge.

Very impressive man, great work

Awesome work👍🏻 Thank you💐

amazing stuff dude!

Superb work, this is going to make life easy

Hi Mark. Thanks for all your work. I have been testing your latest test version. The auto camera calibration is brilliant. A few observations: - I find navigating the Milestones klunky. I would prefer some tabs or buttons across the top (including an 'ALL' button) - when you accept a suggestion, it would be nice if the highlight moved down to the next open item. - something in the calibrate area changes the Driver/Motion Control Type to ModeratedConstantAcceleration which then sends an M204 before each move command and the machine moves like treacle - REALLY slow! - I can't to a Y axis backlash setting because it wants to move the Y axis to -37mm and my soft limit is zero. The primary fiducial is at Y 55.611mm. I guess I could move the fiducial back but will moving it muck anything else up? - the first time I tried the X backlash it showed a nice little plot at the end. The second time I didn't get the plot ?? It would be nice to manually or automatically save these plots for later analysis. High res PNG perhaps? - the test version seemed to install over the current version, even though I selected 'new directory' Win 10 Cheers, DG

@markmaker4345

2 жыл бұрын

Hi diggraph, The milestones were specifically added to prevent users from adopting the often "juicy-sounding" advanced/difficult options too early, i.e. before the basic machine setup is achieved. Some "clunkyness" is intended, to keep users from skipping over the essential (but maybe boring) stuff too easily. It's a bit like levels in a game. You have to earn them first. For the most part, the milestones are cumulative, i.e. all the solutions from earlier milestones are available in the later milestone, so adding an "ALL" is not really necessary. Most Issues & Solutions logic permanently reacts to any configuration changes, so these issues will always also pop up if you are in a later milestone. For instance, if you add a driver later, Issues & Solutions will help you set it up, no need to go back. Re the Motion Control Type: Make sure you understand and set the acceleration limits on the Axes: github.com/openpnp/openpnp/wiki/Machine-Axes#kinematic-settings--rate-limits Re the Y backlash calibration: Yes, your calibration fiducial should be further away, as described here: github.com/openpnp/openpnp/wiki/Vision-Solutions#calibration-primary-fiducial But you can simply move the fiducial coordinate, the location is stored on the head and can be captured there. There is no need to re-do all the other calibration fiducial related stuff. Just change the location and continue with the backlash calibration. There is nothing permanently tied to the calibration fiducial location, so you are allowed to move it around (except between the initial camera calibration and the nozzle offsets steps, those two must obviously be done as a pair). CAUTION: the same obviously does not apply to the homing fiducial. Never move the homing fiducial. Re the graph being stored: that's already the case, it seems you don't have the newest testing version. github.com/openpnp/openpnp/pull/1293 For further troubleshooting, I suggest you go to the discussion group. There are other users there that might be able to help, and it is easier to discuss, including through email. groups.google.com/group/openpnp _Mark

@diggraph

2 жыл бұрын

@@markmaker4345 Thanks Mark. I was on the group but managed to leave the comment on the video. I will try harder next time ;-) Y Backlash now done but no graph. 😞 I thought I had the latest version because I only downloaded it yesterday. V 2021-09-19_21-26-42 Where should I be looking for the latest? I have tuned the acceleration limits using the great MotionPlannerDiags you added and they work well but somewhere during the calib milestone the Motion Control Type got changed and caused the very slow behavior ?? DG

@diggraph

2 жыл бұрын

Ah found the graphs! I was thinking I saw them on the Issues page.

excellent work Mark, what is the reason for "Subject not found" error please??

@markmaker4345

Жыл бұрын

Thanks, @TORQ, you best go to the [discussion group](groups.google.com/group/openpnp), where you can post your log etc.

Awesome work Mark, when is the release? 😎👍

@markmaker4345

3 жыл бұрын

I hope this weekend. But not sure. Maybe only in the testing version for now.

Hi Mark, I have a few questions... 1- What is the distance from your down looking camera to the PCB? 2- What is the height of the elevated platform from the PCB? 3- Which camera and lens are you using that gives you this focal length range? thanks Matt

@markmaker4345

2 жыл бұрын

1- I have a 6mm lens and the camera pcb is about 90mm from the PCB. 2- about 12mm 3- ELP FullHD camera but in HD mode (720p 60fps) which is a crop of the full sensor area, i.e. the focal length is in reality longer than what the lens spec says. All this is more or less the outcome from the Liteplacer mechanics (I made my own camera holder, but the geometry is about the same). The important thing for (1) is that you see enough in the camera view to use the feeders you want, for instance the ReferencePushPullFeeder needs to see some sprocket holes and a lengthy OCR label. The BlindsFeeder needs to see some blinds in the cover, the larger the part pitch, the larger the area it needs to see. My camera sees a ~43mm x 24mm area in the HD mode (720p 60fps). That's what you need to aim for, a bit more would be better. _Mark