MariusG Posted January 19, 2011 Report Share Posted January 19, 2011 (edited) Key Words: Web Instrument Builder, Cloud Instrument, Widget Instrument, Digital Sensor Frame. The cost structure for the combination of LabVIEW on the PC + LabVIEW Web UI Builder does not scale well in the federated use case of measurement applications where things that need to be monitored are very dense, wide spread and Web enabled. For these applications to be cost effective we need the entire application software component to be pushed from local PCs to the Internet. Basically, we need a Web Instrument Builder. Sensors connected to wireless digitizers send data to the Internet and a Data Repository application (an example at http://demo.tag4m.com/ ), which is a web based database with user interface. Think standalone ‘NIDAQ API’ for sensors. Users retrieve sensor data using feeds from the Data Repository to native Web Instruments. Examples of such instruments are the Widget Instrument and Digital Sensor Frame as seen at http://sensedin.blogspot.com/ . The Web Instrument Builder is a graphical programming method for creating web objects and also for ‘wiring’ them into more complex applications that may cross over several web and media sites. The Web Instrument Builder eliminates the cost and complexity of local PC-based software, opens web based measurement applications to unlimited future sensor expansions and reduces application cost by 10x from what a PC-based setup with the LabVIEW Web UI Builder costs today. I am looking for LAVA people interested in working with me on this project, i.e. build native web instruments. Tag4M at http://www.tag4m.com/ offers a free Trial Program to help start this project. Please let me know. -marius info@tag4m.com Edited January 19, 2011 by MariusG Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.