#224

[@RalphBacon]

As I decided to have an argument with a very sharp craft knife, my typing has slowed down considerably. It may take longer to respond to your comments. Sigh. github.com/RalphBacon/224-Superior-Serial.print-statements/blob/main/Thumb%20Argument%20With%20Craft%20Knife.jpg

[@flemmingchristiansen2462]

It would seem that you lost that argument. 🤦‍♂️

[@gg-gn3re]

hey at least you can't miss the space bar anymore

[@RalphBacon]

Yeah, space bar, b, m, n, comma all in one go!

[@bbowling4979]

Ouch! Sorry to hear that. Hopefully it wasn't too bad and didn't hit anything important.

[@RalphBacon]

My thumb _is_ important. Well, to me. And my soldering iron.

[@torquebiker9959]

STOP using "STOP this and that" clickbaits!!!

[@RalphBacon]

So WHY is this click bait? EXPLAIN!

[@joelincz8314]

Sadly KZbin requires every title to have a little bit of clickbait into it or your video won't be recommended to people. When I saw the title I was intrigued but never did I think I could never ever use Serial.print. It was on topic. So clickbait percentage was low, usefulness high for a lot of people. @RalpBacon: Thank you for the title or I would have never seen this. And thank you for the video. My 13 teen your old daughter loved it as well (we are learning about the Arduino environment together).

[@SeaTurtle1122]

It’s entirely truthful, and it makes more people click on the video completely for free. Why on earth would he stop?

[@BeardyMike]

​@@RalphBacon 100% it's a clickbait video title.... But as a newbie programmer this kind of information is incredibly useful, and I wouldn't have found it without your clickbait. I think this video is a great use case for clickbait. Experienced Devs will know what you're going to do within a minute or two, and everyone else can stay for the explanation and demos.

[@DaveBuildsThings]

@@BeardyMikeI totally agree. Took the bait and enjoyed every bite. I've never seen #define used in Serial.print statements before and found this video extremely useful and informative. Just as a side note, you can also use #define debugbegin(x) Serial.begin(x) to remove the serial begin statement as well. Initializing serial takes up memory as well. Thanks for the great video! 👍👍👍

[@abdoolsattarcassim6717]

I am a mech engineering student and I am doing a 99% electrical project for my research dissertation. I spent weeks trying to figure out why my sketch has been printing data every 0,033 seconds (30 Hz) instead of 1kHz+ as it should with timer interrupt. Now I know why........ I really appreciate the video Mr. Bacon. Highly informative and needed!

[@RalphBacon]

Glad it helped you!

[@bknesheim]

This was very long winded about a standard programming method.

[@RalphBacon]

It's not "standard" if you've never done it before, is it?

[@bknesheim]

@@RalphBacon Even if you have never used a metric unit to measure something, it is still a standard. The same can be applied for programming techniques in C, C++ or other languages.

[@Invatator]

I wonder what "standard programming" you are referring to. IoT is a different beast and an entirely different ecosystem for the hobbyist. Not everybody knows this...like Ralph said...its not standard if they don't know about it or never read it, experienced it, and no tutorial or documentation I've read the past 3years mentions it. 😉 That being said, try and be considerate of hobbyists. Thank you

[@bknesheim]

@@Invatator The information is important because the use of #ifdef in C and C++ do make it a lot easier to remove/include debug code. It was the time to get there i criticized because I think that many that could have need for this will fall of and watch something else before he gets to the point. Close to 30 minutes is long bit long. "and no tutorial or documentation". It is "funny" how often that can be a problem since the programmer that write it can so easily forget that even very basic techniques most be learned and #ifdef is something you learn early. It is not perfect and have problems, but it is a simple and easy way to control your debug code.

[@Invatator]

@@bknesheim that's what I mean, ...I don't think I have "proper basic" introduction to C or C++, and used it last time before Arduino like 10-15 years ago, and Arduino feels a bit different. Ifdef define and other "optimizations" don't seem properly introduced to Arduino hobbyists...just "how to get fast through the door". Anyhow...are those concepts you talked about in the C/C++ basics? I can dig out old books if any...as I'm really interested in making my microcontrollers performant and improve myself

[@WatchesTrainsAndRockets]

A word of warning: If you define a symbol to be an expression, put parentheses around the expression to make sure that they evaluate the way that you wish. Example: #define ratio( x, y ) x / y if you use ratio in the following, you will not get what you intended float a = 5.0; float b = 10.0; float c = ratio( a, b ) ** 2; The expected result would be 0.25 (= 0.5 **2 ). UNFORTUNATELY, the compiler was presented with x / y ** 2 The operator precedence of C/C++ will perform the exponentiation first and the the division. This means that c will be 0.05 ( 5 / 100 ) If instead, you change the define to be #define ratio( x, y ) ( x / y ) then the expression seen by the compiler is ( a / b ) ** 2 which is what you wanted.

[@RalphBacon]

A very good point you make, Michael; many libraries will contain all the #defines in "(" and ")" just to be sure (and UPPERCASE).

[@billferner6741]

Interesting topic! But, imho you shouldn't blame the Serial.print statements for slowing down your program when you are not doing the house keeping after debugging by removing those print commands.

[@RalphBacon]

Well, yes, it's always the responsibility of the developer to "tidy up" after coding is finished; I'm hoping this will make it so simple that they will do it. And learn something about pre-processing whilst they're at it!

[@makers_lab]

Yes, however it can also be beneficial to have certain debug / trace logic kept in place so it's ready to be used when adding future enhancements, and testing at release level performance can be necessary while still developing and needing debug code. So for both scenarios, a way to knock out debug code while it's still present in the source is useful.

[@forbiddenera]

Uh but what if your code is timing sensitive? Doesn't necessarily matter about cleaning up after. Also, sometimes serial is used for communication and often s.p is used for that too

[@billferner6741]

@@forbiddenera the topic was serl.print for debugging, not project messages. Those time need to be considered in a project.

[@haroldfinz4863]

Deleting debugging statements after debugging is like throwing away the sponge after the dishes are washed. Complex programs are rarely, if ever, completed and bug-free. And most programs are susceptible to changes in their environment -- e.g., libraries, or 3rd-party connectivity policy changes. It's helpful to build in a way of retracing your steps without having to "re-do from start"

[@edwardowen8668]

Genius idea! I'm pretty picky about my code but every once in a while I forget to take out one of these statements. This is a far better idea. I can even use multiple debug variables to turn different sections on and off as needed. Thank you, sir and my you have a great and prosperous day.

[@RalphBacon]

Glad it was helpful!

[@PaddingtonbearNZ]

I have to say that this "simple" method of deactivating debug statements has to be a winner for all the reasons you highlighted. I will be using it big time. thank you for such a bright shining light on a very simple way round the problem. Even simpler than having all the debug Serial.print statements inside IF debug on THEN.

[@thorbjrnhellehaven5766]

