Monome Grid & Bela

So when I run the line:
"wget https://raw.githubusercontent.com/padenot/bela-utils/master/bela-setup-monome.sh"

I get this error:

--2020-07-15 08:48:49-- https://raw.githubusercontent.com/padenot/bela-utils/master/bela-setup-monome.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... failed: Temporary failure in name resolution.
wget: unable to resolve host address 'raw.githubusercontent.com'

I tried both with and without internet sharing the Bela and the result is the same.

Any ideas? Thanks!

as mentioned, the first step is

giuliomoro connect Bela to the internet

Now, to do that ... see this:

giuliomoro Ultimately the easiest way of getting a Bela connected to the internet would be to connect an ethernet cable into a home router: it is painless and it just works.

if this is not an option, then see this:

giuliomoro you could try to follow these instructions to properly share the network https://github.com/BelaPlatform/Bela/wiki/Connecting-Bela-to-wifi#sharing-wifi-over-usb-with-bela however it is mentioned here that an extra step may be needed (possibly dependent on the version of macos).

Oh sorry about that, I assumed my internet sharing was working before but was wrong!

So I followed the steps on the second option since I don't have an ethernet cable or easy access to a router. And that was successful I think because I now can ping 8.8.8.8.

However, when I run "wget https://raw.githubusercontent.com/padenot/bela-utils/master/bela-setup-monome.sh" I get these errors now:

--2016-11-03 17:32:49-- https://raw.githubusercontent.com/padenot/bela-utils/master/bela-setup-monome.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.112.133
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.112.133|:443... connected.
ERROR: The certificate of 'raw.githubusercontent.com' is not trusted.
ERROR: The certificate of 'raw.githubusercontent.com' is not yet activated.
The certificate has not yet been activated

I'm not sure how to activate this certificate... I'll try looking but any help is appreciated!

that is probably because the date on your board is behind. It should updated in a few minutes after the board is connected to the internet, so chances are if you were to try again now it would work. If it keeps failing, load up the Bela IDE and that should also set the date on the board, at which point you should be able to re-run the line successfully.

Yes I caught that before your next response. Unfortunately I can no longer run the sh script because I already have libmonome now and it exits at that part cuz it says it already exists.

So I just am going through each line of the script and doing it manually now, however, I always get an error when I execute ./waf inside the serialosc directory:

root@bela:/serialosc# ./waf
Waf: Entering directory `/serialosc/build'
[ 8/59] Compiling third-party/libuv/src/inet.c
[10/59] Compiling third-party/libuv/src/unix/core.c
[12/59] Compiling third-party/libuv/src/unix/fs.c
../third-party/libuv/src/unix/fs.c: In function 'uv__fs_copyfile':
../third-party/libuv/src/unix/fs.c:1154:20: error: comparison between signed and unsigned integer expressions [-Werror=sign-compare]
if (s.f_type != / CIFS / 0xFF534D42u)
^~
cc1: all warnings being treated as errors

Waf: Leaving directory `/serialosc/build'
Build failed
-> task in 'LIBUV' failed with exit status 1 (run with -v to display more information)

Hopefully, I can just get this running so I can stop bothering you!

I made a further amendment to the file, as systemd requires a full path to the executable: https://github.com/giuliomoro/bela-utils/commit/33d8e9af84fe603f9e1a344fde8e3f4b4e7b95ee

and another amendment because serialoscd does not daemonise https://github.com/giuliomoro/bela-utils/commit/98b6a93faca1cdd6cd95d072dc6d265d5233d2ea

Ultimately, these two changes affect the content of the file /lib/systemd/system/serialoscd.service. Ensure it looks like this:

[Unit]
Description=serialosc daemon
[Service]
Type=simple
ExecStart=/usr/local/bin/serialoscd
PIDFile=/var/run/serialoscd.pid
RemainAfterExit=no
Restart=on-failure
RestartSec=5s
[Install]
WantedBy=multi-user.target

well my understanding is still the same as it was here:

giuliomoro I know nothing about it, but I would guess that serialoscd is a bridge between OSC and the monome: my guess is that it receives OSC messages from the user application and passes them over to the monome over serial, and also receives serial from the monome and passes it on as OSC to the user application. So, I guess it has to stay open throughout for the program to work!

I guess you now need to send OSC to serialoscd and receive OSC from it, using the OscSender and OscReceiver classes . This can be done using the Communication/OSC example as a starting point. That example relies on bi-directional communication with a node server, but ultimately you only need to send and receive (without the more complex handshake logic implemented in there).

As to WHAT messages to send/receive, I have no idea, that would be in the monome documentation, I imagine? As to WHERE to send the messages (what port), that's hopefully in the serialosc documentation. Note that there will be nothing here that is Bela-specific, so you can probably find better support in specialised Monome forums.
One thing that emerges from the README of serialosc is that you need to plugin the monome for the process to daemonise and do something useful. This may mean that in /lib/systemd/system/serialoscd.service it should be Type=forking as it was originally, instead of Type=simple as I changed it. I cannot test this because I don't have a monome, but you can. Make sure you look at the output of journalctl -f -n 50 -u serialoscd to see if anything useful is printed when the Monome is connected.

ndivuyo @guiliomoror Greetings! I'm getting along fairly well (for my needs at least!) with Bela Salt C++ programming. I'm thinking about buying a Monome Grid to use it to control the Bela Salt. What are the chances of this connectivity working reasonably smoothly?

The above setup should work reliably, but I don't have a Monome so I couldn't try it out. @padenot may also be able to say something about how it worked for him. Because of how the BBG + Bela cape are mounted in Salt, you will need to solder some wires to the back of your BeagleBone to break out the UART signals.

I confirm that plugging a monome device (arc or grid, I tested both) on a Bela just works, nothing special to report, just like any Linux computer. I've been using quite a few packages from different languages to test things out a few years back before writing mine in Rust, also nothing to report, everything just worked, even when stress testing it.

I've only be using the regular Bela, not the mini, I don't know if we should expect anything different? Maybe it has less available power output to drive the monome or something?

Thanks @giuliomoro and @padenot - much appreciated. I'l report back when I have taken some more action! :-)

Hi giuliomoro Greetings! So, I finally got a Monome Grid delivered and installed enough on my Bela Salt so that #include <serialosc_helpers/SerialOsc.h> "works".

However, I'm now trying to get something of https://github.com/daniel-bytes/serialosc_example/blob/master/serialosc_example/serialosc_example.cpp to work in my code - but I'm not sure what files I should put where on the Bela (and anything else I should do) in order to get the sample code working.

Any tips would be gratefully received!

Is serialosc built as a (shared or static) library? If yes, you'll need to set LDFLAGS and CPPFLAGS accordingly for the Bela project so that libserialosc is linked in and the appropriate -L and -I paths are set. You mention you can already include the header file appropriately, is that achieved by placing the source files for libserialosc in the project folder?

Good questions! I will check and report back! :-)