It happens on Windows, too. Yes, it does... No, the serial monitor is not your application.
So there's no way to either tell SerialMonitor or Windows7 to have that serial line permanently in a non-resetting status?
Yes, you can control it in your application. Look in the Playground for the Interfacing with Software section.
Thanks, Paul I will have a look there, play around myself, and only come back when I'm stuck.
My goal is to start an application, connect to a long running Uno, and ask/read what it has done so far.
Neither plugging in the USB cable, nor starting the app and opening the COM port, should trigger a reset,
which invalidates all variables, AFAIK. I understand, variables are undefined at Setup(), and should be cleared there.
BTW: If SerialMonitor cannot really be used to test/simulate this communication, I could go for faster binary instead of ascii.
Any recommendation pro/con ? Is "faster" worth the pain of "not human readable data" ?