Noppatjak Attanon’s Post

A quick preview of how to live with robot from #techsauceglobalsummit.

The three phases of Mobile Robot Adoption 01 - Come up with a concept 02 - Simulate your process 03 - Deploy! Sounds easy right? Contact Fast Track Automation to get started www.fasttrackautomation.ai info@fasttrackautomation.ai #AMRS #Mobilerobots #Simulation

❓𝗛𝗼𝘄 𝗳𝗮𝘀𝘁 𝗰𝗮𝗻 𝗮 𝗯𝗿𝗮𝗸𝗲 𝗰𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁 𝗯𝗲 𝗮𝘀𝘀𝗲𝗺𝗯𝗹𝗲𝗱? 𝗛𝗼𝘄 𝗮𝗯𝗼𝘂𝘁 𝟮𝟱 𝘀𝗲𝗰𝗼𝗻𝗱𝘀?😲 With the help of a collaborative robot (Cobot), this complex task is now done with impressive speed and precision. No errors, just consistent high-quality results every single time. Automation isn't just about saving time ⏱️, it's about boosting productivity and freeing up human hands for more intricate tasks. Wondering how this efficiency could transform your production line? For more information just contact me. #CobotPower #AutomationInnovation #SmartManufacturing #BrakeAssembly #ProductivityBoost #FutureOfIndustry #EfficientProduction Video by UR

Learn about the 𝐚𝐥𝐥-𝐧𝐞𝐰 𝐑𝐕-𝟏𝟐𝐂𝐑𝐋 𝐫𝐨𝐛𝐨𝐭 🤖 at #Automate2024. With a 12kg payload and 1,504mm reach, it's a cost-effective solution for many applications, including #MachineTending, #Assembly, and #CasePacking. Come learn more about this exciting new robot! 🎉 👉 https://okt.to/IrShma Automate Show #AutomateShow #EmpoweringInnovators #MitsubishiElectric

#LeetCode Unique Paths Solved Medium Topics Companies There is a robot on an m x n grid. The robot is initially located at the top-left corner (i.e., grid[0][0]). The robot tries to move to the bottom-right corner (i.e., grid[m - 1][n - 1]). The robot can only move either down or right at any point in time. Given the two integers m and n, return the number of possible unique paths that the robot can take to reach the bottom-right corner. The test cases are generated so that the answer will be less than or equal to 2 * 109.   Example 1: Input: m = 3, n = 7 Output: 28 Example 2: Input: m = 3, n = 2 Output: 3 Explanation: From the top-left corner, there are a total of 3 ways to reach the bottom-right corner: 1. Right -> Down -> Down 2. Down -> Down -> Right 3. Down -> Right -> Down   Constraints: 1 <= m, n <= 100

Day 42 of #100DaysCodingChallenge Problem: Unique Paths Statement: There is a robot on an m x n grid. The robot is initially located at the top-left corner (i.e., grid[0][0]). The robot tries to move to the bottom-right corner (i.e., grid[m - 1][n - 1]). The robot can only move either down or right at any point in time. Given the two integers m and n, return the number of possible unique paths that the robot can take to reach the bottom-right corner. The test cases are generated so that the answer will be less than or equal to 2 * 109. #leetcode #problemsolving #codingchallenge

#Ref10_2: with the same #concept, the #method of trading when we use #robot and do manually by ourselves will be different. If we use robot, we have to #backtest periodically, about 1-3 weeks period, this help us to understand about how the #market recently, then change the suitable operating #parameters. We can see on this short clip and understand how robot work. https://lnkd.in/gDJkGzdv

Things that i recommend if you start with moveit 1 - If you get this error: -XacroException: Unused block "origin", probably your attached part is causing the problem. First ensure the robot with the gripper starts in gazebo as is. If not, remove the inertial part to see if it loads. 2 - If you receive this error: Could not find parameter robot_description_semantic and did not receive robot_description_semantic via std_msgs::msg::String subscription within 10.000000 seconds. Probably your joint_limits.yaml on your moveit config has integers and they expect floats, solution is to add a .0 to all the integers in the file 3 - If you did not see your controllers start, remember to put play in gazebo 4 - If your gripper doesn't show in moveit_setup_assistant is because you must include "file://" in the mesh name in example filename="file://$(find maciv2)/robot_description/meshes/gripper2_gripper_base.dae" 5 - If your robot has parts in red you must recalculate the colission matrix, remember the whole robot is a rigid body unified 6 - Remeber to propagate the clock source over the simulation 7 - Limit the effort of the controller so your robot will not harm itself Hope this.