For instance in my never ending multirotor project where I wrote a FC from the ground up (I'm so close to being done. This allows you to use an oscilloscope / logic analyzer as a cludge to look at the timing of your program.

And then when you send the data out send it byte at a time using Serial.writeĪlso, if you use macros to toggle pins you can change them in about two clock cycles. One of the longest delays from serial.print is the conversion from a number to ascii. If you want to have a consistent and easy to design around time budget for the serial delays send the raw binary for the values you are interested in out instead of ascii. You can send data via serial with the Arduino IDE as well, but you need to. The answers posted so far miss an important part about Serial.print. The Serial.printlnf prints a formatted string to the debugging USB serial. It will slow your program down, especially if you have to output a lot of data. Switching to a higher baudrate (115200), I get 0.200 milliseconds in the beginning (higher? Weird!) and 0.768 milliseconds when I'm around 88 seconds (at 9600 baud taking 9.3 milliseconds to output).īottom line: Serial.print() is blocking, which means program execution will wait for it to finish. By the second bunch, it's taking 9.3 milliseconds to output each string. In the beginning, it's taking 0.19 milliseconds to output each string. When the program first starts up, it's outputting this: 212Īfter a while, it's outputting this: 8008180 Serial.print() does take a significant amount of time, but it varies depending on how fast your baud rate is, and how much data you're ouputting. Assuming you're using something like an Arduino Uno (And not something like a Due), the Arduino will happily spew Serial data into space without anything connected.

Fast serial print arduino