Issue with Talons

[KrazyCarl92]

http://www.chiefdelphi.com/forums/sh...hlight=chassis

This picture shows the electronics on the practice bot. Granted the wiring job is rather disorganized, but we do not use a ribbon cable on the DSC, we use a different type of cable as shown because we find they have far less issues than ribbon cables. It's still possible that this cable could be the source of issues, but not the kinds most teams with ribbon cable issues encounter.

[Mr V]

When we put our practice chassis together we had a "twitch" in our system too. We were not sending any commands to the DSC but the Talons signal light would blink and the motors would move for a brief moment. We switched to a different DSC and the problem went away. Opening up the DSC revealed that one of the chips had let out it's magic smoke. It was one that had been used in the past not a new unit, so it is hard to say when or why it occurred.

[Nirvash]

Our team have noticed random glitches from the drivetrain over the past few years, while no input was being sent, the drive motors would move just enough to make an audible noise, but not move the wheels.
We use Jaguars connected via PWM.

**edit**
Forgot to add, we are also using the round cable from the kop 2 years ago.

[404'd]

Originally Posted by KrazyCarl92

http://www.chiefdelphi.com/forums/sh...hlight=chassis

This picture shows the electronics on the practice bot. Granted the wiring job is rather disorganized, but we do not use a ribbon cable on the DSC, we use a different type of cable as shown because we find they have far less issues than ribbon cables. It's still possible that this cable could be the source of issues, but not the kinds most teams with ribbon cable issues encounter.

We used a (old KOP?) round type db37 cable like the one in your picture, for our first control board, and have seen some glitching problems. I switched to a shorter 1 ft one (not sure where from) for our test drivetrain and haven't noticed the same glitching problems.

Could be related to new cable or not, just my observations.

[Mike Copioli]

Both Al and Alan Andersons suggestions are good. The most likely problem is an intermittent PWM signal either at the software or hardware level.

Another possibility is an excessive periodic loop time. The time out on the Talon is 100 ms. That means if the Talon does not detect a rising OR falling edge after 100 mS, the output will be disabled.

If you have access to an oscilloscope you may us it to verify your loop time by toggling a digital I/O every periodic loop. Make sure you call this in the same area you set the throttle value.

As Alan stated the jump and jitter can be caused by an interrupted PWM signal.

Check for poor PWM cabling and DSC performance issues.

[Ether]

Originally Posted by Mike Copioli

If you have access to an oscilloscope you may us it to verify your loop time by toggling a digital I/O every periodic loop. Make sure you call this in the same area you set the throttle value.

This is an excellent suggestion.

If your team doesn't have a scope and can't afford one, there's a fairly simple and inexpensive way I have used to create a piece of test equipment that will do things like this, using the RS232 or parallel port of an old laptop. If there's enough interest I will post a paper about it. PM me.

[RyanN]

Originally Posted by Ether

This is an excellent suggestion.

If your team doesn't have a scope and can't afford one, there's a fairly simple and inexpensive way I have used to create a piece of test equipment that will do things like this, using the RS232 or parallel port of an old laptop. If there's enough interest I will post a paper about it. PM me.

As scary as it sounds, you can also use a computer's line-in port and Audacity to take in a waveform. You'll want to use a voltage divider to limit the voltage going into your PC as to not fry your sound card, but it's doable and works pretty well in my experience.

http://www.ledametrix.com/oscope/index.html

[Ether]

Originally Posted by RyanN

As scary as it sounds, you can also use a computer's line-in port and Audacity to take in a waveform.

True. I've been meaning to try that sometime. I use Audacity all the time for ripping my old collection of cassette tapes.

You'll want to use a voltage divider to limit the voltage going into your PC as to not fry your sound card, but it's doable and works pretty well in my experience.
http://www.ledametrix.com/oscope/index.html

What's the input impedance of a typical sound card, do you know? It looks like he's got the voltage divider bass-ackwards. He said he wanted to divide his 5-volt input down to 1 or 2 volts.

Food for thought:
If all you are trying to do is measure the timing (not observe the waveform) of a digital signal then you don't need the sound card's ADC. All you want is to capture and timestamp the edges. The parallel port works great for this. You can poll the data pins of a parallel port at 680KHz or so... way beyond the frequency of the audio card.

[KrazyCarl92]

So here's an update with what we tried tonight:

At first we started driving the robot around and did not observe the problem. Then, within 10 minutes the issue started back up again with the same symptoms as before. The robot twitches to the right before driving forward or reverse when it is command to go at high speeds.

To describe the trouble shooting and results we got, I will use the terms "DSC A" and "Cable A" to describe the equipment we started with, and "DSC B" and "Cable B" to describe the components we tried switching out with.

First we switched the cable from Cable A to Cable B since this was the easiest switch. The problem got worse. Now when enabled, the robot just ignored our commands and abruptly twitched turning to the right continuously.

We then tried the original components and got back to square one. Next we tried DSC B with Cable A and the problem seemed to be remedied, but we were unconvinced because we now thought that the problem could be with the cables since it seemed to be significantly worse with Cable B as compared to Cable A when both were paired with DSC A.

When we tried DSC B and Cable B together, we got the same exact symptoms as DSC A and Cable A; the robot does a single twitch to the right before driving forward when commanded to only go forward.

So we went back to DSC B and Cable A since this got us the best results. And after about 15 minutes of driving that way, we have yet to reproduce the problem. I'm hesitant to say that the problem is fixed because the logic is very odd and we haven't tested extensively yet, but the symptoms of the issue have yet to be observed in this configuration.

Can anyone else follow this or make any sense about what these results could mean? Maybe both DSC A and Cable B are bad, but I would expect more sensible results in that case...

[BitTwiddler]

Originally Posted by CrazyCarl92

Can anyone else follow this or make any sense about what these results could mean? Maybe both DSC A and Cable B are bad, but I would expect more sensible results in that case...

At times like this, guesswork and shotgun replacment of parts only takes you so far. Now it's time to take a more analytical approach utilizing test equipment that can reveal the true source of the problem.
I would set those items aside for now and put them up on the bench for serious troubleshooting after ship date.

[Al Skierkiewicz]

Carl,
Is the twitching taking place when the robot is enabled or when you start to drive? Are you able to drive several minutes on one battery without the problem reoccurring?

[Mike Copioli]

To take Al's point further; Have you ruled out a power supply issue to the DSC?

If you are getting mixed results through swaptronics it is time to perform a more focused assessment of the problem.

I would take a serious look at how the problem is reproduced, isolate the components instead of focusing on the system as a whole. Take a single motor controller and pair it with a DSC, PD and Cable on a bench off of the robot. Make every attempt to reproduce the issue. Paying very close attention to the steps being followed and what action cause the erroneous behavior.

Once you are able to deterministic-ally reproduce the problem, then and only then will you be able to take the necessary steps to solving it.

Having said that, if the problem is intermittent finding how to reproduce it can be very difficult. But it is still important to attempt to due so and avoid creation of causal relationships that may not have anything to do with the actual problem.

Break the problem down to it's basic elements. From a hardware standpoint:

What needs to happen for me to make a motor move?

- Motor controller and DSC must have proper power.
- Motor controller must receive a constant, uninterrupted(<100ms) PWM signal
- Digital module on cRIO must be able to provide and uninterrupted non intermittent signal to the DSC.

You must also be able to rule out specific components such as the motor controller itself. The easiest way to do this is provide the PWM signal to the Talon using a secondary form of communication such as a VEX controller or a simple PWM generator or an RC hobby controller. Once you have ruled out the MC, you need to move on to the other components such as the DSC.

Testing the DSC is a little more difficult and requires you to know a little about how it works. But there is a simple test that you can do. If the problem is the DSC it is possible that it is only with one or two channels, try switching the PWM signal to a different channel. Remember that there is a separate driver IC for PWM channels 9 and 10 than there is for 1-8 http://www.usfirst.org/uploadedFiles...matic%20v7.pdf. Sometimes this IC fails or has intermittent issues that could be the cause of your problem.

All of these tests requisite that you are able to reproduce the problem. If you cannot reproduce the problem then you have no way to validate your corrective measures.

Now there is always the possibility that your problem is software. Try loading the default code and performing a simple PWM assignment from a joystick to a PWM channel. Try reproducing the issue on every channel. Compare these results against the actions taken to reproduce the problem.

Following a methodical and step by step approach is the only way you are going to be able to pinpoint the problem and say with any reasonable degree of certainty that you have fixed it.

[nomad725]

I've had this same issue before but it was with the Jaguars. I ended up programming in the holonomic instead of arcade which seemed to solve it. It seems you may be having a similar issue best of luck and hope things go well.

[Joe Ross]

Do you have two single acting solenoids available? Attach one to a solenoid breakout and the other to a relay. Turn them both on all the time. If both actuate when the talons reverse, the issue is that everything is getting disabled. If only the relay one is actuating, it points to a problem with the enable signal in the digital module or digital sidecar. If nether actuate, it's something specific to PWM signals.