Announce Thread: Magpie Modular - uBraids - Braids in 8 HP.
Moderators: Kent, luketeaford, Joe.
Coarse tune problem
Hi.
I built one and have a problem.
The module worked just fine before I cariblate it.
But after cariblation, polarity of the coarse knob have inverted.
Any ideas???
Thanks in advance.
I built one and have a problem.
The module worked just fine before I cariblate it.
But after cariblation, polarity of the coarse knob have inverted.
Any ideas???
Thanks in advance.
Re: uBraids build error/anomaly
Thanks very much.These are all v2. I will post photos tonight.ZZ Ardoz wrote:I've built a bunch from both version of the pcbs (which one do you have?) and have never had an issue with any of Magpie's boards, which are excellent.
Maybe some high-res photos would help - can you provide some?
M. Gilbert
Re: uBraids build error/anomaly
Yeah - not a bad pcb in the batch - or any Magpie board for that matter. If I had to put blind money on it, it would be a bad component.mwgilbert wrote:Thanks very much.These are all v2. I will post photos tonight.ZZ Ardoz wrote:I've built a bunch from both version of the pcbs (which one do you have?) and have never had an issue with any of Magpie's boards, which are excellent.
Maybe some high-res photos would help - can you provide some?
M. Gilbert
- Altitude909
- Super Deluxe Wiggler
- Posts: 3616
- Joined: Wed Aug 24, 2011 5:13 pm
- Location: Meesheegan
Re: uBraids build error/anomaly
That is very strange that some of his output waves are working and some aren't. The circuit does not use different paths for different waveform outputs iirc. Thats stumping me. Different pots not working and all that, I would recommend reflowing opamps and DACs. I cant think of any advice for certain waveforms bot outputting at all. I know some have different relative pitches, and harmonics based on the pot settings, so if the pots are short/open circuit from the op amps, they could come through as very quiet or silent, but that would also impact other waveforms, which would not be working perfectly. I would start by reflowing pots and op amps, anyway, and go from there. Are you sure some waveforms are working "perfectly" Gilbert?ZZ Ardoz wrote:Yeah - not a bad pcb in the batch - or any Magpie board for that matter. If I had to put blind money on it, it would be a bad component.mwgilbert wrote:Thanks very much.These are all v2. I will post photos tonight.ZZ Ardoz wrote:I've built a bunch from both version of the pcbs (which one do you have?) and have never had an issue with any of Magpie's boards, which are excellent.
Maybe some high-res photos would help - can you provide some?
M. Gilbert
My cat can eat a whole watermelon ...
Hi. Yes I did. Here's a picture.Altitude909 wrote:did u have the pot centered when you calibrated?
Picture file
Re: uBraids build error/anomaly
We reflowed opamps and DAC/ADC. We also checked control voltages at the inputs of the ADC. Yes, some waveforms are working.GryphonP3 wrote:That is very strange that some of his output waves are working and some aren't. The circuit does not use different paths for different waveform outputs iirc. Thats stumping me. Different pots not working and all that, I would recommend reflowing opamps and DACs. I cant think of any advice for certain waveforms bot outputting at all. I know some have different relative pitches, and harmonics based on the pot settings, so if the pots are short/open circuit from the op amps, they could come through as very quiet or silent, but that would also impact other waveforms, which would not be working perfectly. I would start by reflowing pots and op amps, anyway, and go from there. Are you sure some waveforms are working "perfectly" Gilbert?
All I have this evening is an iPhone, so this is the best image qual for now. Please excuse flux, etc. from all the extra reflowing. I will get some better images ASAP. Again, this is now just a learning/curiosity project.



If we don't solve this, and I don't think we have the time to start swapping all the passives, we'll chalk it up to experience.
Thanks to all commenters!
Apologies to Altitude909, the comment above was not for us. Yes, our module does calibrate and accurately tracks 1v/oct for what it';s worthmwgilbert wrote:I believe so. I will re-calibrate this evening to be sure. Thanks, and I'll post the result.Altitude909 wrote:did u have the pot centered when you calibrated?

