David Wisti

I tried to run this example in Labview 8.0 but ran into problems with when trying to connect with multiple clients. It seems the problem was here: This is related to a change in Labview 8.0 vi references discussed here. I replaced "Search 1D Array" with the following vi and everything seems to work fine now. Download File:post-319-1138295502.vi

While this doesn't slove your problem of loading locals from the INI file it does make saving and recalling INI files eaiser. This example uses strict type defs as the INI file format. It uses semaphores to prevent race conditions. This example uses open, get, set, & close methods. OpenG Toolkit and Labview 7.0 is required to run this example. Download File:post-319-1138293429.zip

I have to agree with Joe and Jim, OOP is the correct direction. However, there has been some advances from the queue-driven state machine. One of which I use quite often is the event-based queue-driven state machine. NI has called this "Producer Consumer with Event Structure and Queues." More information can be found here Link

I wonder if this effects any other type of reference? Or is it just isolated to vi references?

This not only effects comparison. You can add Search 1D Array to list of bugs, ahem... changes. See attached VI. Yes, I just spent most of the day trying to find out why my code worked fine in Labview 7.0 but acted strange in 8.0. Download File:post-319-1131657927.vi

Modbus TCP is quite a simple and well documented protocol. I have developed a Modbus TCP server and client on the NI cRIO with great success. These vis are not really ready for public release because not all the Modbus functions are supported. I'm willing to send you some examples if your interested. These examples will require you to learn more about the Modbus protocol.

It could be done by reference like this example. Download File:post-319-1131030516.vi

The Request Deallocation seems to deallocate the shift register. When you run the vi again, the shift register is not re-allocated properly. I don't think this has anything to do with the match pattern function.

Do you remember which dlls need to be registered with regsvr32? I wonder if this is a problem with built applications on Windows 2000 too.

Anyone notice the new terminals on "Flatten to String" & "Unflatten from String"? Finally, I can get rid of all that byte swapping and array length code in my TCP communication applications. Incase you can't find the functions, Data manipulation is now a sub-palette of Numeric. prepend array or string size? indicates whether LabVIEW includes data size information at the beginning of data string when anything is an array or string. If prepend array or string size? is FALSE, LabVIEW does not include the size information. The default is TRUE. prepend array or string size? only controls the top-level data size information. Arrays and strings in hierarchical data types such as clusters always include size information. byte order sets the endian format of the data in the resulting flattened string. Byte order, or endian form, indicates whether integers are represented in memory from most significant byte to least significant byte or vice versa.

Interesting... seems like the caption was not visible and possibly never created. Once I made the caption visible the error went away.

I work for an OEM that manufactures machines for the metals industry. We too log the thickness deviation for every single coil every 10 msec and about 255 more signals. However, we don't use Labview to do it. Why reinvent the wheel for this type of data acquisition? IBA has the best solution for us and they have been working in the metal industry for many years. Their product is called PDA & ibaAnalyzer. http://www.iba-germany.com/

:question: Each boolean control has 3 visible parts. The square and round LED also have decal.