No clue where to start on Programming...

[Team3763 Adam]

I have run into yet another problem.

In LabVIEW, I cannot get our other 2 motors to respond to the programming. I've tried with 4-motor and 2-motor drives, and nothing works. We've checked all the hardware and wirings, with nothing working. If anyone can help, it would be great.

I made sure I had everything edited properly in Teleop, Begin, and Finish vi's.
Motors 3 and 4 were wired into PWMs 3 and 4, with neither working. However, 1 and 2 DO work, but because they were pre-programmed, I have no clue what the problem could be.

A simple schematic would be great. A screenshot, anything really.

In need of desperate help.

[Alan Anderson]

Originally Posted by Team3763 Adam

In LabVIEW, I cannot get our other 2 motors to respond to the programming.

For your motor speed controllers, are you using Jaguars or Victors?

What is the light on the speed controller showing, both before and after you Enable the robot using the Driver Station?

[Mark McLeod]

Here's what your Begin should look like and the original drive code must be gone.

Things to watch out for include:

• Making sure you don't have two different drive trains defined
• Making sure the drive name is correct in Teleop
• Make sure your PWM's are all unique

If you get Begin right, then your Jaguars should stop blinking when the robot is Enabled, at least from a code perspective.
That doesn't mean your PWM cables aren't reversed or something.

[Team3763 Adam]

Originally Posted by Mark McLeod

Here's what your Begin should look like and the original drive code must be gone.

Things to watch out for include:

• Making sure you don't have two different drive trains defined
• Making sure the drive name is correct in Teleop
• Make sure your PWM's are all unique

If you get Begin right, then your Jaguars should stop blinking when the robot is Enabled, at least from a code perspective.
That doesn't mean your PWM cables aren't reversed or something.

Thank you so much for telling this! I did NOT know I had to delete the original code! I'll try that tomorrow and tell you how it works.

To answer the previous question, all 4 Jaguars blinked a constant yellow.
-The 2 motors that ACTUALLY worked then displayed a solid green or red, depending on their direction of travel.

[Team3763 Adam]

Originally Posted by Mark McLeod

Here's what your Begin should look like and the original drive code must be gone.

Things to watch out for include:

• Making sure you don't have two different drive trains defined
• Making sure the drive name is correct in Teleop
• Make sure your PWM's are all unique

If you get Begin right, then your Jaguars should stop blinking when the robot is Enabled, at least from a code perspective.
That doesn't mean your PWM cables aren't reversed or something.

I did exactly as you said, I checked and made sure I deleted ALL original code, and I made sure the names were exactly the same. I followed the picture exactly in LabVIEW and the two additional motors are STILL not spinning.

[Team3763 Adam]

http://imgur.com/pHaX7 --- Teleop.vi




http://imgur.com/hic4V --- Begin.vi



http://imgur.com/mE9fR --- Finish.vi



As you can see, I removed the original code, and then added in my OWN code.

I can successfully deploy the robot code to the cRIO.

Then, I switch over to the Classmate and I get Robot Communication and Code.

However, when we move the joystick on our controller, motors 3 and 4 DO NOT respond with the code. There is no signal being sent to either Jaguar.



Please help. If you know what the problem is, please tell. We are desperate right now. It's not our hardware or wiring. The only solution I can think of is the programming itself. So please explain what my problem is.

[Mark McLeod]

The quick answer is to zip the project folder (Documents/LabVIEW Data/project name) and post it here so we can see what the problem is, or at least isolate it to wiring vs programming.
P.S. Your photo hosting site is blocked here, so I'll take a look when I get home.

Potential wiring problems include:

• Power to the Digital Sidecar (All LEDs bright & green?)
• PWM cables (can swap the cables from the working ones to the non-working Jags.
• Low battery voltage of course

[Alan Anderson]

I see nothing immediately wrong with the code. How are you deploying it to the robot?

When you say you "switch over to the Classmate", what exactly does that mean?

[Team3763 Adam]

I have a Host Computer with LabVIEW downloaded onto it, and the Host computer is what I use for programming. I then deploy the code by pressing the right-facing arrow on-screen. Switching over to the Classmate I mean unplugging the Host computer (Ethernet chord) and plugging into the Classmate (again with an Ethernet chord).

[Mark McLeod]

That would be bad, since the white arrow only runs in debug mode and automatically shuts down the cRIO code when your laptop disconnects.
Rebooting the cRIO restores previous code, which obviously is a two motor version.

Either get a second Ethernet cable and go through a switch, so they can both remain plugged in, and/or download the code permanently.

[Team3763 Adam]

We tried reversing the PWM cables, and our battery has full volts.

However, we have NO lights on the Sidecar, and it IS the one provided this year.

That being said, 2 of our 4 motors work properly. As if they were "pre-programmed"

[Team3763 Adam]

If you go to the Project Explorer -> build specifications -> FRC Robot Boot-up deployment and right click Boot-up Deployment, you should see an option "deploy." Would this work to permanently deploy the code onto the cRIO? If not, is there a way to PERMENANTLY deploy any new/changed code to the cRIO while using a Host computer?

[Alan Anderson]

Originally Posted by Team3763 Adam

However, we have NO lights on the Sidecar, and it IS the one provided this year.

No lights would be bad.

Do you have 12 volt power connected to the Digital Sidecar's power input from a 20 amp circuit on the Power Distribution Board? You should. There is enough leakage through the signals from the cRIO to power a couple of PWM outputs, but you're not supposed to rely on that accident.

To permanently load code to the cRIO, "Build" and then "Run as startup". There's really no use for the "Deploy" command in that popup menu.

[Mark McLeod]

Originally Posted by Team3763 Adam

However, we have NO lights on the Sidecar, and it IS the one provided this year.

The Digital Sidecar needs to get it's power from a 12v connection on the Power Distribution Panel wired to one of the white wago connectors that then plugs into the Digital Sidecar.

The ribbon cable does trickle enough power to maybe run a couple of the PWM outputs (unreliably).

[mswalker]

If you installed everything from the LabVIEW USB you should have the FRC Driver Station program on your host computer. You can start that and run it in place of the ClassMate. If you are plugging your ethernet cables into the Wireless Bridge, you can plug both your host and classmate in at the same time. (Just make sure your host has a unique IP address ie not 10.te.am.6 or 10.te.am.5)