Kira’s Status Report for 4/25

This week I focused on final preparation and controller fabrication. Ella delivered our final presentation, and beforehand we did a full dry run to make sure everything we needed to cover was included and flowed well. I worked on the controller by laser cutting the enclosure and soldering the components, although it still needs to be fully wired up. I also cleaned up parts of our motor integration code to make it more organized and reliable moving forward.

Based on the testing we have done so far, the individual subsystems are working well on their own. The focus mechanism functions properly in isolation, the controller accurately reads both analog and digital inputs, and those inputs are successfully sent to the main system to control brightness and color. We also tested the pan mechanism separately and it performed as expected. However, full system integration is still in progress, especially the tilt mechanism, which still needs to be connected and tested with the rest of the system. We also have not completed a full end to end system test yet. So far, no major design changes have been needed, just small improvements like refining the code. The next step is to fully integrate all components and verify that the entire system works together as intended.

Team Status Report for 4/25

This week, our team focused on finalizing both our presentation and key parts of the system. Ella presented our final presentation, and as a group we did a full dry run beforehand to make sure everything was clear and covered all the important points. We also discussed as a team our schedule for the remaining time we have to work on the project.

In terms of overall progress, we’ve successfully tested several subsystems individually, including color mixing,  controller input/output, the focus mechanism, and pan movement. These results show that our core components are working as expected, which puts us in a good position for full integration. However, we still need to integrate the tilt mechanism and run a complete system test to verify everything works together. Moving forward, our main focus as a team is completing integration and performing full system-level testing to ensure reliability.

Team Status Report for 4/18

Currently, the main risks are still integration and timing, especially making sure the LEDs, motors, and controller all work together without unexpected issues. Debugging delays or needing extra components last minute could impact our timeline. To manage this, the team is continuing to integrate and test each subsystem incrementally before combining everything. A key change this week was fully switching to current drivers for the LEDs now that they arrived, which allowed us to finalize the LED setup and made color control more reliable and easier to integrate with the Arduino. No schedule changes have occurred since last week.

Our planned tests are focused on validating full system performance once integration is complete. We have made strong progress assembling the motor systems, so we are close to beginning testing. We plan to verify pan and tilt by recording motion to check rotation angles, test focus by adjusting the lens over distance, and confirm RGB and brightness control through the controller. We will also measure motor noise using a phone decibel meter and check latency by comparing controller input to system response. While full testing hasn’t been completed yet, we are much closer now that the main subsystems are coming together.



Kira’s Status Report for 4/18

This week, I focused on finalizing the controller code and continuing fabrication of the system. I soldered several controller components, laser cut an initial version of the controller box, and revised the CAD model for an updated version that I plan to cut soon. I also worked with Chloe to hook up the LEDs and verify they functioned correctly by sending controller inputs over DMX and confirming proper color mixing.

As I designed, implemented, and debugged these systems, I had to deepen my understanding of DMX communication and how the controller input actually translates to output on the LEDs. I also got more comfortable with hardware debugging and improved my skills in soldering, laser cutting, and CAD. Most of this came from just working through issues as they came up, testing things piece by piece, and adjusting based on what was or wasn’t working. Working with others also helped a lot in figuring things out faster.

Additionally, I continued preparing the system for full integration. Next week, I plan to work with Ella to connect and test the motor in a similar way, and to finalize the main body code so everything can run together. According to our timeline, I’m currently on track.

Kira’s Status Report for 4/4

This week, my team and I presented our interim demo, which we prepared as an interactive way to show our progress. I wrote code to demonstrate the DMX transmitter and controller input by using faders (potentiometers) to send signals from the Arduino to an existing light, showing control of color and brightness. For verification, I confirmed the DMX receiver works by scoping both the input and output signals to check for correct transmission and timing.

As I worked on this, I focused on verifying my subsystem by making sure controller inputs map correctly to DMX values and produce the expected lighting outputs. I also used the oscilloscope to check signal consistency. Going forward, I plan to expand this testing to additional controls like pan, tilt, and focus, and check for accuracy and any noticeable delay.

For validation, we plan to test the full system by checking that the light responds correctly to all controller inputs for color and movement. We will compare expected vs. actual behavior, verify motion ranges, and observe responsiveness to ensure the system meets our design goals and works as intended for a user.

Additionally, our group continued fabrication by laser cutting the first rendition of our controller housing and soldering any components we can at this point. I plan to add more inputs and integrate the motor code with the DMX receiver soon. According to our Gantt chart, I am currently on schedule.

Kira’s Status Report for 3/28

This week I made good progress on the DMX system. I got both the transmitter and receiver working and tested them using an oscilloscope to make sure the signal coming out of the receiver matched what was being sent from the transmitter. I haven’t hooked the receiver up to the rest of the fixture yet, but the core communication is working reliably. I also spent time soldering the controller components so that everything is ready for our demo. On the software side, I went through our code files to make sure they’re clean and modular, which should make it much easier to add the motor and other input/output controls later. Overall, the system is coming together and I am excited to demo our project!

Team Status Report for 3/28

The most significant risk that could jeopardize the success of the project would be frying the LED chip or the power supply. Another risk would be not getting the controller to communicate properly with the light. To manage these risks, we have an extra LED chip and have been testing our equipment before we connect it to our power supply. In addition, to prevent the issue of the controller not communicating, we have a backup plan of wiring the controls directly to the light. However, it would cause us to not fulfill the use case requirement of professional compatibility from the DMX side. So far, changes have not been necessary to the design of the system since last week. Our schedule has changed a bit where the integration and fabrication are happening in parallel. This is because we realized that in order to integrate some components, other parts need to be fabricated first.

Team Status Report for 3/21

The most significant risk that could jeopardize the success of the project would be if the parts that we ordered don’t come in time. We originally had issues with getting our LED chip, but it has been resolved. The other important piece of hardware we need is the connection to the power supply from the cable. However, if we don’t receive it, we will have to solder straight from the cable to our power supply, as one of the options. One change to the design of the system was the power and brightness of our LED. This change was required because we were not able to get the previous LED chip we wanted to order. It was lost in transit, and would take too long to get another one. This increases our cost of the LED chip from $10.99 to $15.99. This is still within our budget. Our schedule has not changed still, since we would start fabrication next week and then assembly.

Kira’s Status Report for 3/21

This week I made solid progress testing the DMX transmitter and basic controller functionality. I set up the DMX shield in transmit mode with the Arduino and used potentiometers as analog inputs to act as “faders” for our controller. I was able to successfully send signals to a theatrical RGBW light and verify that changing different DMX addresses and parameters worked as expected, specifically testing control over color and intensity. I had also planned to test DMX receiving, but since we only had one shield at the time, I couldn’t complete that portion. Now that we’ve received a second DMX shield, I will move forward with testing the receiver next week.

Kira’s Status Report for 3/14

This week my components arrived, so I spent time getting the hardware and perliminary code set up. I worked on assembling the basic system and confirming that the components power on and can be interfaced with so development can move forward. I am a little behind the original schedule due to waiting on parts and the initial hardware setup. Now that everything has arrived, I expect progress to move faster. I plan to meet with my teammate Ella tomorrow to start working on the DMX communication and motor control so we can begin testing basic functionality.