Team Status Report for March 8

Our biggest risks remain that any of our components do not function. Thankfully, the Daisy Seeds have arrived, and they have no apparent issues, so we have a microcontroller and a backup. However, we still have more components that have yet to arrive. We have configured a list of materials that we will order, and we plan to test them rigorously so we know that they function as intended.

This week, our design has stayed more or less the same. We have configured some finer details, including the size of the PCB that will be housed in the pedal.

Our schedule has not seen significant changes. Some issues have pushed work into slack time, so we are somewhat behind schedule, but our order of operations remains the same.

 

Part A (Chaitanya Irkar):

​​When designing and conceptualizing our pedal, one of my primary initiatives was to deliver a compact, easy-to-use product that could be enjoyed on a global level. We understood that not all consumers of our product will have access to the same high-quality resources available to us as CMU students. Emphasis on portability removes an physical restrictions for transporting or even delivering the product to individuals around the globe. It can also easily be shared by bandmates, gifted to friends, and easily stored in any environment, making it catered to individuals of all musical backgrounds. We also spent a significant amount of time designing our pedal interface (knobs, switches, buttons) to make it easy to adjust and view pedal settings. The only “complex” component of our design are the pcb board and Daisy microcontroller. These components will be hidden inside the pedal casing, limiting access to any harder-to-use parts. While our product does promote usage amongst people all over the world, it does require a power supply which could serve as an obstacle for users in areas of unsteady electricity. Such a factor is difficult to mitigate in the context of a guitar pedal design due to the necessity of a power supply to operate. However, we hope that our basic user-interface and other design choices will compensate for any other shortcomings outside of our control.

 

Part B (J. Frantz): 

Our pedal will allowsfor users to subdivide the repeat period into either four or three portions, matching how most contemporary music uses binary or ternary meters. These encompass the most simple divisions of time in music, and there will be a wide range of customization granted by allowing the user to select a meter.

Notably, our pitch-shifting is planned to use 12-tone equal temperment tuning in order to calculate the intervals. This is a standard that is used throughout most contemporary music today, but this is not the only tuning system that exists. Microtonality is prevalent in genres like Indian classical music, but our pedal’s pitch-shifting will not account for this.

These simplifications are design choices made with a semester’s scope in mind. Our primary goal is to make a device that is useful for a wide range of musicians, and we wanted to keep our design simple enough. Allowing for a wider range of meters and tunings is a possible goal for further improvements beyond our capstone.

One important cultural factor to consider is that the general public would not like to be subjected to excessive noise. Therefore, in our delay mechanism, we will restrict the amplitude scalar for each successive delay to be not more than unity. This will ensure that the input sound will not grow exponentially loud and harsh for people in the vicinity.

 

Part C (Nick W):

The main environmental considerations for our project come in production and the energy efficiency of operation. For production the main concerns are the materials used, and how they are produced. Considering this, we are using mass produced interface parts, which don’t have much environmental impact, 3D printing our casing to minimize waste, and using a standard PCB manufacturer, but would likely search for an environmentally friendly manufacturer if these were mass produced. For energy efficiency, we can’t save power in many places since we need most components to be on while the effect is active, but we will turn off some parts such as the screen when the effect is off.

Frantz’s Status Report for March 8

This Week’s Accomplishments:

This week, I continued to make progress on the pitch-shifting algorithm. I retrieved the Daisy Seed microcontroller, and verified that it connected with my computer so I could load a program onto it. I also began teaching myself how to program in C++, as the Daisy Seed uses that language to be programmed.

Status:

My progress is slightly behind schedule since I haven’t finished programming the phase vocoder algorithm, but it is moving along steadily.

Next Week:

Next week, I will reconvene with the team after spring break. I plan to continue programming the phase vocoder pitch-shifting algorithm, and I will research how to rewrite it in C++, a language I am a beginner in. For example, I will determine if I need to write my own direct Fourier transform algorithm or if I could import one.

Nick W Status Report for 3/8

I wasn’t able to accomplish much this week as I got sick at the start of the week and it lasted for the entire week. With the energy I had, I prioritized finishing my part of the design report and preparing for two midterms I had for other classes. We are still behind for the same reasons we were before, as with midterms and my illness we didn’t have time to catch up on work, but we will in the next two weeks, so we will try to get back on schedule in that time. In the next week, I hope to get an initial version of the 3D model done to revise with my group, and work with Chaitanya to help with PCB work.

Chaitanya’s Status Report for March 8

