we have done the updates to the driver station and set our network up to spec. we have also formatted the CRIO with the 2011 imaging tool and image.
however when we go to use the same connection (ethernet) to deploy code we get a comms error right at the start. everything seems to be in order. the Crio is not in safe mode and everything looks good.
anything i might have missed??
if anyone else has the same problem or a fix it would be great
Are you using a crossover cable or straight through?
I know when we went to reimage the cRio this weekend we tried a straight through cable and it would not communicate with the cRio, but once we found the proper cross over cable, the cRio was instantly recognized by the imaging tool on our laptop.
(I am on the same team as jackdawg^^^^^^^^^^^^^^^)
we have tried a PLETHORA of cables, upwards of 15, so we have reasoned out that it is most likely not one of the cables.
If you mean you entered your team number when you reformatted/reimaged the cRIO, that just told the cRIO what its IP address should be. It didn’t give any information to LabVIEW about that address.
unless there is somwhere else to tell it the team number that i am unaware of.
You also need to tell LabVIEW what IP address the cRIO has. When you created the project, there was a brief opportunity to enter that information. If you look at the Project Explorer window, the address should appear in parentheses at the right of the “RT CompactRIO Target” line (i.e. 10.13.07.02). If it’s set to something like 10.xx.yy.02 instead, right-click the line and change the properties to the correct value.
Your programming computer should also have an IP address somewhere in the range 10.13.07.06 to 10.13.07.254, with 10.13.07.06 being the usual choice.