one reason for IF debug on THEN, would be to be possible to enable/disable by input. you would save time, but not size.

[@joselepage7572]

0

[@RalphBacon]

Indeed, I dislike wrapping all my Serial.print statements inside #if...#else...#endif as it destroys the layout of my code. I find this a neater solution!

[@thorbjrnhellehaven5766]

@@RalphBacon the precompiler approach is realy nice to save size, where size is not an issue, comiled if-statements can be nice to enable/disable debuging on the fly, for troubleshooting without recompiling and loading new binary.

[@Conservator.]

Hi Ralph, Just want to say that I enjoy watching your videos. The content is interesting and your presentation style is entertaining. Thank you!

[@RalphBacon]

Thank you very much! Glad you're enjoying them.

[@danielungureanu430]

The initial statement was that Serial.print slows down the microprocessor (and it does) and that's why you will propose a better solution. In fact, the solution doesn't offer an alternative. I just shows a way to enable/disable all the Serial.print lines :( Not quite a solution!

[@therfnoob7697]

yeah, no real solution and too much ads at the beginning...

[@RalphBacon]

I believe it shows a _better_ (and more efficient way) of tailoring your Serial output.

[@gutrali]

​@@RalphBacon How would one use the optional second parameter which specifies the base (format) to use; i.e. Serial.print(0x61, HEX); ?

[@Jeff-kf7om]

Thanks for this great tip! I have a couple of further suggestions: 1. Use all caps when you define a macro so you can tell the difference between a function call and a macro because macros are expanded before compile, and sometimes this is important to know. 2. Surround your macro definition with '"{" and "}" so that multi-statement macros will be guaranteed to behave even if you don't know they're macros. As example, a multi-statement debug macro will compile fine and yet misbehave in code that looks like this: for(i = 0; i < 100; i++) debug("foo");

[@RalphBacon]

Good suggestions, Jeff, thanks for sharing. 👍

[@MakerMike-bx5ms]

I consider myself a beginner and i have never considered this before. I was wondering how there can be almost 30 minutes of video on this topic. But im so glad i took the time to watch it. It was very eye opening to me and informative!

[@RalphBacon]

Glad it was helpful!

[@MakerMike-bx5ms]

@@RalphBacon most definitely! Thanks so much for taking the time to put together this video!!! Merry Christmas!

[@Conservator.]

#Define calls the pre-compiler and does a ‘find & replace’ before compiling the code. As a computer science student, a loooong time ago (1985), I had to write a C pre-compiler as an assignment. It wasn’t very difficult but I’ll never forget the use of pre-compilers.

[@RalphBacon]

Quite so. The modern IDE (not Arduino classic) does have some intelligence regarding precompiler directives which makes it even more useful.

[@tcarney57]

Removing Serial.print() statements from your code is as simple as a Ctrl-F to find them to delete them. Doing so is the same as cleaning up after any job; doing the dishes, putting away tools, or using toilet paper. Cleaning up (or "linting") software code is what any good programmer does. It involves deleting commented-out lines, unnecessary blank lines, excessive comments, etc. Though your #define debug(x) and its associated conditional compiler directive will keep those lines from being compiled in the final version, the debug(x) lines will still be littering the code, impairing long-term readability (even for you after time passes), and adding lines (and associated scrolling) that have no value in the future. Let me just add that there's a click-baitiness to the video title: STOP using something everybody uses. It's a tactic similar to videos that say, "You're Doing {something} Wrong." The current video has been cluttering up my feed for a long time, and I've been ignoring it because it looked like click bait. But I finally thought, "Fine, I'll just see what he says." And I was right: click bait and nothing I think is very useful. You don't even actually advocate stopping the use of Serial.print() debugging. You just show a way of globally deactivating it when it's served its purpose. I understand, of course, that you got credit for my view anyway, and the algorithm is giving you credit for my "viewer interaction." You got what you want, and by complaining about it now so have I. You win, I win.

[@RalphBacon]

Not at all. Removing the Serial.print statement removes a level of documentation from your code that you might well need when (if?) it goes wrong. You put it there originally for a reason, right? Using the method described here keeps it in place but removes it, conditionally, from the compile process, thus putting away the dishes after washing up. 🤣 But allowing you to instantly (well, after a recompile) to reinstate them. After a few decades as a pro developer I've valued decent comments and print statement in code (not just mine). By the way, this was not click bait of any kind. I thought it described my video perfectly as I believe we should indeed STOP using standard Serial.print statements (in the ESP32 world I never use them, using the built-in conditional debugging levels instead). You didn't find it useful, fine. But don't tell me that I'm into sucking you in to watching a video you don't find value in. That's what the STOP 😁 or BACK button is for.

[@MattRiddell]

@@RalphBacon 🤣 100% agree. You even covered it in your video. "Crap, it's broken again - let me put them back in for a sec". This is real world programming. It's not the same as academic programming. Sometimes you have 1 day for a turnaround POC. DRY isn't the best way to do things. Obviously he's right once you move into a final production product that will never change again, but how often does that happen? We're always iterating

[@davidhawley1132]

You should rationalize your debugging code and only leave in what is likely to help in the future (because now you know what helped), review what remains to make sure it has no side-effects that would break your code if it was removed, and then use C# preprocessor directives to control whether you include the debugging code in your executable. A more sophisticated version of the above is to define a set of debugging levels, again which you control by preprocessor directives. Finally, if it is possible in your environment and seems warranted, add some kind of logging, using the same levels strategy as for debugging.

[@natanlisowski]

Yes you can't use printf but you can use sprintf() and it works great just create buffer and provide this string for example to Serial.print()

[@RalphBacon]

I must admit a dislike to creating a buffer of unknown length to receive a message that we then output. I think printf works better and the ESP32 has it built in and now the Arduino can have it for very little cost (code size-wise, I mean).

[@TanjoGalbi]

What is amazing to me is that it has taken you all this time to figure this out. ALWAYS remove debugging code from release versions. I use a #define and #if statements to turn on/off serial.print and other debugging code.

[@RalphBacon]

Absolutely, I couldn't agree more.

[@prlombaard]

Thanks @Ralph for this video. It's one of many differences between a beginner person and more advanced /experienced person. Pre processor directives is amazing.

[@RalphBacon]

Glad it was helpful!

[@JewCheese]

Thank you so much Ralph, not just for this video but your channel in general. You've taught me so much, and you have a very pleasant way of teaching things. Keep up the good work :)

[@RalphBacon]

I appreciate that! Sharing is caring, as they say!

[@nathanvandevyver]

In my personal library I made a header that replaces serial.print with spr or sprl, and I can enter up to 4 different parameters. It's compact, very easy to type, and much more clear to read. Also, with one line of code or even an input wire, I can disable all serial prints at once to speed up the program

[@RalphBacon]

Sounds like you've done a similar thing then, Nathan. I think most coders eventually devise some method of doing this, thanks for sharing.

[@robertmurton7373]

hello Ralph A few weeks ago I just learnt what #if meant and now thank to you I have an application for it, thank you Ralph.

[@RalphBacon]

I knew you were learning this, Robert (obviously) and thought you might benefit. Glad it was helpful!

[@MrJozza65]

Thanks for the information; a useful reference. I have got into the habit of using a DEBUG definition and then wrapping each of my debugging Serial.Print commands in an #if....#endif block, but this way you showed is a much more elegant method that I hadn't thought of before. I am by no means a beginner, but never ignore information like this aimed at beginners, as sometimes I find I've been set in my ways and they aren't necessarily the best!

[@billglass5160]

I was ready to say exactly the same. This method avoids my adding all those #ifdef's. I always start my programs saying I'll only need 1 print so I don't bother with the #define debug. Finally I end up with many more prints and many more #ifdef's.

[@RalphBacon]

I'm sure everyone experiences the same as you, Bill! Me included. I mean, the next sketch will be so simple what could possibly go wrong? Oh.

[@billglass5160]

@@RalphBacone

[@billglass5160]

yes!!!

[@janikarkkainen3904]

My thoughts exactly. While watching the start all I kept thinking was "well, just conditional compile them by wrapping them it #ifdef DEBUG's", but it never occured to me I could alias/macro it all in/out that way. And I mean, I'm not really a beginner either, and I've used both conditional compiling with #ifdef's and macros, but it just never occured to me I could shorthand all of this this way. This is one more confirmation to the idea that it's never wrong to re-review basics even if you are "an expert" - there's always a possibility you've missed or forgotten something useful.

[@JohnAldred]

I had no idea you could #define a function in this way. That's amazing. I was using a bunch of if statements around the serial stuff, but this is much better!

[@RalphBacon]

That's what drove me to doing this, John. I was sick of all the #if...#else...#endif statements everywhere, destroying the layout of my beautiful (ahem!) code.

[@JohnDlugosz]

That's a good indication for reading through "The C Programming Language" or other reference material once a year or so, to remind you of things you may have forgotten or overlooked before.

[@WatchesTrainsAndRockets]

@@JohnDlugosz There is a book by Henry F. Ledgard called Programming Proverbs (short title). It was one of our textbooks in school. It contains a lot of good advice. One of the best pieces is Re-read the Manual. The point is that a lot of what you encountered on previous readings may not have been well absorbed because it had no good relevance or contextual framework within your needs and experiences. As you progress, you encounter new situations which make the relevant and re-reading the manual will allow you to now see how things previously glossed over are now of use.

[@i8BBQ4Lunch]

@@JohnDlugosz I remember that4 book. Now retired, during my career I used C occasionally and every time it kicked my but. POINTERS!!! What are they pointing to, addresses, variables, names of variables! Pull my hair out. ;-(

[@mfx1]

I remember when having a single LED for debugging was a luxury :-)

[@RalphBacon]

Hang on, Martin, you can't possible mean a single LED _just for your own use_ can you? Without sharing with the guy in the next cubicle? Luxury!

[@mfx1]

@@RalphBacon One LED for the whole department, you had to sign for it.

[@oladunk9986]

Yes, the first ones were quite expensive. In 1973 or 74 a red LED cost about US$50 in Norway. At the same time a 7400 quad nand gate chip cost US$ 1.

[@HelloNotMe9999]

4 years of college and nobody ever mentioned this. Not one single professor. I want a refund.

[@RalphBacon]

Ha, ha! But at least you learnt lots of other stuff; this is just the stuff you never get taught at college but find out "on the job". Maybe your professor watched this video and will now be teaching it. I want royalties!

[@ellisgl]

All the people I have worked with that have CS degrees have said the same thing. Apparently most of the the get taught in CS related classes are things you won't use on the job.

[@LakshmikanthAyyadevara]

#if DEBUG_FLAG == 1 #define debug(x) Serial.print(x) #define debugln(x) Serial.println(x) #else #define debug(x) #define debugln(x) #endif This code snippet adds a great value for this video thank you very much , can make your mic little clear so audio is perfectly audible

[@RalphBacon]

Thanks for sharing 👍

[@5Komma5]

Click bait. Stop using Serial.print but still uses it as a #define. You are still using Serial.print and makin it more complicated then it needs to be.

[@RalphBacon]

Thanks for the feedback.

[@CTCTraining1]

Valuable reminder of good practice but worth stressing that any testing needs to be completed on the debug-stripped version of the code ... can’t count the number of times I’ve been chasing bugs generated by accidentally non-included or over-defined values not apparent until the effects of the def changes played out. Keep up the great work 😀👍

[@RalphBacon]

Sorry, Chris, what is this word "testing"? I've looked up the definition in the Arduino Coder's Bible and it states: "Testing, v, The iterative act of releasing code into the Real World and seeing what happens, mostly using the happy path". Sounds about right.

[@iforce2d]

To avoid unused variable or parameter warnings, try this for the no-debugging case: #define debug(x) (void)(x) #define debugln(x) (void)(x)

[@RalphBacon]

Yes, that good to suppress the warnings. Or, _include_ the extra parameters as I do now. Here's an example of the 'Error' level warnings: #if DEBUGLEVEL > 0 #define debugE(x, ...) \ Serial.print(x, ##__VA_ARGS__); #define debuglnE(x, ...) \ Serial.println(x, ##__VA_ARGS__); #else #define debugE(__VA_ARGS__) // Nothing to see here #define debuglnE(__VA_ARGS__) // Or here #endif So now, debuglnE(aNumberGoesHere, HEX); will work.

[@DarylVanHumbeck]

When I first saw this video being suggested to me, I thought this was an advisement against using Serial.print commands for passing information between microcontrollers and computers, so this was a bit of a surprise. On the other hand, I guess this is down to personal code style preferences, as I'd much, /much/ rather NOT use custom-defined preprocessor "functions", as that severely limits what you can pass into them. Given the fact that I've been using C and C++ for years, along with the preprocessor's very powerful replacement system, I'd rather use "#ifdef DEBUG" blocks around the code specifically handling debugging. Plus, this practice highlights your debugging code more strongly than yet another apparent function call that doesn't get coloured as such by the syntax highlighting.

[@RalphBacon]

It's a case of horses for courses, Daryl. Use whatever works for you. I personally hate the #if...#else...#endif construct for debugging statements, but if you don't mind the strange formatting this brings it's not a big deal. I just thought I'd share something I use myself. I think it's useful for hobbyists and beginners rather than professional C++ programmers, but that's just my take on things!

[@vasiliynkudryavtsev]

Nowadays, good compilers will eliminate dead code. Thus, I usually use simple VERBOSE adjective before the Serial.print/printf or blocks doing debug prints, which I defined before as "#define VERBOSE if(0)" or "if (1)". For the different levels of verbosity (e.g. -v -vv -vvv flags) can be done by "#define VERBOSE2 if(verbose_level >= 2)", etc. #ifdef #if look quite ugly, but I also use them in some cases, it's good alternative to have commented out section of old/different code.

[@alexstone691]

@@vasiliynkudryavtsev i love that, im gonna use that from now on for debugging

[@vasiliynkudryavtsev]

@@alexstone691 I'm glad, my experience helps.

[@NicksStuff]

You can do a proper inline debugging with a JTAG programmer on the ESP32

[@RalphBacon]

Yes you can, and I covered this in video #261. Works well enough.

[@NicksStuff]

@@RalphBaconGreat

[@sej7278]

But you left in Serial.begin(); so you've missed the chance to remove a whole library

[@RalphBacon]

Well, yes, I did, but this could also be removed if it is a problem. We can even switch off the UART completely if required: #include power_usart0_disable(); For battery powered projects it might be advantageous.

[@McTroyd]

Compilers are tricky these days. Since that's the only statement left, and the library's not otherwise used, I wouldn't be surprised if it was optimized out of the compiled code. Would certainly warrant some experimentation.

[@RPBCACUEAIIBH]

You can also speed up those Serial.print statements, by simply setting the baud rate to 2000000 instead of 9600 for ATMEGAs, or 115200 for ESP8266.

[@RalphBacon]

I've never used higher than 115200; I will see if my IDE allows me to select a higher speed and see whether I get corruption on long(er) USB leads.

[@GermanMythbuster]

#define DEBUG 0 #if DEBUG == 1 #define DebugBegin(x) Serial.begin(x) #define Debug(x) Serial.print(x) #define Debugln(x) Serial.println(x) #else #define DebugBegin(x) #define Debug(x) #define Debugln(x) #endif

[@RalphBacon]

If it works for you then it works! I haven't tested this but I might give it a try in my next sketch!

[@GermanMythbuster]

@@RalphBacon Yes it works very well

[@simontillson482]

Making a DebugIf(condition, x) is good too. This allows you to have other debug symbols, such as DEBUG_SERIAL, DEBUG_PWM etc. Having DEBUG=0 to switch all debug printing off is useful for a production build, but having all of the prints running when DEBUG=1 can be very tiresome to read, and obviously makes your code very much slower. This more fine-grained approach allows you to just show the debug prints that are relevant to the part you’re working on / testing.

[@StateMachineCOM]

A slightly better, more correct way of defining your debug() macros to do nothing is #define debug(x) ((void)0) instead of really nothing. Please remember that these macros in the actual code are followed by semicolons. So now when they expand to nothing, you have lonely semicolons left in your code. This might sometimes lead to compilation errors and even logic errors. The macros expanding to ((void)0) avoid the empty semicolon problem.

[@RalphBacon]

Hmm, you may be right but empty semicolons are not a syntax error: while (1) { ; } is perfectly legal (and what my IDE insists on converting an empty while(1); to!

[@StateMachineCOM]

@@RalphBacon One example where the empty debug() macro will cause a compilation error is: a ? foo() : debug(...); This will become a ? foo() : ; and that won't compile. I understand that this is a contrived example, but you'd be surprised how "creative" people might be in using your stuff. (For example, people might create their own macros based on yours, which might use something like that.) My point is that it does not cost you anything to define debug() as ((void)0), which will prevent all (or at least most) such corner cases. I like your presentation. I just wanted to help...

[@RalphBacon]

Yes, your suggestion is a good one, and the, er, ingenuity 🤔 of developers cannot be underestimated 😜. So, to prevent potential problems your suggestion is good and I hope others read this comment thread in case they are having some weird compilation errors when using my alternate use of debug.

[@GkTheodore]

@@StateMachineCOM Thanks for pointing out a question I had. I tried your suggestion though and it does not compile. Just leaving the thing empty it does. Mind you, I am using Wokwi's emulator and not the real thing. Nevertheless I would like to thank ALL the people who make helpful videos like Ralph and those who make constructive comments and suggestions like Quantum.

[@infrapale]

Very good message. I have been working with a Nordic chip and initially I was inserting debug messages. Later when I starting the power reduction phase I realized that activating the UART port increased the power consumption more than 10X. Still at some point you really need the serial printing but when moving to running on battery I disable the UART totally. I have not tested on a Arduino if the Serial.begin() is impacting on the power consumption.

[@RalphBacon]

Good info, Tom. And we can disable the UART in the Arduino world by using: #include power_usart0_disable(); which could possibly be part of some precompiler construct too (not done it, but it should work).

[@uki352]

As soon as it goes to some more than an AVR, I use "#define DEBUG(...) printf(__VA_ARGS__), but in more complex systems I prefer to work with tokens added it automatically so I can see the part of the software, the warning is coming from. But for that you have to write an va_args warpper that then connects two printf resulting in something like [ENC] Stream picked up [MOD] setupt tx frequenxy [LO] Frequency set [MOD] Gain set [RF] TX On [ENC] Stream started A bit like the ESP_LOG mechnaism but not that bloated in the output. And I also often have 2 Levels of debug. One that helps you to design the thing and one that stays on forever and gives you a clue in cases your thing doesn't work as expected. But other than that I prefer to work on STM32 and just use JTAG online debugging diretly into the thing, and keep printfs as rare as possible.

[@RalphBacon]

Yes, that sounds like a good method. I sometimes use a spare GPIO pin that only outputs the Debug message when it is is LOW. It doesn't help with program bloat but does keep things moving at speed when you don't need the serial output.

[@bwimtg]

great tip! just wondering what happens to the semicolon when the debug statements are replaced with nothingness. i assume it stays, but empty lines are not compiled into the final program. or would it be useful to include the semicolon in the define statement?

[@RalphBacon]

Extra semicolons get ignored; you can include them as part of the define but that might upset the syntax on the rest of the line that you're using the define. Best to keep it as part of the code, the compiler will remove it anyway.

[@bwimtg]

@@RalphBacon great, thank you for the clarification!

[@u2bist]

Normally I love your videos but I have stopped watching anything entitled, "STOP doing !" So please stop doing that.

[@RalphBacon]

The irony of you stopping watching videos that tell you to stop doing something is not lost on me! Anyway, you missed a good video, and have perpetuated the use of Serial.print in your sketches. Deffo worth watching!

[@tragedyofwind]

another tip, we could have differently debug mode such as 2/3/4/5...etc, so we can preset a bunch of variable in Preprocessor , so we test our code with predetermined inputs as the alpha test. by combined using #define #ifdef to activate and deactivied piece of code.

[@RalphBacon]

I've got a more granular version in my GitHub that allows Errors, Warnings, General, Verbose settings. But another viewer has suggested different names for the debug variable so we can debug just one function, for example. It's something I'm thinking about.

[@planktonfun1]

I always comment serial.print after im done, compiling removes commented bytes and you can always go back to it whenever something goes wrong

[@RalphBacon]

You mean you can always uncomment out the lines again? But this is better than that, you have different levels of serial prints. But it your way works for you, and you're happy with it, keep using it!

[@codebeat4192]

Use capital letters for defines and constants. Video could be 5 minutes to explain such simple method.

[@RalphBacon]

Not really. Beginners need a detailed, step-by-step approach and an explanation of _why_ we do things - no sudden jumping to conclusions or they get lost and switch off. Yes, I use CAPS for constants but I'm not always a fan for #define names.

[@philiphillebrand2965]

👍👍👍👍👍 Thank you, thank you,, I had just come to the realisation of why my code and memory usage was changing and realised I needed to take out all the boating "print" statements. But now you have given me a way to manage debugging in a nice convenient way, so thank you for your video and your help. ...!! Very much appreciate learning how to write better code. ...!

[@RalphBacon]

You're welcome! Glad you are finding it useful, Philip.

[@jvernice]

Thank you for the very comprehensive tutorial. Excellent tutorial for beginner programmers, but it could be cut down to a 5 minute video for intermediate to experienced programs.

[@RalphBacon]

Glad it was helpful! And, yes, for those beyond beginner stage it doubtless could be done more succinctly but! This channel is about getting beginners' projects off the ground so more detail is required. Incidentally, if I watch a video that is going too slowly for me I just increase the playback speed to 1.25x or even 1.5x and it gets things moving along rather nicely!

[@jvernice]

@@RalphBacon I subscribed to your channel as you lend a very comfortable and comprehensive means of educating about Arduino. Thank you, again. Best regards

[@miguelraulgonzalez7744]

Brilliant!!!

[@RalphBacon]

Thanks for the feedback!

[@jacklewis100]

Blimey....15 minutes to get to the point...... Still it was actually quite a nice idea, eventually :-)

[@RalphBacon]

Just 15 minutes, Jack? I must remember to pad it out a bit more! But seriously, setting the scene for beginners is essential. Glad you (eventually) liked it though!

[@ficeto]

ESP32's log_x functions are defined inside the ESP32 Arduino core (esp32-hal-log.h and esp32-hal-uart.c). You do not need any additional library and maybe you should have mentioned that ArduinoIDE has a menu item to control that log level. Define is needed only for PIO

[@RalphBacon]

Good information, thanks for sharing!

[@rogerdeutsch5883]

Great solution and great explanation. Will use this in future. Subscribed

[@RalphBacon]

Awesome, thank you!

[@MobCat_]

#define DEBUG #ifdef DEBUG Serial.begin(9600); Serial.print(debug message); #endif if you comment out //#define DEBUG and then compile it, all your serial functions should be removed in the compiled bin, well as far as i understand it anyways. just using an if debug == 1 is not enough as your still doing that check. Also #ifdef is already part of the sdk and you wont need a lib for it.

[@thomasrichter3635]

I would also recommend such an approach👍I always define myself a function that wraps around the serial.print function. Inside of this wrapper function i will have the #if ... statement. With this you can keep your code a little cleaner, as you don't need precompiler statements in every print call, you just call the wrapper function☺️

[@RalphBacon]

Yes, removing the Serial.begin is very doable and ensures the entire library is removed by the linking process.

[@Divino_1]

You dragged a 3 minutes video way too long but it's a great concept for beginners.

[@RalphBacon]

I'm glad you said "it's a great concept for beginners". Imagine yourself being taught to drive a military tank. (I hope you don't have military service, especially in a tank 😲). Do you think 3 minutes of instruction is enough to even get you to move the tank forward (without destroying everything in its path)? Put yourself in the shoes of a noob who needs every single thing explained in a clear and concise way. At least once. Ideally more than once. That's why it's as long as it is. 😜

[@eglintonflats]

3 min video is too short for google to plant any adverts. Therefore, no money. Get it?

[@seditiousmonkeyart]

Hey there Ralph. Another great video; informative and entertaining. I'm going to add this to every sketch I develop from now on. It is just to simple and easy not to do.

[@RalphBacon]

Fantastic! I'm using it right now in my current sketch, Adrian, and it works very well! It can be tweaked as required too, or the Advanced version can be used (in my GitHub).

[@jstro-hobbytech]

Thank you so much. I never realized you can do that type of define outside of a header file or such. You need more of these videos haha. Add a member button to your screen too. I don't expect anything in return but you work hard and deserve for the community to pay you back if they want.

[@RalphBacon]

You're very welcome!

[@Stinktierchen]

I have been using FOR AGES bool debug = true; if (debug) { Serial.print("my text here or whatever") } and thats it... Okay thank you. And I am sure a lot of people are actually doing it this way. Why do I think its better? Because you can fast an easy create differen Serial debugs for different tasks. like add another one that shouldnt be run with another. bool debug2 = true; if (debug2) { Serial.print("my text here or whatever") } And so on.. makes it even better and faster

[@RalphBacon]

Having granularity with debugging is a good idea; if you look at the Advanced example in my GitHub you will see a variant of this, where I have Verbose, Debugging, Warnings & Errors selectable as debugging level too. But now I'm thinking that having some descriptive debugging names like you suggest - good idea, thanks for sharing!

[@jamess1787]

function debug(text){ if (debug){ serial.print(text); } } 😁 + Indentation //I wonder if there's a way to detect if the potential of the tx pin changes....... Could enable debug when something is plugged in.... 🤠

[@ttac2011]

Lots of blabla

[@RalphBacon]

Thank you for the feedback.

[@borayurt66]

I do add a lot of debugging Serial.print lines in my code and I've seen countless times that how they slow everything. What I do is to add a global boolean variable "debug" and start every Serial.print line with if(debug). That way if the value of debug is 0, then all the debugging lines just don't work. Also if I have an IO pin that I don't use I add a header to it in the final design that I can put a jumper and turn debug on, leave the jumper off and turn debug off. This way I don't have to recompile and re-upload the the code if I ever need to debug it after some time of use. Yes, I know that although this method prevents slowing down, it does not not help (and even makes it worse) with the bloating of the complied code. This is exactly why I just loved this approach, all I need is to combine this with my pin controlled debugging somehow. Thanks! Much appreciated info!

[@RalphBacon]

Yes, I've done similar with a spare GPIO pin controlling the output. But you cant use that method with precompiler directives, as the code will either contain the debugging lines or it won't!

[@KW-ei3pi]

Very nice Ralph. I've watched this a couple of times, and picked up things each time, as I'm new to this stuff. I really like the way you explain things. Effective and entertaining as well. Personal thought: When you change the code during the video, you use a Screen Transition. It sometimes causes me to get lost and I have to "find my place" again on the screen of code. I know you do this to save time and not show backspacing the code and rewriting it, but since you are explaining it anyway, I think I would rather follow along as you do so. Just my personal thoughts. Thanks. Regards

[@RalphBacon]

I'll bear your feedback in mind the next time I do a code walkthrough. 👍

[@zulfqarali8603]

Good but you talk too much, gets bit boring .

[@RalphBacon]

My middle name is boring. Ralph Boring Bacon. That's me. 😲

[@edinfific2576]

You can always stop watching, nobody is forcing you.

[@MrRenoman2011]

Thanks Ralph I'm just starting out with Arduino at the my late stage of life but I find it very cool. I look towards many more of your videos.

[@RalphBacon]

Best of luck!

[@sammyk7024]

As a retired developer and present day electronics hobbyist, it pleases me a lot when I see other developers implementing the same ideas or methods I come up with myself. This "I'm not that stupid" feeling is awesome. Thank you so very much! I use to call it "VERBOSE", instead of "DEBUG" though. (old console habits) I also like you using a decent IDE. I do understand The arduino IDE was designed for laymen and beginners, but the thing is just awful. just for fun, here's a one liner for blinking an LED: #define BLINK_LED digitalWrite(LED_PIN, millis() % 1000 > 500) Have fun! And stop arguing with sharp objects :D

[@RalphBacon]

I'm keeping well away from sharp objects, Sammy, of that you can be sure! Yes, I'm also sure that many of us seasoned developers have all got our ways of _doing things_ and they serve us well. I like the blinking LED code; pity the pinMode statement could not be included! Oh, it can, there we are. For others reading this: #define BLINK_LED pinMode(13,OUTPUT);digitalWrite(13, millis() % 1000 > 800) In the loop just call: BLINK_LED;

[@sammyk7024]

@@RalphBaconYou're absolutely right! I forgot to mention the setup, as I'm actually using it on pin 13 which doesn't need a pinmode setup. Just copied and pasted. My bad.

[@piuselectronics5707]

Nice video, just used this in my code and the speed increased considerably

[@RalphBacon]

Great, glad to hear it!

[@bluegizmo1983]

I usually just comment out the serial.begin statement in Setup when I'm finished with the code. Doesn't really help with code cleanup at compile, but it does get rid of the slow speed issue due to serial outputs.

[@RalphBacon]

So by including the Serial.setup(x) as part of the overall #define we could get the best of both worlds, I guess?

[@WistrelChianti]

Thanks! Really nice explanation of how to do functions using the preprocessor.

[@RalphBacon]

Glad you enjoyed it!

[@jessicacarter8264]

Hi Ralph. I do something similar. I have a function debugPrint() which checks whether isDebug() is true (which is an analog read if it's brought low it's true, on A0, usually in my code) and then I have an #ifdef _DEBUG_ENABLED_ #define debugPin A0 #define debugLED 13 #endif then you just need to define _DEBUG_ENABLED otherwise it doesn't compile in any debug support. It's useful if you're developing on a huge processor (like ATMega2560) and then wanna compile it down to 328 (for example). I think adding a counter to the debug function might be useful, but haven't thought about it, since haven't had much time without brain fog to work on Arduino projects.

[@RalphBacon]

I think experienced programmers, like you Jess, will probably all be using some variation of this, tailored to the way you like it. But beginners will never have used any precompiler constructs so I'm hoping this introduces them to the concept as well as allowing them to make their programs look more streamlined without #if...#else...#endif statements everywhere! Good to hear from and hope you're enjoying the new pad.

[@davidverheyen6635]

Great Idea! Until now I used a function for that and commented the serial.print out after debugging so the text was not sent. Your way the text dissapears completely so it is much better.

[@RalphBacon]

Glad you found it useful, David!

[@GiladBarkai]

The warning here is very useful - as it hints the counter doesn't perform its intended (by name) task. The ability to turn off 'usage only for debugging' is beneficial even beyond space and runtime.

[@RalphBacon]

That's where the ESP32 with its granular display levels wins out - keep on the fatal error messages ("E") and perhaps warnings too ("W") and only use the other levels for actual debugging. Very efficient.

[@avejst]

Great tools Thanks for sharing your experience with all of us 👍😀

[@RalphBacon]

No problem 👍

[@bgdexter]

Another thing you should cover here: there is almost never a reason not to use the F() macro on string constants, especially debug strings. F("…") addresses the string directly in the flash memory region. If you use a string without F(), it needs to be copied into RAM first.

[@RalphBacon]

Now you've got me thinking whether the #define should have included an embedded "F(x)" macro... if it can be done.

[@bgdexter]

​@@RalphBacon ​ You can't do that without fixing the argument type to string literals. As Arduino is C++, to my knowledge there is no way to get macro polymorphism (as with "_Generic" in C). A template function won't help because you need to apply the type switch before the actual function call on the arguments, i.e. outside the template scope. But I'm always eager to learn something new, so tell me if you find a way. OTOH, keeping F() in the call doesn't really hurt, and possibly serves as an awareness reminder.

[@kirbymurdstone4925]

Thanks you so much for this! My code was working fine, but it always bugged me that the serial was constantly printing to nowhere and taking up processing time. Now I have a solution! and...Now I have to go back and update ALL my sketches!

[@RalphBacon]

Glad I could help! Well, I'm sorry about the mountain of work ahead of you, though. No, really.

[@cho934]

Thanks you very much! Excellent explanations and very useful ! will use it and promote it in our association ;)

