#286

check out the ganssle link. even with polling there will be bad data, as a nasty bounce can be very long

so cpu isn’t an issue (no interrupts) but high speed turns are tricky to filter (any suggestions to improve the norns filtering welcomed)

#287

sorry yes indeed, i only meant that the MI modules are polling at relatively slow rates and that’s a very different situation.

(whereas norns GPIO has multiple acquisition threads, blocking until /dev/input/x has stuff available… ultimately from an interrupt… right? you know, i’m gonna double-check that [*].)

look at gannsle again. you rarely get bounces/chatter in those longer windows. (though he does point out some super gnarly examples from mechanical switches - i would hope that our encoders aren’t so challenged!) what you often get is potentially long settling time, ringing &c. with a little bit of noise. while that settling ramp is crossing logic-high threshold you get spikes in the digital acquisition. i guess for whatever reason settling/ringing isn’t an issue on the MI boards past 1ms. (or whatever the UI tick timer period actually is.) (it might not be an issue on our boards either, if we switched to polling, which we don’t really want.)

this is exactly why a) hysteresis is kinda more important than lowpass, b) a voltage comparator can help, c) supply fluctuations make everything way way worse.

[*]

yeah, i think so. we open inputs as posix file descriptors and don’t set 0_NONBLOCK flag - maybe we should explicitly clear it in the code to make the intention more obvious - and then we simply wait on a read with no other delays. i still haven’t doublechecked what happens between the CPU and the input file (“lots!”) @tehn or anyone knows off hand, i would like to be enlightened.

1 Like
#288

Cool, good to know that (along with all the other input here - thanks!).

And thanks for the link to the schematic. I had not gone looking for it previously.

#289

Can you describe whatever problems you’re having? Are you able to get to the norns SYSTEM>WIFI screen and choose ADD? At which point you should see your available wifi networks. Then enter your password. Make note that the scroller for the password entry has both upper AND lowercase letters, so keep scrolling.

Or have you already done this and you are not connecting to your local network?

(really stupid question - are you using a pi that does not have built in wifi - like the older pi3’s?).

#290

thanks @okyeron so yes after adding a network it gets stuck on ‘activating’, only way I found to link Fates to a computer is creating a hotspot network

#291

If you have ethernet on your regular computer, you can always use the eth port on the pi for a quick network.

There’s also the UART connection on the back, but to be honest I’ve not really tested that with the current disk image - there might need to be some configuration to make that happen. (and you need to have a UART adapter cable thingy)

Option 3 is plug in a keyboard and HDMI monitor to the pi to debug.

1 Like
#292

Are you running multiple frequency bands on your WiFi router? I had to turn off one of my bands to get it to connect.

1 Like
#293

Yes indeed I have a 2.4 and 5Ghz, for some reason it only adds the 2.4Ghz network, but still struggle to activate on it

#294

I turned off my 5ghz band and after a reboot or two, with some patience, it showed up and connected without further issues.

3 Likes
#295

Im looking at the mouser bom and it appears as if the MEC switch is out of stock.

Would this do?:

https://www.mouser.es/ProductDetail/MEC-Switches/5GTH920?qs=sGAEpiMZZMsgGjVA3toVBPjP8QioiSm51yY4L5YTKHY%3D

Thanks

#296

yes, they are recommended as an alternative

1 Like
#297

I’m curious why the denouncing circuit on the encoder outputs is not symmetrical, i.e., the “B” phase output is not connected to 3v3 through a resistor? Perhaps @tehn is the better person to ask

2 Likes
#298

@frankchannel you just found a bug! :rainbow:

weird news is the existing boards work. but i’ll get the files fixed.

(this is proper on the actual norns, just the shield has missing resistors).

5 Likes
Approaching - DIY norns shield
#299

See note above

Mouser cart is NOT up to date. Check GitHub BOM for alternates

You could also get the 5GTH935 in a pinch (higher actuation force - 35 instead of 20)

Also Also - build guide got updated yesterday too.

1 Like
#300

My Octopart BOM for Fates Board:
Link: https://octopart.com/bom-tool/fX3ixXTQ

Is essentially the same of okieron´s github BOM…but with the encoder cups and the PCB spacers etc… (all in one BOM)
All the parts are in stock on Mouser: 79.42€ + TAX (deppend of your country)
image

Pd: whitout Raspberry PI , PCB and case.

6 Likes
Approaching - DIY norns shield
#301

After lots of troubleshooting, it turns out the display issue was rooted in the interaction between my SD card and the pi boot sequence. I was originally using an old 4GB class 4 sdhc card that was super slow. Based on dmesg, my very uninformed hypothesis (guess) was that this was causing some sort of race condition between bcm2708_fb and fbtft. I have logs of both good and bad dmesg if anyone with deeper knowledge about that stuff wants to take a look. Once I switched to a 32GB U3 card the display started working reliably.

However, oddly, the wifi worked flawlessly with the slow card, but would not work out of the box at all with the new card. I did a bunch of things that ultimately resulted in wifi working w/o having to disable 5ghz on my AP (which is an older airport extreme that does not have the ability to disable 5ghz). Specifically, I connected directly from my laptop via ethernet, reconfigured eth0 to not use dhcp because that kept shutting down the interface when dhcp timed out, added a wlan0 config to /etc/network/interfaces that pointed to wpa_supplicant, configured wpa_supplicant accordingly, disabled bluetooth and deleted all of the cruft config files in NetworkManager that came from my repeated attempts at connecting via the norns UI.

I have no idea why wifi was working fine w the old slow card and not w the fast new card, but I have a suspicion, based on the display issue, that it stems from what happens when the pi is scanning for devices and loading various drivers on boot. That said, I’m new to the pi OS so, these are just guesses. Hope this maybe helps someone else!

1 Like
#302

Has anyone updated to the new norns version on their Fates?

#303

just for you I tried it … seems to be working ok.

(I just did update from the norns update menu item)

and sidekick continued to work after update too, so thats a bonus :slight_smile:

2 Likes
#304

I am neck deep in hardware testing (smd-assembled boards) so haven’t had time to check yet.

If anyone gets a Supercollider Fail please post about that.

Good news! Thx!

2 Likes
#305

Thank you for your bravery!

2 Likes