:confused: how much storage is free on your DISK? you can check by navigating to the main menu and hitting K2 to get the alt screen:

DISK is top right

1 Like

Thank you, that’s the issue no space! :slight_smile:

Hello, I was just wondering… is the norns analog audio input digitally converted prior to the monitoring signal path? Or is there a way to hear the audio input truly bypassed (fully analog)?

If it is converted, like I’m assuming it is, what is that conversion quality-wise? Also, does that introduce any latency? Thanks!

Apologies if I scrolled and missed the answer to this. I’m running ubuntu linux and I’m trying to follow these steps:

On Mac/linux, open a terminal and type:

  • screen /dev/tty.usb
  • then, press TAB to autocomplete your serial number
  • then type 115200

So, in total: screen /dev/tty.usb[TAB KEY] 115200

I can’t seem to find a way to tab key in linux terminal. I can do it on MacOS but not in linux on an X1 Carbon. I’m a complete novice to this stuff I’m learning as I go so I really just am curious to know why I can do it in Mac terminal but it won’t work in Linux terminal?

this was very helpful, thank you!

Sorry, but I don’t really understand the question. Are you saying that tab completion is not working in your terminal at all? And you’re running a non-modified Ubuntu install? Would be very odd if tab completion wouldn’t work in that case.

2 Likes

Thank you for replying. Per my own ignorance I attached a screenshot I hope this helps to explain what I’m seeing. With Norns connected to my PC via the USB cable I type out the code out. When I get to the part to press the tab key to autofill, my pc makes a prohibited noise like it doesn’t recognize that input. I believe I just installed the regular distro from the ubuntu site. I tried to do it via the linux terminal from the windows store and same behavior which is why I’m really confused.

It looks like you don’t have screen installed. You can install it by entering
sudo apt install screen in your terminal.

1 Like

Really appreciate you guys helping me learn. I was able to run that command successfully. However, I still can’t type out the full line of code: screen /dev/tty.usb[TAB KEY] 115200 – when I press the tab key the cursor doesn’t move over so I can type out the rest of the 115200 code. I’m trying to get to the nmtui for Norns if there is another way.

Just to be sure, how are you connected to Norns? You should be connected via the USBmini connector, the same connector that the power cable goes in.

Yup I have the same cable that was plugged in to the power adapter plugged in to my PC.

1 Like

Does tab work as auto-complete for other commands? If not, you may need to install auto-completion as well.

sudo apt install bash-completion

2 Likes

on Linux I think the serial path is

/dev/ttyA

then tab (away from computers right now, can someone confirm?)

1 Like

@acajide
@tehn

the path is wrong, on linux it will show up as /dev/ttyUSB...,
not /dev/tty.usb... or /dev/ttyACM...
(the last would be true for crow, which is a class-compliant ACM device; norns uses a separate, proprietary USB-UART bridge from FTDI.)

5 Likes

FYI you can always check device names with dmesg after plugging in a device (or with dmesg -w whilst plugging in a device):

$ dmesg
...
[  812.040789] usb 2-1.6.1.3: new full-speed USB device number 13 using ehci-pci
[  812.197657] usb 2-1.6.1.3: New USB device found, idVendor=0403, idProduct=6001
[  812.197661] usb 2-1.6.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  812.197663] usb 2-1.6.1.3: Product: FT232R USB UART
[  812.197665] usb 2-1.6.1.3: Manufacturer: FTDI
[  812.197667] usb 2-1.6.1.3: SerialNumber: A9053JK3
[  812.200835] ftdi_sio 2-1.6.1.3:1.0: FTDI USB Serial Device converter detected
[  812.200867] usb 2-1.6.1.3: Detected FT232RL
[  812.201287] usb 2-1.6.1.3: FTDI USB Serial Device converter now attached to ttyUSB0

So it’s called ttyUSB0.

Alternatively just tab complete /dev/tty, it’ll show a lot of options, including the one that we just pulled from dmesg (it’s all the way on the right in the code block below)

$ screen /dev/tty<tab>
tty%      tty11%    tty15%    tty19%    tty22%    tty26%    tty3%     tty33%    tty37%    tty40%    tty44%    tty48%    tty51%    tty55%    tty59%    tty62%    tty9%     ttyS3%                                            
tty0%     tty12%    tty16%    tty2%     tty23%    tty27%    tty30%    tty34%    tty38%    tty41%    tty45%    tty49%    tty52%    tty56%    tty6%     tty63%    ttyS0%    ttyUSB0%                                          
tty1%     tty13%    tty17%    tty20%    tty24%    tty28%    tty31%    tty35%    tty39%    tty42%    tty46%    tty5%     tty53%    tty57%    tty60%    tty7%     ttyS1%                                                    
tty10%    tty14%    tty18%    tty21%    tty25%    tty29%    tty32%    tty36%    tty4%     tty43%    tty47%    tty50%    tty54%    tty58%    tty61%    tty8%     ttyS2%

dooope, tysm ez + simon. updated docs! (@tehn / @acajide)

https://monome.org/docs/norns/manage/#no-wifi-mac--linux + https://monome.org/docs/norns/maiden/#serial-no-wifi

2 Likes

then, press TAB to autocomplete your serial number

There’s no serial number for (serial) devices on Linux, it’s just /dev/ttyUSB<enumeration number>.
I think that line can just be removed because the line above it already shows the full thing to type?
(or did serial number mean enumeration number here? :roll_eyes: )

2 Likes

oo! ty. i misread those messages apologies! will correct when i get home!

edit: done! @simonvanderveldt, can you give it another look for approval?

LGTM :slight_smile:

I guess we could potentially roll the additional sentence below the list into the list itself?

So instead of

  • then, type: screen /dev/ttyUSB0 (or whatever enumeration number was given)
  • then type 115200

Have doubts? The line should read: screen /dev/ttyUSB<enumeration number> 115200

We’d get

  • then, type: screen /dev/ttyUSB0 115200 (replace ttyUSB with whatever enumeration number was shown in the dmesg log)

What do you think?

You are a bad ass sir. Thank you for pointing me in this direction, everything is working great and all I had to do was plug it in and wait about 2 minutes like you said. Went to check for a signal and connected to my network without a problem without doing anything additional. Strong signal too, very happy.

3 Likes