New Programming Core needs help with simple motor control

[Greg McKaskle]

The Simple Motor VI looks fine for verifying things. It includes the Start Communications icon to connect to the DS. It has a loop in it, so no need to continuous run.

If your RSL is not blinking, is the small LED on the digital breakout board blinking? The LED helps distinguish between bad signal or power to the big light or an issue with the signal to the breakout board.

One of the things that hasn't been discussed is the ribbon cable. I've heard of bad cables and backwards cables over the last few years. Can you try another?

Greg McKaskle

[bharrison6]

Originally Posted by Greg McKaskle

The Simple Motor VI looks fine for verifying things. It includes the Start Communications icon to connect to the DS. It has a loop in it, so no need to continuous run.

If your RSL is not blinking, is the small LED on the digital breakout board blinking? The LED helps distinguish between bad signal or power to the big light or an issue with the signal to the breakout board.

One of the things that hasn't been discussed is the ribbon cable. I've heard of bad cables and backwards cables over the last few years. Can you try another?

Greg McKaskle

The only leds on the breakout board that are lit up are the 5v the 6v, the bat led, and an led beside the 1 (see pic). They are all green and steady on in every configuration and under every circumstance for this rig. Also every part on this rig has been worked at one time or another and each piece has been swapped out with another piece that has worked at one time or another.

I was wondering though. Does it matter if the crio that I am using is the longer 16 bit version or the shorter 32 bit version? Also does it matter if I am using a crossover cable? I know what they are since I have wired both CAT 5 and CAT 6 but I don't know if the one I am using is crossover or not without checking the wires and looking up the colors for crossover. I would think as long as I can deploy code to the crio the network cable is fine. If I remember my networking class right most NICs can actually detect if it needs the crossover and compensate anyway.

Thanks again for yall's help.

P.S. If anyone thinks I should try this with a different programming language and has some java or c++ code I can try out I can see if I can get a copy of those compilers and try to get this running on a different programming language. I know both decent enough to work with it. I just want to see this thing turn a motor and then I can take the next step.

[bharrison6]

Also above it looks like 1 and 2 are on, but its actually just 1 and a reflection off the plastic.

[bharrison6]

Also I am reformatting my CRIO for like the 10th time just to make sure something isn't wrong there and I noticed with this 32 bit 4 slot crio that there are no physical dip switches. Everytime I reformat the CRIO I see the dip switch positions and the console out dip switch is flipped. I have no idea what it does, but I do click on it on the FRC image tool and turn it off before formatting. It does somehow turn itself back on the next time I try formatting though.

[bharrison6]

Just reimaged it with another computer and deployed the project template code. The only change in the code was in the begin.vi where the open motor is set to victor instead of jaguar. No PWM signal, no RSL signal.

[bharrison6]

I just noticed after reading what other problems people are having that our driver station is reading 0 Volts. This might be of some significance as to what the problem is.

[Joe Ross]

Originally Posted by bharrison6

The only leds on the breakout board that are lit up are the 5v the 6v, the bat led, and an led beside the 1 (see pic). They are all green and steady on in every configuration and under every circumstance for this rig. Also every part on this rig has been worked at one time or another and each piece has been swapped out with another piece that has worked at one time or another.

I was wondering though. Does it matter if the crio that I am using is the longer 16 bit version or the shorter 32 bit version? Also does it matter if I am using a crossover cable? I know what they are since I have wired both CAT 5 and CAT 6 but I don't know if the one I am using is crossover or not without checking the wires and looking up the colors for crossover. I would think as long as I can deploy code to the crio the network cable is fine. If I remember my networking class right most NICs can actually detect if it needs the crossover and compensate anyway.

Given that all 3 power LEDs are brightly lit, 2 relays are lit, and the RSL is not, I would guess that there is a problem with the Digital Sidecar, DB-37 Cable, Digital Module, or the connection between the cRIO and the Digital Module.

None of the other things you mentioned would matter.

Originally Posted by bharrison6

I just noticed after reading what other problems people are having that our driver station is reading 0 Volts. This might be of some significance as to what the problem is.

This means that one of the conditions in R70 isn't met, but does not affect driving motors.