I have a dedicated strip down dual core PC laptop. Its running real fast. I have 3 ezb boards running through ARC and am very impressed at how smooth the program runs. The only problem I ever had with it bogging down was once I had about ten ADC monitors running. Everything grown to a slow crawl. However as soon as a positive them the program picked right up. I was running a camera for a while and really saw know slow down issues. I'm running windows 7.

Thanks Dave (long time no hear,just taking a breather i hope) I am responding also, to keep this thread "in view" for a bit longer to harvest more replys! The ADC monitors slowing things down is just the thing I am looking for.

I'm guessing I can help on this but my head is full of goo at the moment and I'm all messed up thanks to a few nasty germs trying to bring me down... So basically, this should remind me to relook it over when I am "with it".

I will touch on the benchmark control quickly though. Start a new project, connect to the EZ-B with no controls, add control Benchmark and run it to see your communications "speeds". This will help with your working out the timings of scripts. For instance, if it can read the ADC port 40 times a second then you can read all 8 5 times each every second. So if you have sensors being checked you need 1/5 seconds of delay between reading, or 200ms. That's without anything else happening too.

As a rule of thumb, where possible and acceptable I use a sleep of 500ms or sometimes more than 1000. My battery monitor for instance checks every 2000 ms because it's not going to be a problem, it leaves it possible to check the IR sensors every 100ms without saturating the communications.

Hopefully that made sense, or enough sense to understand. Like I said, I will revisit this one when my head is clearer

Thanks SO much Rich! Your benchmark suggestion is perfect. It makes total sense and get better "but my head is full of goo at the moment and I'm all messed up thanks to a few nasty germs trying to bring me down... "..for a moment a thought you were talking about "another thread"

@irobot58 I've been very buys with "real life". Summer has many demands when good weather only lasts a few months (as you should know living up there in there in Gods country). When I have been able to work on the B9 it's been doing wrench turning. I have him taken apart right now doing little upgrades and enhancements in prep of moving him out of the shop and to a more viewable location in the house.

I've been lurking almost every dayhere on the forum and storing little tricks, tips and needed info for when I start working on EZB control again. I need to get deep into my ARC project and clean it all up and tweak it with all the recent ARC enhancements. I'm really excited and will hopefully will get back to that stage soon. This is one reason this thread you started sparked my interest. I've had small problems with timing between the 3 EZB boards and motor movements. For example when I pull the power pack on B9's side he should appear to go completely dead and slump over. "Sometimes" he will wait up to 10 seconds before slumping over. I think I narrowed this delay down to the way the commands are issued in my "Kill" script and the the way I have the Sleep commands set up (kinda like Rich mentions above). Length and placements of this command seems to be key.

Good luck and have fun! Dave Schulpius

@Dave thanks for the update! I believe Richs idea of adding commands and observing the Benchmark is pure wizard! Although it does take time but when the "Eureka" moment arrives it makes all worth while....and the research continues...like looking for the perfect chicken wing meal or beer!

Ummm.... beer.

I've always wondered why am I going to a port and reading the ADC value and using up time, when the pc already has the value, because it displays it if I bring in an analog meter, graph or digital readout. Can't I get the ADC of a port from the pc?