Also the inductor coming off of the VDDA pin does not have a value.
We are working on a digital and analog multi effects pedal. I will post some pictures and videos once we get the pedal up and running! Right now we were able to get the hardware to run a gain patch, so i am working on making a few more patches for our project. Also going to set up a custom pcb, hopefully in place of the owl digital board, using the owl firmware, but if not, a board that we can plug the owl digital into.
So i was in the lab today and we made some progress. We were able to get rid of the extensive noise on the output. We realized that we set up one of the GND pins incorrectly. The rest of the night went as follows.
We initially started with a problem where the input was clipping due to the biasing on the opamp. After inspection of the codec datasheet we realized that it need the 3.6v maximum analog input voltage. Because some of the notes we were playing were getting distorted from this, we decided to put a simple voltage divider to attenuate the input signal slightly to make sure it did not clip, we will change this to an internal potentiometer later on to allow the user to get that slight distortion of desired. Is this a common problem when setting this up? or did we set it up incorrectly?
After this we were able to get a clear output, however it was VERY small, and we had to turn the amp up very high to hear the output. We added a 100x gain amplifying circuit to account for this. There is still some noise in the output (we want to get rid of it completely if possibe), but it is less than before. Is there a reason the output from the owl digital board is so small? is this expected?
Lastly, since we are now able to get an output to go through to the amp and hear it, we were testing a simple gain and simple delay effect on the board. I am not sure if we maybe had the bypass mode set up on accident, but we were unable to get the effect to actually modify the signal. These effects worked fine in the online compiler and testing webpage, but did not work on hardware. Where on the owl control can i set the bypass like you said? I cannot seem to find it (and does it tell me if it is enabled or not). Also what should the bypass pin (PE4) be set to when we do not want it to bypass? the circuit for it was slightly confusing, and i want to make sure we have it going to the right value to keep bypass off.
I will go back to the lab during this week to try to work out some of these kinks, but I figured i would post my problems and questions along with any fixes i had.
Thank you, (sorry for the long post)
So I got the firmware loaded (for now I only have Freeverb as the only patch loaded) and I am trying to get this dev board set up with a guitar input and output to an amp to test the freeverb patch. I have linked an image of the way i have it set up currently. I am using the owl pedal schematic to set up the input and output filters.
Now the problem is that when playing the guitar through this setup it came out VERY distorted and noisy. You can tell that there is some sort of output from the owl digital board, and it changed slightly when messing with the potentiometers, but it in no way resembled a normal guitar output. I took a video of the sound, and i can post as a comment tomorrow to see if there is a simple reason why it is messing up.
So, basically, do you have any suggestions for setting this up the correct way? Am i missing anything that could cause the output signal to be so messed up? Or could it simply be the patch i was trying to run? Right now i am going for the basic ability to take a mono input perform the modification of the signal, and give the output.
Also one of the things a friend was asking about was what voltage do the opamps need to be at?
Okay, got it working. It was just me being dumb, and i just had to change out my usb cable. After that it allowed me to see it with dfu-util -l. Also i ran into some problems with the make for owlware. I was able to fix them by 1)making sure all of the extra stuff is installed, and 2)using sudo make for some of the make commands that were not working.
Also when trying to do the firmware update through OwlNest and OwlControl, however it is not recognizing the device when it is plugged in.
I noticed at a second look that there are two spots for the power pins. One is right next to IC1 and the other is connected to the codec. When powering over usb, should USB_VBUS be connected to the 5v input next to the codec or the IC1? Will this affect the device being recognized at all?
So i am running into a bunch of errors when making the owlware dir. First problem was the biquadfilter.h was not given. Next the Olilarkin dir was empty in the owlware patches (just commented this out in factory.h). But now i am getting errors in the hpp files, such as FloatParameter does not name a type and other vars not declared in the scope.
I will update here if i figure it out, otherwise if someone knows the fix, it would be greatly appreciated if you help out!
Also when it says in the readme to “
make to build
Builds/OwlWare.elf” and “
make bin to build
Builds/OwlWare.bin” does this mean these files should be in the directory builds dir already or will it build them and put them in there?
When i ran the git submodule init and update nothing seemed to change in the owlware directory. What are these commands supposed to add?