Quote:
Originally Posted by Greg McKaskle
Is it possible that you are fast user switching and running the DS in both driver and developer accounts?
If not, let me sound like an optometrist for a minute to see if we can discover what is causing this.
Log into the classmate DS as developer. Note that means booting with shift key down or exiting the DS in driver first. Run the driver station from the Start menu. Open the task manager from a right click on the task bar.
If the system watchdogs are occurring, what is the CPU load? Does this get better or worse if you plug in the stop button? Does it get better or worse on a particular DS tab? If you click the button on the dashboard video to halt the video, better or worse? Go ahead and close the DB, better or worse.
If one of these makes the situation significantly different, please post the results.
Greg McKaskle
|
I am very sure that I haven't been fast user switching, I only ever use one account at a time and make sure the other one is logged off.
When I run the DS and Dashboard in developer, interestingly enough, I get significantly less system watchdog expirations, but still more then if I use a completely different computer. It goes down to about 3 or 4 every 5 seconds rather then the 5-6 per second I was getting when in the driver account.
In task manager, when the DS is running the CPU is always at 100%. The DS usually uses 50-60% the Dashboard uses 10-20% and something called mscorsvw.exe uses whatever is left. Occasionally another process will use a bit of CPU, but nothing unusually high.
Amazingly enough, after a few minutes, mscorsvw.exe went away and the watchdog expirations almost completely stopped. I still get one when switching tabs or windows, but that is much more acceptable then what I was getting before. However, this was with no vision and a e-stop button plugged in. When I turned vision back on, and used the override for the stop button, the number of errors went way back up.