REVISIT: Using SD Cards with Arduino - Record Servo Motor Movements

@inq FYI @hinobot

For contrast, here is a version for 4 pots/servos that uses 2 buttons. One button is used for indicating that the servos are all set and their position should be recorded on a single line in the file on the SD card. The other button indicates that the entire range of motion has been captured and the recording is complete.

It may not fit your perceived needs, but may offer some alternatives for program design and operation. Note that this is for the record side only.

Note that the sketch will compile clean, but I don't have the parts to test it; no guarantees.

@will - Since you're going with a Claymation / Industrial robot mentality, how do you key in the time you want for each "step"?

@inq I would think that would have to be a constant determined by the length of time it takes for playback to complete the longest "line" of data, so it would be set at playback and be a constant value.

I kept the recording process in a text file format so that it can be manually edited and corrected if/as/when required. This would also allow it to be modified by adding the estimated "step" time in ms at the beginning of the file.

Then the file could be played again and again with different times and the inter-line timing could be adjusted to make the best possible playback sequence. The playback sketch would first read the line delay, then a line of positions, move the servos and, if required, pause until the interline delay time had elapsed.

This would become more useful as more and more pots and servos are added.

@inq 

I should also mention that the process can be ramped up by eliding values which didn't change. That is, a typical line might contain moves for all servos and look like

20,35,160,45

whereas if the servo hadn't moved during that time slice you might see something like 

,15,24,

where servo 1 and servo 4 did not move. You might also see something like

,,,

because none of the servos moved in that time slice.

@hinobot - I was wondering if you've made any progress on your project.  I host a user's group at our local library and thought this would be a great project for us to do as a group.  The library has a 3D printer and I've looked on Thingiverse and found several animatronics eyeballs that seem do-able.  Wondering what you were using and if you'd gotten anything motivating to report...

Also, I know you are using this to learn and teach your daughters hardware, software, 3D printing... I tried to comment the code to be self explanatory, but if you have any troubles understanding or explaining it to your daughters, I'd really appreciate the opportunity to elaborate.  It helps me become a better teacher to my own students... pre-teen through senior citizens.

Thanks.

VBR,

Inq

@will That is almost identical to how video frames are compressed (MPEG), MOST of the scene is identical so the data need not be stored again. 

@inq One thing I didn't see discussed is using a micro SD card for file storage. The average card is very well known for developing errors, the high endurance cards are more resilient but now we can use USB sticks and other USB based storage like SSD and even boot from them. I would highly recommend a small SSD for much better longevity.

Posted by: @zander

@inq One thing I didn't see discussed is using a micro SD card for file storage. The average card is very well known for developing errors, the high endurance cards are more resilient but now we can use USB sticks and other USB based storage like SSD and even boot from them. I would highly recommend a small SSD for much better longevity.

... and I assume you are volunteering to show us how you connect a USB stick to a MPU like a ESP8266 or ESP32???

I've never needed the SD card even though I had the hardware in drawers.  The 3MB on the typical ESP8266 or 15MB on the pro version has always been far more than I've ever needed for a project.  I think our local users group may go for doing a set of these recording eyes and as I described above, I can record nearly 2 hours of movement on four servos on 3MB.  If I need to "compress" it, I can get 2.5 hours.  Considering, we may do 30 seconds and have it repeat, we won't be needing an SD.  

Here's a quick demo of both the recorder and playback Ralf.

VBR,

Inq

@inq Oops, I thought a Pi was in play. If there is enough memory on the esp's then that would be the way to go obviously.

Just as an exercise, are there enough free pins (4) on the 8266 to connect an SD? Not 100% sure CS is needed, could just tie it to G or 5V as needed.

@inq Looking good. I assume each 'eye' could be moved independently without much/any increase in complexity and playback time.

How feasible to add 2 more servos so each 'eye' has 2 degrees of freedom.

And if I am really 'going for it', what does it take for the 'eyes' to pop out and dangle on springs? Getting them back may be the issue however.

Posted by: @zander

@inq Oops, I thought a Pi was in play. If there is enough memory on the esp's then that would be the way to go obviously.

Just as an exercise, are there enough free pins (4) on the 8266 to connect an SD? Not 100% sure CS is needed, could just tie it to G or 5V as needed.

Hmmm... I plead the 5th.  I'm cheating...

"https://www.amazon.com/ACEIRMC-Shield-ESP8266-Compatible-Module/dp/B09S3HFFHZ"  

https://www.amazon.com/ACEIRMC-Shield-ESP8266-Compatible-Module/dp/B09S3HFFHZ

I don't know what pins are active under there. 🤣 

I think there are still as least 4 pins available to drive servos.  For this animatronics project, I think 3MB will be more than enough for anything... even 16 servos.

But... I'm glad @hinobot brought up the thread.  It gave me a quick way to explore the capability.  I can see using the SD card memory for the mapping on the Inqling Jr. project.

Posted by: @zander

@inq Looking good. I assume each 'eye' could be moved independently without much/any increase in complexity and playback time.

How feasible to add 2 more servos so each 'eye' has 2 degrees of freedom.

And if I am really 'going for it', what does it take for the 'eyes' to pop out and dangle on springs? Getting them back may be the issue however.

The limitation was purely on the recording hardware side.  There's only one Analog input.  I just chose to read the same input and applied it to each servo and recording.  Using an ESP32 and using a pot for each DOF desired would be easy.  On the code side, the only thing needed is two lines of configuration code per added servo/pot.  There was no appreciable performance hit that I could see.  One of those 16 channel servo boards hooked up to I2C could be used and record 16 channels for something with eyes and a neck and whatever.  Also remember, the ESP8266 can be bumped up to 160MHz and cover even more.

I think my user group here may "Go for it".  We probably will load it up with sensors so the eyes will follow people here in the library.  Hopefully, we'll have it ready to put up by Halloween! 

Have to give the eyes popping out thing a thought or two. 🤣