Constant failure to deploy

[Scott_the_Idabot]

The "target destination directory" in the build spec is correct, i.e. has no /c in the path.   The /c I was referring to is in the "local destination directory".   I guess the real question is where did the /c in the .ini file path come from?

[MarkBlack]

Its very possible the Target Destination Directory was changed at some point, and therefore the path in the INI file was changed.  The INI is updated during deployment but because the deployment failed the INI file was never being updated (a bad cycle to be in ).  This issue could have also been resolved by reimaging the cRIO which would place a default INI file (with correct paths) on the controller.  This being said by looking at the INI file you got the core of the issue, and this will help everyone down the line who is troubleshooting a similar problem.

Thanks!

Mark

NI FIRST Support

[mgurgol]

I am also receiving the failure to deploy issue.  I received it after re-imaging the cRio, so I would assume that it is not the .ini file.

If I rebuild and click the disconnect and remove buttons should it correct the problem?

Re: FTP

If I wanted to FTP to the cRio, I would copy the entire contents of my build directory on the PC to the c:\ni-rt\startup directory?

As background, I have been working on this project since update 3a.  I have been successfully able to deploy it until yesterday.  Yesterday I added control for our final two servos (open, set angle, close).  After that the system failed to deploy.