i2c multiplexer for oled's

vivian

giuliomoro
alt text
these remote errors.

alt text

giuliomoro

So the OLED is correctly selected, as you can see from the 0x3c.

Those errors are the expected ones at startup. When you send /osc-test do you get any further errors or printouts? Can you try other commands as well, from the local.scd file (use the ones without ~tar)

vivian

giuliomoro the ide recieves it, but nothing prints on the oled
alt text

giuliomoro

OK I think I fixed it in a new commit.

Update and follow the instructions from https://forum.bela.io/d/1668-i2c-multiplexer-for-oled-s/47 again and try again

vivian

giuliomoro yeah can confirm its working great.
the remote errors still run on build but functions well. thank u!!

giuliomoro

great!

vivian

giuliomoro
alt text

giuliomoro

Nice!

vivian

giuliomoro quick question, im getting close to finishing this little project im working on and wanted to ask about the appropriate way to compile all the background scripts like the i2c encoders and i2c display...just all in one project?

giuliomoro

It's probably best to have each of them as a separate process running on the board. Basically, go through these instructions twice, once per each program: https://learn.bela.io/using-bela/bela-techniques/running-a-program-as-a-service

vivian

giuliomoro also slightly noob question but in the main cpp for the u82g how do i change 'parameters' from horizontal lines to vertical?

bela_robert

@vivian excited to see the end result!

vivian

bela_robert ive still some work with trills to do but its getting there!

giuliomoro

See the highlighted line and the following ones: https://github.com/giuliomoro/O2O/blob/main/main.cpp#L265
The "lines" are drawn with "drawBox". The parameter order seems to be:
(xstart, ystart, width, height). Fulll reference for that and the othwr u8g2 methods can be found here https://github.com/olikraus/u8g2/wiki/u8g2reference#drawbox

nickcamillo

@giuliomoro Is using osc to send messages to the screen for the purpose of making development easier or is there a specific functional / timing reason for setting up communications with oled displays this way? I only intend on sending updates to the screens from within my Bela.

giuliomoro

There could be several reasons, but this is mainly down to separation of concerns.. It is a different process that has nothing to do with the Bela process. The process can be started before or after the audio-processing process, according to your requirements. The process can even crash and your audio code will keep running. You don't have to modify your Bela project to support the display(s) at a low level, so for instance you can reuse the same code to drive the display while your program only implements the message sending at a higher level. So much so that - and this is the "killer app" - you can send OSC from any language, without using or knowing C++. So your program can be Supercollider, PureData or Csound and you only have to send out OSC (which is relatively straightforward in any of these).

However, if you have a C++ Bela project, you can reduce the communication overhead and communicate to the screen directly using the C++ API rather than using OSC.

nickcamillo

@giuliomoro I'm getting some errors in the 020 repo on build once #define I2C_MUX is uncommented:

Makefile:510: recipe for target '/root/Bela/projects/oled-displays-2/build/main.o' failed

In file TCA9548A.h: only virtual member functions can be marked 'override' column: 16, line: 15
use of undeclared identifier 'oldTarget' column: 2, line: 145

nickcamillo

@giuliomoro I got around these errors by commenting out both lines shrug

I'm trying to run the update script to pull in the u8g2 dependency in a different project but I keep getting the warning about usage that displays if no directory is supplied. Am I using it correctly?

from the bela console

in ~/Bela/projects/project-name

sh update.sh path/to/u8g2/on/local/machine

giuliomoro

nickcamillo got around these errors by commenting out both lines shrug

That's what I would have suggested too

nickcamillo warning about usage that displays if no directory is supplied.

That also displays if you supply an argument that is not a valid existing directory. Do you need a leading forward slash?

nickcamillo does a mcp23017 example still exist

https://github.com/giuliomoro/MCP23017/blob/bela/render.cpp

giuliomoro

you are specifically meant to run this project as a separate project from your Bela code. As this project contains a main function, it will never call Bela's setup, render, etc. If you want to use this code as part of a C++ project including audio processing code using the Bela API, then you should rename the main function to something else and call it from within your setup() function.

nickcamillo I got around these errors by commenting out both lines

that's now on the main branch with a few more edits.

nickcamillo I'm trying to run the update script to pull in the u8g2 dependency in a different project but I keep getting the warning about usage that displays if no directory is supplied. Am I using it correctly?

this needs to run so that the machine running update.sh can access the specified path. For instance, if you have /path/to/u8g2/on/local/machine on your local computer and run update.sh on the board, it won't work. I just updated to the latest u8g2 (1bd25a7e657e20ef0efdab1c9cb5ba4e0aeae75b) and updated the update script so that it should be mostly automated. This update and updated update can be found on the update branch.

nickcamillo

giuliomoro @vivian does a mcp23017 example still exist? I can't seem to get the basic LED example of the shift register in to work but i have a bunch of 23017's lying around

« Previous Page Next Page »