![]() |
4 CIMs causing robot lockup
Good morning everyone,
We are now utilizing 4 CIMs instead of 2. The code works happily when configured for 2 motors, but when you configure it for 4, turning left (and only turning left) causes it to spin at full speed for about 1/4 of a second, then die. Very strange. We have checked for wiring issues and CIM issues. We have tried leaving the code the same and unplugging 2 of the CIMs, then the other 2 to try to identify if it is hardware and the problem persisted whenever CIMs were separated. We have tried unplugging the 4 CIMs from 1,2,3, and 4 and plugging them into 5,6,7 and 8 with the same results. Again, putting the code back to just 1 and 3 and it works just fine. We have also replaced all 4 CIMs and swapped out the 4 jaguars. I'm down to wondering if it's the new cRIO we received this year. But that seems odd as it is fully functional outside this one turn. That or maybe the way your declare the CIMs has changed slightly. Any thoughts? Oh! we have also tried 2 separate laptops, one running the 2012 software and one running the 2013. Thanks! The following is our code: Code:
/*----------------------------------------------------------------------------*/ |
Re: 4 CIMs causing robot lockup
Try carefully working your way down these two checklists: http://www.chiefdelphi.com/forums/sh...39&postcount=5 http://www.chiefdelphi.com/forums/sh...19&postcount=4 |
Re: 4 CIMs causing robot lockup
When you say you unplugged the CIM, did you unplug the CIM from the motor controller, or unplug the motor controllers PWM cable?
I don't see anything obviously wrong with your drive code, so I agree with Ether that it is likely an electrical issue. One potential (but unrelated problem) with your code is your drivingStyleModifier toggle. Unless your driver can press the button and release it in less then 0.005 seconds, the driving style modifier will continually toggle. You'll want to remember the previous state of the button, and only toggle if the current state is true and the previous state was false. Another potential (but unrelated problem) is your firing mechanism. If both buttons one and two are pressed, the relay will be set to forward and then very quickly be set to reverse. This isn't good for the hardware. You should use a if, else if, else structure to make sure that only one value is set for each iteration. |
Re: 4 CIMs causing robot lockup
Have you checked that each motor is running the same direction? What you describe sounds like the motors are fighting each other causing the current to skyrocket.
|
Re: 4 CIMs causing robot lockup
Wow. Super embarrassing. I'm amazed it functioned at all. The digital sidecar was not powered at all. Totally not plugged in aside from the serial communications cable. I'll send a followup once I confirm that fixes it tonight.
Thank you! |
Re: 4 CIMs causing robot lockup
Oh, and thank you. I'll update the code to reflect those suggestions as I had noticed that it didn't switch driving modes when Y was hit and I can definitely identify the damage that could come from alternating current forward and backward rapidly in the device. Thank you guys!
|
Re: 4 CIMs causing robot lockup
Yup, that's all that was wrong. Thank you guys!
|
Re: 4 CIMs causing robot lockup
Quote:
|
Re: 4 CIMs causing robot lockup
Quote:
|
Re: 4 CIMs causing robot lockup
To clarify my previous statement: the field magnets were reversed when the motor was assembled. Dissassembly and reversing the field magnets during reassembly fixed the rotation issue.
|
| All times are GMT -5. The time now is 09:49. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi