different software times, impossible?

[lutherblisset]

the first train is fixed 400 pulses, 50% on and 50% off. for the second train i can set another number of pulses, but the totale time must be the same of the first train, same start same end, maybe two pic serially connected?

[richard]

so wave 1 is 400 pulses of [ pulse width x] : therefore duration = x * 800
wave 2 is y pulses of duration/(y*2) ; assuming 50% duty

y range is ?
x range is ?
tolerance is ?
repeat rate is ?

[lutherblisset]

the only fixed thing is the 400 pulses of the x, with 300us on and 300us off, on the other side y i must have the choice to set different pulses (100 to 600). But whatever pulses have the y the goal must be to reach the end at the same time....

[richard]

But whatever pulses have the y the goal must be to reach the end at the same time....

how do you define the end ?

depending on what you think a reasonable resolution is (and achievable) not all possible pulse counts in the range 100-600 will divide exactly into the duration .

what is the duration 800 * 300 uS or 799 * 300 uS ?

how do you intend the sync to be eg leading edge low to high transition to trailing edge high to low transition ?

can the final y pulse just be truncated to fit ?

[lutherblisset]

hello richard, first of all thank you. The y pulse can be always approximate to the unit, so it's never truncated. Only the pause change to reach the total time together at the x pulse. the x pulse is fixed 400*600=240000=240milliseconds, so the y pulses.

[lutherblisset]

i will make a test to see if the logical circuit connected to the pic accept "on" states duration other than "off" states, not symmetrical. Cause if the only important thing is the distance between the beginning of every "on" state maybe the software can be easier....

[Amoque]

It is, I understand, also possible to run more than one pic from a clock source. You mentioned connecting pics serially, but I do not see this as a solution; however, two (or more) sync'ed to the same clock...