UPDATED!!!!!!!!!!!!!!!!!!! 4/17/2012

So i am updating this thread, mainly just this first post.

I have been hard at work on this project, my machinist has been bugging me to get some images put out there, so i figured I would oblige him.

Chronos 2.0 is going to remain open source, however we are currently neck deep in the patent process. The main reason for this is to make sure we can build these all we want. We also plan to offer complete systems and various kits. No pricing has been determined, however i have been constructing complete rails for negotiated prices. I have 3 that i am working on which will contain the Chronos 2.0 control package.

Introducing Chronos 2.0 control system.

Prototype box 1

Prototype box 2

Prototype box 2

Prototype box 2


Things have been going well. the Code is nearly finished and I am pleased to say the code is 95% mine, the only part i did not write is a software library for the alternate serial port, which i think i will be ditching. The main problem is I ran out of room on the Arduino for all the features, i am confidant i will get everything working, i just need to rework some of my code to work a little but smarter.

This system is going to be primarily centered around WSM (Wait-Shoot-Move) shooting, it does have an option for continuous movement as well.

I am also considering ditching the limit switches. Unless you are careless you should not need them.

The basic routine will work as such, you put it on MGO (master go) and hit a direction, and it will start its routing based off default parameters. It will trigger your camera and keep everything in sync.

To go more advanced you can select the distance you wish to travel (metric or standard selectable), the number of shots you want to take in that travel (30 - 9999), any sort of movement delays, ramp type (symmetrical and asymmetrical), ramp rate (5-50 symmetrical, 10-90 asymmetrical) and the direction you want to go, and weather you want Chronos to keep the timing or slave off of another systems signal.

Yes, it IS compatable with bulb ramping devices. It can even sync up to any external intervalometer including built in intervalometers on a Nikon or a built in Canon (as long as you have a hotshoe or pc port)

The movement construction works like this.

|---------Interval Delay-----|-Shutter open----Bulb delay---Shutter shut-|---Aftershot buffer-----|

So if you want a 5 second interval with a 1 second bulb delay the time would work like this.

Interval set to 5 seconds.
Bulb set to 1 second.
Buffer set to .25 seconds.

Wait 3.75 seconds.
Open shutter,
wait 1 second,
close shutter,
wait .25 seconds for the buffer delay (selectable from .1 to .9 seconds).

without the bulb, it would wait 4.75 seconds, trigger the camera, then wait the .25 seconds buffer before moving.

During the shooting you can cycle through the number of shots taken, shots remaining, time elapsed, and time remaining.

Why have the buffer? Because Chronos 2.0 will trigger a split second BEFORE the system moves, not AFTER. This is the WSM (wait shoot move) system. This gives the camera the maximum amount of time to settle before it triggers. So the buffer is used to make sure it does not start moving when the shutter is open when NOT in bulb mode. The buffer can be stretched out to 9/10ths of a second.

On slave mode it runs like this.

Detect open
Detect close
Wait buffer
MOVE

This sequence allows it to work with bulb ramping devices, as the trigger that starts the buffer and the movement is the shutter CLOSE signal received from the intervalometer.


We do not have any sort of a release date, i have been putting as much time as possible into this system getting it ready, unfortunately time is at an absolute premium. I have finished the design of Chronos 2.0 arduino shields and I hope to start milling them out with my CNC within the next couple weeks. The next step after that is to remove the Arduino altogether and consolidate the entire system onto a single board. I ran into a hitch with my CNC router that i am working though, but i hope to have it figured out soon.


I still have to work out the repeat modes, re-work the automatic microstepping, etc, pre-movement shooting delays, etc.

There is a continuous movement mode as well, you select how far you want it to travel, and travel time. Continuous does not support the other cool WMS features, the continuous mode does not trigger the camera either. all it does is move.

The three rails I am finishing up will be beta testing this software for me.

So in a nut-shell, that is where I am at.

To all the quiet forum lurkers, which seem to be a bulk of who contact me on this, if you want to reach me offline of the forums i can be reached at ProjectChronosHelp@gmail.com

Good stuff. I ordered a simple Arduino enclosure to house all my electronics. I had to perform some modifications to get everything to fit.

On another note. My Office/Lab:) is under construction. So either I work on my stuff out in the 32ºF garage or just wait until the office is finished. I am choosing the latter. This will give me a chance to order some parts.

Thanks for the response about the limit switches.

EDIT: the info on this portion was old news.

EDIT: the info on this portion was old news.

Dropping by to say that I love your videos explaining how all your stuff is put together.
I watched all of them and really enjoyed'em, can't wait to see how your new project turns out!

Thank you Matjoez

I've been hard at work the past few days working on the code. Im not really much of a programmer so it takes me a while to troubleshoot my code. I know there are probably better ways to do what i am doing, but so far it is all working out nicely.

