Michael Aivaliotis

Care to share?

I think it does. 12.txt shows up at the top of the list but it should come after 10.2.txt. Also 10.txt should come before 10.1.txt

I think you mean to say window or panel instead of Page. See here: Creating Pop Up Panels

I suggest you attend the upcomming OpenG webcast. Some exciting stuff is brewing...

Well I guess it exists on some computer somewhere. Assuming the file exists, then I would suppose that NI would have access to it. If this all sounds very vague then it was intended to be that way.

Well hey, you never said "universal" I was assuming that the AB[space] was constant and the only thing changing would be the number. Hmm, what do you mean by 10.1 and 10.10 etc? Do you have dots in the filename? Also, what is the end purpose of all this. Why would you have vi's named this way? Is this some sort of revision control system on your vi's or are you trying to do multiple instantiation? You could do that but does that guarantee sorting? Don't know. One way that will work for sure is to use a defined separator between your number and the text name. For example a dash (-) or underscore (_). Ex: Really Long File Name-1.3.4 This way you can use my method and replace the Scan From String function with a match pattern function and just extract the number portion that way.

Here you go:

Well, why not copy over the code from the other PC again? I have no idea what Plv.dll is, do you? Is it the driver for the daq card? If so, then you need to copy or install the driver given to you from the manufacturer.

Ya, the scripting help for the methods and properties is already written however it requires some actual files that need to be installed on your computer (*.chm files etc.). The help of course is not embedded in the executable.

Those of you who were fortunate to attend this past NIWeek in August 2004 might remember a sneak peak at the new version of LabVIEW 8. Various functionality was demonstrated at a keynote. As you can see, the development environment has been totally revamped. It looks a lot like some other text based language development environment (we won't mention names). LabVIEW 7 Express was targeted towards the newbie developer. LabVIEW 8 is targeted more to the experienced developer and the person working on larger projects. Some nice features include the ability to define various hardware environments so you can simulate attached hardware :thumbup:. As with all previous releases of LabVIEW, NI will initiate (or has initiated) a beta program for the next release. You can line up and hope to be accepted in this beta program here: LabVIEW Beta Program If you really want to influence how things work in future releases of LabVIEW then I suggest you try to get on the beta program.

Sow it turns out I got involved in creating an HMI interface with LabVIEW that interfaces to a PLC. Oh joy! :thumbdown: I started off by using datasocket and OPC to read and write values to the PLC. It turns out that this method becomes unusable for anything larger than 100 variables. The data transfer is painfully slow. This has been confirmed by NI support. So then I convinced the customer to go with the LabVIEW DSC module. I started adding tags in the DSC engine and everything started to go well. Now I have about 320 tags setup in the engine and it is again painfully slow to transfer data back and forth. How slow? It takes over 5 seconds to get a variable change to show up in the PLC. Unbelievable! Ok, so now I'm looking at the hardware interface to the Allen Bradly PLC. It is a serial connection at 19200 baud. Yes, I agree, this could be the bottle-neck. However does anyone out there have any experience with the DSC engine? Before I go shelling out cash for new hardware (ethernet connection). How can I make sure that this is not an inherent problem with the DSC engine and nothing to do with the hardware?

What is the point of your post besides for the only purpose of bashing NI? You don't provide any information to allow anyone on this list to help you.

It seems like you're new to LabVIEW so I hope you're not insulted by me stating the obvious. Can't you just use a numeric constant on the digram with a value of 0?

Can you post a screenshot of the frame\case that does the message sending. Something sounds fishy. You are mixing the terms case and state. Are you using a state machine architecture or a plain event structure in a loop?

I don't mean to be G worshiper, but can't you just create what you want in pure LV without ActiveX? What features in the ActiveX status bar are you keen on? I bet I can do the same in LV.

I guess what you need to do is find out what IP address the client sees. I don't really have a good solution but I know that you can ping external resources and they will give you back your IP. One example is getting the HTML for the website: http://whatismyip.net/cgi-bin/your_ip_is.cgi You can then parse the html and find out what your external IP is.

This is why i'm still running 7.1 I don't think the problem has anything to do with your stop button or the loop itself. It is probably related to what happens in your code after the loop stops. What code runs after it. Hmm, Is this a built application or VI's? Have you installed all the required modules in LV for your program? Perhaps during the upgrade you didn't install something that you should have? Yes, well I don't think there will be anything in the options that will help you here.

You have to use the bundle function on the diagram and wire each control reference control into the bundlw function. I think the problem occurs when you grab the controls and put them into the cluster. You must do this programmatically as I state.

Everyone... Let's not forget the "Empty String/Path?" Function. It can also check if a string is empty (blank) with only one node.

Yes. I already reported this in LV7.0. I guess it still exists in 7.1... :thumbdown: See my post: http://forums.lavausergroup.org/index.php?showtopic=142

Here you go:

It sounds like you found a solution. Another way is to create the file in the c program and then have lv check for the presence of the file. When LV toggles the boolean then have lv delete the file. Repeat this process. This way you can have the c program verify that LV saw the file and toggled the boolean. As you say, NOT pretty but works. Why not get LV to do the DAQ card directly?

It looks like you're writing data to the chart plot name. Can you show us the diagram?

Try using a USB mouse if you can.

The error is comming from another VI that is trying to write to the same file you are trying to read. When you use the "read characters from file.vi" it sets the read-only flag on the file. This means while you are reading the file, all other vi's accessing the file will give an error.