Пікірлер

• 
  @markmaker434526 күн бұрын

  Please read the user group. _Mark

• 
  @djrezafxАй бұрын

  Hello Engineer, I had a question, what kind of camera did you use for these devices, do you have a part number?

• 
  @markmaker4345Ай бұрын

  I'm using the ELP Full HD camera No. ELP-USBFHD01M. "Full HD USB Camera Module 1080P USB2.0 OV2710 Color Sensor Support MJPEG". I recommend longer lenses than they usually advertise (>= 6mm).

• 
  @markmaker4345Ай бұрын

  I forgot to mention that this Full HD camera requires two root USB ports on the computer, while the recommended ELP 720p camera model can be operated on one USB port.

• 
  @contomo5710Ай бұрын

  openSCAT?? that sounds disgusting

• 
  @technomech303Ай бұрын

  I'm getting started on this software, and I must say that this video has proven to be extremely valuable. Thank you so much for sharing your knowledge.

• 
  @markmaker4345Ай бұрын

  ;-)

• 
  @endimac73637 ай бұрын

  Fantastic. Can you say what bootom camera model you are using ?

• 
  @markmaker43457 ай бұрын

  I'm using ELP FullHD cameras, but at reduced 720p resolution, which then runs at 60fps. But the recommended camera is the ELP 720p one, because you can then attach wtwo cameras to one USB port, whereas with my cameras I need two ports (bandwidth). See the recommended cameras in the Wiki: github.com/openpnp/openpnp/wiki/Build-FAQ#what-should-i-build

• 
  @svetozar1619 ай бұрын

  Hi your project is very best! I have one problem. Thickness of tape inset is very small. Real thickness components tape approx. 0,6 mm! Sliding is so tight. Sixagonal shaft too very big. Where are is a change it? Thank you

• 
  @markmaker43459 ай бұрын

  Thanks! Only the small and fast to print Tape Inset needs to be reprinted to adapt a different tape. See at 4:40 in the video where the tape is inserted. In OpenSCAD use the Customizer (right side pane) and there the Tape Specification section to adjust tape thickness etc. "Sixagonal shaft"? I don't understand. For better discussion, go to the OpenPnP discussion group at groups.google.com/g/openpnp.

• 
  @svetozar1619 ай бұрын

  thank you@@markmaker4345

• 
  @WillianMai10 ай бұрын

  Saw your post some months ago. Now I am revisiting. Why would they reject it? I just don't get it. Aren't they open to improvements and fixes?

• 
  @markmaker434510 ай бұрын

  Well, I'm not neutral in this, so you see for yourself in the Pull Requests I made. All is linked from my blog. makr.zone/smoothieware-new-firmware-for-pnp/500/

• 
  @yoremkastor11 ай бұрын

  Open source but no step file anywhere...

• 
  @markmaker434511 ай бұрын

  It does not work that way. The model is parametric. Best watch the entire video, especially the part about the test prints. You'll need to download OpenSCAD, but don't worry, you just enter Parameters in the easy to use Customizer GUI, no need to really have any OpenSCAD skills.

• 
  @yoremkastor11 ай бұрын

  @@markmaker4345 Yeah but that is a whole new learning curve. I am just looking for examples to edit. Thx for the reply.

• 
  @sergea1138 Жыл бұрын

  Fantastic

• 
  @pasplusvite Жыл бұрын

  merci

• 
  @fabiankropp1792 Жыл бұрын

  Is there any plan to incorporate this into the main release any time soon? I don't want to end up having to use test branch in production :-( But the feature would be really great - as the ESP32 module I need to place is rather bi g :-) (at least too big for the LumenPNP V2 that I have)

• 
  @markmaker4345 Жыл бұрын

  Yes, I guess the test branch will be integrated back soon. But that also means I consider the current test branch very mature, in fact it has many bug fixes the stable branch has not. 😉

• 
  @friemae Жыл бұрын

  Really awesome developments!

• 
  @markmaker4345 Жыл бұрын

  Thanks!🤭

• 
  @arthurheito3867 Жыл бұрын

  the footprint tab on my openpnp doesn't have which version you are using

• 
  @markmaker4345 Жыл бұрын

  You need the testing version. openpnp.org/test-downloads/

• 
  @torq7280 Жыл бұрын

  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.

• 
  @zdenkostanec16222 жыл бұрын

  Cheers Mark for an awesome job, and thank you for the time you are putting into the OpenPnP to make it better and better.

• 
  @gabx3iel2 жыл бұрын

  Awesome job as usual. I don't think I've got any excuses left to try openpnp on the Neoden4

• 
  @kolimator25442 жыл бұрын

  Great feature

• 
  @InfiniteNesLives2 жыл бұрын

  Amazing work! Super excited to start using these latest vision features! Been anxious about how my placement accuracy with TQFP-100 will turn out for an upcoming build but not anymore! 😍

• 
  @bbyeler2 жыл бұрын

  What settings should I enter for the 5050 led strip thanks. :)

• 
  @markmaker43452 жыл бұрын

  Such questions are best asked in our discussion group, KZread comments are too limited. groups.google.com/group/openpnp

