Comments on: Arduino-serial: C code to talk to Arduino http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/ Random experiments, circuits, code, rapid prototyping, sometimes things to buy, and the odd tune by Tod E. Kurt. Sun, 14 Mar 2010 04:13:46 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: joshua wojnas http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/comment-page-6/#comment-59665 joshua wojnas Tue, 16 Feb 2010 21:07:26 +0000 http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/#comment-59665 FTDI & teensy++ are both much faster than the arduino usb interfaces the teensy site shows in its usb serial exaple a high speed serial interface that the virtual com port goes as fast as it can in the benchmark example. Has anyone documented virtual serial port speed? FTDI & teensy++ are both much faster than the arduino usb interfaces the teensy site shows in its usb serial exaple a high speed serial interface that the virtual com port goes as fast as it can in the benchmark example. Has anyone documented virtual serial port speed?

]]> By: FRANX http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/comment-page-6/#comment-59088 FRANX Thu, 11 Feb 2010 19:13:33 +0000 http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/#comment-59088 high duty of CPU is due to the reason that this program never close serial previously opened high duty of CPU is due to the reason that this program never close serial previously opened

]]> By: jack http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/comment-page-6/#comment-59085 jack Thu, 11 Feb 2010 18:33:54 +0000 http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/#comment-59085 any way to set DTR to off (in order to avoid arduino autoreset? any way to set DTR to off (in order to avoid arduino autoreset?

]]> By: Linux Ubuntu…serial things « FABLAB adventures http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/comment-page-6/#comment-58873 Linux Ubuntu…serial things « FABLAB adventures Tue, 02 Feb 2010 19:30:23 +0000 http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/#comment-58873 [...] http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/ [...] [...] http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/ [...]

]]> By: stealthcopter.com » Python: interfacing with an arduino http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/comment-page-6/#comment-58820 stealthcopter.com » Python: interfacing with an arduino Mon, 18 Jan 2010 21:08:57 +0000 http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/#comment-58820 [...] original arduino-serial.c – by Tod E. Kurt. [...] [...] original arduino-serial.c – by Tod E. Kurt. [...]

]]> By: Spiros Gezerlis (sgez) 's status on Thursday, 15-Oct-09 09:36:53 UTC - Identi.ca http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/comment-page-6/#comment-56885 Spiros Gezerlis (sgez) 's status on Thursday, 15-Oct-09 09:36:53 UTC - Identi.ca Thu, 15 Oct 2009 09:36:59 +0000 http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/#comment-56885 [...] Arduino-serial: C code to talk to Arduino -- http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/ [...] [...] Arduino-serial: C code to talk to Arduino — http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/ [...]

]]> By: todbot http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/comment-page-6/#comment-53002 todbot Tue, 23 Jun 2009 18:54:42 +0000 http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/#comment-53002 Hi Tyler, Try putting the delay before the send. You need to wait for the Arduino to start up before sending it data. Like this: <code> arduino-serial -b 9600 -p /dev/ttyUSB0 -d 5000 -s ra -r </code> I increased the delay in case you have an older Arduino. If that doesn't work, then I'd need to know what the sketch is like you're running on the Arduino before being able to help more. For instance, depending on how your sketch is set up, you might need to add a delay between sending and receiving because your PC is often faster with serial than the Arduino: <code> arduino-serial -b 9600 -p /dev/ttyUSB0 -d 5000 -s ra -d 200 -r </code> That inserts a 200msec delay between sending and receiving. Hi Tyler,
Try putting the delay before the send. You need to wait for the Arduino to start up before sending it data. Like this:

arduino-serial -b 9600 -p /dev/ttyUSB0 -d 5000 -s ra -r

I increased the delay in case you have an older Arduino.

If that doesn’t work, then I’d need to know what the sketch is like you’re running on the Arduino before being able to help more. For instance, depending on how your sketch is set up, you might need to add a delay between sending and receiving because your PC is often faster with serial than the Arduino:

arduino-serial -b 9600 -p /dev/ttyUSB0 -d 5000 -s ra -d 200 -r

That inserts a 200msec delay between sending and receiving.

]]> By: Tyler http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/comment-page-6/#comment-53001 Tyler Tue, 23 Jun 2009 15:50:53 +0000 http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/#comment-53001 Hi todbot, I'm using your code and everything seems to work fine except when reading back a response. It seems to only echo back the input as a response. I type- $arduino-serial -b 9600 -p /dev/ttyUSB0 -s ra -d 2000 -r where ra should read back a pin value and does through serial monitor and cutecom. I've tried the delay in various places and no delay at all. Any idea why it would only echo back the input? Hi todbot,
I’m using your code and everything seems to work fine except when reading back a response. It seems to only echo back the input as a response.
I type-
$arduino-serial -b 9600 -p /dev/ttyUSB0 -s ra -d 2000 -r
where ra should read back a pin value and does through serial monitor and cutecom. I’ve tried the delay in various places and no delay at all. Any idea why it would only echo back the input?

]]> By: Jack http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/comment-page-5/#comment-51450 Jack Mon, 18 May 2009 13:46:58 +0000 http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/#comment-51450 Hi todbot, Thx for your answer : put a 5000 ms delay is the solution ! ++ Jack Hi todbot,
Thx for your answer : put a 5000 ms delay is the solution !
++

