{"id":54,"date":"2008-12-01T13:57:37","date_gmt":"2008-12-01T18:57:37","guid":{"rendered":"http:\/\/chrismeyer.org\/wordpress\/?p=54"},"modified":"2008-12-01T13:57:37","modified_gmt":"2008-12-01T18:57:37","slug":"labview-crio-real-time-system-manager","status":"publish","type":"post","link":"https:\/\/chrismeyer.org\/wordpress\/?p=54","title":{"rendered":"LabVIEW cRIO Real-Time System Manager"},"content":{"rendered":"<p>If you are running LabVIEW and a Compact RIO ( cRIO ) controller, you may need to use the system manager to view your memory or processor usage at one point or another.\u00a0 The only difficulty is that LabVIEW auto-fills the machine name and no port number!<\/p>\n<p>To get to the system manager, open up your <strong>project <\/strong>(not the individual VI you are running).\u00a0 From the project menu, click<\/p>\n<p><code>Tools -&gt; Real-Time Module -&gt; System Manager<\/code><\/p>\n<p>Once System Manager Opens, you&#8217;ll have:<\/p>\n<div id=\"attachment_55\" style=\"width: 250px\" class=\"wp-caption aligncenter\"><a href=\"http:\/\/chrismeyer.org\/wordpress\/wp-content\/uploads\/2008\/12\/system-manager.jpg\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-55\" class=\"size-medium wp-image-55\" title=\"NI cRIO System Manger\" src=\"http:\/\/chrismeyer.org\/wordpress\/wp-content\/uploads\/2008\/12\/system-manager-240x300.jpg\" alt=\"NI cRIO System Manger\" width=\"240\" height=\"300\" srcset=\"https:\/\/chrismeyer.org\/wordpress\/wp-content\/uploads\/2008\/12\/system-manager-240x300.jpg 240w, https:\/\/chrismeyer.org\/wordpress\/wp-content\/uploads\/2008\/12\/system-manager.jpg 512w\" sizes=\"auto, (max-width: 240px) 100vw, 240px\" \/><\/a><p id=\"caption-attachment-55\" class=\"wp-caption-text\">NI cRIO System Manger<\/p><\/div>\n<p>The first thing to do is to enter the Machine Name \/ IP Address.\u00a0 This is the IP of the cRIO that you are trying to communicate with, in this case my IP Address is actually &#8220;10.0.0.2&#8221; rather than the auto-filled value.\u00a0 If you use the project name as was automatically inserted <strong>it will not work!<\/strong><\/p>\n<p>The next step is to configure the port number, in this case I&#8217;m using port &#8220;3363&#8221;, again this value is empty by default and will not work!\u00a0 You may be using a different port, but I&#8217;m pretty sure that 3363 is the default, leave a comment below if it&#8217;s not.<\/p>\n<p>Next select options you are interested in*** on the Resources, VIs, and Alerts tabs below.\u00a0 You can now click &#8220;Start Monitoring&#8221; and you should be off an running.<\/p>\n<p>*** One very important note, if you selected a low Update Interval (every few seconds) you are very likely going to see high processor usage, this is normal as the cRIO has to use extra clock time to send you statistics, try lowering your update interval to see a more normal usage when just the VI is running. ***<\/p>\n","protected":false},"excerpt":{"rendered":"<p>If you are running LabVIEW and a Compact RIO ( cRIO ) controller, you may need to use the system manager to view your memory or processor usage at one point or another.\u00a0 The only difficulty is that LabVIEW auto-fills the machine name and no port number! To get to the system manager, open up [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-54","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/54","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=54"}],"version-history":[{"count":1,"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/54\/revisions"}],"predecessor-version":[{"id":56,"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/54\/revisions\/56"}],"wp:attachment":[{"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=54"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=54"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/chrismeyer.org\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=54"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}