#21

You have to ssh into Norns and run the above commands from tehn’s post about the bandaid fix.

#22

Thanks for the clarification! I was able to figure put what I needed to get this fixed. Going to test out later.

1 Like
#23

PLEASE do not attempt this fix unless you’re already familiar with git — don’t worry, a forthcoming update will include the encoder fixup which will be a straightforward process.

2 Likes
#24

I might be seeing this issue, after updating my norns (which had been sitting for longer than i would like to admit) to 190930.

I was playing with the circles lib and saw that my cursor was not behaving correctly when i turned encoder 2. The X axis (encoder 2) was kinda bouncing around if i twisted the knob back and forth, the Y axis (encoder 3) had no issues. After trying to find an issue in the code i tried swapping which axis the encoders control. The issue was then on the Y axis and not the X axis. So it seems that the issue is coming from the encoder.

I think I have one of the first batch norns. Is there a test script so i can validate if this is the issue im having?

#25

first batch I would just assume it’s time to send it in for a fix. email help@monome.org and we’ll get you fixed up

1 Like
#26

I’m excited to get it fixed and sad to send it away. Thanks!

1 Like
#27

As in, if you have a first batch but haven’t sent it in to repair the encoders, one should do so?

I’m in that boat: first batch Norns but I haven’t noticed my encoders acting funny yet. Should I just send it in as an insurance policy?

#28

PLEASE, no. :slight_smile:

breaking isn’t inevitable. and it’s a lot of work for me to fix, and $ and fossil fuel to ship around.

5 Likes
#29

Excellent, thanks for the clarification. I didn’t want to send things along needlessly.

#30

I too have noticed one of my encoders sometimes acting a little frustratingly - I’d call it very minor bouncing. But a bit like the scratchy pot on my 0-Coast, I have just lived with it cos I live on the wrong side of the Atlantic from Monome and Make Noise and it seems strange to send something such a long way to get repaired.

1 Like
#31

if it gets worse, email!

#32

I’m wondering if this update will help with knobs on Norns. I can’t even use many apps anymore cause when I turn knobs parameters with move really fast or go backwards forwards sporadically. Cheat Codes which was my fav app is the worst really. It’s almost impossible to use now because of how the parameters jump around so much. Unfortunately I stopped using Norms a couple months back because I would get so aggravated with it.
As much as I love grids/norns I will be forced to sell them if this update didn’t fix the glitchyness off the knobs.

2 Likes
Norns: update 201023 / 201029
#33

edit: we’ve learned good info! full details here: Norns: jumpy / defect encoders

9 Likes
#34

Oh man. Thanks @dan_derks, and for asking about this @Nornsrulez.

I’ve been experiencing similar jumpiness (though not quite as bad sounding) and my encoders just failed the test you suggested Dan. Trying to decide if I’d like to attempt this myself (likely not) but question: is there a good way to test the E1 encoder?

1 Like
#35

for sure! we’ve tried to keep this info searchable, but glad we can help clean up some less-than-ideal experiences :slight_smile:

folks who feel comfortable with an iron and have any experience working with solder wick will quickly get their legs with this – brian’s video above is a nice confirmation that you can tackle it with a little less finesse than you’d assume. if you’re on the fence, though, i’d say send it in :slight_smile:

mmm. it should manifest the same in any script that uses E1 as a scroller – since it was already evoked, the main menu of cheat codes could be a good test.

1 Like
#36

@Deru, i just finished replacing a wonky encoder on my norns. for what it’s worth, if you are comfortable de-soldering stuff, it’s a breeze!

2 Likes
#37

Thanks @dan_derks. In terms of the E1 encoder, what I mean is that it doesn’t control a level on the LEVELS page so it’s harder to diagnose in that example. I was curious if there was an ‘official’ way for visualizing that one as well. All good though I’ll mess around.

And thanks @Justmat. I’ve soldered some throughout the years but I don’t have a good setup atm so I’m thinking about the buy-in costs… Do either of you have a guess as to the amount I’d need to spend to get a decent enough setup? Like $100 or something? More?

Thanks all!

1 Like
#38

personally, if i didn’t already have something workable, i’d want to send it in. :sweat_smile:

2 Likes
#39

for sure – sorry, i didn’t mean to make it seem like your question wasn’t clear. it was a really good one, so i spun up this lil test script, which should basically be the same as what the LEVELS page example does, but for all three encoders:

-- encoder test

screen_dirty = true

function init()
  counter = {}
  for e = 1,3 do
    counter[e] = 0
  end
  clock.run(screen_redraw_clock)
  redraw()
end

function enc(e,d)
  counter[e] = util.clamp(counter[e] + d,0,100)
  screen_dirty = true
end

function redraw()
  screen:clear()
  screen.level(15)  
  for i = 1,3 do
    screen.move(120, 22 + (10*i))
    screen.text_right("e"..i..": "..counter[i])
  end
  screen:update()
end

function screen_redraw_clock()
  while true do
    if screen_dirty then
      redraw()
      screen_dirty = false
    end
    clock.sleep(1/30)
  end
end

i echo mat’s message, but anything that has an actual temperature control and can reach 800-900 degrees would be perfect for this sort of stuff. a good-for-life station would be ~$100, add $15 for solder and braid

2 Likes
#40

Amazing. Thanks for that @dan_derks.
They are indeed all jumpy :wink:

Email incoming, thanks again!
B

1 Like