#369

I have experienced these digital artifacts as well in Kayan and Earthsea. I have not been able to recreate it willingly

#370

The other crash I’m seeing is with MLR when trying to load samples from my tape recordings - is this a known issue?

#371

I had a few corrupted tape recordings, some zero-byte lengths and stuff like that. They were causing MLR and Foulplay to crash the sound engine. You might want to make sure the tape recordings are ok.

1 Like
#372

I locked my norns in a crash loop while working on maiden. A line of code made it freeze but hard resetting relaunch the bad code at startup and makes the Norns crash again :sweat:

I already submitted an issue on Github, but is there a turnaround in order to escape that loop?

#373

You can connect to your device by serial-over-USB:

On my mac, norns appears as /dev/tty.usbserial-AL04CN1O, which I can connect to using screen inside a terminal session:

$ screen /dev/tty.usbserial-AL04CN1O 115200

Then once you’re in (log in as user ‘we’ password ‘sleep’) you can find your script inside the dust directory and use an editor like nano or vim to edit your script:

$ cd dust/scripts/me
$ nano script.lua

(Or if by “working on maiden” you mean you were working on maiden itself, find and fix the code there.)

Then restart your norns (sudo reboot) and things should come back up as normal.

#374

There isn’t any serial port on my laptop and i’m working on a Windows computer :frowning: Is there a way to access my norns directory via USB in order to delete the faulty script?

#375

Unfortunately you can’t just see the norns disk like a USB drive; it’s a bit more involved than that.

You don’t actually need a serial port, what I was suggesting uses “serial over USB”. That is, you use the included charging cable to connect your PC to the norns’ mini USB port. Over that USB connection you can emulate a serial connection, just as if the two computers were connected by serial ports.

It’s been a while since I’ve used Windows, but I think you can use PuTTY to connect to your norns over a serial connection. I believe these instructions should be relevant to what you need to do here. Once you have a connection, the instructions in my previous post should still be valid.

Let me know if you need more help; I’ll make sure to update the norns docs with these troubleshooting instructions. It would be good to know if the PuTTY approach works on Windows.

2 Likes
#376

Ok it worked perfectly, thank you for your help :slightly_smiling_face:

2 Likes
#377

Wonderful! :slight_smile:

2 Likes
#378

Yeah, works well! I’m primarily on Windows 10. There’s already a line on this in the norns-image readme:https://github.com/monome/norns-image/blob/master/README.md (in the Serial Connection section)

Also, I’ve found WinSCP helpful for transferring files to/from norns via wifi. There’s nothing on WinSCP in the docs, though.

2 Likes
#379

Thanks for this tip! Just downloaded it and simply linked up to my Norns and downloaded my Tape recordings. Much faster and simpler than USB Sync.

#380

I used sftp to try to replace dust on norns with the latest dust master branch. I think I did something wrong because I can’t load any scripts on norns.

I opened maiden and started a script using the publish feature. once I start clicking buttons/moving encoders I get in an unresponsive state. Tracebacks in the REPL console:




norns.script.load("study/study2.lua")
# script load
# cleanup
# script clear
# script run
loading engine; name: PolyPerc
<ok>
lua: 
/home/we/dust/scripts/study/study2.lua:66: attempt to index a nil value (global 'selected')
stack traceback:
	/home/we/dust/scripts/study/study2.lua:66: in field 'key'
	/home/we/norns/lua/menu.lua:281: in function </home/we/norns/lua/menu.lua:258>
lua: /home/we/dust/scripts/study/study2.lua:83: attempt to perform arithmetic on a nil value (global 'number')
stack traceback:
	/home/we/dust/scripts/study/study2.lua:83: in function 'encoders.callback'
	/home/we/norns/lua/encoders.lua:56: in function 'encoders.process'
lua: /home/we/dust/scripts/study/study2.lua:83: attempt to perform arithmetic on a nil value (global 'number')
stack traceback:
	/home/we/dust/scripts/study/study2.lua:83: in function 'encoders.callback'
	/home/we/norns/lua/encoders.lua:56: in function 'encoders.process'
lua: /home/we/dust/scripts/study/study2.lua:83: attempt to perform arithmetic on a nil value (global 'number')
stack traceback:
	/home/we/dust/scripts/study/study2.lua:83: in function 'encoders.callback'
	/home/we/norns/lua/encoders.lua:56: in function 'encoders.process'
lua: /home/we/dust/scripts/study/study2.lua:83: attempt to perform arithmetic on a nil value (global 'number')
stack traceback:
	/home/we/dust/scripts/study/study2.lua:83: in function 'encoders.callback'
	/home/we/norns/lua/encoders.lua:56: in function 'encoders.process'
#381

Fixed above by trying again to merge dust from github master into the dust on norns via SFTP and then restarting.

I think that this might have be an SFTP client race condition error, where I triggered a delete of dust before loading the new version in, and it wasn’t finished with the delete before adding some of the new files in (so those got deleted).

1 Like
#382

Finally received my norns in the mail (thank you @hypnosapien!) this afternoon after it got stuck in customs for a good two weeks (and cost me a bunch extra :confused: ).

I’m having trouble with what seems to be the battery.

It will only turn on when it’s plugged into a USB power source, and as soon as I unplug it will turn off. So it’s not running on battery at all.

The battery level on the levels page goes in between -1 and 0, which I thought was an issue with the power reading as mentioned earlier in this thread, but I’ve left it plugged in to charge for several hours and it’s still not running of its battery.

Any thoughts @tehn?

1 Like
#383

I should also mention that it doesn’t seem to be charging when it’s not turned on (signaled by no flashing LEDs on my portable charger).

#384

i’m sad to say that’s not a good sign. it should definitely charge.

e-mail info@monome.org and we’ll set up a repair. perhaps i can first try to send you a replacement battery.

#385

Maybe the battery got disconnected from the board somehow during shipping?

#386

i’d suspect a defect battery before a disconnection— that connector is too tight actually

1 Like
#387

Thanks a bunch! I have just sent you an email. Hopefully replacing the battery will be enough, and at least I can still use it with an external power source for now.

#388

I got this message when trying to ssh into my norns after having trouble connecting through maiden:

Cannot recognize "ssh we@192.168.0.12" as a System.Int32 due to a format error.
The same message appears when connecting via hotspot…
Cannot recognize "ssh we@172.24.1.1" as a System.Int32 due to a format error.

No idea how this would’ve happened tbh.