Show Posts
Pages: [1]
1  Using Arduino / Sensors / Re: Color Sensor TCS230 on: December 12, 2013, 11:23:57 am
It is almost impossible to get values 100% accurate. But protecting the sensor from infrared light is one thing you can do to minimize  the problem. Also, when it is adjusting the white and the black frequencies, is difficult to point it to something really white or black. My experience: it will never be totally accurate!
2  Using Arduino / Sensors / Re: Color Sensor TCS230 on: December 12, 2013, 10:40:30 am
You meant 'pin', right?

If yes:

Sensor -> Arduino UNO
pin OUT -> pin 2
pin S2 -> pin 3
pin S3 -> pin 4

ColorRecognitionTCS230PI tcs230(2, 3, 4);

3  Using Arduino / Networking, Protocols, and Devices / Re: APC220 working on linux. on: February 04, 2013, 10:23:42 pm
Great! Thank you! I was a long time looking for solutions... you save my live. Actually a few hours!
4  International / India / Re: reg : MMA8451 on: November 12, 2012, 06:12:19 pm

I do not know if you still want the driver. If yes, it is ready to test.

5  Using Arduino / Sensors / Re: Color Sensor TCS230 on: October 07, 2012, 11:33:42 pm
You should note that the sensor is very sensitive to infrared, so you may need a sharp IR cut filter if you want to measure visible light only.

I are right.

My sensor is this one; these 4 led on the top of the board cannot be turned off! It becomes hard to test it with black objects. I don't recommend this one. 
6  Using Arduino / Sensors / Re: Arduino and TSC230 color sensor on: October 07, 2012, 04:57:02 pm
See this topic:,118967.0.html, I posted something that could help you.
7  Using Arduino / Sensors / Re: Color Sensor TCS230 on: October 07, 2012, 04:53:35 pm

I have written the driver for this device. Here on my github:

 I'm still adjusting it, but you can clone the repository and test it. 

There is a example inside the library.

To install just type sudo make install (or copy into the correct "libraries" folder if you want).

To see the doc, type make doc. It uses doxygen to generate the documentation and will create a folder called "doc" inside the library.

8  International / India / Re: reg : MMA8451 on: October 02, 2012, 11:01:41 pm
Hello, friend

As I said, I was working on a driver for this sensor.

I's really complex to get all those datasheet on mind to write the code, but I'm trying! smiley

I got into a complication: The sensor works using 3.3V , it's not a problem, except for the i2c interface which also uses 3.3V. To work it around I bought a Logic Level Converter device that safely steps down 5V signals to 3.3V and steps up 3.3V to 5V. (It is cheap, about $1.95, I'm no sure if I can write here the site where I bought it)

I'm still waiting for it to arrive, BUT I put a preliminary version of the library on my repository (

Be careful,  I didn't test it smiley It has a few useful methods do configure and read the data. It does not deal with the FIFO yet.

Anyway, you can get it there and maybe help me to improve it.

Best Regards!
9  Development / Other Software Development / Re: eFLL (Embedded Fuzzy Logic Library) - Fuzzy Logic on Arduino on: October 02, 2012, 10:44:31 pm
The library looks nice!

BTW: I'm proud to see Brazilians contributing with the Open Source community.
10  International / India / Re: reg : MMA8451 on: September 26, 2012, 09:31:28 am
Hello, friend

I'm right now writing a driver to communicate with the MMA8451 module;

It will be available soon on my repository on

I hope I can finish it this week!

11  Development / Other Software Development / Re: How about to create an IO API (library) for Arduino?! on: September 18, 2012, 04:55:52 pm
Ok, I will write some examples tonight...

but first, just to avoid some mistakes,

is *not* a proposal to replace any of the already existing stream libraries such as Wire, Serial, Ethernet Client, Ethernet Server, SD

but *yes* to work above them.

Best Regards.
12  Development / Other Software Development / Re: How about to create an IO API (library) for Arduino?! on: September 17, 2012, 03:50:06 pm
Let me try to explain this a little better.

A few months ago I was working with a GLCD module.
Originally, I was using PIC microcontroller, cross-compiling with SDCC compiler.
Unfortunately it generates a huge final code.

So I decide to do it with Arduino. I created a little driver to draw
bitmap images and text on that GLCD module.

As you know, there are a lot of bitmap fonts and drivers out there. But
everyone has it's own way to organize such bitmaps, and it's own way to
read it. Usually they store the bitmap in the program memory.

A bitmap font usually is an array of bytes, such bytes are grouped to
represent a charactere in the GLCD display (glyph). Usually the groups
are sequentially stored, corresponding the ASCII table.

Considering this, I thought that my driver could be more generic. So I could
create a font format that works similar to the above approach, but doesn't
require to have all glyphs. The font could has only the used glyphs,
saving some memory.

(My bitmap font format:

I started to write the font class and then I realized that I need to store the
font bitmap somewhere, and I also need to read it.

Whereas my goal was to make something generic, my solution about reading the
font bitmap need to be generic too.

So I created the IO library, firstly it had only InputStream and its
subclasses. I got excited and wrote a lot of more classes.
13  Development / Other Software Development / Re: How about to create an IO API (library) for Arduino?! on: September 17, 2012, 10:43:54 am
Sure, it will spend some extra bytes.

I created 2 sketches right now just to compare.

One just uses  an external eeprom driver, which is a very simple driver using Wire. Another uses an InputStream to read from the such driver.

The first:
Uses 5692 bytes

The second one:
Uses 6114 bytes

The overhead was 422 bytes.

 Of course, Arduino has only a few bytes of program memory. But my point is: In some projects, it's important to have some "contracts" about what kind of streams we are using.

For ex, I was creating a font format to write in a GLCD module; the "writer" (a driver to print chars on GLCD) needs to read the font bytes from somewhere and use it to print the char to the GLCD module. But the font bytes could be anywhere, like eeprom, external eeprom, memory, etc; so how can the "writer", generically, read it without care the source of the stream?

The IO library solved my problem, I just wrote different input streams, one for each source. And the driver must only know that it will read from a InputStream.

I spent some extra bytes but I won a lot in generality.

Sorry about my English, I'm learning... smiley-wink 

14  Development / Other Software Development / How about to create an IO API (library) for Arduino?! on: September 16, 2012, 07:41:27 pm
So I've been working on a project to create an IO API for Arduino. Something like the Java IO.

I was creating some libraries that deal with a sort of streams, like serial, eeprom and so on. And I felt that there is no library to deal with streams in general.

So I created one!

It's called ArduinoIO. I created a site with the documentation and the link to the github source code.

My wish is just share with you my library. Please feel free to comment, help, complain or just use!

The site is: Please take a look on it.

Pages: [1]