![]() |
Re: No communication?
10.32.72.2
i have already gone through all of this many times. like way to many. but nothing is working properly. |
Re: No communication?
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. |
Re: No communication?
sorry...
Have you tried booting it in SAFE MODE? |
Re: No communication?
its fine, im just getting frustrated, and yes safe mode and everything
|
Re: No communication?
ok my one problem is that i can't connect to my crio, at all. :/
|
Re: No communication?
The only other suggestion I can think of right now is to try another ethernet cable... perhaps it is a bad cable.
|
Re: No communication?
Quote:
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 Quote:
Also, regarding the use of MAX. If you had really read the manual, you would have noticed this bit of information: Quote:
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 |
Re: No communication?
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.
|
Re: No communication?
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 |
Re: No communication?
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.
|
Re: No communication?
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?
|
Re: No communication?
Quote:
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. |
Re: No communication?
Why didn't I have to do this before? Worked completely fine before i had all these problems?
|
Re: No communication?
5 Attachment(s)
Quote:
So you're at your project window, right? Attachment 12471 Following Alan's instructions: Quote:
Quote:
When it's done, it should look like this: Attachment 12474 Quote:
Quote:
|
Re: No communication?
ok. thats weird. ill get it working later. but i never had to do that before. it just sorta. worked right away. O_o
|
| All times are GMT -5. The time now is 20:09. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi