View Full Version : No communication?
Alright. I am the tech officer for the Carroll County Robotics team. I am having a horrible time working on the programing this year. It mostly started when I reinstalled LabView for the newest version this year and had to install LabView real-time to our cRio. To do so I formated the cRio and set it up with the same settings as before when I got to it. I proceded to Install LabView Real-Time and work on the programing again. From the Computer we are working on I can see the actual cRio from the computer and i have the router set up to communicate. But im having no luck communicating with the actual robot and cRio. I have set up the computer with a hard wire set up from the computer to the cRio and deploy a code to the cRio with no avail. I am getting a error on the cRio program saying inconsistant IP and when I try and deploy a code to it it gives me an error telling me that it can't communicate with the cRio. I have changed the wires many times and used the crossover cable to try and work things out and have had no success. If anyone can help. I would greatly appreciate some tips. :confused:
Alan Anderson
21-02-2012, 16:30
I am getting a error on the cRio program saying inconsistant IP and when I try and deploy a code to it it gives me an error telling me that it can't communicate with the cRio.
I don't recognize "inconsitant IP". Can you give us the actual text of the error, and tell us exactly what steps you take before you see it?
Hjelstrom
21-02-2012, 16:58
Did you set your team number correctly? Someone at our practice on Saturday had a similar problem and they had a typo in their team number or in the ip address (I can find out exactly what the fix was later if this doesn't help).
Alright. i know i haven't misspelled our team number. and the error doesn't have a specific text. down at the bottom of the program it just simply says inconsistant IP.
Alan Anderson
21-02-2012, 22:52
In what program do you see this message?
Please tell us exactly what you're doing, step by step, in as much detail as you can manage.
Ok so I formated the cRio and set up the ip adress for it using Measurement & Automation Explorer found in the national instruments. I followed the instructions to do so from this website: http://zone.ni.com/devzone/cda/tut/p/id/7191
When I plugged in the IP adress on Measurement & Automation Explorer i saved and refreshed the max on the cRio and Down at the bottom of the Measurement & Automation Explorer I have a message stating that i have inconsistant IP's. Im using a static IP adress and all the settings i remember.
Alan Anderson
22-02-2012, 10:59
Ok so I formated the cRio and set up the ip adress for it using Measurement & Automation Explorer found in the national instruments.
You should not be using MAX.
To format the cRIO and load the proper files onto it for FRC, you need to use the 2012 FRC cRIO Imaging Tool. If you have applied the most recent updates, you will be able to choose the required v43 image. Follow the directions in the Getting Started (http://www.usfirst.org/sites/default/files/GettingStartedwiththe2012FRCControlSystem_RevA.pdf ) document.
Ok so I formated the cRio and set up the ip adress for it using Measurement & Automation Explorer found in the national instruments. I followed the instructions to do so from this website: http://zone.ni.com/devzone/cda/tut/p/id/7191
When I plugged in the IP adress on Measurement & Automation Explorer i saved and refreshed the max on the cRio and Down at the bottom of the Measurement & Automation Explorer I have a message stating that i have inconsistant IP's. Im using a static IP adress and all the settings i remember.
MAX is not the way to do it if you're trying to prepare a cRIO for competition use. Follow this FIRST-specific guide instead: http://www.usfirst.org/sites/default/files/GettingStartedwiththe2012FRCControlSystem_RevA.pdf
(accessible via usfirst.org > FRC > game & season info > kit of parts > control system)
Ok, Thanks a lot. I'll try out using the cRio imaging tool next time we meet. thanks for the advice.
alright i have a even more serious problem, right now i can't connect to the crio at all. i can't set up any ip adresses and nothing is working and im getting rather stressed, please someone help. ::ouch::
MamaSpoldi
01-03-2012, 15:56
When using the cRIO Imaging Tool you should be directly connected to the cRIO. (If it is an 8-slot version, then make sure you are plugged into Port 1). The imaging tool should scan and find the cRIO and then tell you what it modules sees. Does that at least work?
MamaSpoldi
01-03-2012, 16:08
Do you have a 4-slot or an 8-slot cRIO? Are you sure it is getting power (ie. are the lights lighting)?
Did you set the IP address of the laptop you are using to image? Should be 10.32.72.5 (if is driverstation classmate) or 10.32.72.6 (if it is another programming laptop).
everything is working properly. it is a 8-slot cRio. everything is working fine. but when using max and the imaging tool nothing connects at all.
alright. i checked my ip adress and it is set to 10.32.72.6 my crio has a ip of 10.32.72.2 and a subnet mask of 255.255.0.0 and same for my computer.
MamaSpoldi
01-03-2012, 16:12
What is your IP address set to?
You can look at specific instruction in the "How to Configure Your CompactRIO" section of this document:
http://www.usfirst.org/sites/default/files/uploadedFiles/Robotics_Programs/FRC/Game_and_Season__Info/2012_Assets/Getting%20Started%20with%20the%202012%20FRC%20Cont rol%20System_2.pdf
10.32.72.2
i have already gone through all of this many times. like way to many. but nothing is working properly.
We had the problem with the students using MAX on our robot... I don't know where people are getting this information from in the FRC documents to use MAX. It's simply not in anything, and you should NEVER use it.
If you're running into problems, may I suggest starting from step one on https://decibel.ni.com/content/docs/DOC-20204.
It is critical to follow the steps one-by-one. This is a tried and true method of getting your whole control system working. Skipping steps, or doing what you think is right is not the way to go with this stuff. Stick with the manual, read it and follow it like you would if you were told to defuse a bomb.
Once our guys got hold of this document, they had it running within an hour.
MamaSpoldi
01-03-2012, 16:29
sorry...
Have you tried booting it in SAFE MODE?
its fine, im just getting frustrated, and yes safe mode and everything
ok my one problem is that i can't connect to my crio, at all. :/
MamaSpoldi
01-03-2012, 17:01
The only other suggestion I can think of right now is to try another ethernet cable... perhaps it is a bad cable.
ok my one problem is that i can't connect to my crio, at all. :/
dokusou,
Are you using a crossover cable (yellow in this year's KOP), and connecting directly to the cRIO from your PC?
If yes, then...
Have you set your PC's LAN (wired) to:
IP: 10.32.72.6
Subnet: 255.255.255.0
I believe this might be your biggest issue, as you said
everything is working properly. it is a 8-slot cRio. everything is working fine. but when using max and the imaging tool nothing connects at all.
alright. i checked my ip adress and it is set to 10.32.72.6 my crio has a ip of 10.32.72.2 and a subnet mask of 255.255.0.0 and same for my computer.
You're subnet should be 255.255.255.0. The subnet mask is used to separate a single LAN into multiple LANs. Setting this wrong will cause you to have communication problems.
Also, regarding the use of MAX. If you had really read the manual, you would have noticed this bit of information:
Considerations Before Running the cRIO Imaging Tool
Before configuring the cRIO with the cRIO Imaging Tool, you must ensure that the hardware and software are configured properly. You should also ensure you have all of the latest updates, including the latest Utilities update.
Do not use the cRIO Imaging Tool on the cRIO over a wireless connection. If the connection is lost, the data that the cRIO Imaging Tool writes to the cRIO will be corrupted.
Do not use Measurement and Automation Explorer (MAX) to install additional software on the cRIO. MAX overwrites the FRC VIs on the cRIO, which makes the cRIO unusable for the FRC competition. If you use MAX to install additional software on the cRIO, you must use the cRIO Imaging Tool to restore the device to a usable state.
Before running the cRIO Imaging Tool, ensure the SAFE MODE switch on the cRIO is turned off (this only applies to the cRIO-FRC, on the cRIO-FRC II, the dipswitches are only available on the cRIO Imaging Tool). For routine use, do not use the cRIO Imaging Tool when the cRIO is in SAFE MODE.
Please for the sake of humanity, read the documentation, word-for-word. It would most likely had prevented all of this frustrations you have been experiencing. I do know that occasionally things happen, but from everything that I have read here, you have no patience, and you haven't read any of the documentation.
The FRC Control system is now a very complicated system. With complicated systems, one small mistake will break everything. It is important to follow the directions. I run into this issue so much with my team, so my patience is running thin. These people are trying to help you, but you are not providing them with good information.
So here's my real advice.
Start from scratch. Forget all the problems you have already had. Start with the document linked to you multiple times in this thread. Follow them word-for-word.
Sincerely,
Ryan Nazaretian
ok. thanks a bunch. for some odd reason NI has been telling me to use max for the cRio. :/ ill fix it all soon i hope. and im sorry for not reading all the documents. i tried to in the begining and when something didnt work right with that i went to NI and they told me to fix it using one thing. and i assumed it was right. I apologize greatly for being impatient. and me and my teammates greatly appreciate the help. ill try and add better info in later posts. and again. im sorry for all the frustration. and thanks again for all the help.
Greg McKaskle
03-03-2012, 09:00
The application engineers are accustomed to using MAX to inspect the device state and to modify settings. If they are asking you to use it, then by all means, do it. On the other-hand, using MAX incorrectly will introduce unexpected issues.
You made no mention about firewalls. In the past, I borrowed a laptop and spent thirty frustrating minutes trying to get the imaging tool and MAX to see the cRIO. It was due to the firewall, which I was not used to checking for.
Greg McKaskle
Alright, I'll make sure to check all firewall settings. right now im just working on getting the computer to the setting it should be so I'll check that right away. I'm using the directions provided above and using them step by step and double checking my work to make sure everything is set up correctly. Hopefully I can get everything working when we meet tonight. :) thanks everyone for the help.
Alright, so last problem I've ran into. Everything else is fixed. (yay) When deploying my robot project to the cRio I go into LabView and open my project and go to main.vi and right-click and hit deploy like im supposed to. When i do this everything says it works, no errors come up and everything is a-ok. Now when i close out of the VI it has opened my computer looses connection with the cRio and I have to wait for it to reconnect. When its reconnected everything seems ok except the Robot code isn't being found. When i open up a VI normally and hit run at the top of the VI it Says its deployed properly like before but if i close the VI the code stops being read by the driver station. Is this a communication error with the cable im using? (crossover cable(yellow)) or is it simply something i need to do with the imaging tool?
Alan Anderson
30-03-2012, 10:50
Now when i close out of the VI it has opened my computer looses connection with the cRio...if i close the VI the code stops being read by the driver station.
You're describing "running" your code from within LabVIEW. When you close the VI you're running, you stop running the code.
In order for code to run automatically upon powering up the cRIO, you need to build it and load it onto the cRIO with a flag set for it to be run at startup:
Open the "Build Specifications" line in the Project Explorer window.
Right-click the "FRC Robot Boot-up Deployment" line and choose "Build".
Wait for LabVIEW to compile the code into a real-time executable ".rtexe" file.
Right-click the "FRC Robot Boot-up Deployment" again and this time choose "Run As Startup".
Wait for LabVIEW to push the code onto the cRIO. (If you get a message telling you you're about to replace running code, just say Okay, because that's exactly what you are trying to do.)
When prompted, click the button to reboot the cRIO and wait a minute for it to start running the code you just gave it.
Now it'll run every time you turn on the cRIO, whether or not LabVIEW is open on your programming computer.
Why didn't I have to do this before? Worked completely fine before i had all these problems?
Why didn't I have to do this before? Worked completely fine before i had all these problems?
I have no idea how you got away with doing that... What Alan said above is correct.
So you're at your project window, right?
12471
Following Alan's instructions:
Open the "Build Specifications" line in the Project Explorer window.
Right-click the "FRC Robot Boot-up Deployment" line and choose "Build".
12472
Wait for LabVIEW to compile the code into a real-time executable ".rtexe" file.
12473
When it's done, it should look like this:
12474
Right-click the "FRC Robot Boot-up Deployment" again and this time choose "Run As Startup".
Wait for LabVIEW to push the code onto the cRIO. (If you get a message telling you you're about to replace running code, just say Okay, because that's exactly what you are trying to do.)
When prompted, click the button to reboot the cRIO and wait a minute for it to start running the code you just gave it.
12475
Now it'll run every time you turn on the cRIO, whether or not LabVIEW is open on your programming computer.
ok. thats weird. ill get it working later. but i never had to do that before. it just sorta. worked right away. O_o
Alan Anderson
30-03-2012, 13:36
Why didn't I have to do this before? Worked completely fine before i had all these problems?
If it worked completely fine, then the code must have been built and sent to the cRIO at some point. If the "Always run deployed code on startup" option was checked when the cRIO was imaged the first time, either "Deploy" or "Run as startup" would have worked, but it's good practice always to use "Run as startup" just to remove one potential point of confusion.
When you reimage the cRIO, the process erases any previously deployed code. You don't need to build the project again unless you've made changes, but you do need to put the built code into the cRIO's filesystem. The simplest way to do that is to use the "Run as startup" menu command.
vBulletin® v3.6.4, Copyright ©2000-2017, Jelsoft Enterprises Ltd.