Re: uBraids build error/anomaly
I cant tell from this resolution, but the STM32 looks to have some suspect pins around the bottom left side from the pic viewing angle. I would drown it in flux and gently reflow around that. This chip is usually the culprit when sound functions aren't working, especially if the op amps et all are clean.mwgilbert wrote:We reflowed opamps and DAC/ADC. We also checked control voltages at the inputs of the ADC. Yes, some waveforms are working.GryphonP3 wrote:That is very strange that some of his output waves are working and some aren't. The circuit does not use different paths for different waveform outputs iirc. Thats stumping me. Different pots not working and all that, I would recommend reflowing opamps and DACs. I cant think of any advice for certain waveforms bot outputting at all. I know some have different relative pitches, and harmonics based on the pot settings, so if the pots are short/open circuit from the op amps, they could come through as very quiet or silent, but that would also impact other waveforms, which would not be working perfectly. I would start by reflowing pots and op amps, anyway, and go from there. Are you sure some waveforms are working "perfectly" Gilbert?
All I have this evening is an iPhone, so this is the best image qual for now. Please excuse flux, etc. from all the extra reflowing. I will get some better images ASAP. Again, this is now just a learning/curiosity project.
If we don't solve this, and I don't think we have the time to start swapping all the passives, we'll chalk it up to experience.
Thanks to all commenters!
My cat can eat a whole watermelon ...
Re: uBraids build error/anomaly
What's your criteria for "working", i.e. have you looked at the output with a scope? Assuming the signal path is unchanged from the regular Braids, there's a few places to systematically localize the issue (DAC output, pre-/post-filter, AC coupling, output gain) and/or compare behaviour with other waveforms. If you haven't done so, checking the relevant voltages for the output path (+-12V at the 072, DAC 2V5 reference), and looking for changes in either V or signal when output is good/bad would be a first step.mwgilbert wrote:We reflowed opamps and DAC/ADC. We also checked control voltages at the inputs of the ADC. Yes, some waveforms are working.
Re: Coarse tune problem
What's the voltage source for calibration, or better: have you measured the 1V/3V you were using to calibrate?mitchel6 wrote:Hi.
I built one and have a problem.
The module worked just fine before I cariblate it.
But after cariblation, polarity of the coarse knob have inverted.
Any ideas???
Thanks in advance.
Re: uBraids build error/anomaly
Thanks! We have another build session this weekend and will do that. I will also post a real image after that.GryphonP3 wrote:I cant tell from this resolution, but the STM32 looks to have some suspect pins around the bottom left side from the pic viewing angle. I would drown it in flux and gently reflow around that. This chip is usually the culprit when sound functions aren't working, especially if the op amps et all are clean.
Thanks! Yes, we looked at the output with a scope.pld wrote:What's your criteria for "working", i.e. have you looked at the output with a scope? Assuming the signal path is unchanged from the regular Braids, there's a few places to systematically localize the issue (DAC output, pre-/post-filter, AC coupling, output gain) and/or compare behaviour with other waveforms. If you haven't done so, checking the relevant voltages for the output path (+-12V at the 072, DAC 2V5 reference), and looking for changes in either V or signal when output is good/bad would be a first step.
We did check all supply voltages everywhere, but will check for V changes between settings. The signal when output is bad is nil.
Re: uBraids build error/anomaly
Well I'm a measure/localize-first kind of guy, so I'd check the signal at the DAC. If it's also nil, then a likely cause are the SPI lines and maybe some mechanical stress using the encoder is enough to cause intermittent faults. Coincidentally I think they're the bottom side, left-most pins on the stm32 as GryphonP3 suggests, so a reflow-first approach may well things working quickermwgilbert wrote:Thanks! Yes, we looked at the output with a scope.
We did check all supply voltages everywhere, but will check for V changes between settings. The signal when output is bad is nil.

Re: Coarse tune problem
The voltage source is a References App of O_c.pld wrote:What's the voltage source for calibration, or better: have you measured the 1V/3V you were using to calibrate?mitchel6 wrote:Hi.
I built one and have a problem.
The module worked just fine before I cariblate it.
But after cariblation, polarity of the coarse knob have inverted.
Any ideas???
Thanks in advance.
And yes, I measured the 1V/3V by DMM.
Here's a weird one:
I have built about 20 of these so far, always able to get them up to 100%, then on this most recent batch, I had this identical problem on 2 modules:

Little line to the left. All of the pins on the associated chips are perfect. The only thing that has changed from my normal process is that my screens were from a newer adafruit order than my old stock. Maybe a coincidence though? If so, has anyone seen this problem and dealt with it before? I've troubleshot all usual display culprits over and over to no avail.
I have built about 20 of these so far, always able to get them up to 100%, then on this most recent batch, I had this identical problem on 2 modules:

Little line to the left. All of the pins on the associated chips are perfect. The only thing that has changed from my normal process is that my screens were from a newer adafruit order than my old stock. Maybe a coincidence though? If so, has anyone seen this problem and dealt with it before? I've troubleshot all usual display culprits over and over to no avail.
My cat can eat a whole watermelon ...
Could be a SH1106 vs. SSD1306 (the OLED driver) disparity; they are mostly compatible except for a minimally different memory layouts (IIRC 128x64 vs 132x64, so off by 4px). Depending on the graphics library used you might be able to change the type or offset to compensate.GryphonP3 wrote:Little line to the left. All of the pins on the associated chips are perfect. The only thing that has changed is that my screens were from a newer adafruit order than my old stock. Maybe a coincidence though? If so, has anyone seen this problem and dealt with it before? I've troubleshot all usual display culprits over and over to no avail.
Re: Coarse tune problem
Calibration went wrong using an o_C? Inconceivablemitchel6 wrote:The voltage source is a References App of O_c.
And yes, I measured the 1V/3V by DMM.