[@RalphBacon]

Glad it was helpful!

[@pflasterstrips7254]

if you would define the debug functions as regular C functions, and have a boolean that can turn them off (make the functions do nothing), shouldn't the compiler detect that all that and actually optimize the code such that the debug functions are not even encoded to any processor instructions.

[@RalphBacon]

That's exactly how Espressif do it on the ESP32. They have various logging levels that are not even compiled if the Core Debug Level is not set to certain messages. This here, is a simpler version of that.

[@gg-gn3re]

define is good for debug, where the compiler handles it. But using it in cases like "LedPin" (Which I have seen many times like you said) uses more memory than a const if you use it more than once. Const occupies 1 place in memory, but if you put "13" all over the place it's going to use more.

[@RalphBacon]

Hmm. I'm pretty sure using a #define macro name instead of a const does not use more memory. The #define method just substitutes the value _before_ compilation, so: #define ledPin 13 digitalWrite(ledPin, HIGH); becomes digitalWrite(13,HIGH); Using literals here, is not memory hungry (it's a one byte integer). But it can depend on the compiler. Using a const: const uint8_t LEDPIN = 13; digitalWrite(LEDPIN,13); will require the LEDPIN value to be retrieved from memory by code unless the code has been optimises and the value substituted like a literal. The compiler will try to keep the const value out of SRAM (it knows it cannot be modified). Which one uses less memory is hard to determine.

