First, as I described in my other replies, the we followed the wiring diagrams, and successfully used them to drive our drivetrain around for about 30 minutes.
Second, by “serial cable” I meant the db37 cable used to connect the digital sidecar to the digital io module in the crio. Sorry I used wrong name.
Any other ideas?
Thanks.
We will definitely check this tomorrow, as this is a new assembly of the electronics and it very well could be the issue, I just didn’t think to check it.
We had a similar failure but do not expect this to be your exact issue. We started to lose PWM outputs one after another until half the board had no output. We replaced the DSC and checked the bad one only to find a crack. The way the board is laid out, the crack cut the lines to one of the output devices but not the others.
Check to see if they really are getting a forward or reverse signal. Green on the Jags is forward, red is reverse.
Why do I ask? I’m guessing you’re using ports 1, 2, 3 and 4 for your drive motors. 3 and 4 are on one side, correct? If so, then everything is working as it “should”, just not what you are expecting. (Since on a normal FRC drivetrain, the left side is a mirror image of the right side, and the motors are rotated 180 degrees…) You’ll need to change your code to drive motors 3 and 4 inverted, or on the OUTPUT side of the corresponding Jags (The side with M+ and M-), make the motor’s red go to M- and the motor’s black go to M+.
If that isn’t what you’re doing… then something very strange is going on indeed.
EDIT: I guess I didn’t understand your problem correctly. You’re saying that the problem isn’t inversion but lack of control?
2 digital sidecars did the same thing, including a brand new one from the KOP. We also opened up the digital sidecar and do not see any cracks/debris/etc.
any other ideas?
thanks.
Yes. The problem is that the motors just spin and we have no control of them when we should be able to control them using the joystick. This is only the case for the first four ports too, since we can control them exactly as we like in the rest of the ports. We had our drivetrain running on the other ports because the first four ports will not work. The motor controllers are wired as they should be. It is really strange. We e had problems with the sidecar last year, but then it was just that metal shavings got into the sidecar and shorted it out. This is not the case this year (we opened it and checked). Any ideas, because right now we are stumped. Thanks.
Only of the “are you sure it’s plugged in?” sort. For example, what revision of the cRIO image is installed?
afclsn, Can you take a picture of your side car and electronics layout for us?
Thanks.
Try making some code that allows you to directly control each output (As a Jaguar… like jag[1].Set(joystick.GetAxis(1)) ). See if the problem is really hardware or just your code not doing what you think it does.
Yeah, we did this before we tried it with code for the mecanums, and it had the problems with the simple code.
I will get one up shortly.
Just checked, all three power lights are green.
Here is our layout, without the motors connected.
We connect the black motor wire to the M- port, and the red motor wire to the M+ port.https://docs.google.com/file/d/0ByDtApfHHB3xSUhWbjBrVXl5WDdVUkItZkRHWEtXTEZ0V0hZ/edithttps://docs.google.com/file/d/0ByDtApfHHB3xRTh1UUtLeWNsWFE1LU8zMjNtck9fd1FOMXRr/edit
I think you forgot the attachment. Correction it doesn’t look like those pictures are public.
I noticed this when I posted it, but due to the securities on our school network, I couldn’t easily fix them. Here they are now.
I case the photos don’t work
I noticed you are using the ribbon cable. Could you have a backwards ribbon cable? I know those were floating around and its also easy to make backwards if you not careful. I am not sure of the symptoms of a backwards we have never had one backwards, but I know other teams have. Does anyone know if this could be the symptom they are seeing?
This was the pre fabricated ribom cable from the kit, plus we tried it with another pre fabricated cable (an actual cable, not a ribon cable), so I don’t think this is the problem, but all these cables were new this year so it is a possibility. I will check it tomorrow with the ribon cable we used last year and know works.
Thanks.
So thanks for all the suggestion. Last Friday the sidecar started working again, and it was set up exactly as it was Wednesday and Thursday. This is good because the sidecar now works, but is also bad, because we don’t know what went wrong. If you any other ideas as to what went wrong pleas let us know so that in the case it happens again we and other teams have a reference to go off of.
Thank you,
Team 4474
Bet the multipin connector was not fully seated at one or both ends.
I was going to mention that driving your mecanums for a half hour might be just about the limit for a battery to handle. I know it is tempting to keep the testing going, but you really have to watch the power level during testing and driver training runs.