This week, I focused on getting the PCB layout off the ground. My first obstacle was finding the proper layout footprint in a PCB design tool. My familiarity with Autodesk Fusion360 led me to look into finding a footprint in the Fusion360 library. After conducting extensive research in the Fusion360 library and looking for download options online, I concluded there were no options to proceed with Fusion360. I looked into alternatives and settled with using KiCad for my layout tool as the Daisy footprint was uploaded to the open source library in KiCad. I have attached a screenshot of the print below.

I then looked into the standard sizing of guitar pedal casing to determine the size of the board. After conducting brief research, I decided to size my board with a width of 2.85” and a height of 5”. I have defined the board outlines in my layout. In addition, I contributed to the design requirements and system implementation portions of the design report, amongst other minor formatting contributions. As part of the report, we finalized an initial draft of the bill of materials. While further discussion is needed to determine if any more components are required for our product, this initial list allowed me to begin my search for layout footprints of materials in the KiCad library and online. My next goal is to use the pinout of the Daisy Seed to begin connecting the I/O pins and power pins to the appropriate components.

I am still on schedule as the barebones of the PCB are coming together. I hope to have a board layout next week. I also want to begin prototyping my components on a breadboard. However, this might temporarily be on hold until I can determine basic tests to prototype as waiting for full functionality of our desired features will take too long and limit the duration of time for which I can prototype.

Frantz’s Status Report for February 22

This Week’s Accomplishments:

This week, I researched and began to program the pitch-shifting algorithm. The bucket size will be an important trade-off, as both pitch accuracy and low latency are important considerations for our users. I have been largely busy with other responsibilities this week, but I have not been idle for this project.

Status:

Our progress is on schedule.

Next Week:

Next week, I will meet and discuss with my team. We will continue to research and order components. I plan to finish programming the phase vocoder pitch-shifting algorithm, as I continue to await the arrival of the Daisy Seed.

Nick Status Report 2/22

I had less time to work this week, as I had a midterm, lab, and essay due. Sunday, we finished up the slides for our design presentation as a group, and in class, I did peer reviews for the others. I continued searching for the remaining components that we haven’t ordered yet, but need to confirm with the group that they are what we envisioned and that they will work with the microcontroller. Also did some research on how to add some additional features we were considering on the hardware side. We are technically behind, but this was planned for in the slack time we allocated in our schedule. Next week, I have two midterms, but still hope to get the parts ordered, work on the schematic in lab with the group, and finish my part of the design report later in the week when I have more time. I also need to talk to discuss the feedback from the design presentation at our meeting Monday.

Team Status Report for 2/22

So far, the biggest risks remain the same as last week, mainly with components or parts of our design not working as intended or being broken. We have ordered multiple of the parts we have decided on and will order multiple of future parts to mitigate this, as well as planned for alternatives to our PCB if that doesn’t work. We also considered some alternative methods to implement the current planned features of the pedal, as our microcontroller is more specialized and none of us have ever used it before, and while we have tried to look for any issues in planning, we need backups in case we miss something.

No major changes have been made to the design yet. With this being a week many had midterms, we did not have as much time as in previous weeks, so we prioritized getting the design presentation done and prepared for, as well as getting a start to the report. We have some concerns about the design, as it seems from the feedback of our presentation that there was some confusion about the way we explained the functionality, so we will discuss this further in our meeting Monday.

Chaitanya’s Status Report for February 22

This week, I focused on ironing out exactly which models of components we need for our user interface. I researched switches, buttons, 7-segment displays, etc. and made a list for ordering. I also finalized the overall implementation plan involving the daisy seed and its interaction with i/o devices. I presented our design on Wednesday in class and answered questions as well. I began working on the PCB schematic/layout, finding the exact model of the Daisy Seed Microcontroller and other hardware components of our pedal interface. I have began to wire periphery based on pinout and desired function. I have not started prototyping, but I will do that once a PCB layout is somewhat finalized to make efficient use of time.

While I have made some progress, I am slowly starting to fall behind. I have been dedicating a lot of time to documentation (design presentation). However, in doing so, I have lost track of the actual project progress. My plan to get back on track involves dedicating some time over break to get a preliminary draft of the PCB done to show to group members, professor, and TA for feedback. Then, the following week or so can be allotted to finalizing the layout and sending for manufacturing.

Chaitanya’s Status Report for February 15

Professor Sullivan and Gordan (TA) noted that our MVP lacked some details. Hence, my first priority was to iron out our MVP. I did this early in the week after meeting with my group, noting the following details in a Google Doc:

