#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
#1869

I don’t have a grid but I have connected a QWERTY keyboard for Orca :frowning:

#1870

The problem is unfortunately more and more frequent

Could someone help me figure out how to solve? :frowning:

#1871

can you test with it removed from the case? I’m wondering if there’s some kinda short happening somewhere maybe?

Also plugging into HDMI can give you a console to see where the startup process might be stuck

#1872

I can try but it happens randomly.
If it happens again what can I do with HDMI?

On FATES I also installed ORAC. Could there be a problem with the OS swap on startup?
if it can be useful sometimes it happens that it doesn’t restart after going into standby.

#1873

The HDMI output should give you a console output of the linux system startup processes. You can look for errors there. There’s also logs but I’m not sure which ones to tell you to look at.

You can also check over SSH when it gets stuck and see if you can still login/etc (is linux running?). If not, then its likely a linux system problem or perhaps power related(?). If things are running, but norns or orac are not starting, then journalctl -r can give you some info to see if there are errors. dmesg is also helpful to look for power related warnings (like Under-voltage detected!).

Then the following will show info/status for the norns processes:
systemctl status norns-matron.service
systemctl status norns-crone.service
systemctl status norns-jack.service
systemctl status norns-maiden.service
systemctl status norns-sclang.service
and then orac/sidekick
systemctl status orac.service
systemctl status sidekick.service

1 Like
#1874

I have this case. Ended up putting capstan tape on the case where it meets with the screen pin solder points to solve the problem . I don’t know if your problem is the same but it does worth a try to use it without the case and see what happens.

1 Like
#1875

thanks:) could you show me exactly where to put the capstan tape?

#1876

thanks for the exhaustive answer. if it happens again I will try to remove it from the case.
even if as mentioned before it happens randomly. Don’t you think that if there was some short even when restarting it shouldn’t restart?