Linear to S Curve conversion

[Darrel Taylor]

Silly me, I was going for a 3rd order polynomial. Doh!

But you're right mat! Add a negative sine.



luminas,

Now I assume there's more information to it.
Obviously you don't want the integer results from 0-10. I'm sure you want some decimals or something.

Can you elaborate a little?

Best regards,

[luminas]

Hi Darrel & Mat,


Thanks for your great information

I want to compensate result of an ADC input ( 0 - 1024 )
what is the formula to do this ?


Jon

[skimask]

Hi Darrel & Mat,
Thanks for your great information
I want to compensate result of an ADC input ( 0 - 1024 )
what is the formula to do this ?
Jon

Look at D_T's last post...the formula is RIGHT THERE.
D_T has already done the hard work for you.

[Darrel Taylor]

...the formula is RIGHT THERE ...

Yeah, well, except that the range is from 0-1023 now, and PBP's SIN function takes a "Binary Radian" input (0-255), giving a result of -127 to 127. Sure, it's all there.

But now we need to line it all up.

Got any idea's?
<br>

[skimask]

Yeah, well, except that the range is from 0-1023 now, and PBP's SIN function takes a "Binary Radian" input (0-255), giving a result of -127 to 127. Sure, it's all there.
But now we need to line it all up.
Got any idea's?
<br>

We don't know how 'hard' he needs his compensation curve...for that matter, we don't know a lot about this 'function'...

'Divide down' the SIN result to make it less agressive, multiply it up for more compensation, add in some linear interpolation to 'fill in the blanks'...
We just don't know what's 'REALLY' needed here.

If this was some sort of R/C controller for a model airplane or something, I'd think he was trying to add a bit of double sided 'exponential throw' into his programming...

[Darrel Taylor]

We don't know how 'hard' he needs his compensation curve...for that matter, we don't know a lot about this 'function'...

OK, so let's stick with what we DO know.

The original Data spanned from 0-10.
If we expand that to 10-bit, we can make it 0-1000, plus 23. Just multiply by 100.

And, since the PBP SIN function takes an 8-bit input, we can divide the A/D value (X) by 4 to get the Angle in "Binary Radians". (I assume this is the 'Divide down' method)
Then running it through a short PBP program I got the SIN(A) values. (shown in the odd gray color)



Here you can see "Less than Optimal" results.
It's quite a large error.

So I guess the question now is ....
What's the "multiply it up for more compensation" method?
<br>

[Acetronics2]

Got any idea's?

<br>

YES ...

IF our friend would dare to tell us what's the FINAL use ot this curve ...

Alain

PS: Tools for you, Darrel ...

http://curveexpert.webhop.net/

[luminas]

Wow, this is more than what I expected from the forum. Great !

Darrel: You are right, first problem is solved with the negative sine things,

now the question is" how to adjust the " hardness " of the curve


Alain: The purpose of this curve is to compensate the output of a joystick to suit players response in a game.

Some player like "agrresive" joystick response while some other like "standard,linear" response.

Jon

[mat janssen]

Gain!
x-aSIN(B)
a is the gain.

[T.Jackson]

The purpose of this curve is to compensate the output of a joystick to suit players response in a game. Some player like "agrresive" joystick response while some other like "standard,linear" response.

I'm a bit puzzled by that - wondering if you could explain further?