NOVEMIQ / Robotics software notes
From motion to deployment.
Practical engineering notes for startups and enterprises building software for robots. Explore motion, hardware integration, simulation and monitoring through original illustrative diagrams.
Motion planning vs motion control: where the handoff happens
Planning chooses a feasible route through the robot’s configuration space. Control follows a reference using feedback. A successful plan alone does not establish that the physical robot will track it accurately.
Read the engineering note →02 / Hardware integrationROS 2 hardware integration starts with an interface contract
A robot driver needs an explicit contract for commands, feedback, units, operating modes, and failures. Transporting a message is only one part of integrating a motor or robot.
Read the engineering note →03 / SimulationIsaac Sim and ROS 2: define what crosses the simulation boundary
A simulation integration needs a deliberate boundary: which commands enter the simulator, which observations leave it, and which clock the software uses. The ROS 2 bridge connects these worlds; it does not establish physical validity.
Read the engineering note →04 / Motion engineeringWhy a robot path needs timing before execution
The same geometric path can be traversed in very different ways. Timing determines the requested velocity and acceleration along it, which makes trajectory processing an important execution boundary.
Read the engineering note →05 / Hardware integrationWhat to include in a robot software integration brief
A useful integration brief identifies the hardware, intended task, interfaces, operating environment, and acceptance evidence. A list of robot models alone is not enough to estimate engineering work.
Read the engineering note →06 / Remote monitoringRemote robot monitoring is not the motion control loop
Monitoring collects state and events for diagnosis. Motion control acts on a time-dependent reference. Keeping those responsibilities distinct helps define what the robot must do when connectivity changes.
Read the engineering note →07 / SimulationA simulation test matrix for robot software changes
A repeatable simulation test starts with named conditions and expected observations. Replaying a pleasant demonstration tests less than a deliberately varied set of task and environment conditions.
Read the engineering note →08 / ROS 2 architectureJoint names, units, and frames: small contracts with large consequences
Robot software components must agree on the meaning of state. Correctly delivered numbers can still be wrong for an application if units, joint names, or coordinate conventions differ.
Read the engineering note →09 / Robotics software servicesWhat robotics software engineering services should deliver
Robotics software engineering services should produce maintainable integrations and reviewable evidence around a defined application. The scope should state what runs today, what is custom work, and what remains future development.
Read the engineering note →10 / Motion engineeringBefore benchmarking robot motion, define the experiment
A motion benchmark is meaningful only with its task, hardware, configuration, measurement method, and limitations. A headline speed improvement without that context is difficult to reproduce or compare.
Read the engineering note →