• 
  @alexscott42772 жыл бұрын

  All that in openSCAD, just crazy! My mind boggles at the thought... True guru territory!

• 
  @markmaker43452 жыл бұрын

  Thanks! :)

• 
  @DRawwrrr2 жыл бұрын

  Thanks for all the great work! I've got a Liteplacer running OpenPNP with a tinyg and it's been "90% working" for the last 3 years. Every 6 months I put in a couple days working on getting it to 100% and it's great to download the latest version of openpnp and see the improvements.

• 
  @Mike4_friends2 жыл бұрын

  Great improvement for user of OpenPnP - congratulations - keep up the great work!

• 
  @MoviePropElectronics2 жыл бұрын

  I like your feeder. I have printed one and it went well, but it doesn't fit to the Index PNP machine. Any idea how I could adapt either the parameters on SCAD or/and the Index Pnp?

• 
  @markmaker43452 жыл бұрын

  Can you please ask the same question on the discussion list? You could perhaps send a photo of where you want to mount it. groups.google.com/group/openpnp

• 
  @cpirius2 жыл бұрын

  That's awesome! Thank you for your work!

• 
  @fkiesel94422 жыл бұрын

  I was waiting for something like this for a very long time. This makes Vision so much easier!

• 
  @alialmorsed82182 жыл бұрын

  Good job 👍

• 
  @diggraph2 жыл бұрын

  Great stuff. Congratulations to both of you.

• 
  @julianbinder23712 жыл бұрын

  amazing stuff dude!

• 
  @omnaraiya2 жыл бұрын

  Can’t thank you enough for your contribution to the open pnp community. Keep being awesome!

• 
  @tobi46852 жыл бұрын

  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..

• 
  @ahadgd2 жыл бұрын

  Awesome work👍🏻 Thank you💐

• 
  @diggraph2 жыл бұрын

  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

• 
  @markmaker43452 жыл бұрын

  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

• 
  @diggraph2 жыл бұрын

  @@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

• 
  @diggraph2 жыл бұрын

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

• 
  @friemae2 жыл бұрын

  awesome work mark!

• 
  @DRawwrrr2 жыл бұрын

  Very impressive man, great work

• 
  @mattodin82242 жыл бұрын

  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

• 
  @markmaker43452 жыл бұрын

  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

• 
  @esta7382 жыл бұрын

  That is bloody fantastic cant wait for it to be available

• 
  @euginetomsonpalatty79602 жыл бұрын

  Looks awesome, can I know the micro-stepping value in x and y axis

• 
  @markmaker43452 жыл бұрын

  It is 16 micro-steps. More info is here: makr.zone/choosing-a-motion-controller-the-panucatt-azteeg-x5-gt-32bit/455/, config files linked towards the end of the article.

• 
  @zdenkostanec16222 жыл бұрын

  Awesome work Mark, when is the release? 😎👍

• 
  @markmaker43452 жыл бұрын

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

• 
  @fkiesel94422 жыл бұрын

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

• 
  @fxframes94152 жыл бұрын

  Awesome work! 👏🏻

• 
  @jon_raymond2 жыл бұрын

  Thank you for sharing your knowledge.

• 
  @carlohwang51372 жыл бұрын

  Good news! Thanks, Mark!

• 
  @Mike4_friends2 жыл бұрын

  Amazing work Mark! Thanks for your efforts !

• 
  @vinaydand82432 жыл бұрын

  Superb work, this is going to make life easy

• 
  @cpirius2 жыл бұрын

  Wow, awesome additions. Thank you!

• 
  @madytyoo2 жыл бұрын

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

• 
  @asteriondaedalus68592 жыл бұрын

  Sorry, tried asking a question on the project site, but it would never accept the message (just sat there despite all mandatory fields set). The test print. Is the axle diameter changed when changing the clearance values please? Or is it only the size of the hubs. I am trying to work out how brave I can be printing out a batch of feeder bodies ahead of any chore of fitting fiddly bits :)

• 
  @markmaker43452 жыл бұрын

  There is a design principle, that the smaller/removable part has the play applied. So you only need to reprint the smaller/removable part when the play is not right. Still, I would not print multiple bodies before having tested everything together in one test feeder. Also test the fit (the squeeze) on the extrusion mount, which is in the body, of course. This feeder is optimized to work without any external (metal) parts. The downside is that everything must really fit together nicely, not too hard and not too loose. Once you figured it out, document everything and then go ahead and print a whole series. The idea is to invest a bit of time tuning up front, but then have a very, very cheap and easy to assemble feeder that you can multiply. As to the makr.zone comments not working, I'll have a look. You can also use my email which is on the site.

• 
  @asteriondaedalus68592 жыл бұрын

  Hi! Great design. I recommend people look at the parameterisation approach even if they aren't wanting to print this, as it is illuminating.

• 
  @markmaker43452 жыл бұрын

  Thanks!

• 
  @pentachronic3 жыл бұрын

  Very cool!

• 
  @captaindavejseddon87883 жыл бұрын

  Very good design, well done.. :)