Infinite Industrial Robotics (IIR) is advanced software developed to enhance automation in product handling. As the main gateway to the “DPPS Infinite” ecosystem, IIR enables engineers, designers, and automation professionals to craft intelligent layouts for palletizing, depalletizing, and beyond.
Whether you're in manufacturing, distribution, or retail, IIR provides a user-friendly interface for designing, simulating in 3D, and optimizing product arrangements with precision.
With IIR, automation becomes more efficient, flexible, and reliable. Reduce costs, prevent errors, and maximize your robotics potential with our powerful design platform.
Visit the DePeuter Packaging Solutions website to explore the full “DPPS Infinite” ecosystem and discover how IIR can take your operations to the next level.
Effective Date: June 12, 2025
This Privacy Policy describes how Infinite Industrial Robotics (the "App") handles your information when you use it.
We do not collect, store, or share any personal information from users of Infinite Industrial Robotics.
IIR does not collect any usage data or analytics.
IIR does not use cookies or similar tracking technologies.
IIR does not integrate with any third-party services that collect personal information.
The App is not intended for use by children under the age of 13. If we become aware we’ve collected personal data from a child, we will delete it.
We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new policy on this page.
If you have questions about this Privacy Policy, please contact us:
Email: itsupport@depeuter-es.com
Last updated: June 12, 2025
These Terms and Conditions constitute a legally binding agreement between you, the End-User, and DePeuter Packaging Solutions ("DPPS") for the use of the Infinite Industrial Robotics ("IIR") software.
By accessing or using IIR, you agree to be bound by these Terms and Conditions. If you do not agree, you may not use the software.
IIR is provided "as is" and "as available" without warranties of any kind, either express or implied, including but not limited to warranties of merchantability, fitness for a particular purpose, and non-infringement.
To the maximum extent permitted by applicable law, DPPS and its developers shall not be liable for any indirect, incidental, special, consequential, or punitive damages, or any loss of profits or revenues, whether incurred directly or indirectly, or any loss of data, use, goodwill, or other intangible losses, resulting from your access to or use of the software.
DPPS is not obligated to provide maintenance, technical, or other support for IIR. The End-User is encouraged to report bugs and suggestions to improve the software.
You are solely responsible for ensuring the compatibility of IIR with your systems and for validating all output before implementation in industrial environments. DPPS is not responsible for errors, malfunctions, or damages caused by improper use or lack of validation.
All content and code within IIR remain the intellectual property of DPPS and its authors. Any modification or redistribution must credit the original authors and clearly state that the software is not the original version.
These Terms are governed by and construed in accordance with the laws of the State of Texas, USA. Any disputes arising out of these Terms shall be resolved exclusively in the courts located in Harris County, Texas.
By installing and using the app, you waive any and all defenses you may have based on the electronic form of these Terms and Conditions and the lack of signing by the parties to execute these Terms.
If any provision is found to be invalid or unenforceable, the remaining provisions shall remain in full force and effect.
IIR Mobile Revision: 1.2
IIR shows project content as a list of existing layers and each layer content as a list of jobs; where layers and jobs are numbered.
The software is divided into several screens and sections. Some screens might include a different set of components depending on the type and content of the project. A general summary of each section is presented below.
IMPORTANT NOTE: The container's offsets move the layout's edges on all its four sides, and controls the distance to which a product can be placed from the physical boundaries of the container. An offset is measured per coordinate's axis (x or y), from the boundary of the container (which is the point 0) to the outer edge of the layout. The outer edge of the layout could be internal or external to the container's area, depending if the offset's value provided is positive or negative respectively. The edges of the layout overlap the container boundaries when the offset values equals 0. To be allowed offset's values must be smaller than the half of the product's width and its location is represented in the work area by red lines (see sample pictures).
The app also includes functions related to the project setup and general data transference such as:
The 'Robot Approach' or 'Job Start Point' is one of the most important design principles to follow when designing an infeed project. The movement approach tells the robot what's the right entrance point and angle it must use to execute each product placement inside the placements sequence designed to avoid it colliding with the products already placed inside the container. Outfeed projects do not require the user to specify the robot movement approach, it will always move straight up when executing a job.
Make sure to specify the right robot approach for each product placement inside the sequence when creating the design of an infeed project. Diagonal movements are the best approaches to avoid products collisions when doing a placement. Robot approaches are implemented as follows:
Move to Top Left Corner ![]() ![]() ![]() ![]() |
Diagonal movement oriented from the bottom right corner of the quadrant limits to the top left corner. When using this approach to place a product the design should not have another item, or part of another item occupying the area bounded by the top and left sides of the current item (coordinates for all other items already placed must have a minor value in the X and Y axes). |
Move to Top Right Corner ![]() ![]() ![]() ![]() |
Diagonal movement oriented from the bottom left corner of the quadrant limits to the top right corner. When using this approach to place a product the design should not have another item, or part of another item occupying the area bounded by the top and right sides of the current item (coordinates for all other items already placed must have a bigger value in the X axis and a minor value in the Y axis). |
Move to Bottom Right Corner ![]() ![]() ![]() ![]() |
Diagonal movement oriented from the top left corner of the quadrant limits to the bottom right corner. When using this approach to place a product the design should not have another item, or part of another item occupying the area bounded by the bottom and right sides of the current item (coordinates for all other items already placed must have a bigger value in the X and Y axes). |
Move to Bottom Left Corner ![]() ![]() ![]() ![]() |
Diagonal movement oriented from the top right corner of the quadrant limits to the bottom left corner. When using this approach to place a product the design should not have another item, or part of another item occupying the area bounded by the bottom and left sides of the current item (coordinates for all other items already placed must have a minor value in the X axis and a bigger value in the Y axis). |
Move to Left Side ![]() ![]() ![]() ![]() |
Horizontal movement entering from the right side of the quadrant with a straight direction to the left side using the specified value for the Y axis. When using this approach to place a product the design should not have another item, or part of another item occupying the area bounded by the top and bottom sides of the current item (coordinates for all other items already placed should have a minor value in the X axis or enough gap when having a bigger or minor value in the Y axis). |
Move to Top Side ![]() ![]() ![]() ![]() |
Vertical movement entering from the bottom side of the quadrant with a straight direction to the top side using the specified value for the X axis. When using this approach to place a product the design should not have another item, or part of another item occupying the area bounded by the left and right sides of the current item (coordinates for all other items already placed should have a minor value in the Y axis or enough gap when having a bigger or minor value in the X axis). |
Move to Right Side ![]() ![]() ![]() ![]() |
Horizontal movement entering from the left side of the quadrant with a straight direction to the right side using the specified value for the Y axis. When using this approach to place a product the design should not have another item, or part of another item occupying the area bounded by the top and bottom sides of the current item (coordinates for all other items already placed should have a bigger value in the X axis or enough gap when having a bigger or minor value in the Y axis). |
Move to Bottom Side ![]() ![]() ![]() ![]() |
Vertical movement entering from the top side of the quadrant with a straight direction to the bottom side using the specified value for the X axis. When using this approach to place a product the design should not have another item, or part of another item occupying the area bounded by the left and right sides of the current item (coordinates for all other items already placed should have a bigger value in the Y axis or enough gap when having a bigger or minor value in the X axis). |
Move Down ![]() ![]() |
Direct robot movement down from a bigger Z coordinate in the specified X and Y product's placement coordinates. When using this movement approach to place a product you have more freedom to design the placements sequence but gaps in between products is a MUST because the probability of collisions increase considerably. Living gaps ensure there will be no collisions if a product comes with factory imperfections altering the specified dimensions. (coordinates for X and Y axes are exact and do not give space to errors). |
In this section of the tool, an automatic simulation is generated according to the project information. The simulation takes into account different factors that are described below:
Below is an example of how a simulation looks for a project containing 2 layers and 6 jobs per layer.