Quote:
Originally Posted by apalrd
There are very few teams who autoshift well. Very very very few. Some try it, most implementations are quite poor, it requires a LOT of calibrations to be perfect for it to actually make a difference.
|
Well at TORC, we are running two speeds this year, for our first time ever. We have done some autoshifting code, but it is really it is another adaptation of 2013 bee code, with some simplification due to halo drive code.
If you are a Labview team, do yourself a favor and download the killer bees 2013 code that is posted in the CD-Media and look at the "drive_auto_trans.vi" that (I assume) Andrew wrote. It is very well documented, and if you read it, you can understand the logic.
You will not be able to drop this vi in and run it, as you do not have the same operator interface their divers use, which complicates that particular .vi. But if you read the comments, and follow the logic, you can put together a very good functioning auto-shift code in a couple of days with minimal labview experience. We are just getting the bot running, but the autoshift code is debugged, and working, the kickdown and coastdown work well with our initial estimates on switch points. We still have some tuning to do on the up-shift, point. We are having some issues when the right and left do not up-shift in sync, which is mechanical in root, but hoping to minimize it with tuning.
Thanks again to Andrew, apalrd, for excellent work, and sharing. We owe you some more swedishfish!.
Scott.
PS, you misspelled TORC in your tagline.
