Bare conductive touch board not working properly

Hi Community ! :slight_smile:

I've allready bought the Bare conductive Touch board for activities related with a workshop with artists in my fablab in Dax (France).
What ever I do I'm not able to make my touchboard work ! The only thing I'm able to do is to change the MP3s by popping up the sd card and changing the files in my computer.
I'm working with Mac OS 10.9.5 and I'm running the 1.0.6 version of Arduino (the last one).
The touch board is selected in the Tools---> type of board menu.
The TTY port is chosen as explained in tutorial
Whatever the .ino code I choose I have an error message. These messages always look like this : a file is not declared in the scope.

For Proximity MP3 :
This report would have more information with
"Show verbose output during compilation"
enabled in File > Preferences.
Arduino: 1.0.6 (Mac OS X), Board: "Bare Conductive Touch Board"
ProximityMP3.ino:28:29: error: Compiler_Errors.h: No such file or directory
ProximityMP3.ino: In function 'void setup()':
ProximityMP3:69: error: 'MPR121' was not declared in this scope
ProximityMP3:70: error: 'MPR121' was not declared in this scope
ProximityMP3.ino: In function 'void readTouchInputs()':
ProximityMP3:99: error: 'MPR121' was not declared in this scope

For the touch Usb midi program :
This report would have more information with
"Show verbose output during compilation"
enabled in File > Preferences.
Arduino: 1.0.6 (Mac OS X), Board: "Bare Conductive Touch Board"
Midiinterface:29: error: 'MIDIEvent' does not name a type
Midiinterface.ino: In function 'void setup()':
Midiinterface:34: error: 'MPR121' was not declared in this scope
Midiinterface:37: error: 'e' was not declared in this scope
Midiinterface.ino: In function 'void loop()':
Midiinterface:44: error: 'MPR121' was not declared in this scope
Midiinterface:49: error: 'e' was not declared in this scope
Midiinterface:67: error: 'MIDIUSB' was not declared in this scope
Midiinterface:71: error: 'MIDIUSB' was not declared in this scope

As anyone experienced such issues ? Is there any solution for this with my configuration or is it only possible (as explained in the "Bare Conductive Compiler Error Handler") to make the touchboard work properly using Arduino 1.5.6 (only with windows PC) ?

Thanks for your answer
Regards

Hey @poloolop - try using 1.5.6 or later. Check out How To Change The Code On The Touch Board With The Arduino IDE – Bare Conductive for more. Saw that you emailed us as well. We'll respond there too.

Matt

Thanks Matt, you were right !!! that was the problem ! thank you so much !

Hello, we have a very strange issue here in the extreme southern part of Switzerland (Chiasso).
No tty port shows up in the list when we connect our touchboards.
We tried already on different operative systems...
We are a beginner and a software developer...
It seems none had this kind of problem right now.
Please help!

serena

serenacangiano:
Hello, we have a very strange issue here in the extreme southern part of Switzerland (Chiasso).
No tty port shows up in the list when we connect our touchboards.
We tried already on different operative systems...
We are a beginner and a software developer...
It seems none had this kind of problem right now.
Please help!

serena

Next time, start a new thread - this is a 7 month old thread, and the only thing it has in common with your problem is that they happened to be using the same board.

Have you installed the drivers?

http://www.bareconductive.com/make/installing-the-touch-board-driver-in-windows/

Unfortunately their website is largely devoid of information on the hardware, so I can't even figure out what they're using for the USB serial interface (so as to direct you to alternate drivers, if they exist)

DrAzzy:
Next time, start a new thread - this is a 7 month old thread, and the only thing it has in common with your problem is that they happened to be using the same board.

Actually, that seems to me to be a quite excellent reason for adding to the thread.

Keeping common information in one place.

Otherwise it becomes necessary to refer to other similar threads, which is clumsy.

(Hint: Do not use the default number - 20 - of "messages to display" under "look and layout" in "profile" - use the maximum; 50. Even that is a trifle inconvenient. If there are many answers, you want to see them easily.)