Try a system reset and getting closer to wifi router / delete then re-add network

1 Like

small persistent problem still occurring…
updated all three norns and that all went as plan.
did my usual test with MANGL and all is well.

norns #2 however…
left it on for a bit and after the screen went to sleep it would not wake up.
the LED on the back was blinking.
turned back on the WiFi via a USB power switch and sent a ;restart from maiden.

not sure why this is only happening on norns #2.

thanks for any help!

oh yeah…
one other weird thing.
(not sure if this matters but…)
with norns #2…in maiden i noticed it looked different than the other two norns’ maiden windows.

it didn’t have the new refresh all and update all button across the top.
like this:

it just looked like the old maiden view.
weird…
:waffle:

it doesn’t seem to work…how big is this update? what’s the alternative update method? thanks!

Are you on a Shield or factory Norns?

factory…

I’ve found with the included wifi nub I need to get pretty close to my wifi router (nub is fine but my old Airport Extreme is a little retro and slow)

What have you tried so far? Is the network page showing a proper activated wifi connection?

it’s all sorted now, thanks for your help. I should be more patient :slight_smile:

1 Like

If you refresh the browser window 1-2 times for norns #2 it should update. I mentioned up thread that there is (or was) a browser cache system which is causing this - that cache has been removed as part of this release but it may take a refresh or two in the browser to purge the previous version.

2 Likes

Heads up: I had a keyboard.lua script in my app’s (Awake-mod) lib that caused loading problems for all scripts once a load was attempted. Once I renamed it, the issue was resolved - plus all my keyboard functionality was broken since I used the old keyboard commands (keyboard.event) and my script referenced the keys by number. Changing to keyboard.code and referencing the codes as strings made everything work. Makes the code a lot more readable - great addition!

2 Likes

Using a Norns Fates here, keep getting an “up to date.” message when attempting to update on wifi.
UPDATE: After a reset, and deleting and attempting to add my network, I now have NO sound and it refuses to connect to my wifi.
Time for a hard reset?

Fates update is not available yet. I expect I’ll get the fork updated and tested later today or tomorrow.

Please follow up on the Fates thread if your no-sound issue persists.

1 Like

UPDATE

minor typo hotfix added to the update which affects anyone who might be fiddling a bunch with the reverb settings. (if you don’t use the reverb, you’d likely not notice).

you can re-run the update by holding K1 while selecting SYSTEM > UPDATE

4 Likes

Can this be disabled?

Not currently but that could probably be added as an option. Is the concern privacy or something else?

The motivation for the added behavior was to reduce what has become a frequent source confusion and questions - script X doesn’t appear in maiden.

1 Like

Primary desire is just to align with my general approach; I don’t have any device doing auto-anything if I have the option.

Secondary question is whether there is version checking baked in; I’m often 1-2 system versions behind and so would want to avoid script updating if there were breaking changes.

Just to be clear the only thing which is updating is the list of available scripts, specifically this file.

The scripts installed on the device are not automatically updated.

Not in the traditional “package manager sense”, my last post in the maiden thread touches on this to some degree.

7 Likes

Roger that. Apologies for the misinterp. Thanks @ngwese!

EDIT

i think it’s the MIDI Fighter MIDI Twister causing this problem again.
powered it off and now norns #2 is behaving.
:slight_smile:


booting up things again for the night…
norns #2 is now booting up and then after the digi-dust it goes blank.

was able to power the WiFi and send ;restart.
this is what maiden reported:

Summary

