Drive Train Curves Only While Backing Up

[Ozuru]

Originally Posted by GeeTwo

I concur. What do the outputs of 3, 4, and so forth look like? Whichever one disagrees with the others should be reserved for standalone (one controller) functions, not the drive train.

I'm not sure I understand what you mean, sorry. Are you referring to the individual motors themselves or do you mean the PWM ports?

[BitTwiddler]

Originally Posted by Ozuru

Thanks for all of the replies so far everyone.

I'm not there testing but have someone else testing. I'm going to be recalibrating them (and consequently posting here with my findings) sometime around 3 PM EST today. Maybe I'm interpreting the oscilloscope wrong -- here are the images I received. Linking to rather than embedding the pictures because they're massive.

Oscilloscope Reading #1
Oscilloscope Reading #2

The readings are from the PWM signals with the ports swapped running the very basic code below I wrote to confirm it wasn't a programming issue.

.

I see the difference in pulse widths which would make one side travel faster than the other. I'm betting this would be solved by recalibrating the controllers to the input values.

[GeeTwo]

Originally Posted by BitTwiddler

I see the difference in pulse widths which would make one side travel faster than the other. I'm betting this would be solved by recalibrating the controllers to the input values.

These pulse widths are being determined by the 'RIO, not the controllers.

[E Dawg]

We had exactly the same problem earlier in the season and it turned out to be the joysticks, so make sure it's not those. You can do this by watching the joystick outputs on the Dashboard. If that is the problem, you can easily fix it by putting in a bigger deadband.

[MrForbes]

Are you saying that the direction of curving is following the code, not the hardware?

if so, you'll have to get some help from a programmer....and I suggest you post images or listings of your code so they can see what you have done.