![]() |
motor controller profiles
My programmer team and I just collected some data on the operation of all 3 motor controllers. Jaguars, Victors, and Talons. We put a motor on a wheel with a gearbox and an encoder. We collected the minimum value that had to be sent to the controller to start the motor moving forward and reverse, the maximum forward and reverse speeds, and a graph of speed over time. We had the program increase the value sent to the controller by 0.01 every 0.5 seconds until it reached full power then decrease the value by 0.01 until it reached full reverse power, then increases again until it reached a stop. I've made sure the controllers were properly calibrated and used the correct class for each.
Jaguar: Start value: 0.110 Reverse start value: -0.060 Top speed: 543.478 units/sec Reverse top speed: -543.478 units/sec ![]() Victor 884: Start value: 0.090 Reverse start value: -.060 Top speed: 657.895 units/sec Reverse top speed: -568.182 units/sec ![]() Talon: Start value: 0.070 Reverse start value: -.060 Top speed: 543.478 units/sec Reverse top speed: -568.182 units/sec ![]() |
Re: motor controller profiles
Were you using the correct class for each controller? Each motor controller has different input timing requirements.
|
Re: motor controller profiles
1) Was each motor controller properly calibrated? 2) Did you use the proper driver for each motor controller? 3) You didn't mention which model Victor you tested. It looks like the older 884, not the new 888. |
Re: motor controller profiles
Ah. ya I noticed that there were different classes for the different controllers but forgot to swap out the code at the time. The talon was properly calibrated and I'm fairly sure the Victor was. Ill correct the data when I re-run the tests tomorrow.
|
Re: motor controller profiles
Quote:
(I know how I'd do it with a test like this, but for completeness it would be helpful if you'd document how you did it) |
Re: motor controller profiles
The reason I believe the Victor may have been improperly calibrated is because the lights didn't light up exactly how the instructions said they should. I think that on the Victor we may have just done a factory reset. I will confirm that everything has been properly calibrated before the test tomorrow so we can get more accurate data.
|
Re: motor controller profiles
1 Attachment(s)
Here's the data that's present overlaid on top of each other (as best I can) for comparison:
Attachment 13585 |
Re: motor controller profiles
I re-ran the tests with the motor controllers properly calibrated and using the correct classes. the graphs have been updated but there was no significant change. I hope this data will be useful. also keep in mind that the values will change depending on the motor, gearbox, encoder, and battery life. These values are fairly arbitrary on their own and are mainly useful for seeing the comparison between the different types of motor controllers. For instance the dead zone around zero for talons seems to be significantly smaller than the the dead zone for the other 2.
|
Re: motor controller profiles
1 Attachment(s)
|
Re: motor controller profiles
I believe it was a fluke in the data. A random sudden spike.
|
Re: motor controller profiles
If you have a Victor 888 and would be willing to run your test with that, it would make your data set complete and help put things in perspective. |
Re: motor controller profiles
I definitely would but I sadly don't have any, and I don't think that we'll be getting any because the talons seem pretty reliable. I do wish we did though so I'll probably have someone order them after this season.
|
Re: motor controller profiles
Quote:
|
Re: motor controller profiles
Quote:
Thanks for posting, this data looks very interesting. Would you consider sharing the code that you used for the comparison? If you did, perhaps someone else could repeat the test with the 888. Al G. |
| All times are GMT -5. The time now is 08:41 PM. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi