VIRTUAL INSTRUMENTS BEYOND THE PERSONAL COMPUTER
• Recently, commercial PC technologies have begun migrating into embedded systems. Examples include Windows CE, Intel x86-based processors, PCI and CompactPCI buses, and Ethernet for embedded development. Because virtual instrumentation relies so heavily on commercial technologies for cost and performance advantages, it also has expanded to encompass more embedded and real-time capabilities.
• For example, LabVIEW runs on Linux as well as the embedded ETS real-time operating system from VenturCom on specific embedded targets.
• The option of using virtual instrumentation as a scalable framework that extends from the desktop to embedded devices should be considered a tool in the complete toolbox of an embedded systems developer.
• A dramatic technology change example that affects embedded systems development is networking and the Web. With the ubiquity of PCs, Ethernet now dominates as the standard network infrastructure for companies worldwide.
• In addition, the popularity of the Web interface in the PC world has overflowed into the development of cell phones, PDAs, and now industrial data acquisition and control systems.
• Embedded systems at one time meant stand-alone operation, or at most interfacing at a low level with a real-time bus to peripheral components.
• Now, the increased demand for information at all levels of the enterprise (and in consumer products) requires you to network embedded systems while continuing to guarantee reliable and often real-time operation.
• Because virtual instrumentation software can combine one development environment for both desktop and real-time systems using cross-platform compiled technology, you can capitalize on the built-in Web servers and easy-to-use networking functionality of desktop software and target it to real-time and embedded systems.
• For example, you could use LabVIEW to simply configure a built-in Web server to export an application interface to defined secure machines on the network on Windows, and then download that application to run on a headless embedded system that can fit in the user's hand.
• This procedure happens with no additional programming required on the embedded system. You then can deploy that embedded system, power it, connect to the application from a remote secure machine via Ethernet, and interface to it using a standard Web browser.
For more sophisticated networking applications, you can graphically program TCP/IP or other methods with which you are already familiar in LabVIEW and then run them in the embedded system.
• Recently, commercial PC technologies have begun migrating into embedded systems. Examples include Windows CE, Intel x86-based processors, PCI and CompactPCI buses, and Ethernet for embedded development. Because virtual instrumentation relies so heavily on commercial technologies for cost and performance advantages, it also has expanded to encompass more embedded and real-time capabilities.
• For example, LabVIEW runs on Linux as well as the embedded ETS real-time operating system from VenturCom on specific embedded targets.
• The option of using virtual instrumentation as a scalable framework that extends from the desktop to embedded devices should be considered a tool in the complete toolbox of an embedded systems developer.
• A dramatic technology change example that affects embedded systems development is networking and the Web. With the ubiquity of PCs, Ethernet now dominates as the standard network infrastructure for companies worldwide.
• In addition, the popularity of the Web interface in the PC world has overflowed into the development of cell phones, PDAs, and now industrial data acquisition and control systems.
• Embedded systems at one time meant stand-alone operation, or at most interfacing at a low level with a real-time bus to peripheral components.
• Now, the increased demand for information at all levels of the enterprise (and in consumer products) requires you to network embedded systems while continuing to guarantee reliable and often real-time operation.
• Because virtual instrumentation software can combine one development environment for both desktop and real-time systems using cross-platform compiled technology, you can capitalize on the built-in Web servers and easy-to-use networking functionality of desktop software and target it to real-time and embedded systems.
• For example, you could use LabVIEW to simply configure a built-in Web server to export an application interface to defined secure machines on the network on Windows, and then download that application to run on a headless embedded system that can fit in the user's hand.
• This procedure happens with no additional programming required on the embedded system. You then can deploy that embedded system, power it, connect to the application from a remote secure machine via Ethernet, and interface to it using a standard Web browser.
For more sophisticated networking applications, you can graphically program TCP/IP or other methods with which you are already familiar in LabVIEW and then run them in the embedded system.
1 comment:
Hi, & good day to you, Yokara.
I'm Abasster & I contacted you on SocialSpark. Splendid blog you have here. I know coz I've been following your blog for months. I hope to come here more often. This post sounds complex to me. :-\ You see, I'm still just beginning to learn electronic circuits on the weekends.
By the way, I just posted a new batch of voyage articles & a Forbidden City Palace Museum Historical Artifacts Part I slide show on my blog at http://voyage.aimvotal.com/
I hope that you may want to take a look at them. Please do leave a comment or two to help me improve my blog. Thanks in advance. Keep in touch.
Abasster
P/s: I hope to see you more over at my voyage blog, ok.
Post a Comment