Are there requirements for deterministic data messaging for distributed LabVIEW applications across an Ethernet/IP network?

[RTI]

Our company, RTI, just entered the Alliance program at NI recently. We are curious if power users of LabVIEW have requirements for running distributed, networked multiple LabVIEW applications in a real-time, deterministic manner? We are not attempting to make this a sales call, but if we should move forward with development of VI's that would allow distributed LabVIEW applications. We have already scoped out the effort but would desire guidance on VI layout, descriptions and ways to give a "LabVIEW" experience and not a disjointed VI that looks unprofessional. We are not sure if demand exists for this requirement. We would like to talk with
and investigate what LabVIEW users want. We have attached a brochure on this real-time data messaging technology for your review. Maybe there is no need and we apologize for taking up NI Developer Zone bandwidth and your valuable time. We look forward to your responses.

[mikeporter]

The best way to have VIs with a professional appearance is to have a developer create them that is knowledgeable with LV and good programming style. From the tone of your post you apparently have some concerns in this area. I would be glad to help. Michael Porter, mlportersr@webtv.net

[Ben]

I strongly agree with Mike.

I am currently re-writting an application that was developed by one of those big "C" shops.

After reviewing their code I told the customer that the person who designed and developed the original app was probably a very good C programmer. Unfortunately that was not enough to do the same in LV (i.e. 1200+ global variable references and 1 shift register).

To quote my wife,

"You gotta shift the para-dig-em"

Ben

[RTI]

Your comments make perfect sense. We'll contact you once we have created this real-time LabVIEW distributed environment for your review. We are still curious if requirements exist for deterministic distributed LabVIEW applications across Ethernet/IP?

[waldemar.hersacher]

We are developing applications which have a distributed layout. E. g. we have 2 or more test places which have no user interface and 1 place where all configuration and monitoring and data storage takes place. We use TCP/IP for the inter computer communication. For this purpose we have developed a library which has a similar interface and usage as the queue VIs from LV 6.0.2. We support automatic reconnect on TCP/IP level and an acknowledged transfer so the application programmer can choose to do some temporary storage on the local machine if the server part is not running for sometime. We have not seen any market for that so we do not plan to sell it.
From a lecture at the NI VIP days in Munich in 2001 personal from Siemens A&D stated to
get a real time like behaviour over ethernet with TCP/IP you have to take care that the load will not exceed 30% of the bandwidth.
For more information you can contact me at waldemar@hersacher.de.
Waldemar

[unclebump]

what I would love to have is a driver to make LABVIEW and/or the DSC engine act like a MODBUS TCP/IP slave on the same ethernet network as MODICON MOMENTUM plc's. No more messing with OPC servers and tag engine. I have no experience with the real time hardware, they may be capable of that now.