LED - Brightness mode - Finished
POS - High speed position - Finished
DEL - Number of shots to delay before the movement begins - Finished
INT - Intervalometer - Finished
BULB - Bulb controller - 80% Finished, need to add Buffer Delay feature.
SHOT - Number of frames - Finished
DIST - Distance to move 0-36 inches 70% finished, need to add metric/standard conversion.
RAM - Offset and Symmetrical velocity ramping modes Finished and Functioning
RPT - Repeat movement - Not finished
RVS - Reverse movement - Not Finished
MGO - Master Go (internal intervalometer) Finished
SGO - Slave GO (slaves to external intervalometer) Not finished
CONT - Continuous Movement, NOT Finished

I also have to get the limit switches written in, and a few more options as well. So far it looks real nice and i tested the movement yesterday, im hoping to get the trigger written in today and do a test run of the two velocity ramping modes today.

I had a hell of a time getting the ramping modes to work. I originally written the ramping modes in a separate engine sketch just to test it out and see if i could get them to work. Importing them into Chronos 2.0 sketch was a real headache. I have about a dozen floats and longs that i use in the sketch, and i would find issues with the variables i had already written into the chronos 2.0 code. I did eventually get it figured out and it works wonderfully. I am sure other guys like Shutterdrone could have done this while blindfolded and on drugs.

I feel good though because so far this is 100% my code. No libraries or outside help (so far).

Here is a sample run of two of the velocity ramping modes.

This is a linear ramp, not an S-curve. I have used S-Curved before and i really cant tell much of a difference between the S-curved and Linear from looking at these vs what i have had in the past.

I configured two ramping modes. Offset and Symmetrical.

offset you chose a point of peaking, where it hits its highest speed, from there it will slow down. In this case i chose 75% Offset (first half of the video), so it slowly gains speed for the first 75% of the movement then quickly slows down on the last 25%. I have this selectable between 10-90%

On the second half of the video, i used a 25% symmetrical. What this means is the first 25% it speeds up, the last 25% it slows down, between this it will maintain an even speed.

This is selectable between 5% and 50%

I am pleased with the results on this. BTW, the ramping is for SMS only.




Now what is left is to work out the repeat and reverse modes On the ramping it uses float values which it have to be resolved into non-decimal amounts of steps with a rounding process i set up. So normally it is 140,000 steps for 35 inches, when using the ramping i usually get between 139,000 to 141,000 steps as a result of this rounding process. Chronos keeps track of exactly how many steps were taken, so after a routine it wil be able to produce that routine again forward, or backwards in reverse with the ramping mirrored or asymmetrical, or it can rewind and repeat the exact same mode from the exact same spot. So i will be able to set chronos up, run a timelapse, have it rewind, and perform the identical movement from the same starting point again, or later. SO i can do one in daylight, then repeat it at night if i wanted.

I also need to add in the code for the limit switches, and also get working on the timers. Right now it is just a simple "delay(delaytime); " setup. Which is fine for testing, but not good enough for real work, so i am working on some timers to use to replace the delays so shutter speed and movement do not alter the actual intervals. Not a big deal, i just need to get to it.

a few more options need to be coded in, but so far it is coming along nicely. Rather than being confined to 3 speeds of continuous, 3 speeds of continuous ramping with no options, and a SMS master and SMS slave mode with 14 selectable movement resolutions, i now have a very customizable and repeatable slave/master SMS system with two customizable ramping modes with automatic microstepping switching with other goodies and delays, which gives me almost limitless options for movement control.

And the best part, is i get to maintain that nice tactile feel, i dont have to wade through any menus, and the setup is extremely simple and quick.

I also have my CNC router setup and running. I have not had time to mess with it, with a full time job, single dad, girlfriend, chronos, yard work, etc, but i am hoping to get some time to start fabricating my own Chronos 2.0 circuit boards which will be fully functional and just need a pair of limit switches and a stepper to control. I am also considering building a Chonos 2.0 Arduino Shield. As the soldering and wiring seem to be an issue for many people who want to build one.

So be on the lookout for complete Chronos 2.0 kits which will include a control box (much smaller than mine) and all the brackets needed.

Updated the start of this thread, Added some pics of the new control box, etc.

Very nice. Looking forward to following your process and seeing the final product.

Great Stuff Jack!

Turned out pretty nice.

Looking epic!

Just like to say that i received my rail from Chris a while ago but due to circumstances beyond my control i haven't been able to devote any time to it.

First Chris had to send it to me unassembled due to freight charges, so that took me a bit of time to assemble it, also i added some of my ideas to the mounting system as all my gear uses RRS quick release plates and clamps so for convenience i added RRS plates and clamps to the rail.

Now that i have the mounting system done i will read the instructions on how to operate it.

Done another mod, i made a platform for the controller box and the battery.