update vi on cRio

[Steffen01]

Hello,

I updated some vi on a compact Rio, but it seems, it does not take the changes?

What I did, in the Labview project, edit said vi on the cRio, saved. But it seems, when I run the main vi on the PC host, the changes in the subvi did not come through. What to I have to do?

Thanks!

[JensG69]

Did you build a new rt-executable, deployed that onto the cRIO and restart your cRIO?

Jens

[crossrulz]

---

@Steffen01 wrote:

What I did, in the Labview project, edit said vi on the cRio, saved. But it seems, when I run the main vi on the PC host, the changes in the subvi did not come through. What to I have to do?

---

RIght-click on the target in the project and select "Deploy".  Remember that the cRIO is not on your computer.  It is its own system that can run completely independent of your system.  So simply making updates in the project does not update the cRIO.

[Steffen01]

I did not re-compile the run time.

Have to try deploy again, I think I only deployed the vis, not the target.

I have to put more variables in to check on the PC host main vi anyway, see what happens.

[Steffen01]

it says there is a RT target running already, this would be the previous compiled version

[jwscs]

yes, i presume, that you have set the "run as startup" option

when you want to deploy a new build version, it will show you wether something is still running and give you the option to stop it and deploy,

you can of course unset the "run as startup" and reboot the crio.

the quick and dirty way i came up to not have the startup app, is to ssh into the crio, and delete the following, then restart.

rm -r /c/ni-rt/startup/data
rm -r /c/ni-rt/startup/project
rm /c/ni-rt/startup/startup.*

you will then get an error message when you deploy a build, but that is ok.

NOTE: mess with the linux on the crio at your own risk, you should know a little commandline fu 😉

[Steffen01]

yes, you can then to select to stop. Then deploy again. Then I had to reboot it until the main vi would run it. Hope it did not fall back to an older version.

There are some PID outputs that don't make sense and the PIC vi is on the cRio.

[Steffen01]

do I have to send a nother bitfile? But I only updated some vis for the real time target? Its in hybrid mode.

[jwscs]

i presume you have set your entry vi correctly in the build configuration.

my steps are (all via right click on the build configuration):

clean, build, deploy, run as startup (i think you can omit the deploy, but i do it anyways)

then the crio restarts and executes you entry vi.

but it sounds to me, as if you run the vis from your development environment,

and not standalone.

then it might be good to disable the auto run.

the develompment environment should deploy all needed vis (not the ones you call asynchronously) when executing a vi,

but since i almost never use it this way i might be wrong.

[Steffen01]

yes, from the development environment. Dont want to recompile just yet, just try a few changes. Most are on the PC host, but some on the cRio, but on the real time side, not the FPGA. No idea, I read through the reference guide, there was something on network variables. Put them on host PC as well, then it should get them. This would be ok for slow ones I guess, logging once per second. But would be good for testing and maybe the variable engine is stuck