Are you using the USB connection for the serial communication? The serial CDC driver uses Bulk transfer which doesn't guarantee a set bandwidth or latency. If you want that you should use a true RS-232 connection or a similar type of connection. You can try connecting the Arduino board to another USB port - one that has fewer devices connected to it. But for any of this to work, you must not fill the buffer on the serial interface faster than it can empty. (115200bps/10cps = 11520Bps for 8N1, note: 1b for the start bit)
Don't use the Serial Monitor for high bandwidth traffic; it cannot handle it. Use PuTTY, Hyperterminal, or some other terminal program.
Yes I'm using the USB port, but I'm using the same port as I used before with no other hardware alterations to the PC. I'm not really using the Serial Monitor for anything except making sure the Serial stream is actually working. Which it was before, but now is not.
If you don't want to understand what is causing the problem or how to fix it then I don't see what help you're expecting here.
I added the time functions, it began freezing things, I remove the time functions, it's still freezing and I need to know how to fix it. All I want to do is get it back to the way it was before playing with time so I can then begin experimenting on other things.
Go back to the version of code that worked before. If you've changed the hardware since then, change it back to how it was at that time. If you've installed any software on the PC that could have any bearing on USB or serial ports, uninstall it. (Mobile phone apps are a favorite.)
I do want to understand, but I understand that some of the suggestions about only sending the data when it changes or other ways of sending the data, isn't relevant yet. I'm working on a faster way to send data, which is what led me to trying and figure out how long the simulated outputs were taking, so I could see where the slowest code sections were and know what to work on first.
I am using the version of code that worked before, with the exception that the new code is commented out. Could the compiler be doing something weird with the comments and still including them a little, or something else weird? My process went like this code that works -> code with time measuring functions causes Serial Monitor to freeze -> new functions commented out, but they still freeze.
Here's the version of the code that used to work. As you can see, it's identical to the above code if the commented lines are actually removed. But even going back to this, the Serial Monitor still freezes, and using another program like PuTTY or my own test application, shows very slow transfer of data rather than the continuous stream of data this code used to produce:
Interface to Orbiter Flightdeck
int analog = 0;
analog = analogRead(0);
sprintf(pitch, "<129 %4d>",analog);
for(int i = 0; i<100; i++)