that looks like the right adapter. Plug it in, reboot and run

ifconfig -a

What's the output?

wlan2 Link encap:Ethernet HWaddr 10:da:43:08:89:12

inet addr:192.168.4.1 Bcast:192.168.4.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:2810 errors:0 dropped:0 overruns:0 frame:0
TX packets:273 errors:0 dropped:1 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1038423 (1014.0 Ki😎 TX bytes:34777 (33.9 Ki😎

I see that it is sending and receiving packets so that's good. I'm sure it's about my router, but ultimately I want to connect directly with my phone.
what i really want to do is this:
https://fleshandmachines.wordpress.com/2012/10/04/wifi-acces-point-on-beaglebone-with-dhcp/

basically, install instructions for hostapd, which is giving errors:

Get:1 http://ftp.us.debian.org/debian/ jessie/main libnl-genl-3-200 armhf 3.2.24-2 [18.3 kB]
Get:2 http://ftp.us.debian.org/debian/ jessie/main libnl-3-200 armhf 3.2.24-2 [51.1 kB]
Get:3 http://ftp.us.debian.org/debian/ jessie/main libnl-route-3-200 armhf 3.2.24-2 [101 kB]
Err http://ftp.us.debian.org/debian/ jessie/main hostapd armhf 1:2.3-1+deb8u3
404 Not Found [IP: 2610:148:1f10:3::89 80]
Fetched 171 kB in 0s (247 kB/s)
Failed to fetch http://ftp.us.debian.org/debian/pool/main/w/wpa/hostapd_2.3-1+deb8u3_armhf.deb 404 Not Found [IP: 2610:148:1f10:3::89 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

any ideas?

While the board is connected to the internet (e.g.: through your router) run

 apt-get update

Before your run apt-get install

Also make sure the date on the board is correct. Opening the IDE while the board is running should set the date ( until the next reboot )

disco!!!

should I set the wlan2 address, network and netmask to the same addresses as the usb0 adapter?

thanks for the help.

No you should not, that could prevent the usb connection from working.

From what I can see, in combination with the tutorial you linked to, your network seems to be ok. Have you tried connecting to it from another device? Unless you go through the second step of the tutorial(dhcp), you will have to manually set the ip address on the device you use to connect to the network (e.g.: 192.168.4.2)

It works. I am seeing the IDE from my phone. woohoo. thanks for making yourselves available. I will be happy to take some video and photos to show my project once it is finished. This puts me a big step closer.
Thanks again.
A.D.

a month later

Hello,
My board came in just in time for me to play over the holidays. Thank you, I'm so excited.
....so, the osc objects in the current version of pd are reliant on [netreceive]
The message from the ide is: netreceive is not supported by Bela, use the C++ wrapper instead.
I see the C++ osc example but has trail been blazed for getting the messages into pd?

btw, I'm currently trying to use a javascript library called NexusUI to make web objects that broadcast osc messages.
http://nexusosc.com
It uses AJAX to relay messaging with a file called nexusOSCRelay.php. It worked on a MEAN stack that I set up on my desktop so I thought I would move ahead with testing on the bela webserver. I'm hitting the page on the webserver with my phone and the objects are rendering ok. If it was working (ports defined correctly, etc.), would I see print messages in the osc C++ example as they came in from the webpage?

Happy Holidays to all at Bela.

    adowty glad to hear you got your board before Christmas!

    When I made the scope-sliders example for Bela I considered using nexusOSC to do it, but I decided against it for the following reasons:

    • AJAX is much slower and less efficient than a websocket, especially over a local connection
    • I don't like PHP, I'm not sure its even installed on the Bela image by default, and all of the Bela web server code is programmed in node.js so I didn't want to add another language to the mix.

    When you change the scope-sliders, some js running in the browser sends the data over a websocket to node.js on the board which then relays it over OSC to Bela. My recommendation would be to do something similar, using the OSC example here as a starting point. You could still use nexusUI for the GUI objects with this method. We are actually planning on separating the sliders from the scope at some point which would make this all a lot easier, though that hasn't happened yet.

    That said, the nexusOSC route should work fine, and yes I think you should see your OSC messages printed to the IDE console if everything is set up right, though it will only work if the format of your OSC messages is exactly as the code expects.

    Once you've got it working with the C++ example hopefully @giuliomoro can point you to some advice on getting it working with PD.

        Hi guys, I want to set up a symbolic link to the public folder to make development faster.
        what is the path to the files I see in BELABOOT, the volume I see on my desktop?

        ln -s ~/Bela/IDE/public/mywebfolder /path/to/BELABOOT

        it's /boot/uboot. I am working now on netsend/neterceive on libpd.

        hello,
        I implemented a properly threaded [netreceive]. It works for UDP (-u) and with or without -b. No TCP at the moment.
        Pd's original object would check for new data on the socket from within the audio thread (pure evil!), this one checks for new data in a separate thread (which is handled by the Bela program, so you will need a new default_libpd_render.cpp to account for this ) and adds the data to a ring buffer. It then requires a bang in order to output its data. Upon bang, it reads from the thread-safe ringbuffer and outputs the data.
        Let me know if you want to access this version or you prefer to wait till I implement an "auto-timer" so that you do not need to bang it (and it goes back to being fully compatible with the "regular" [netreceive])

        Note: this [netsend] requires a `bang` to poll for received data

        Actually: done.
        UDP should be working fine, but not TCP.
        I don't think [netsend] is working at the moment.

        You need to update your board to this version of the core code (note - in case you were using a custom render.cpp file - you will need to apply these changes to your file as well).
        See here for info on how to update to an "experimental release".

        Happy New Year guys. I'm knee deep in this now.
        I did the update. (f.y.i. it erased my little webpage, so i had to re-copy it back to the public folder)
        Giulio, your last two posts seemed to indicate that at first, you had [netreceive] sort of fixed and then you posted again suggesting that you had it all the way fixed.
        Just to clarify, do I need to replace my default_libpd_render.cpp or did the update cover that?
        (I'm not even sure what this is and thus, haven't created a custom one yet)
        Also, do I need to [metro]>[bang] the [netreceive] or did that get fixed for the distro linked to above.
        I'm getting sound out of the board. (good)
        osc is not yet working. links to the socket.io, jquery, and nexusUI libraries are good.
        The NexusUI node.js example I linked to the other day has this line where address is defined:
        var socket = io.connect('http://127.0.0.1:7562');

        would you say that was correct?

        Then I have a pd patch called osc_test that looks like this:
        [metro 100]
        |
        {listen 7562}
        |
        [netreceive -u -b]
        |

        • |
          [oscparse]
          |
          [print]

          pd print messages should go to the ide message board, correct?

          Hello,

          it erased my little webpage

          that's expected, the update script currently replaces all the following files/folders:

          core include Makefile lib examples Doxyfile IDE

          in fact, an "advanced user" placing/editing files there is supposed to know this. A warning pops up when you do the update but we may want to make it more clear.

          This updated version of libpd does not require the [metro]--[bang], it will automatically send a message to its output when a new input comes in.
          The default_libpd_render.cpp and libpd are automatically updated.
          default_libpd_render.cpp is used as the default wrapper around your Pd patch when using libpd. You don't have to know about it unless you want to change something about it (e.g.: for a custom application). In that case, you'd use it as a template to craft your own. I mentioned it here because in case you had your own custom rende.cpp, then in order to get [netreceive] to work, you would have needed to apply to your file those changes I applied to the default one. But it seems like you don't need to worry.

          Try with

          [netreceive -u -b 7562]
|
[print]

          and see if anything gets printed to the console.
          If it does, and it looks too much like gibberish, then nexusUI (which I know nothing about) may not be sending binary but plain text, so try removing the -b (which stands for "binary").

          nothing yet. I have looked through all other mentions of osc on the forum.
          I'm not an an advanced user by any stretch. I'm an instrument builder. I need to make an audio effect, I learn PD; I need to cut a complex shape out of wood, I learn CNC; I need to make a webpage, I learn web languages. I am reading about node, npm, socket.io and server side js but I am not really getting it yet. However, I am pretty determined to get this to work and I don't want to install php if you don't think it will be a good idea. I don't expect you to support anyone else's products or work.

          From my reading, it appears I need to set up a custom "nx" server by running a small js file server side.
          For the scope sliders, it appears there is a js file called scope-worker.js which has similar code to what I need to run but with different parameters. I can see that it is running in my browser console, but it is not called from the html file. Is scope-worker.js called when node.js starts up or when the scope is started? Is there an ini file somewhere that starts it? and finally, should I use different ports in my script to avoid conflicts with the scope?

            Oh wait I see what your issue is:

            adowty var socket = io.connect('http://127.0.0.1:7562');

            If you are trying to send OSC over the websocket, then the Bela program will not be able to handle it, because it does not support websocket or TCP. Even when I'll fix the TCP in [netreceive], it will not be enough: websocket is built on top of TCP and some additional patching is required, see e.g. this patch which does not even use [netereceive], rather it uses [mrpeach/tcpserver].

            Long story short: I'd suggest NOT to try and handle a websocket connection from within libpd:

            LiamDonovan When you change the scope-sliders, some js running in the browser sends the data over a websocket to node.js on the board which then relays it over OSC to Bela.

            As Liam suggests, the easiest way to handle a websocket connection with the browser (assuming it is what you want) is to have node handle the websocket with the browser and relay the messages to the Bela program over UDP.

            Not sure about how scope-worker.js is loaded, but you may want to start your experiments with running your script in a stand-alone script, in a different node process, it is surely going to make debugging easier in the beginning: make it an entirely different script and run it with node yourscript . As long as you listen on different ports than the ones used by the Bela IDE, your stand-alone script should work fine, the script will be fast at starting / stopping and development is easier.