10-24-2017 12:32 PM
The SW is pretty standard. The cRIO FPGA acquires the input signal and the RT target does some computation and passes some values to the HMI SW via network shared variables (NSV). The use of HMI is optional for our use case.
I tried several built options, updating the cRIO SW, deploying the NSV during the start of windows HMI SW (using the built options in the HMI build specification), but always without success.
Any help would be much appreciated.
Thank you.
11-27-2017
07:36 AM
- last edited on
01-09-2025
03:47 PM
by
Content Cleaner
Hi there, this sounds somewhat familiar to issues I have had in the past. Have you got all the required software installed on your Rio? It is worth finding the device in MAX and Add/Remove Software and check for network related software, particularly "Network Variable Engine".
The NSV updating only once is interesting, what are these values? Can you verify that it took a new measurement, or could it have been the last measurement that was taken? In the past I have had it where NSV update once (i.e. go from some default indicator value) to the last measurement that was read (it said something was 400deg C, and it definitely wasn't...).
Also can you try writing something really basic and deploying that as an executable? Could just be a random number written to an NSV or something. If that works, then you can be sure the software (or lack thereof) isn't the issue. I couldn't get my program to run on startup properly so had to find a less optimal solution, but deploying something small seemed to work, it was when I deployed my whole program with lots of NSV (70+ perhaps) that I couldn't get it started, not sure how many is too many per se.
So to summarize:
Hope this helps.
Edit: Found a couple of links for you to have a look at just in case
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YIDuCAO&l=en-US
http://www.ni.com/white-paper/5715/en/
http://www.ni.com/tutorial/9900/en/