New Programming Core needs help with simple motor control

Technical NI LabVIEW
#8

The program you posted may work, but is not the officially supported way of programming the cRIO (last I heard). If you have been able to run the code, does the Motor Output indicator change in response to the control value? Since the WPI Robotics libraries are installed, there should be a cRIO project option in the Project wizard. Running the program from a normal VI and with inputs from a normal VI control may work correctly, but it has been too long for me to remember definitively. I would suggest creating the cRIO project, including the appropriate code there, and downloading and running the code to see if it works.

Posting as much information as you can (pictures included) will help speed up the process of figuring out what is not working. PM me if you have any questions about this post.

EDIT: Just making sure, you are enabling the Driver Station before you test the motor, right? (no offense intended at all)

#9

As mentioned above, you should either run the template code or an example. All of these have the framework code for the safety protocol.

Also, that sure looks like a 9472 in slot 1 of the cRIO. It shouldn’t stop the motors from working, but neither it nor the intended analog module can work if they are swapped.

Greg McKaskle

#10

Ok, so I have created a project that has the template code. I have followed the instructions found here. https://decibel.ni.com/content/docs/DOC-14723 In addition to completing the simple motor control vi and running it. I have also packaged the entire template project and deployed it to the Crio. I then open up the driver station that installs with the update and attempt to run the code in test mode and manually changing values.

The problem is that the Victor 888’s are not receiving pwm signal (yellow blinking light). I have done all these same things to the other test rig with the jaguars and its the same problem, no pwm signal (yellow blinking light). Both rigs share none of the same parts and were wired by the same people who wired the robot last year. (In the case of the jaguar robot it was the test rig from last year). All parts have worked before. (In the case of the current rig I am working with that has the Victor 888’s, it has been as soon as a few weeks ago).

Again I am completely new to robotics but not to programming or computers. There has to be some step I am missing. I would think though that if I deployed the Template code to the robot (I used the deploy tutorial, I built the code and deployed as startup) that when it prompts to reboot and after it finishes the reboot that RSL would light up in the disabled mode. Nothing lights up. In fact I have yet to do anything that has enabled me to get the RSL to light up. Attached is pics of what I have been doing.

Also I removed the 9472 and Ill figure out what slot it needs to be in later.




#11

Instead of using the Simple Motor Control example, try loading a new robot project on it. On the welcome screen of LabVIEW, click on the create new FRC robot project button. From there, enter your correct IP address, and see if that code will run.

#12

No offense taken and I am glad you asked this because I am not sure if I am. If you look at the guide above me it doesn’t say that I need to do anything other than deploy the code via the run button and manipulate the variables in the front panel.

Now when I tried to deploy the template code (unchanged other than changing the jaguar to victor in the begin vi) I complied the code and deployed as start up. When I did that I ran the driver station as illustrated in the pic in the post above.

If there is something else I am supposed to do then this may be the step I am missing. I am very new to robotics. Our team is on their 5th season but our programmer left last year and this is my first year on the team. I know programming and computers, but this still has a learning curve. Thanks again for your help.

#13

I did that this morning. I setup a completely different computer with labview. Created the project. Complied the project. Deployed the project to run on startup. It rebooted and still no RSL and even when opening the driver station and going to test mode, there is no change. The good news is driver station obviously reads code on the robot and when I tried redeploying the code again it ask me if I want to continue because there is already an active code running on the robot.

#14

I think I may see the problem. Instead of clicking “Run” from the Simple Motor Control.vi", Open up the “Robot Main.vi” and click “Run Continuously”.

Also, try runing your code with Teleoperated selected on the Driver Station, not Test. The Test function will return values to the test screen, while Teleoperated should control it normally.

#15

18awg wire has plenty of current carrying capacity for the digital sidecar. I suspect that when you used 18awg wire, one of the connectors was clamped on the insulation of the wire, rather then the wire. There may have been some connection, but it wasn’t a good connection. When you switched to 14awg, and redid the connections, all connections were good.

#16

I have tried both run and run continuously for the simple motor control. As for the Robot Main.vi I have not ran the code within Labview. The reason is because I can not run the code within labview and open up the driver station at the same time. I therefore compiled the code deployed the code to the robot to run on start up and then open the driver station.

#17

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

#18

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.

#19

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

#20

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.

#21

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.

#22

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.

#23

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.

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

#24

Teams run LabVIEW and the Driver Station simultaneously all the time. What’s keeping you from doing it?

I therefore compiled the code deployed the code to the robot to run on start up and then open the driver station.

If you’re trying to run the Simple Motor Control example, you must run it interactively. You have to be able to change the front panel control while it is executing in order to change the value being sent to the motor.

If you’re doing a Compile followed by a Run as Startup, then you’re not running the example. You’re running Robot Main, which calls all the other Team Code.

#25

originally, when running lab view, I got an error message about trying to connect to the CRIO when opening the driver station. I assumed they couldn’t both connect at the same time. Since that time I have retried it with success. In fact the last few pics I posted of the driver station was when it was running with lab view open with the robot main open and running continuously. I have tried compiling and run as startup on the example code after changing the variable to a constant of .5 with no success but otherwise I am just running it and manipulating the variable on the front panel of lab view.

#26

The battery voltage is measured using the first slot and the analog module. Until that is installed, the DS will not know the voltage.

The bigger cRIO and smaller cRIO are not that different. The processor in both is a 32 bit Freescale processor. The performance is slightly different due to cache size, the RAM was increased, and physical elements like the power connector, second enet port, and dip switches were removed.

The imaging tool can read the dip switches just to help diagnose broken ones – happens more often than you’d think. For the 4-slot, it can also set them. The one begin set determines whether the serial port is used to output console print statements or used to communicate with another serial device, like a sensor.

As Alan said, simply pushing run on the VI will be the faster way to run your VI. Be sure that the VI contains the safety info. If you run a lower level VI, it will indeed run, but without established communications with the driver station, the outputs will be disabled and that safety feature can cause confusion.

There should be no issue running DS and any other development environment or tool. If you get an error, please post it so I can better understand what is going on.

To make further progress on getting your motors to run, I’m with Joe. Focus on getting the RSL LED to light up or blink. I’d start with the cable, but it could be the digital breakout board. If that doesn’t fix it, work backwards and try another digital module. Also, remove the module in the cRIO and inspect that the backplane pins aren’t bent and don’t have debris shorting them. Also make sure that the module is fully inserted and the side clips engage. The imaging tool shows that it is recognized, so I doubt that there is an issue with engagement or pins.

Greg McKaskle

#27

Just wanted to let everyone know that the problem was the digital sidecar. Here is what happened. I had no RSL light for the test robot that we had set up. After verifying that the code was right I started swapping parts out. When I swapped out the digital sidecar I also swapped the power for it. The power cable was not properly installed so the sidecar did not get enough voltage. The test rig that I brought home to work on had the digital sidecar that I took off the test robot. That sidecar is bad and did not work. When I got back to school and worked on the test robot I simply adjusted the power cable in the breaker panel and the sidecar started working. I also replaced the side car on the test rig and it too started working. Very unlikely circumstances lead to a very troubling problem. Thanks to everyone who helped figure it out.