Hacker News new | ask | show | jobs
by acyou 662 days ago
Thank you.

I have seen machines with visual pressure curve output on the operator screen for each part. I also think some machines have automatic pressure monitoring already built into the machine control, but it's certainly not transformer model based.

I didn't know they were using resin molds, that takes cheap aluminum prototype scale up mold to a whole new level.

Last time I checked, the mold design software itself has the same UI as 1999 AutoCAD.

How many images/angles can you effectively sample and compare on that hardware in a 30 second cycle time? How would you process images from more than one camera? If you have 8 cameras, can the defect recognition software run on 8 threads?

Are injection mold operators mostly located in low labor cost areas? Is any reshoring happening?

2 comments

Injection molding houses are heavily concentrated in LCOL areas -- but it's a massive market, so, so much of modern materials are plastic that there's a lot that's done in the US/Canada/Mexico, in North America, and Germany/Italy/Austria.

For just the automotive industry, there are 120 injection molding contractors in Michigan alone. Onshoring and reshoring are desired for really customer facing parts -- you spend a lot of weight on packaging to mitigate scratches when you produce abroad then assemble domestically.

Staying with automotive, electrification is driving the injection molding industry -- as your weight shifts to "big battery with a shell around it" more of the total components of a vehicle are injected.

Zooming out of automotive, biomedical device packaging is a huge injection molded business that's stayed in the US and is growing.

Steph here - each image takes about ~250ms on a small single board compute like an Nvidia Orin Nano. On something larger like an RTX 4080 GPU it's less than 100ms. Because we're running big models we can't really just spin out more threads ourselves, we throw them over to the GPU (or deep learning accelerator - depending on the platform) and the driver's internal scheduler decides how to get it done.

In a robotic packaging scenario most of the time is spent by the robot picking up the objects and moving them, so for a 30 second cycle we usually get less than a second to take multiple pictures and make a decision about the part. For a smaller number of images - like 4 - it's pretty easy to handle with cheap hardware like an Orin Nano or Orin NX. If we've got more images (like 8) and a tight time budget (like less than 2 seconds) we'd usually just bump up the hardware, like going to a higher tier of Nvidia's line of Orins or using compute with an RTX 4080 GPU or equivalent in it.