Hm, incorrect voltages and/or knob positions are the obvious things. Does the v/oct input work properly?
Will check tomorrow - left my studio for the night. I have 3 more on the workbench ready to do the hardqare as well so we will see if the problem persists with those. Thanks for the reply!pld wrote:Could be a SH1106 vs. SSD1306 (the OLED driver) disparity; they are mostly compatible except for a minimally different memory layouts (IIRC 128x64 vs 132x64, so off by 4px). Depending on the graphics library used you might be able to change the type or offset to compensate.GryphonP3 wrote:Little line to the left. All of the pins on the associated chips are perfect. The only thing that has changed is that my screens were from a newer adafruit order than my old stock. Maybe a coincidence though? If so, has anyone seen this problem and dealt with it before? I've troubleshot all usual display culprits over and over to no avail.
My cat can eat a whole watermelon ...
- Altitude909
- Super Deluxe Wiggler
- Posts: 3616
- Joined: Wed Aug 24, 2011 5:13 pm
- Location: Meesheegan
That's a faulty display. Got one from adafruit myself, they should replace it. It's why I make my own screens now. You would think that for what they charge, there would be better QC. I looked at the bad one I had under a miciroscope and the solder paste they used to solder the flexboard was not even remotely close to being gone, no doubt shorting adjacent pinsGryphonP3 wrote:Here's a weird one:
I have built about 20 of these so far, always able to get them up to 100%, then on this most recent batch, I had this identical problem on 2 modules:
..
Little line to the left. All of the pins on the associated chips are perfect. The only thing that has changed from my normal process is that my screens were from a newer adafruit order than my old stock. Maybe a coincidence though? If so, has anyone seen this problem and dealt with it before? I've troubleshot all usual display culprits over and over to no avail.
Re: Coarse tune problem
Inconceivable yes. I also checked ICs and passives around it.pld wrote:Calibration went wrong using an o_C? Inconceivablemitchel6 wrote:The voltage source is a References App of O_c.
And yes, I measured the 1V/3V by DMM.
Hm, incorrect voltages and/or knob positions are the obvious things. Does the v/oct input work properly?
V/OCT input is working properly..
Thanks for letting me know before I pulled my hair out even more troubleshooting. Two in one batch!! Thats terrible. I will give them a shout tonight.Altitude909 wrote:That's a faulty display. Got one from adafruit myself, they should replace it. It's why I make my own screens now. You would think that for what they charge, there would be better QC. I looked at the bad one I had under a miciroscope and the solder paste they used to solder the flexboard was not even remotely close to being gone, no doubt shorting adjacent pinsGryphonP3 wrote:Here's a weird one:
I have built about 20 of these so far, always able to get them up to 100%, then on this most recent batch, I had this identical problem on 2 modules:
..
Little line to the left. All of the pins on the associated chips are perfect. The only thing that has changed from my normal process is that my screens were from a newer adafruit order than my old stock. Maybe a coincidence though? If so, has anyone seen this problem and dealt with it before? I've troubleshot all usual display culprits over and over to no avail.
My cat can eat a whole watermelon ...
- Altitude909
- Super Deluxe Wiggler
- Posts: 3616
- Joined: Wed Aug 24, 2011 5:13 pm
- Location: Meesheegan
I had 2 bad ones in the last lot. And quite a few where the screen itself was really not put on straight enough to qualify as a good job. a bit disappoiniting. Will be making my own ones after this as well.Altitude909 wrote:That's a faulty display. Got one from adafruit myself, they should replace it. It's why I make my own screens now. You would think that for what they charge, there would be better QC. I looked at the bad one I had under a miciroscope and the solder paste they used to solder the flexboard was not even remotely close to being gone, no doubt shorting adjacent pinsGryphonP3 wrote:Here's a weird one:
I have built about 20 of these so far, always able to get them up to 100%, then on this most recent batch, I had this identical problem on 2 modules:
..
Little line to the left. All of the pins on the associated chips are perfect. The only thing that has changed from my normal process is that my screens were from a newer adafruit order than my old stock. Maybe a coincidence though? If so, has anyone seen this problem and dealt with it before? I've troubleshot all usual display culprits over and over to no avail.
It didn't flicker, no. I sold one with this issue to a customer at a discount a week or two ago who wanted one without waiting for a new batch and didn't mind the line. He said the screen went totally dead after being on for a few hours straight. Now I have to replace it with a new one for him, at Adafruit's fault. On these ones in this batch, I swapped both faulty displays out for others which work perfectly. So the displays were definitely at fault all three with identical issues. Weird!! Cant believe this level of QC. I hope they dont make me jump through hoops over there for replacements. When I sent a support message informing them of the problem they said I need to address the issie in the forums and get approved by a moderator for replacement. Sounds promisingAltitude909 wrote:Does it flicker? Maybe it's bad parts and not a process thing.. I replaced the bad display with a eastrising part and it worked fine

My cat can eat a whole watermelon ...