[@gg-gn3re]

​@@RalphBacon When you're using multiple like I said: #define ledPin 13 printf("%d", ledPin); printf("%d", ledPin); printf("%d", ledPin); printf("%d", ledPin); Is: printf("%d", 13); printf("%d", 13); printf("%d", 13); printf("%d", 13); in this scenario you're assigning 4 different constants, all of them are 13 vs const int ledPin = 13; printf("%d", ledPin); printf("%d", ledPin); printf("%d", ledPin); printf("%d", ledPin); living in a single place of the program. I'm talking I've seen programs with hundreds of places that define rewrites at compile time. In situations like above program size will be bigger.. but if you're running those defined preprocessor consts all over the place especially running simultaneously it ends up being more memory, too (as well as having to be loaded into memory, and removed rather than just sitting there as a global constant for the program's entire running duration) That's all I meant though, not for like single use things doesn't really matter

[@dafydds]

Another great video... I've not programmed in C for 25+ years, and have forgotten more than I remember, but this was just excellent. I'm still working on a project and knew I had to control my serial print statements as I 100% knew I had to remove them at final runtime/build. I was about to add in my own function for this, but this video makes me double check how I go about it. I love the idea of controlling the compiler to just filter out my unnecessary serial print commands 🤣 ... Thanks for this 👍

