|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: Crio Not Taking Code (Different Problem)
"Deploy" can mean different things based on who's saying it, what tool they're using, and what they're thinking when they say it. You might be doing something subtly incorrect, or even wildly incorrect for what you want to have happen. Please tell us exactly what you're doing when you try to deploy -- which buttons you're clicking, what keys you're pressing, how long you're waiting, that sort of detail.
|
|
#2
|
|||
|
|||
|
Re: Crio Not Taking Code (Different Problem)
Im am working with Elliot. We have found another issue. Every once and a while an message woud come up the an I/O unit was not install properaly
|
|
#3
|
|||||
|
|||||
|
Re: Crio Not Taking Code (Different Problem)
That just means that the optional Cypress board is not plugged in.
It's meaningless to you if you don't use it. |
|
#4
|
|||
|
|||
|
Re: Crio Not Taking Code (Different Problem)
so then why would it give us that error message?
|
|
#5
|
|||||
|
|||||
|
Re: Crio Not Taking Code (Different Problem)
The message tells you that the I/O unit is not connected. You will see it if the I/O unit is not connected. If you don't have the I/O unit connected, the message is not describing an error; it is describing an expected condition.
|
|
#6
|
|||||
|
|||||
|
Re: Crio Not Taking Code (Different Problem)
If you were using the Cypress board for IO, then it would be important to you to know you forgot to plug it in.
The Driver station can't tell if we want it to be there or not, so it just tells us when the Cypress isn't connected and lets us worry about if that's a problem or not. Last edited by Mark McLeod : 24-06-2011 at 08:53. |
|
#7
|
|||
|
|||
|
Re: Crio Not Taking Code (Different Problem)
so how do we fix the problem of the code not staying on the crio
|
|
#8
|
|||||
|
|||||
|
Re: Crio Not Taking Code (Different Problem)
We can't tell you what to fix if you don't give us some details about how it's going wrong.
|
|
#9
|
|||
|
|||
|
Re: Crio Not Taking Code (Different Problem)
We download the C++ program to the robot and reboot it with the clam. When it turns back on the robot shows no code
|
|
#10
|
|||
|
|||
|
Re: Crio Not Taking Code (Different Problem)
Quote:
Have you checked the console? Is the FRC_UserProgram.out ending up on the cRIO in /ni-rt/system/ as expected? |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|