About Airic Lenz

Hej, my name is Airic Lenz. I'm a hobby / freelance photographer living in Stockholm. My specialities are landscapes, cityscapes and long exposures. I really like pictures with a Zen like feeling that show things invisible to the bare eye. I am also doing time-lapse photography and thus am developing this open-source system for motion-control of time-lapse equipment. This allows me to combine my hobby - photography - with my profession - IT. Beyond that I do street photography as well as shooting peoples moods and situations spontaneously.

miniE v2 update 1

Hello everyone,

it’s time for an update with some information where the project is standing.

First of all I want to thank Anderl who is helping me with the 3D development of the system. This is aiming in making the system as small as possible while taking care of the heat development and other arrangement tweaks (of much more components than the original system had). There will also be an enclosure for the second version of the system which will provide a safe and good looking home for your motion controller!

Here is a picture of the current state:

miniE_arrangement-1

Another decision has been made – I am going for the Big EasyDriver. It will deliver the extra bit of power needed for avoiding (or at least minimizing) one of the biggest problems with the 1st version – missing torque. You can still use whatever stepper driver you like if you need something else than the Big Easy Driver.

Here is the bottom side of the system which will house them:

miniE_arrangement-2

The 1st version of the PCBs will be done within the next days and after that they will be ordered immediately. When the 1st prototypes are running the actual development of the software can take off. I started with converting the software into libraries where it makes sense to improve the maintainability of the code and also to slim it down and make it more modular. Effectively this means rewriting almost all the code but it will be worth it!

I was able to gather very valuable input regarding the direction the system needs to take for being of interest even for professionals. During the last days I was working on benchmarking and tweaking different aspects of the system to meet these requirements (I never did this for the 1st system). One example is the repeatability of moves – precisely speaking the timing (crystal speed) differences of different Arduinos vs. their frequency stability. The figures that are coming back from these tests will help me in making the system more effective, stable and accurate.

Thanks too all of you that supported and continuously are supporting the project with ideas, input and feedback! I really appreciate that!

I am looking forward to the 1st prototype and to share some photos of it with you! Stay tuned for more.

miniE_arrangement-3

Cheers,
Airic

miniEngine 2 development

Hello everybody,

I hope you all have a good Easter time!

The free days, we all enjoy right now, allowed me to work a little bit on my new Rhino Slider based track as well as on the software. Here comes some information on the development of the 2nd version of the miniEngine software. I thought I let you know what it will basically look like.

splash screen
The 1st idea for the new splash screen (it’s actually animated)

First of all – I spent a lot of time doing research and hardware analysis for the next version as I wanted to have a hardware platform that has some more reserves for future developments than the current system. It also needs to be affordable and, what’s very important to me, as easy to use as possible. It is hard enough to be out in the field, possibly in bad weather, handle all the equipment and then focus on the shoot you want to do. I want a system that isn’t an additional thing one needs to care and think about.

So I searched the web for possible displays (ready to use so that you guys can build your own mineE system from off the shelf parts), did some breadboard based prototypes and figured out which way to go. One main problem I had was that bigger graphical screens – which I really want to use – need a lot more processing power than simple 16×2 character LCDs. I also want to have a better input method than the quite buggy buttons of the DFRobot shield. So this is the feature list I came up with after the research- and input collection process:

  • Arduino Due bases (ARM) for having tons of performance and flash space
  • capable of controlling multiple motors
  • 2.4 inch graphical TFT display with 320×240 pixel (including touch sensor for later features)
  • SD card (implemented later)
  • rotary knob for main menu navigation and motor control
  • daisy chaining capability
  • time lapse as well as video features
  • open source

Right now I am working on a system architecture that fulfills al my requirements. So I started rewriting major parts of the code to realize a new version of the system which is easier to maintain and can be simpler further developed (Hopefully this lowers the entrance barrier and some of you will contribute to the development with your ideas and features). One example of this modularization work is the motor control which I extracted from the code and put it into a standalone library.

The motor control which allows one to move the motor with the rotary knob is also implemented and working pretty fine!

I plan to develop a new version of the shield that then holds all the required components. I thought an initial version will have 2 motor drivers, the input buttons / knobs and of course the display.

I will continue working on the system and hope that a first version will be available this summer. The next main steps are setting up a 1st version of the shield and then start developing the new user interface – I am still not quite sure how this will look like 😉

Here are some screenshots of the display I am going to use with speed tests, UI layout tests and the font that I developed to fit as much information on the screen as possible.

