Missing Files?

[Garii]

Rescently, While tring to build code for our FIRST robot. I ran into some issues with labview that i havent been able to adress.

at first it started as a buld problem. the "menus" directory was missing files (.clt i think) in subdirectories such as "math" and "signal processing". I corrected this error by importing these from the "old_menus" directory thinking that the program had simply been terminated while moving directories. The build did in fact complete. but im faced with another problem

now when i try to deploy the code as start up to the CRIO it fails with the error "CRIO Startup Deployment(failed)"

im thinking these problems are related
and im considering reinstalling labview fresh.
suggestions?

[Greg McKaskle]

at first it started as a buld problem. the "menus" directory was missing files (.clt i think) in subdirectories such as "math" and "signal processing". I corrected this error by importing these from the "old_menus" directory thinking that the program had simply been terminated while moving directories. The build did in fact complete. but im faced with another problem

now when i try to deploy the code as start up to the CRIO it fails with the error "CRIO Startup Deployment(failed)"

I wonder if the build was an error or the silly warning about file name collisions where it copies library files and it really isn't an issue. Just ignore the Warning.

When you say you corrected it by importing from the old_menus, directory, what do you mean? What steps did you take?

When the deployment fails, is there any other information? I don't remember for sure, but I thought there was a dialog left open that detailed the issues.

I don't really know that a reinstall is needed unless you think that you've truly deleted things from the vi.lib directory. If so, you may just try a repair. I don't know that it saves any time, but you should be careful with any of these approaches as it is a point where you can lose work.

Greg McKaskle

Greg McKaskle

[Garii]

When you say you corrected it by importing from the old_menus, directory, what do you mean? What steps did you take?

When the deployment fails, is there any other information? I don't remember for sure, but I thought there was a dialog left open that detailed the issues.

i found the ctl files i needed were in this directory. all i did was append the "menus" directory to "menu_broken" and renamed "menus_old" to "menus"

when the deployment failed i was unable to bring up any other info. it simply told me the deployed had failed. i searched for logs on it but didnt find any.

however the filename collisions you mented WERE an issue, but it seems that wasnt just it. I ignored the file name collisions and when i attemped to build i would get the error something similar to "C:\program files\... yada yada ...\menus\signal processing\somefile.ctl is missing" then it would suggest i replace forward slashes with backward slashes if im running OSX...Im not... so its a pretty useless suggestion. All i did was search my machine for the files and i found them in the "menus_old" directory

[Garii]

Just to follow up
The exact Error message I recieved is as follows

FRC Robot Boot-up Deployment (failed to deploy)
it apears in the deploy dialog box, as one of the task its has completed. (ie that lil box that apears when you deploy code)

[Garii]

Hello, if this thread is still alive I'm still having the issue with the FRC startup error. Reinstalling or repairing labview had no effect and the error is still apearent. I'm going to try deploying code from anouther backup computer and see what we get but this may be Crio problem all together. That concernes me

[Mark McLeod]

Was your code moving at all from PC to PC?
In other words created on one machine, then moved to another?

Can you create a brand new default Basic or Advanced Framework (with no changes) and successfully deploy it, or does that fail the same way?

[Garii]

Originally Posted by Mark McLeod

Was your code moving at all from PC to PC?
In other words created on one machine, then moved to another?

Can you create a brand new default Basic or Advanced Framework (with no changes) and successfully deploy it, or does that fail the same way?

I wish I could have read this sooner

Yes, moving the code over to a different framework DOES work.
However only when using the BASIC framework. Moving to the ADVANCE framework caused the error to reapear.

Does labview use a universal FRC startup config for the ADVANCED robot framework?

Maybe BASIC and ADVANCED have seperate bootup config files?

in anycase. thanks to everyone who helped resolve this problem. I'll Do some digging and see why the FRC bootup deployment doesnt work in the Advanced Framework. Just for futur refference

Also on a side note this came just as we updated the software. maybe a bug in the update.

Regards, Jared

[Mark McLeod]

Originally Posted by Garii

Also on a side note this came just as we updated the software. maybe a bug in the update.

It's possible you were caught by the software update changing vi's you were using and your project still trying to use old versions of those vi's.
The Advanced Framework may use the same vi, but both the new and old versions may be getting compiled together causing a conflict.