Khalid

QUOTE(vronto31 @ Jan 31 2008, 01:43 PM) Another option is to use OPC. I know SAP supports at least the OPC-DA interface. Google it. -Khalid

QUOTE(psiam @ Feb 23 2008, 03:02 AM) Not exactly sure what you mean by a "UI" page. If you mean a web page, you can use the DataSocket VIs passsing it the URL. The output string will be the source code of the web page. Regards, -Khalid

[quote name='

Hi Marius, I must commend your willingness to learn. Here are some basic resources for learning LabVIEW: http://www.ni.com/academic/lv_training/how_learn_lv.htm http://forums.lavag.org/knowledgebase.html&showarticle=3 After this, you will want to pick up a good book, like Jim Kring's LabVIEW for Everyone. Of course, monitoring these forums and participating in the discussions is invaluable as well. Good luck! -Khalid

OK, now I am curious.. -Khalid

Welcome Mike! It's a small world indeed... see you around -Khalid

Marius, You should look at the Event Structure in LabVIEW, and use that instead of the While Loop. With the current implementation you are polling the Save and Load buttons all the time in the While loop. With Event Structure you would get an event whenever any of these button's values change (after you set it up that way). Plus, with your Vb background, you will like Events As for passing the array reference into the subVI and then using a Property Node, I guess it can be considered similar to using a pointer. But, you don't want to do that in LabVIEW unless you have a good reason. Because, Property Nodes execute in the UI thread (which is other than the diagram thread), and this will cause a thread-switching which is expensive. Here's a comparison of Terminal versus Property Node versus Local variable: Local variable = 15 times slower than Terminal Property node = 653 (!!!) times slower than Terminal The above is from the following post: http://forums.ni.com/ni/board/message?boar...essage.id=90261 Depending on how long you will be working with LabVIEW, you may want to stop thinking in terms of C and VB, and start thinking in terms of data-flow programming. Regards, -Khalid

To get the output from a subVI into its caller VI, the most staright-forward option is to create an output terminal on the subVI, and use that in the caller VI. Hope this helps. -Khalid

Hello, Are you talking about Siemens' HMI software WinCC? If yes, how does LabVIEW fit in the picture? If not, what is this Wincc? Please provide more details. Thank you, -Khalid

Hi Marius, I looked at the VIs. I am not sure what the task is. May be you can describe what you are trying to achieve, i.e, the functionality desired -- without going into the implementation details. This should help us program it. Regards, -Khalid

Hello Harry, Looking at the manual briefly, it doesn't list the Modbus addresses for the parameters explicitly anywhere. However, sections 5.4 and 5.5 do list some examples. In these sections, the register addresses are specified in paranthesis. You will want to contact the device manufacturer to get a complete of Modbus register addresses. Gut gl

Not exactly what we want, but the following runs the IE in LabVIEW's ActiveX container and then gets the screenshot: Regards, -Khalid

It depends on the communication protocol the PLCs use. Please find out the exact communication protocols the PLCs use. We can then discuss the options available for communicating with LabVIEW. -Khalid

I am guessing you would like to communicate with the two PLCs using LabVIEW. Please write in detail as to what exactly you are trying to accomplish. The Delta PLC uses the Modbus protocol as per the attachment. And I am again guessing -- based on your previous posts -- you have been able to communicate with it. What communication protocol does the Omron PLC use? Alternatively, does it come with an OPC Server? Also, please share any details and VIs that you have tried so far. Regards, -Khalid

So, did you try the example from Keithley's website? What errors are you getting, if any? Regards, -Khalid