Binary file (standard input) matches
fonts:
0: 04B_03__.TTF
1: liquid.ttf
2: Roboto-Thin.ttf
3: Roboto-Light.ttf
4: Roboto-Regular.ttf
5: Roboto-Medium.ttf
6: Roboto-Bold.ttf
7: Roboto-Black.ttf
8: Roboto-ThinItalic.ttf
9: Roboto-LightItalic.ttf
10: Roboto-Italic.ttf
11: Roboto-MediumItalic.ttf
12: Roboto-BoldItalic.ttf
13: Roboto-BlackItalic.ttf
14: VeraBd.ttf
15: VeraBI.ttf
16: VeraIt.ttf
17: VeraMoBd.ttf
18: VeraMoBI.ttf
19: VeraMoIt.ttf
20: VeraMono.ttf
21: VeraSeBd.ttf
22: VeraSe.ttf
23: Vera.ttf
24: bmp/tom-thumb.bdf
25: bmp/creep.bdf
26: bmp/ctrld-fixed-10b.bdf
27: bmp/ctrld-fixed-10r.bdf
28: bmp/ctrld-fixed-13b.bdf
29: bmp/ctrld-fixed-13b-i.bdf
30: bmp/ctrld-fixed-13r.bdf
31: bmp/ctrld-fixed-13r-i.bdf
32: bmp/ctrld-fixed-16b.bdf
33: bmp/ctrld-fixed-16b-i.bdf
34: bmp/ctrld-fixed-16r.bdf
35: bmp/ctrld-fixed-16r-i.bdf
36: bmp/scientifica-11.bdf
37: bmp/scientificaBold-11.bdf
38: bmp/scientificaItalic-11.bdf
39: bmp/ter-u12b.bdf
40: bmp/ter-u12n.bdf
41: bmp/ter-u14b.bdf
42: bmp/ter-u14n.bdf
43: bmp/ter-u14v.bdf
44: bmp/ter-u16b.bdf
45: bmp/ter-u16n.bdf
46: bmp/ter-u16v.bdf
47: bmp/ter-u18b.bdf
48: bmp/ter-u18n.bdf
49: bmp/ter-u20b.bdf
50: bmp/ter-u20n.bdf
51: bmp/ter-u22b.bdf
52: bmp/ter-u22n.bdf
53: bmp/ter-u24b.bdf
54: bmp/ter-u24n.bdf
55: bmp/ter-u28b.bdf
56: bmp/ter-u28n.bdf
57: bmp/ter-u32b.bdf
58: bmp/ter-u32n.bdf
59: bmp/unscii-16-full.pcf
60: bmp/unscii-16.pcf
61: bmp/unscii-8-alt.pcf
62: bmp/unscii-8-fantasy.pcf
63: bmp/unscii-8-mcr.pcf
64: bmp/unscii-8.pcf
65: bmp/unscii-8-tall.pcf
66: bmp/unscii-8-thin.pcf
*** WARNING *** The program ‘matron’ uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=matron
OSC rx port: 8888
OSC crone port: 9999
OSC ext port: 57120
starting lua vm
running lua config file: dofile(’/home/we/norns/lua/core/config.lua’)
MATRON
norns version: 0.0.0
git hash: c987e6d
platform: 2
running startup
start_audio():
arc added: 2 monome arc m1100119 m1100119
grid added: 3 monome 128 m1000648 m1000648
norns.startup_status.ok

script clear

SCRIPT ERROR: NO SCRIPT

network connections:

1 DEATHNOTE
available engines (38):
Glut
Sway
Showers
Rudiments
Warb
Shepard
Grendy
Fiahod
SimpleDelay
Sines
Pixelbangs
Greyhole
Ack
Phyllis
MGlut
Decimatec
Dronecaster
MollyThePoly
Decimator
R
PolyPerc
Hachi
YggdrasilSynth
Benjolis
Timber
Downtown
Passersby
Pools
Timber_Takt
Stack
SCgazer
Manifold
PrimitiveString
BandSaw
None
HereThere
Haven
Lissadron

1 Like

I also misinterpreted that as updating all scripts and was about to post a big “this will cause problems” …
Updating the list of available scripts on boot makes far more sense. :slight_smile:

4 Likes

Perhaps a note to add when this gets added to the docs, The sequentially part appears to be very important. (Testing on Shield) you must do K3, then K2, then K1 in order and then holding all for 10 secs.

Hitting them all at once did nothing, hitting K1, then K2, then K3 also did not work.

4 Likes