02-18-2012 02:23 PM
Hello Community!
I'm very excited to join a community that is centered around Robots. (I'm in love with robots!)
Anyway, my team and I are having problems with finishing the 2012 Robot Project (Simple Motor Control). We have everything we need installed from the USBs - all the updates and everything. I'm my teams lead programmer and everytime I try to finish the project, it stops and crashes. An error pops up.
The part I get stuck on is where I have to put the Start Communication and Stop Communication boxes into the Block Diagram. I've tried to recover the files but once they're "recovered", only the Front Panel comes back. The Block Diagram is nowhere to be found.
I'm stuck right now, so please help me out. Any comments will be helpful.
Thank you!
(One other question: Is it possible that I could transfer LabVIEW to another lap top and I'd still be able to program our robot from that lap top? Furthermore, can I still program without being connected to the RT CompactRIO Target!)
02-20-2012 09:04 AM
Hey,
Did you install the updates listed here:https://decibel.ni.com/content/docs/DOC-20147? It sounds like their was an installation issue with the LabVIEW Update for FRC. Do you have any antivirus software running - if so turn it off. Do you have administrator priviledges on the PC you are installing LabVIEW on?
To answer your second question. You can use another computer to program with LabVIEW. You don't need to be connected tot he cRIO to work on your program - just to deploy it to the cRIO and test it.
02-21-2012 09:30 AM
Thank you very much Kevin_F for your input. Your advice was helpful.
After fixing our Robot Project issue, I've managed to run into another problem. I'm to the point where I'm able to test the motors, but I can't seem to get it running. The motors do not turn or respond at all. Everything is connected properly and the cRIO is downloading my commands. However, the motor isn't responding at all.
Do you have any advice concerning that?
02-21-2012 09:39 AM
Hey,
There are a couple of other threads on here that have other teams debug steps for this issue but so summarize the major debug steps-