System Configuration (Module 4)
|------| | mp | |------| ^ . . . v |------| | mc | ---> A_out |------|
Module 4 introduces actuators (motors, LEDs) with Aout to allow our system to take action in the physical world. Similar to Module 1 on Generative Art, this system configuration takes no inputs. Here we focus on generative systems that produce analog outputs, rather than digital outputs. We can still optionally include a connection a microprocessor for digital output.
Interactive Kinetic Art
|------| | mp | ---> D_out |------| ^ . . . v |------| A_in ---> | mc | ---> A_out |------|
In module 5 we combine all previous system configurations to build installations that can take user input Ain and actuate Aout accordingly. This system configuration is utilized for purposes of augmented experience design. In this chapter, we combine modules 4 and 5.
Basic Philosophy of Kinetic Art
Kinetic art in the context of creative embedded systems bridges the gap between the “cyber” and the “physical”. This appeals to our more visceral human instincts to examine motion. With such systems, we can visualize bits being flipped or augment motion with computation to create complex patterns that would de difficult to implement in a purely physical system.
To first explore the basics of kinetic sculpture, view the video below which illustrates some core ideas behind the practice - outside the realm of embedded systems.
Module 4: Actuators
Due March 26th - no late work please!
This assignment requires you actuate the physical world - you may choose one of two configurations for this project - either 1) kinetic sculpture or 2) Interactive kinetic art. The difference amounts to whether or not you choose to integrate input from the user into your work. You are provided in your kit with the following hardware.
- 28BYJ-48 Step Motor
- SG90 Tower Pro MicroServo
- DC Brush motor
You may create a team of up to three group members. Your group may not have overlapping members from the previous assignments. When working in a group, your hardware resources are pooled. Your device must adhere to the following specification. You must use a minimum of (2*number of group members) motors and may use as many motors as you have available to your group. The device must have an enclosure or enclosures.
Your device must utilize an API (to be provided) that will allow you to start the device in motion. More details to come on the API usage in class. The device must be safe to operate in intervals of at least 30 seconds multiple times in a row.
If you are interested, you are invited to display your work in Milstein on the 5th floor for the time period of March 27-28.
- (10 pts) A link to your git repository with a program that runs on the ESP32 or the Raspberry Pi to control your device. The program must meet the following criteria:
- (10 pts) Utilizes your actuators
- (8 pts) Successfully combine earlier system configurations through use/reuse of sensors, config code, and physical design principles.
- (2 pts) Is in the spirit of the class as broadly interpreted by the instructors. Art is subjective, we want you to get comfortable with this ethos.
- (10 pts) Quality and thoroughness of documentation and standard deliverables.
A video of your device in action.
As always, the standard deliverables. If working in a group, you may all submit the same code repository and a single blog post. The post should detail, in your own words, the creative vision of the device you have created. You should detail the technical challenges you specifically (as opposed to other group members) faced during the implementation of the device.