Robotics and CMMs

NinjaBadger Correct me if I'm wrong. Reading from the forum, when someone is talking about a front end application for automation, is that someones own homemade version of the IO flow manager? As instead of purchasing IO FM from Hexagon, they had the skill necessary to create their own?

It depends, but in most instances no.

Automation can refer to two things, one is software automation (like macros in Excel or Scripts in PC-Dmis - where common tasks are coded and happen automatically. The other is more what you might consider automation, i.e. Robots and the like interacting with the CMM.

Typically a front end application I'd consider to be an operator interface, like Inspect.

I created my own which I'm very proud of, but unfortunately it didn't really sell (this was before I rejoined Hexagon) and it's only in use in a couple of companies.

IOFM is for automation, although it can be used as an operator interface, it can do some things better than Inspect with regards to pallets/ multi-loading parts (although maybe doesn't look as slick/modern). Primarily however it's used for integration with automated cells (typically loading/unloading parts via a robot or automated conveyor type systems).

Historically these type of applications were all bespoke, but much of the functionality is the same, so it was turned into a generic product which can be used in maybe 90% of instances where this type of interaction is required.

That said, for sure, if someone has the required skills and knowledge, they could code something to do what IOFM does. But in most cases it wouldn't make financial sense to do so (the cost of creating bespoke would probably out weigh the cost of purchasing IOFM).

NinjaBadger Correct me if I'm wrong. Reading from the forum, when someone is talking about a front end application for automation, is that someones own homemade version of the IO flow manager? As instead of purchasing IO FM from Hexagon, they had the skill necessary to create their own?

It depends, but in most instances no.

Automation can refer to two things, one is software automation (like macros in Excel or Scripts in PC-Dmis - where common tasks are coded and happen automatically. The other is more what you might consider automation, i.e. Robots and the like interacting with the CMM.

Typically a front end application I'd consider to be an operator interface, like Inspect.

I created my own which I'm very proud of, but unfortunately it didn't really sell (this was before I rejoined Hexagon) and it's only in use in a couple of companies.

IOFM is for automation, although it can be used as an operator interface, it can do some things better than Inspect with regards to pallets/ multi-loading parts (although maybe doesn't look as slick/modern). Primarily however it's used for integration with automated cells (typically loading/unloading parts via a robot or automated conveyor type systems).

Historically these type of applications were all bespoke, but much of the functionality is the same, so it was turned into a generic product which can be used in maybe 90% of instances where this type of interaction is required.

That said, for sure, if someone has the required skills and knowledge, they could code something to do what IOFM does. But in most cases it wouldn't make financial sense to do so (the cost of creating bespoke would probably out weigh the cost of purchasing IOFM).

Thanks for the clarification.