bcd
- 9th August 2008, 09:38
Hi All,
Just want to bounce some ideas of everyone for a project I am working on at the moment.
I have an application that controls 6 channels of dimming over RS232, but what I am struggling with is the ability to fade a channel to a know value over a certain time.
As an example lets say I want to fade from level 0 to level 255 over 10 seconds. This means every second the value has to change by 25.5.
What I was thinking of doing was using DT Interrupts to generate an interrupt every 0.1 second where we could do some maths to increment the value as required. Using the values from the example above I would have to increment by 2.55 values every interrupt - 2.55 * 10 (25.5 per second) -> over 10s gives us 255.
One option I though of was to multiply the value by 10 so 255 becomes 2550 (defined as word rather than byte) which would allow me to have 1 decimal place precision. I could then check if the lowest value > 5 and if so increment. I might need to set a bit to mark if we did a 'roundup' step so the count doesn't get too far out too quickly
So steps would be: (over 100 time periods - 2.55 steps per period (becomes 25.5 steps as we x10)
step1 - increment by 25 - 254 steps remaining - output is 0025 (rounds to 3)
step2 - increment by 25 - 253 steps remaining - output is 0050 (rounds to 5)
step3 - increment by 25 - 252 steps remaining - output is 0075 (rounds to 8)
step4 - increment by 25 - 251 steps remaining - output is 0100 (rounds to 10)
...-...
step 253 - increments by 25 - 1 step remaining - output is 2525 (rounds to 253)
step 254 - increments by 25 - 0 step remaining - output is 2550 (rounds to 255)
This gives a running average of 2.5 steps per time
There is a bit of maths that I think I might need to do some Long string manipulation to make things work, but does it sound like I am close with this idea??
We Know the Start Value, Finish Value and required Fade Time.
these give me number of steps to do each interrupt. I just need to work out how to do decrement or increment based on the remaining number of steps and the if it is less than 1 we miss a step, or if a whole number we inc / dec by that much, but a value that has a value to the right of the decimal place then we hold off unless it is greater than 0.5.
Once we reach the end of the fade time we might need to do some bumping to the final level to make up for any rounding errors.
I seems to work OK for values I try, but I might need to try with some weird values to see if it still holds up - 33 - 101 over 5 seconds ??
(68 steps over 5 seconds or 50 interrupts = change by 1.36 per interrupt !! aaarg !)
Any thoughts anyone ?
bill.
Just want to bounce some ideas of everyone for a project I am working on at the moment.
I have an application that controls 6 channels of dimming over RS232, but what I am struggling with is the ability to fade a channel to a know value over a certain time.
As an example lets say I want to fade from level 0 to level 255 over 10 seconds. This means every second the value has to change by 25.5.
What I was thinking of doing was using DT Interrupts to generate an interrupt every 0.1 second where we could do some maths to increment the value as required. Using the values from the example above I would have to increment by 2.55 values every interrupt - 2.55 * 10 (25.5 per second) -> over 10s gives us 255.
One option I though of was to multiply the value by 10 so 255 becomes 2550 (defined as word rather than byte) which would allow me to have 1 decimal place precision. I could then check if the lowest value > 5 and if so increment. I might need to set a bit to mark if we did a 'roundup' step so the count doesn't get too far out too quickly
So steps would be: (over 100 time periods - 2.55 steps per period (becomes 25.5 steps as we x10)
step1 - increment by 25 - 254 steps remaining - output is 0025 (rounds to 3)
step2 - increment by 25 - 253 steps remaining - output is 0050 (rounds to 5)
step3 - increment by 25 - 252 steps remaining - output is 0075 (rounds to 8)
step4 - increment by 25 - 251 steps remaining - output is 0100 (rounds to 10)
...-...
step 253 - increments by 25 - 1 step remaining - output is 2525 (rounds to 253)
step 254 - increments by 25 - 0 step remaining - output is 2550 (rounds to 255)
This gives a running average of 2.5 steps per time
There is a bit of maths that I think I might need to do some Long string manipulation to make things work, but does it sound like I am close with this idea??
We Know the Start Value, Finish Value and required Fade Time.
these give me number of steps to do each interrupt. I just need to work out how to do decrement or increment based on the remaining number of steps and the if it is less than 1 we miss a step, or if a whole number we inc / dec by that much, but a value that has a value to the right of the decimal place then we hold off unless it is greater than 0.5.
Once we reach the end of the fade time we might need to do some bumping to the final level to make up for any rounding errors.
I seems to work OK for values I try, but I might need to try with some weird values to see if it still holds up - 33 - 101 over 5 seconds ??
(68 steps over 5 seconds or 50 interrupts = change by 1.36 per interrupt !! aaarg !)
Any thoughts anyone ?
bill.