Input:

  • Sequence of notes played
  • Time shift (delay) specified by knob
  • Amplitude Modulation specified by knob 
  • Specify beat – 1, 2, 3, 4 

Output:

  • Sequence of notes delayed by specified time shift + indefinite amplitude modulation
  • Notes will be played based on beat specified 

Stretch Goals

  • Pitch Shifting – user specifies number of octaves 
  • Tap Tempo – specify delay based on how user taps guitar pedal
  • LED Buttons

This provided some clarity for the basic and additional functionality of our pedal that will be crucial when answering questions about the design next week. In addition, Nick and I began the brainstorming process for additional hardware functions. Being hardware-focused individuals we want to ensure that our contributions are meaningful and show in the functions of our pedal. We plan to have a list by coming Monday to present to Professor Sullivan during our meeting. The middle of the week involved drawing the diagram for our design, making notes of interface functionality, and specifying a clear user interface to promote maximum usability. The hand-drawn diagram below that I created from our group meeting early in the week will be used next week when explaining design details. I also drew the graph (originally created by Josie) in a clear and easy-to-understand manner to provide a presentable visual for next week’s presentation.

The late parts of this week were dedicated to ironing out further design details, particularly with our PCB. I contributed to our design review presentation that I will be presenting next week.

My progress seems to be on schedule at this point. It was noted that getting our pcb back in a timely manner is not a guarantee. My hope is that our slack provides me ample time to get the board back. However, we will be prototyping using a breadboard and/or a PCB dev board, which will serve as our backup. While this is not ideal as the circuitry will go inside our pedal that is moving up and down when pressed, it will ensure that we can deliver our MVP in the case that we cannot rely in a timely fabrication of our board.

In the next week, I would like to get a jump on the PCB design and finalize the schematic and specific use of the board by next week so that I can get the board to tapeout in a timely manner. I would also like to begin prototyping our board using the daisy seed to get a feel of how our circuitry will look. This will involve further study of the pinout of the daisy seed and relating that to the various design details that we will be finalizing prior to our presentation next week.

Team Status Report for February 15

Currently, our most significant risks are the possibilities that the components we receive arrive broken or stop working during testing. We are addressing this by ordering extra parts to use in this case.

This week, we made many changes to our prior designs for the pedal. We settled on using rotary encoders for our dials instead of potentiometers, and we decided on a mechanism to control pitch-shifting. Pitch-shifting greatly increases our pedal’s functionality in a way that will be beneficial to our end users. Using potentiometers would limit our dials to controlling one parameter each, so we rejected that idea so that one dial could control pitch shifting for any of the sequence beats. We decided to use the delay time’s rotary encoder to change the pitch (in semitone increments) to whichever sequence note is selected among a set of switches. We also decided to allow users to mute the first note in the sequence, which we imagine could be useful and easy to implement.

Our schedule has more or less stayed the same. We are not behind on anything, and we anticipate having time to spare in case any of our components arrive late.

Part A (J. Frantz):

Our pedal will be a tool for making art, but there are still important safety issues to take into consideration. For starters, our pedal should be sturdy enough to withstand a person’s stomp. If our pedal were to shatter if someone presses too hard, it could send pieces flying and potentially injure someone. Also, it could expose our circuitry, which would be a shock hazard. Given that we want our pedal to be used indoors or outdoors, we want our pedal’s insides to be safe from the rain. So, we should ensure that the casing is water resistant.

Part B (N. Walker):

Our pedal should be usable by people from many different cultural and social backgrounds, and the most significant consideration for that is making sure anyone can understand how to use it. We cannot expect everyone who might use our pedal to speak the same language, but as it is an effects pedal for instruments, we can expect that they will understand basic musical terminology. Knowing this, we can use musical terms on the interface, such as “tempo” for delay time or using the terms for different beat patterns to control the delay patterns, and therefore make it as culturally accessible as possible.

Part C (C. Irkar):

By producing a single pedal, we provide an affordable alternative to expensive music technologies that have a wide range of functions that might not perfectly meet the needs of the user. A custom pedal allows us to cater to the needs of guitarists while reducing the cost of hardware, making it more cost-effective to produce and distribute. The compact design of our product makes it more portable, enabling musicians to easily transport our product and use it in an environment of their choosing. While the functionality of our pedal is our top priority, having a user interface that is straightforward and easy to use is something we will push heavily for. Our goal is to create a product that both an amateur and a professional can use. Considering these economic factors will mold our product into a user-friendly, affordable, and portable device that can aid any musician.