[@RalphBacon]

Glad you enjoyed it! And helped you too. Awesome!

[@winandd8649]

Definitely going o use this, thank you!

[@RalphBacon]

Great!

[@thorntontarr2894]

I risk being unable to see the obvious but the Simple and Advanced Example at github don't seem to demonstrate 'printf' and I also don't see how the printf library gets included into Platformio. Can you elaborate; I appreciate the issue with the sharp knife - been there, done that. Cheers.

[@RalphBacon]

Thumb is slowly healing, Thornton, thanks! The Simple and Advanced sketches do not use printf at all; the Advanced example shows a more granular approach to debugging levels (I'm using it right now in my new sketch). I'll be doing a complete video on printf very soon. In the meantime, you can include it in the *PlatformIO* environment by clicking on the Alien Head, choosing *Libraries* and entering *arduino-printf* in the search bar. The first entry in the resulting list (on my system, at least) was *LibPrintf by Embedded Artistry* which you can then click and *Add To Project* Note that ESP32 projects won't need this, ESP32 has printf already built in.

[@thorntontarr2894]

@@RalphBacon Clear reply, cheers, mate.

[@brancheternal]

I thought you were going to suggest toggling GPIO pins to indicate execution state. It's fast and if you have a multi-channel scope and only a few events to monitor it's good for getting an indication of when things are happening. Anyway, it's something that I do when printing to serial takes too much time or would result in excessive output.

[@RalphBacon]

You can also control the Serial.print statements if a particular (spare) GPIO is low. Connect a jumper between the pin and GND to turn Serial.print statements on, remove it when done for faster execution. The macro in this instance would interrogate the state of the (input) pin, ideal for those on the ESP32 that are INPUT only.

[@brancheternal]

@@RalphBacon Yeah, that is a good strategy as well.

[@btomas225]

I used to use them as dummy delays in functions. Don't forget, DELAY doesn't work in a function and sometimes you need a delay. I would put them in a for loop or a while loop to simply waste time. I did later find out that DELAY MICROSECONDS is the only delay that actually does work in an external function.

[@RalphBacon]

When you say _external_ function, are you referring to a pre-compiled module that you just linking in? The standard delay(x) function works everywhere in the Arduino environment AFAIK.

[@JorgeLestro]

Nice! I've reduced 1656 bytes in my last code with this method. Thanks!

[@RalphBacon]

That's good going, Jorge, well done.

[@wolfgangkuechle9085]

Nice and easy trick, thank you for presenting. Best part of it: It can easily be extended to introduce debug levels for more or less detailed debugging information.

[@RalphBacon]

Yes, you are right, it's what I also do! the ESP32 does it automatically (log_X where X is the debug level you want).

[@zaca211]

Great tip here. Preprocessor statements are so underrated. I usually make a debug function that takes a string then passes it to serial.print. Inside the function i use #ifdef statement to determine if the serial.print function gets run. I'm sure the compiler is smart enough to know the function has no code and to omit the function entirely when there is no definition. #define _DEBUG void debug (char *inStr) { #ifdef _DEBUG serial.print("debug: "); serial.println(inStr); #endif }

[@RalphBacon]

Yes, the compiler will exclude "empty" (or even unused) functions. The only downside I notice with your method is that you will have to format the string yourself (possibly using snprintf?) rather than just letting the standard methods do all the heavy lifting.

[@guitchess]

I'm definitely one of those beginners who haven't done that sort of thing. Great vid. An excellent example of how precompiler statements can be used. Now I have to see if works with my PIC MCs. Thanks for the tips.

[@RalphBacon]

Glad it was helpful!

[@gpTeacher]

Very informative Ralph! I'll be incorporating the printf and your preprocessing into my future work. Thanks Very much!

[@RalphBacon]

Good stuff, Gord, glad it helped.

[@gpTeacher]

@@RalphBacon As you folks on the Island say, "Works a treat! Thank you! I'm learning to fly RC airplanes and need a countdown timer for the battery life. My new project. This trick is working nicely. Sorry to hear about the knife wound. I've been redoing the back deck and my hands are full of slivers. I hear ya.

[@timmiyg5894]

Why does the Serial class initiation remain? - Could you not use the same method to remove Serial.Begin(xxx) from compiled code?

[@RalphBacon]

Yes, you could, but you don't really save much space (a few bytes at best). Not like the complete Serial.print statements now being sent into the ether! Additionally, you might want to actually still output an actual Serial.print statement (eg fatal errors) so this would still be needed.

[@RelentlessHomesteading]

Nicely done. Stumbled across your channel, while stumbling along relearning coding after over a couple decades. I'll be checking out some of your other videos, I see some very interesting topics which may be useful on my planned projects. Thankyou, RH 😁😁

[@RalphBacon]

Welcome aboard! There is always a link to a pdf in each video description that contains a list of all my videos, so you can search for keywords. Happy viewing!

[@RelentlessHomesteading]

@@RalphBacon Thankyou. I've already loaded a number of those videos to my watchlist. Appreciated your nRF24L01 video - implementing that on a current project here. Seems you've 'been in the game' for some time - as one who started programming by punching holes in cards I can appreciate that. My first 'development system' was one I had to DIY as my University did not have any way to load programs. 🎵🎶 ...Oh that was a long time ago - LOL Thankyou.

[@vasiliynkudryavtsev]

One of your problems, mr. Bacon, is that you go Serial.begin(9600). You can be 96 times faster with 921600.

[@RalphBacon]

The highest speed I use (usually with ESP32s), Vasily, is 115200; I will try higher speeds and see how it copes. The Arduino, with its 16MHz processor speed, is surely limited to 115200 at best? I tend to use 9600 on the Arduino to make it super safe and no risk of corruption. I guess I should increase that too! I can remember when 300 baud was the maximum I could get from some chips!

[@vasiliynkudryavtsev]

@@RalphBacon 921600 is one of standard values for UART. The FT232 USB-UART chip has 3Mbaud maximum data rate, same is for many clones and alternatives. As for microcontrollers, they usually have hardware implementation of UART, cpu clock is not that important.

[@vasiliynkudryavtsev]

@@RalphBacon Also, how faster one can go over UART for different boards can be a good investigation for your future video. BTW, for esp8266 and esp32 I used 921600 with no problems. 115200 is very safe for atmega328p (depending on USB-UART IC).

[@RalphBacon]

Hmm. If I clock an Arduino at 8MHz then my maximum sketch upload speed is only 19200, otherwise it might fail. On the other hand, an ESP32 can upload at 921600 no problem at all! There must be a correlation between processor speed and clock speed. Unless this is only true for storing program code into Flash (which is slower, we know).

[@vasiliynkudryavtsev]

​@@RalphBacon Well, this is true. The correlation is in how good and functional is the clock divider or PLL in MCU. That can be proved only experimentally or computed from datasheet.

[@stevetobias4890]

Very nice, excellent tip!

[@RalphBacon]

Glad you like it!

[@noweare1]

Very useful video Ralph, thank you.

[@RalphBacon]

Glad it was helpful!

[@juanjosefernandez2332]

Excelente. Saludos de Mar del plata, Argentina. Gracias.

[@RalphBacon]

Muchas gracias, Jaun. Me alegra que hayas encontrado útil el video. ¡No olvides ver mis otros videos también! Pues, hasta luego!

[@originuk]

I like the fact how you've converted a debugging output line into a macro - either print it or not, rather than check if debug mode is set, then print if so.... neat.

[@RalphBacon]

Glad you found it useful!

[@Cptnbond]

Thanks, good content as usual. Cheers.

[@RalphBacon]

My pleasure!

[@simonwhite3137]

This debug is a sweet little trick Ralph, thank you! And of course the "real" Serial.print() commands can be left as they are, so it declutters the Serial display too.

[@RalphBacon]

You're welcome, Simon!

[@digihz_data]

Hi Ralph, very good point about the Serial taking up memory and time. This is the way i do debugging (taking your "Simple_Example/simple.ino as a reference") #include //Debug options start. #define serialBaudRate 115200 #define debugEnabled true //Setting this to false will disable ALL debug options below. #define debugSetup true //set to false if you dont want to debug this. #define debugAddOne true //set to false if you dont want to debug this. #define debugLoop true //set to false if you dont want to debug this. //Debug options end. int addOne(int inX) { #if debugEnabled && debugAddOne Serial.print(F("Received value:")); Serial.println(inX); // Other processing done here Serial.println(F("Returning.")); #endif return inX + 1; } void setup() { #if debugEnabled Serial.begin(serialBaudRate); Serial.println(F(""));//Make sure our first Serial print gets on a new line. #endif #if debugEnabled && debugSetup Serial.println(F("Setup complete.")); #endif } void loop () { static unsigned long counter = 0; unsigned long b = addOne(counter); #if debugEnabled && debugLoop Serial.print(F("Counter:")); Serial.println(b); #endif // Emulate other processing being done herek delay(5000); }

[@RalphBacon]

And I use t hat way too sometimes, but I don't like using the #if construct in my code as it destroys the layout (to my eyes at least). If you look at my second (Advanced) example it shows a more granular way of doing things that might help.

[@digihz_data]

True​t that it destroys the layout a bit, but at least you can turn on and if exactly what you want to debug this way. Your advanced example is a good approach to of course, I just wanted to show another way of doing debugging. After all, we all have different tastes about things. Anyway, great thanks to you for your videos, they are superb.

[@JohanDegraeveAanscharius]

I needed that for such a long time! Thanks!

[@RalphBacon]

No problem! 👍

[@jeroenjager]

Genius! Nice one mate!

[@RalphBacon]

Glad you think so!

[@robertherzog2087]

I've watched so many videos with demos that show the serial output on a separate window, but I can never find anything showing how it is done. My output always shows at the bottom of the IDE 2.0 sketch. Will you please explain how to set this up?

[@RalphBacon]

That's because you are using the in-built Serial Monitor of the Arduino IDE. I'm using a standalone program called CoolTerm which is nice, and it's free too, although Roger is grateful for any donation if you find that you use it a lot: freeware.the-meiers.org

[@xDR1TeK]

Unused variables in proper compilers would be optimized out. Example, the STM32 cortex M series compilers. Not sure about the arduino though.

[@lsfornells]

Arduino uses the GCC compiler, so yes, this also applies

[@RalphBacon]

It's quite amazing what is removed as part of the optimisation process, including whole functions.

[@lsfornells]

@@RalphBacon Indeed. As a retired software engineer having worked in customised compilers and language interpreters for several companies, I’m currently an occasional contributor of the LLVM Compiler project, so I can confidently assert that a modern compiler is able to make certain optimisations and code transformations that are even beyond what an average programmer would be able to implement in assembly language

[@BaronVonBiffo]

I wish I had multiple personalities so I could give this more than one 'thumbs up'. Wonderfully elegant solution.

[@RalphBacon]

Thank you indeed. Don't forget to look at the Advanced Example in my GitHub! github.com/RalphBacon/224-Superior-Serial.print-statements

[@AHaensel]

I understand what you're doing but I don't understand why you're doing it. If program and data don't fit into memory in debug mode what does it help if they do in production mode. It also makes the program behave differently in development than in production, which is undesirable. Only in rather unusual circumstances I can imagine it might be helpful: If you 1. use heap (discouraged) or 2. want to use OTA updates with production builds only (cumbersome because you first have to serially flash a production build) or 3. want to use different hardware with smaller memory for production (unlikely for hobbyist applications).

[@RalphBacon]

My ESP32 was on the border line with its partition scheme; by using the more advanced features of my debugging method it reduces the code size (ie I eliminated all the Verbose lines) I was able to fit in the remaining code quite easily without having to re-partition - including all the SPIFFS/LittleFS stuff which would have been a pain. That all said, I hear you. If it does only just fit with some debugging lines switched off, then if you re-enable them, it will no longer fit, especially on the Arduino. The upside of reducing program bloat is that it compiles more quickly and uploads more quickly, even if it's 1Mb in size, like mine. Ignoring the space-saving for a moment, there's still a lot to be said to support using this method to keeping the program nice and clean. Far, far better than #if...#else...#endif statements everywhere. Don't you think?

[@markvreeken]

This was extremely helpful. Thanks a lot and keep up the good work.

[@RalphBacon]

Glad it helped!

[@johnczaia9124]

Thank you very much, Ralph! That was exactly what I was looking for!

[@RalphBacon]

Glad it helped you, John!

[@mast3rbug]

You can use Serial.println with single line, it's easy: Serial.print("This is the value of the loop: " + String(loop) + " and the value of the next variable " + String(variable2));

[@RalphBacon]

If you can stringify the variable then that's fine but not really as useful as a standard C++ function like printf!

[@Crusher9mil]

Awesome simple solution 👍🏻👍🏻 For the remaining unused 'b' variable couldn't you do a define for that as well so it'll get toggled on/off like the rest?

[@RalphBacon]

Almost certainly although I have not tested that. Go on, have a go!