Hello,
This is my first time using an Arduino nano board (Atmega284p), I need it for the Hagiwo VCO build.
When I try to upload I get an error saying that the board is not responding.
Heres what I did so far:
Connected board to computer via USB.
Installed Arduino software.
Selected port and board type.(shown as connected, LEDs on board turn on).
Added VCO code to sketch, added mozzi library.
Successfuly compiled the code.
Tried to upload multiple times but failed.
Tried to reinstall bootloader but failed for the same reason. (device not responding).
I’m lost… Any ideas?
are you sure where the problem is located?
I recently had a wild ride with win11 and arduino drivers. i had to use older drivers and tried several itterations till i found a working one.
TL;DR: try a different pc preferably with a different OS
I’m pretty sure that It’s a Chinese clone. It’s my first attempt with Arduino (or clone), so I was not aware that it needs a special driver, since the Arduino software did recognize a connected device. I’ll give it a go.
Switching to the old bootloader seems to do the trick. Thanks!
I’m attempting to build an adaptation of Hagiwo’s design (actually It’s a mixture of his 3 Arduino VCOs) made by someone on Github named Test Bild.
Unfortunately there seems to be a discrepancy between the schematics and the board design, as the scematics mentions 5 100nf caps while the board only has 3 such footprints. And since It’s a Github, I can’t contact the author directly.
Did anyone try this specific build or can advise?
I would imagine they are just decoupling caps being but I just checked the schematics before I read another reply properly and there are only 3 x 100nf caps
I don’t see the problem. The schematic says there’s five, the PCBs have five footprints. (Two on the main board are silkscreened on the other side for some reason.)
Ah, I finally see what you’re talking about — there are five in the schematic and in the KiCad design file but two are missing from the Gerbers. There are other discrepancies as well.
Exactly. I’ll wait a bit to see if Test Bild replies to my submitted issue, and if that doesn’t happen, I’ll finish the build as-is and see what happens. Thanks for helping out!
I have a fair amount of experience with Nano+Mozzi & HAGIWO builds, they tend to work pretty well. Very forgiving circuit. Even designed my prototype board for Mozzi a while ago (i will do a v2 with fewer issues eventually)
In addition to Testbild’s schematic, you should consider cross-referencing Pansapiens’, which does things a bit differently, and is easier to read:
Don’t sweat the capacitors, except for the one in the output path, none of them make or break the circuit.
One gotcha you might run into that nobody seems to bother to document: Mozzi has to run in HIFI mode. You have to edit a C++ header to make that happen.
Thanks!
A bit of a shame I know about this after fabricating the boards and being halfway through the build, but there’s always next time, I guess.
About the importance of parts, the Testbild version specifies a %0.5 tolerance for two of the resistors.
I only have %1 tolerance resistors, how bad is that?
Regarding the HIFI mode, I assume that Testbild’s code already has it, but just in case, what should I look for? (assuming I’m not a code person)
The precision of the output resistors is crucial to the Dual PWM output that Mozzi uses.
If you have a bunch of resistors, just measure them to get as close as possible. Don’t forget that you can produce 499K by using two 1M in parallel, and 3.9K with a 4.7K and 22K in parallel.
Personally I bought a bag of 499K and test them before use (those that don’t make the cut end up in circuits that require a pulldown resistors where the value doesn’t matter.)
The other resistor values shouldn’t be too sensitive, except for the voltage divider on the gain input
