PS: I also need off phase to be 500 to 10,000 times or more longer.
westfw:
Did you see this thread: http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1230286016How exactly timed does the "off" time have to be?
Well for proof of concept total cycle time will likely fall around
1000 Hz (.001 sec) give or take. At this point adjusting the
Mark/Space timing will be needed, but if the concept is proven
I will be able to pour in some real money $
I will check these things THANK YOU ALL
@westfw:
Need to get the OL off the computer, the code does not
display properly on the iPhone. Need iPad I guess 
Accuracy of OFF times is not at all critical, I take it
you are implying it will be in a multiple of 62.5 nSec
which is perfectly acceptable. The ON increment is small
enough that a multiple will work well. A few nSec one way
or the other prolly makes no difference at all at this point.
Off times will be huge in comparison to the On times.
Later I believe that true nanosecond control will pay dividends
but the basic design is likely to work with these specs. It will
SURELY yield some valuable data if not total proof of theory.
I take it you are implying it will be in a multiple of 62.5 nSec which is perfectly acceptable.
Yes, it will be a multiple of 62.5ns (everything will be!), but that isn't the point.
The point is that if you have a short-ish "on" pulse, you only have to generate "exact" code for the duration of that pulse. If you need both the on and off times to be accurate (note that "accurate" is different than "short"), you pretty much have to control ALL of the code, which is MUCH harder. Figure that an average Arduino program can output a nearly exact 62.5ns pulse every 10ms +/- 5 ms (which is a LOT of variation in the off time.)
You're not reinventing MPIR, are you?
undeRGRound:
Seems the PWM is limited in speed and I need
to have the ability to set an output and a pause and repeat.
To be honest I don't understand this.
Your PWM output can be up to the clock speed.
Thus you can have one pulse every 62.5 nS.
That isn't "limited in speed".
@ westfw:
That could be acceptable for proof of concept. Slow but OK.
65 to 200 Hz is relatively slow (I see 1000 Hz as my low end)
But materials questions arise @ 1kHz range anyway.
What is MPIR? Hope no one has done what I'm doing
@ Nick Gammon:
I had read that using the native PWM was slowed by the coding
Or something, what I am trying to do is get a minimal ON pulse
and adjustable on/off phases. The intended device to be controlled
is not an LED, I just need the ^**above^^^ mentioned pulses and
a wide range of adjustability. For now let's just say all I need is to
Generate a 'Scope Trace which is mostly FLATLINE...
undeRGRound:
@ Nick Gammon:
I had read that using the native PWM was slowed by the coding
Or something...
Oh aye.
Where did you read that?