pvandervelde / nadoni

nAdoni is a library that provides a way to check for updates to one or more binaries via an update manifest, and then to download an archive containing the updated binaries.

Welcome to Patrick's corner

I've been a software engineer for 15 years. I've worked in a range of industries, from emergency services to the cinema, and on projects where software shipped directly customers or to internal development teams.

I'm interested in designing and building autonomous mobile robots with four-wheel independent steering (also known as a swerve drive). The prototype has ROS2 code for robot description, the Gazebo world and the steering controller. I've also contributed a significant amount of the ROS code for the SCUTTLE robot.

Other interests include:

• All kinds of autonomous mobile robots
• Electronics
• Computer Aided Design (Rhino3d, Fusion360, AutoCAD)
• Rock climbing
• Gardening
• Woodworking

Latest

• Swerve drive - Motor limitations
• Four wheel steering simulation - 0 degree linear to rotation - velocity limited
• Swerve drive - Using Nav2
• Robotics - Making URDF models
• Four wheel steering robot - Omnidirectional drive
• Swerve drive - Motion profiles
• Swerve drive - Control animations
• Swerve drive - Better movement by controlling the body motions
• Swerve drive - Verification of the kinematics solution
• Four wheel steering model with ROS2 controllers - Ignition Gazebo first movement

Github stats

nadoni's Issues

Set up build server on AppVeyor

Automatically add API documentation to the web site

The website automatically includes the wiki pages but not the API documentation. If we can generate Markdown files for the API documentation then we could include those in the web site generation process.

Before we do that we'll have to sort out some questions:

• How are we going to deal with different versions of the API. Preferably we'd like to include all versions but that might be tricky to provide
• Where are we going to get the assemblies and XML documentation files from. It would probably be best to get these from the releases.

Set up automated build for website

Through #1 it is now possible to automatically generate the website content. We should set up an automated build for the website so that any changes automatically get deployed.

Link content on website and github wiki contents

It would be nice if we could write the documentation in one location and then have that published both in the github project wiki and on the website. If possible also pull in the API documentation, links to downloads, blog posts, and other reference materials