McChubby007 wrote:It is a large and complex topic, and most 'Arduino people' are not interested; it is what industry uses. I decided to share this with you as you are interested which pleases me.
As far as my 3us timing goes, obviously you cannot cheat physics and 70 chars @ 115200bps = 5ms. The 3us that I quote is delay impact on the user's calling code when doing the trace; what actually happens is that this data is then buffered and sent over serial (or wi-fi or SD/Spiffs) in the background during idle foreground activity. In reality the delay to user code is actually even less, more like 800ns. For an Arduino Uno it is abut 40us as that processor is a lot slower and 8-bit architecture.
If you have any questions about this subject in general or the tools specifically then please ask, as I am happy to share my knowledge, since as I say, most arduino hobbyists don't seem that interested.
I'm curious and this can be useful someday.
I am not such an ordinary user.
Development for an automation company. So sometimes I move with some deeper things.
Even if I do not use this knowledge, it's good to know how it works.
Glad you like to help and share knowledge!
I get sad when the person knows how to help and speaks: go search on google.