#1847

i don’t know about precisely this situation but i do not think it is good to use these “floating ring” cables. this could (i think) lead to phase cancellation issues because the inverted “floating” part of the signal doesn’t go anywhere. try some different cables and see if the problem persists.

1 Like
#1848

@atlas
@zebra

Thank you so much for all the interest and availability. I found the problem.

I used these cables that I usually used to direct DC Coupled signals from the sound card to the modular one and in fact on Thonk there is also a note about it
https://www.thonk.co.uk/shop/floating-ring-cable-14m/

Note due to the floating ring on the 1/4″ connector, using these cables to take a signal out of your modular and into the 1/4″ input of an external device will work but is not ideal. It depends on how the input is balanced or whether it auto-detects a signal as being balanced or unbalanced. This is often not documented with consumer devices. The signal is likely to be clean and audible, but may have some unpredictable side effects (inversion or attenuation etc).

Now I’m using these Doepfer Adapter Cable 6.3 / 3.5 mm to record from Ableton to Fates and there is no more volume loss. Thank you very much Ezra :slight_smile: I’m sorry for the time you spent on me.

Ciao (:

3 Likes
#1849

glad you got it figured out! one more experience in my toolbox of diagnosing audio problems.

1 Like
#1850

I’m reading through posts related to power supply with fates, and from what I can tell, a raspberry pi consumes about 1000mA at full load. I’m curious, and tempted to try, if anyone has connected their Fates using the pi3 to a USB power on their modular? I have an Intellijel TPS80W PSU, and a USB power jack connected to the 5V rail. The TPS80w supplies 1500mA, and I have 1300mA to spare.

Edit: I also see on the Raspberry Pi website that recommended PSU current capacity is 2.5A (for the 3 B+). I should also note that I often, but not always, will have a grid connected, and a basic keyboard as well. If memory serves me correctly, a grid can consume up to ~600mA? I think a keyboard will be negligible? The newhaven display max current draw (according to the documentation) is 375mA (on 3.3V). I’m not exactly sure how these all fit into the equation though.

#1851

You could try, but you’ll likely get undervoltage warnings* from the pi (red led will go off and on again).

* If the power supply to the Raspberry Pi drops below 4.63V (+/-5%)

I have various “2.5A rated” PSUs and many of them throw undervoltage warnings.

I suggest just using a quality well rated PSU.

#1852

Thanks @okyeron, I didn’t even think about the voltage regulation part.

I do have the 3A usb-c power supply that came with a Pi4 which is what I’ve been using on my pi3 Fates build. That has worked without issue. I’m just looking for ways to unplug another wall wart if able.

If 5V from my current modular PSU isn’t stable, I won’t pursue this further. I might try logging some data on that tonight to see how stable that is.

If it is stable, I’m curious if my amp draw will be a concern. I’m not sure if the 2.5A recommended PSU for the Pi 3 is to account for all the peripherals attached to it that could draw power, or if there is something like a high current draw when the device is turned on. But my first guess is, if I had no peripherals attached, and only Fates connected via USB to my modular PSU, that my peak amp draw would probably be under 1A. I suppose I could just plug in my fates with the usb-c PSU that came with my pi and measure the amp draw to find out. I’ll give that a go too.

Edit:
Saw this in the DIY Norns Shield thread. I think I’m just not gunna worry about using my modular PSU as a power source.

#1854

I’ve been having this weird encoder issue. Enc1+2 are bouncy when I max out stuff quick(like mixer levels) they bounce between levels. Is this a hardware issue? It started occurring, as far as I know, with the latest update.

#1855

It is a hardware issue as there is no debouncing on the encoders . I guess you started noticing it now because you have your fates for sometime and a bit of dust has accumulated in the encoder, without debouncing this would result in a jumpy encoder . You can try modding to caps there, check example.

download

6 Likes
#1856

The only thing my terrible synthrotek PSUs are capable of doing is powering a terminal tedium and a few other modules without noise. Only good thing it still does.

#1857

I’m new to hardware debouncing, is there a range of cap values that should work for this? I should have some 0602 around that will fit…

1 Like
#1858

I’d try with 10n, if that doesnt work maybe 100n .

#1859

Those supplies need de-bouncing. Mine switched my whole rack on and off at 20 Hz. Then I sent it back.

#1860

Yeah man, it’s got serious issues-both units I have. They’re garbage and couldn’t really recommend them at all. My main case has two of the metatronic mods PSUs in it and I have been super happy with those. I wish I could return the old PSUs but I built them myself from panel/PCBs to save that extra $15 or whatever; hindsight 20/20. One of them does power the “test” case still though and works well enough with my Terminal Tedium and some analog stuff.

#1861

IMG_0352


I just finished building my fates!
Theres a clicking/ticking sound, and a very high pitched squeal, but playing samples works (clicking continues, high pitch noise continues). Any ideas on where to start troubleshooting?

Edit:
I reflowed all the pins on the codec chip, made sure they’re not bridging. Now its worse haha. There is no high pitch squeal on the headphone or line outs, no clicks. But now when the meters show signal on the in and out, about halfway up on the meter consistently. Also when I try and play back a sample, I can’t hear anything. I’m guessing I overercooked the codec chip?

#1862

Not really sure what to suggest.

You might try going back and testing just the Audio system with the info here: https://github.com/okyeron/fates/blob/master/troubleshooting.md#audio-tests

Picture of the soldering around the DAC chip? Do you have proper voltages?

1 Like
#1863

Thanks for helping me okyeron, I just checked the voltages and the 3.3v near the GND and 5V test points is only giving me 0.87V. I already swapped the regulator for another one, same thing. The 3.3V test point with the pi installed does give me 3.3v.

I’m new to soldering smd, and I did have a tough time at the beginning with the audio codec, but looks to be fine to me.

image
image2123×2560 1.42 MB

#1864

yeah - that’s not good. The 3.3v there powers the codec, so that’s likely where the problem is coming from. (the Pi supplied 3.3v goes only to the display)

Check all the 100n caps to be sure they are not shorted under the component.

Check the USB-C connector soldering as this is an area where shorts can happen. I usually check the 5v and GND pins for continuity before applying power. Then check 5V and 3.3v. You can do this with the PI disconnected if you’re wanting to just test the USB-C jack and power.

Also check the orientation of C19

1 Like
#1865

Thanks so much @okyeron! I had a two part problem, earlier when testing voltages I had shorted out the 3.3V regulator, and had replaced it, but I guess one of the two legs that receives power hadn’t made proper contact.

And, the clicking issue I had with the codec last night was likely solved when reflowing solder around the chip.
I now have a working Fates! Thanks for all of your hard work, it is greatly appreciated!

2 Likes
#1867

Today after returning from vacation I turned on my Fates, the red light was on but the black screen and the operating system did not start. However, a restart by turning off the power socket was enough and it started again.

ORAC is installed in my NORNS (if this information is useful).
I wanted to find out if it has already happened to someone and if there is a way to do a chekup.

Thanks

#1868

Maybe this helps: I sometimes find that my Fates gets stuck while booting in case the Grid is plugged in. As soon as I remove (and then replug) it, everything is okay.

1 Like