While, technically, these three projects are three *separate* projects (as in, they have different end-goals), they all feed into each other. I'm talking about:

• 'commonCode' (this project)
• #operation: Learn The MIPS (PIC32MX1xx/2xx)
• #2.5-3D thing

A description of these three projects, and how they feed into each other, follows the video, so be sure to click the "Read More" link!

Click "Read More!"

This "project," commonCode:

is an attempt to make available to the public the commonCode libraries/system I've been developing/using for over a decade. There's *quite a bit* to be done in this process... In addition to making the libraries/system available, there's also the plan to make them "architecture-independent," standardize the flow, and more. And, as (ironically) mentioned in another project's log (https://hackaday.io/project/6450-operation-learn-the-mips-pic32mx1xx2xx/log/20769-wins-and-tcnter):

Basically, as-of little more than a few months ago, I seldom looked at commonCode as a project of its own... it's always been developed/improved as a result of some other project[s] that makes use of it... I'm actually quite amazed at how much I accomplished that way, as looking at it *directly*, now, seems like a *huge* undertaking.

#operation: Learn The MIPS (PIC32MX1xx/2xx)

on the other hand, is a specific attempt at porting commonCode to a specific new architecture. In doing-so, however, I'm getting a first-hand look at quite a bit of underlying commonCode which has been buried deep for quite some time... and... making that stuff architecture-independent! (Woot! One of the end-goals of *this* project (commonCode)!)

In addition, of course, that project is also a great learning-experience for a new-to-me microcontroller architecture, and more. And, also, compiles quite a bit of getting-started info--from various scattered sources as well as utter banging-of-the-head-on-the-table--on getting a PIC32 running with a minimum of entry-requirements (software/hardware) that many "hackers" might already have laying around and can certainly be useful for other projects.

#2.5-3D thing

finally(ish), is a specific project based on the porting of commonCode to the PIC32... Its specific end-goal is a 2D or plausibly 3D Cartesian system to be used e.g. for pen-plotting, lasering, or maybe even CNC-routing. A side-result of using the PIC32 in this system is that doing-so will force me to revisit my motion-control related commonCode, and... make that stuff architecture independent (Woot! One of the end-goals of the other two projects!)

In addition, this Cartesian-system has turned a bit into a mechanical challenge which could be quite interesting... A tiny 3-axis system which is assembled from little more than one sheet of laser-cuts... a "business-card kit" of sorts, which once snapped-together could be like a hand-driven etch-a-sketch and an optional snap-on attachment for motors.

...others

I say "finally(ish)" above, because, again... nearly all my code-bearing projects from the past decade use and contribute to my commonCode system, making use of several commonThings. Wee!