Instrument Studio<\/strong>, a focus on hardware and performing measurements, and the ability to deploy to a personal cloud.<\/p>\n\n\n\nPractical Workflow Demonstration with Nigel<\/h2>\n\n\n\n To demonstrate the capabilities of Nigel during the webinar, NI Solutions Marketer David Prida set up a practical application example. In the example scenario, he was acting as an engineer who was tasked to measure output ripple from a buck converter.<\/p>\n\n\n\n
For the first prompt, he asked Nigel to explain measuring output ripple from a buck converter. As a result, Nigel responded with an in-depth answer filled with well organized information. It explained what output ripple is and how to measure it, providing a step-by-step guide<\/strong> as well as practical tips and reference images with further reading suggestions.<\/p>\n\n\n\nThe second prompt asked Nigel for help with recommending a PXI scope to assist with that application. Nigel has an extensive knowledge<\/strong> of NI hardware, and provided practical recommendations alongside a list of key selection criteria in response to the query.<\/p>\n\n\n\nThe third and final prompt in the example scenario asked Nigel for a LabVIEW example of performing that measurement testing the knowledge of NI software in addition to hardware. In response, Nigel was able to give a specific function name, describe the VI, and provide a diagram<\/strong>. To take things a step further, David asked Nigel how to augment\/modify the code for vpp measurement.<\/p>\n\n\n\nThis demonstration showcased Nigel\u2019s vast knowledge of NI\u2019s hardware and software, highlighting its ability to enhance testing workflow productivity!<\/p>\n\n\n\nFEATURED QUESTIONS AND ANSWERS<\/h3>\n\n\n\n Question<\/strong>: \u201cCan Nigel access my own VIs and codes to suggest improvements?\u201dAnswer<\/strong>: Any normal VI in your project can be described by Nigel. It currently only uses a single VI if you prompt with \u201cdescribe vi\u201d, but the ability to use more context from your project is a future feature.<\/p>\n\n\n\n<\/p>\n\n\n\n
Question<\/strong>: \u201cCan Nigel write Python code, or code for an instrument driver?\u201dAnswer<\/strong>: Nigel (in LabVIEW 2025 Q3) can not write code for those programs yet, but that capability is in the works.<\/p>\n\n\n\n<\/p>\n\n\n\n
Question<\/strong>: \u201cIs Nigel coded for other languages?\u201dAnswer<\/strong>: Yes! Nigel currently supports 95 languages.<\/p>\n\n\n\n<\/p>\n\n\n\n
Question<\/strong>: \u201cHow is Nigel trained, if not with customer data?\u201dAnswer<\/strong>: Nigel is not \u201ctrained\u201d, it is \u201ctaught\u201d \/ \u201caugmented\u201d. Trained models may be used in the future with NI\u2019s data.<\/p>\n\n\n\n<\/p>\n\n\n\n
Question<\/strong>: \u201cCan Nigel help in code with other vendor hardware?\u201dAnswer<\/strong>: Base models do have vast amounts of knowledge of the world in general, but if you are asking for specifics about things outside of NI\u2019s walls, it may be inaccurate.<\/p>\n\n\n\n<\/p>\n\n\n\n
Question<\/strong>: \u201cWhat is the advantage of Nigel over an LLM such as ChatGPT or Gemini?\u201dAnswer<\/strong>: First, the types of answers that Nigel gives. Nigel focuses on the specific domain instead of trying to solve things generally. Second, the facts that have been used for Nigel are specific to test and measurement. As Nigel continues to get smarter, it will get more insights. NI is also holding themselves to a higher standard for answer quality than other LLMs<\/p>\n\n\n\n<\/p>\n\n\n\n
Question<\/strong>: \u201cCan Nigel produce documentation?\u201dAnswer<\/strong>: Yes! Nigel can produce documentation for code that doesn\u2019t have any.<\/p>\n\n\n\n<\/p>\n","protected":false},"excerpt":{"rendered":"
According to Moore’s Law, which was first observed in 1965, the number of transistors in semiconductor chips doubles every two years. This pales in comparison to the rapid explosion of Artificial Intelligence (AI) tools, which have been experiencing exponential growth at 2-3 times that rate! In a recent webinar, engineers from Emerson\/NI gathered to discuss […]<\/p>\n","protected":false},"author":1,"featured_media":3322,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[8],"tags":[35,65,229,393,437,1005,918],"class_list":["post-3319","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-national-instruments","tag-ai","tag-artificial-intelligence","tag-emerson","tag-national-instruments","tag-ni","tag-nigel","tag-test-and-measurement"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.apexwaves.com\/blog\/wp-json\/wp\/v2\/posts\/3319","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.apexwaves.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.apexwaves.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.apexwaves.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.apexwaves.com\/blog\/wp-json\/wp\/v2\/comments?post=3319"}],"version-history":[{"count":10,"href":"https:\/\/www.apexwaves.com\/blog\/wp-json\/wp\/v2\/posts\/3319\/revisions"}],"predecessor-version":[{"id":3346,"href":"https:\/\/www.apexwaves.com\/blog\/wp-json\/wp\/v2\/posts\/3319\/revisions\/3346"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.apexwaves.com\/blog\/wp-json\/wp\/v2\/media\/3322"}],"wp:attachment":[{"href":"https:\/\/www.apexwaves.com\/blog\/wp-json\/wp\/v2\/media?parent=3319"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.apexwaves.com\/blog\/wp-json\/wp\/v2\/categories?post=3319"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.apexwaves.com\/blog\/wp-json\/wp\/v2\/tags?post=3319"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}