Software update to 2.0.3

Thank you all for submitting feedback and bugs! This allowed me to improve the software and here it is: alpha version 2.0.3! This release fixes some bugs and even adds some new stuff. I highly recommend updating to this release (Don’t forget to update the libraries too)! These are the changes:

Documentation
  •  updated the documentation (added small system-user-manual)
  • added some information about updating the software
 Software
  •  fixed a bug which started moves from the wrong position if not moved to home before
  • fixed a bug that moved the motor in the wrong direction when using the function “Move home (all)”
  • fixed a bug which caused the motor direction to change sporadically during motor jogging
  • added a new menu font and a font-option to the settings
  • Minor user interface changes
  • added all needed libraries into the repository

The biggest change, which you will see immediately, is the new font. I thought it might be nice to have a more readable and clear option. There is a new option for choosing the font so that you can go back to the old one if you like:

new font

I also started working on a Windows client for creating keyframe-based moves. This is in the very early stages but I hope to be able to release it before the summer. Main focus will be defining the bezier-curve based moves and then either save them as a files or directly submit the data to the USB-connected miniEngine.

…and as always – Have fun!
Airic

Shades – a time-lapse movie

Hello everyone,

I finally got enough clips for a 4min time-lapse video. I spent the last 1 ½ years on refining my equipment and shooting some clips when possible. Here is the result:

It was shot using the miniEngine – bot with motion control as well as simply on a tripod. All 3 existing version were used.

For those with some interest how my time-lapse workflow looks like – it includes the following tools:

  • Adobe Lightroom for the development of the single RAW pictures / video frames
  • LRTimelapse for de-flickering
  • Quicktime Pro for combining the frames to video-clips
  • Final Cut Pro for the video cut

Surely this is just one of many, many possible workflows but this is how I do it.

I hope you enjoy it!
Cheers,
Airic

miniE v2 release

Ladies and Gentlemen,

I worked hard the last couple of days to get everything together and write an initial documentation. Now I am done and just released the miniEngine v2 to the public, to you. It is now available in the shop:

shop.airiclenz.com

big set

..and all required files are committed to GitHub:

github.com/airiclenz/miniEngine2

The ones of you that have any questions, please post them in the forum. I am happy to answer them there.

Cheers,
Airic

Documentation graphics

Hello everyone,

here is one of the graphics, I created for the documentation that I am currently writing. I thought some of you might find that interesting.

Assembly

[Click me for full resolution view]

I’m planning to open the shop this Sunday (2013-12-15).

Cheers,
Airic

miniE v2 update 4.1

Hello everyone,

this is just a quick update on the Bezier-motor-control engine. I worked the last days pretty much all of my free time on the new “core” system and can say that it is more or less done. I now can define moves based one Bézier curves – or in other words by defining 4 points (2-dimensional: time; position) per curve. The engine is then processing the data to a list of linear segments (based on linear functions). So every curve becomes 200 linear segments. To get a smooth move, I developed an algorithm, that uses a finer granularity where the curve bends the most. In the picture below you can see the segmentation (in this case 100 segments):

intelligent_BezierSegmentation

Every motor-movement in the next version will be based on this new methodology as it allows detailed planning of the motors position in time. I even allows to get information about the speed of the motors at any time. On top of that is the motor movement much smoother as it was with the old delay-based engine. It also allows much greater speeds. I was able to move my dolly along my 100 cm (4 foot) track (this one) in 6 seconds with nice speed-ramping on both sides.

Because the DUE is fast enough and the motor position calculation is based on an easy linear function, there should be plenty of processing power for doing all this for 2 motors simultaneously. Right now there are approx. 0.05 motors steps done per processing loop. This means that the DUE only needs to step the motor every 20 processing loops. [Edit: Running 2 different curves with 2 motors simultaneously is tested and working perfectly.]

The only drawback is that this new control-methodology is making extensive use of the 96kb RAM that that the Arduino DUE has to offer. One of the curves with its 200 linear sub-segments is taking 2400 bytes of RAM. That means that in theory 40 of these curves can be stored in the DUE’s memory. Because the systems itself needs some of the memory too, lets say that 20-25 curves can be stored. I think that this is a good amount to design some pretty complex video-moves. Here is another example of how such a move can look like:

move_graph

It consists of 3 curves and here is the actual source-code to define such a move by hand:

// x coordinate = time in ms
// y coordinate = motor position in cm
curve[0].p0 = Point( 0, 0);
curve[0].p1 = Point( 6000, 0);
curve[0].p2 = Point( 10000, 50);
curve[0].p3 = Point( 20000, 50);

curve[1].p0 = Point( 20000, 50);
curve[1].p1 = Point( 30000, 50);
curve[1].p2 = Point( 31000, 35);
curve[1].p3 = Point( 40000, 35);

curve[2].p0 = Point( 40000, 35);
curve[2].p1 = Point( 51000, 35);
curve[2].p2 = Point( 51000, 100);
curve[2].p3 = Point( 70000, 100);

The cool thing is that I can read the motor position for any time I want. This will end up in a feature to kind of fast preview the programmed move – for example with 16x speed.

I guess I need a good user interface for editing these curves on the system now!

Cheers,
Airic