Jack

]]> By: todbot http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/comment-page-5/#comment-51430 todbot Tue, 12 May 2009 00:59:30 +0000 http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/#comment-51430 Logger? I'm not sure to what you're referring. The "arduino-serial" program isn't a data logger. It's not really designed to be run for long durations, just to quickly get a chunk of data from an Arduino and exit. However, "arduino-serial" does emit its output on stdout, so it's output can be redirected to a file as you have done. What is this "logger" program you're running? It's very clearly not arduino-serial. Logger? I’m not sure to what you’re referring. The “arduino-serial” program isn’t a data logger. It’s not really designed to be run for long durations, just to quickly get a chunk of data from an Arduino and exit.

However, “arduino-serial” does emit its output on stdout, so it’s output can be redirected to a file as you have done.

What is this “logger” program you’re running? It’s very clearly not arduino-serial.

]]> By: josh w http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/comment-page-5/#comment-51429 josh w Tue, 12 May 2009 00:50:46 +0000 http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/#comment-51429 the serial logger you have does not output to a text file using >>. I have this in my command line logger is the binary output. ./logger>> test.csv is their any way I can make that work? I am using ubuntu. Will I have to write more c to open a real file or create one and fprintf to it? I have tried your program also it does not print help to the text file ether. the serial logger you have does not output to a text file using >>.
I have this in my command line logger is the binary output. ./logger>> test.csv is their any way I can make that work? I am using ubuntu.
Will I have to write more c to open a real file or create one and fprintf to it?

I have tried your program also it does not print help to the text file ether.

]]> By: josh w http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/comment-page-5/#comment-51409 josh w Fri, 08 May 2009 04:01:01 +0000 http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/#comment-51409 I have just gotten two arduino's not two pc's so maby i can make them talk at eatchother. ... I have just gotten two arduino’s not two pc’s so maby i can make them talk at eatchother. …

]]> By: josh w http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/comment-page-5/#comment-51408 josh w Fri, 08 May 2009 03:59:59 +0000 http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/#comment-51408 I think their is a relationship with the arduino program being on using that com port. Also I still have the 1 second light on 1 second light off delay. So I think as that decreses the buffer or lack of buffer in my c program causes problems. I herd somewhere the arduino has a print f buffer in its c code. If that fills up maby that is the problem. I think their is a relationship with the arduino program being on using that com port.
Also I still have the 1 second light on 1 second light off delay. So I think as that decreses the buffer or lack of buffer in my c program causes problems. I herd somewhere the arduino has a print f buffer in its c code. If that fills up maby that is the problem.

]]> By: todbot http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/comment-page-5/#comment-51407 todbot Fri, 08 May 2009 03:19:07 +0000 http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/#comment-51407 What do you mean by this exactly? Do you mean causes the /dev/ttyUSB0 device to disappear from the "/dev/" directory? Or do you mean the device is still present, but it cannot be opened? Or do you mean the serial port on the Arduino becomes unavailable to the running sketch? I have a feeling you are running into buffering issues of either the FTDI chip on the Arduino or the Linux device driver. Normally when you're transmitting so much data at such a high speed, you use the hardware flow control lines so you can pace your transmitting so as not to overflow any buffers. I don't think the Arduino Serial class gives you access to those lines (or even runs them to the Arduino MCU) One way to test if this is an Arduino or PC problem is to have two PCs or two Arduinos, and connect them together, sending data from one and receivin on the other. What do you mean by this exactly?
Do you mean causes the /dev/ttyUSB0 device to disappear from the “/dev/” directory?
Or do you mean the device is still present, but it cannot be opened?
Or do you mean the serial port on the Arduino becomes unavailable to the running sketch?

I have a feeling you are running into buffering issues of either the FTDI chip on the Arduino or the Linux device driver.

Normally when you’re transmitting so much data at such a high speed, you use the hardware flow control lines so you can pace your transmitting so as not to overflow any buffers. I don’t think the Arduino Serial class gives you access to those lines (or even runs them to the Arduino MCU)

One way to test if this is an Arduino or PC problem is to have two PCs or two Arduinos, and connect them together, sending data from one and receivin on the other.

]]> By: josh w http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/comment-page-5/#comment-51406 josh w Fri, 08 May 2009 03:00:57 +0000 http://todbot.com/blog/2006/12/06/arduino-serial-c-code-to-talk-to-arduino/#comment-51406 things seem to run right 1 time then the port disappears could it not be closing? void loop () { Serial.println(i++); delayMicroseconds(1137); if (i > 99){i=0;} } this runs in arduino ide but the c code causes the port to disapear after 1 run. things seem to run right 1 time then the port disappears could it not be closing?

void loop () {
Serial.println(i++);

delayMicroseconds(1137);
if (i > 99){i=0;}
}

this runs in arduino ide but the c code causes the port to disapear after 1 run.

]]>