menu mock-up
A first menu mock-up. I used this for some rotary encoder tests and for getting an idea how the UI could look like. This look possibly changes in later iterations.

fonts test
The fonts I am planning to use for the user interface

font
Here’s a close-up of a font I designed for the new system (there was no font with the size I wanted available)

fill test
Just a fill-rate test to check the painting performance of the screen

Video tutorials

Hello together,

I found a nice site that provides some great tutorial videos covering time lapse photography. There are 3 episodes covering the basics of DSLR based time lapse creation including a bunch of other great tips and links. Here is where you find the 20+ minutes of free tutorials:

learntimelapse.com

Airic

new Forum

Hello together,

because the communication using the blog here is not the best way to exchange information (e.g. many nested comments that look very ugly and are hard to read), I added a forum to this site.

This will enable you to initiate communications, talk to each other and search the available contents. Also because all the information on openmoco.org was lost during a server fault, I thought it could be nice to have an alternative for you to ask me or look for information.

I hope it will help you in finding your way with the system! Please feel free to join the forum for asking your questions, discussing or commenting the system.

The home of the forum is here: www.forum.airiclenz.com

There is also a link in the menu bar.

Airic

Happy new year 2013!

Hello and big thanks for all of your support during the last year!

A lot of things happened in 2012.

I started a little web shop for making it easier for you to get your hands on the miniE shield. The demand was bigger than expected and now there are more than 100 original miniEngines running with the red shield out there! I don’t know how many more there are.

Then, with thanks to Cinetics, the system was used for a very cool project where it was heavily further developed in terms of usability and also in terms of functionality. It was Kickstarted with big success and if want to check the result out, have a look here: CineMoco

For a project that started just as a little hobby project and for personal purposes – I think this is pretty cool!

Thanks again to all of you and have a great new year 2013!

I am looking forward to the steps the miniE system will take in the future.

Airic

miniEngine took the next step

During the last months I worked closely together with Cinetics, a company that helps people create captivating video through controlled camera movement. Togehter, we developed the CineMoco system. It’s controller is based on the original miniEngine software but was much further developed.

screenshot 1
The main screen in the new run-mode

It received a whole new user interface and some other cool new features like:

  • added 128×64-pixel based UI
  • added stop-motion mode (add-on to S-M-S mode)
  • added run-mode (set up the system based on total values not on cycle values)
  • added video mode (focuses on smooth motor movement)
  • added HDR functionalities
  • added bulb ramping functionalities
  • added main processor sleep after a certain amount of no action
  • added battery and external supply measurement
  • automatic battery calibration (min/max-value based)
  • added basic communication protocol for setting up master-slave configurations (not yet implemented for advanced functionalities)
  • up to 32 devices chained (1master + 31 slaves)
  • based on serial communication
  • added keyframes functionality

screenshot 2
The new video mode together with the new keyframe set-up

The software is still Arduino based, but this time it has to be an Arduino Mega (you might need to update some pin assignments) due to the fact that the software is written for a proprietary hardware. It is open-source and you can check it out on Sourceforge!

screenshot 3
in the menu

miniE shield documentation

Hello,

first of all – BIG THANKS to all of you who ordered the shield or the set!

I followed your requests and created a little documentation that hopefully answers the questions you might have! Please drop me a comment if there is something left open or unclear!

version 1.1 & shield update

Hello,
I cleaned up the motor code and added 2 new ramping types. The new arc-tan ramping is the default style now. It is much smoother that the old sinus shaped ramping. The used ramping can simply be selected in the code’s main file in line 133 (e.g. for going back to sinus shaped ramping). I also added limit-switch checks to the motor phases (every 150ms). And finally, the motor phase is no longer (fully) blocking. I added a check for SELECT key presses to the it. So one is now able to stop the engine even during motor phases.

Shield update

The shields are ordered and currently in production. If everything goes well, I will be able to send them out to you very soon. This is how hey will look like:

miniE shield v1.3

Have fun!
Airic

miniE shield & version 1.0

Hello,
thank you all for participating in the poll. I decided to set up a web shop and sell the miniE shield PCBs. So please keep patient until everything is in place. Possibly I’ll add sets that require the PCB plus all minor parts like resistors, pin headers and co.

miniE - version 1.0

Also I uploaded the version 1.0 of the original miniE system. It contains some minor bug fixes and is meant to be the start point for more systems based on miniE. So yes, I will continue working on the system and further develop it. A branch without timed programs and RTC but with a jog function is one possible way to go. I am also thinking about a beefier version with much more capabilities (e.g. more than one motor, daisy chaining, better input, …).

Until then, have fun!
Airic