Cartesian to angle

[davidthefat]

Originally Posted by AdamHeard

Why? That's terribly cumbersome compared to the methods already posted.

Well, it takes less clock cycles to just retrieve data from an array compared to calculating the angle on the fly. Even though a look up table does take up considerable amount of space in the RAM (Not really since we are dealing with 64 MB of RAM...) Also given the level of accuracy we only really need, about ± pi/180 radian. I think it should be fine.

[AdamHeard]

Originally Posted by davidthefat

Well, it takes less clock cycles to just retrieve data from an array compared to calculating the angle on the fly. Even though a look up table does take up considerable amount of space in the RAM (Not really since we are dealing with 64 MB of RAM...) Also given the level of accuracy we only really need, about ± pi/180 radian. I think it should be fine.

The cycles are a nonissue on the cRIO, and using the function is substantially less code/setup time.

[Ether]

Originally Posted by davidthefat

Well, it takes less clock cycles to just retrieve data from an array compared to calculating the angle on the fly.

Where do you get your information ?

[EricVanWyk]

Originally Posted by Ether

Where do you get your information ?

You must spread some Reputation around before giving it to Ether again.

[PAR_WIG1350]

Originally Posted by davidthefat

Well, it takes less clock cycles to just retrieve data from an array compared to calculating the angle on the fly. Even though a look up table does take up considerable amount of space in the RAM (Not really since we are dealing with 64 MB of RAM...) Also given the level of accuracy we only really need, about ± pi/180 radian. I think it should be fine.

Wait, the crio only has 64 MB of ram? Yes, it does indeed. You learn something new every day I guess.

[jhersh]

Originally Posted by PAR_WIG1350

Wait, the crio only has 64 MB of ram? Yes, it does indeed. You learn something new every day I guess.

... and the new cRIO-FRC2 has 128 MB of RAM.