cougar controller testing

[MPaulHolmes]

You guys are awesome! Keep it up!

[roverT]

Is the PWM duty going to be returned with a value of 0 to 100 ......percent duty cycle

no point having the scale go to 512 if its only ever going to go to 100...

Cheers,

Trevor

[MPaulHolmes]

Right now the pwm duty has a resolution of 512, but the accuracy is only maybe 7 or 8 bits. I'm planning on increasing the accuracy (since there's now time because there are no while(); stuff during A/D conversions. So, if the resolution is greater than 8 bits, will that be a problem with the software that's assuming 8 bits? Or will there be a conversion to 8 bit, or should I cut it out with the 9 bit resolution stuff?

[charlie_fd]

The software now is sending/receiving 16 bit values. Values up to 15 bit will work since we need a sync bit. With the sync values we are using now (0xF0) you can go up to 12bit before we need to change that

[roverT]

ah, ok, I understand.

ya the client is just the slave......it can do anything you need.

that being said do we want to translate that into a % duty cycle on the client side?

[taffy]

Awesome work guys! Keep it up.
I will be watching this with interest, could be very interesting to have this running on board.

[roverT]

I think I have a few more things nailed down.

-write to file is done.....writes to csv (Comma delimited)
-Auto Scale or fixed 0-512
-Cleaned some things up a little
-add some more comments.
-Changed suffix to match Charlies change...


Write to File, eg. Graph in Excel

Cheers,

Trevor