David Wisti

QUOTE(Darren @ Sep 21 2007, 05:52 PM) but FPGA doesn't support variants...

Understanding Modbus addressing can be confusing because the memory map is part of the address. I suggest reading the ModbusTCP specification to help. Also, theres some good info at Modbus.org. For simple testing, I use Modpoll, a free command line based Modbus master.

I've been wanting to create Ethernet/IP VIs for some time now, Nice job! I have a ControlLogix 5555 CPU and a 1756-ENBT/A Ethernet/IP card to test these VIs. Once I have some free time, I will post my results.

http://forums.lavag.org/index.php?act=atta...post&id=656

The Code Repository has a nice INI file viewer example created with a tree control. Tree Control API

A single-process shared variable with a single element RT FIFO enabled will accomplish this without any code. QUOTE(John Rouse @ Jul 5 2007, 09:47 PM)

opcware.com has an OPC client toolkit with a Labview example. I've always wanted to create some wrappers around OPCDAAuto.dll with Labview but never seem to have the extra time. Labview can be a OPC client with shared varaibles only with the DSC module. I guess you need DSC to support a tag database.

QUOTE(Thang Nguyen @ May 1 2007, 10:42 AM) The only open-source way I know is http://libnodave.sourceforge.net/index.php' target="_blank">libnodave. You might be able to use the win32 dll with Labview.

Just wondering, how are you going to get the S7-300 to communicate Modbus TCP? Were you going to use the Siemens FB OPEN MODBUS / TCP Library? (2XV9450-1MB00-0YE0) I have used datasockets in the past only because it was well before shared varibles were created (Lv7.0). If a shared variables can be an OPC client without the DSC module, I would go that route. Shared variables seem much simpler than datasockets but I have never connected them to an OPC server.

QUOTE(Eugen Graf @ Mar 26 2007, 01:34 PM) Does VMWare Server expire? It was free but my licence says no expiration. http://forums.lavag.org/index.php?act=attach&type=post&id=5302''>http://forums.lavag.org/index.php?act=attach&type=post&id=5302'>http://forums.lavag.org/index.php?act=attach&type=post&id=5302

I had problems with VPC2007 crashing on my laptop. I use VMware Server with Labview 7.0 Pro installed in WIN2K with out any problems. One nice feature VMware Server has over VPC2007 is USB support.

Or a right-click > Find All Instances would be nice! You can search for text in the label as a work around, if you didn't change the default label.

I had a similar problem a while back with "remote" FPGA open which is really just a special VISA open. The FPGA open/close/read/write timeouts can not be set. So, one solution was to use a VISA open with a custom timeout. I experienced the same problem and just gave up... Heres the post at NIs website.

How are you sending the application to the system tray? .NET or API? I've used the InvTray toolkit to minimize to the system tray without any problems. Maybe its problem has something to do with minimizing to system tray thats causing the problem.

Khalid, I thought the original NI Modbus library was not working correctly in 8.x, did you fix this library for 8.x? I like the idea of cleaning up this code. I always wondered why NI decided to put all these VIs into 1 library. I think serial and TCP should be separate library's. I also think master and slave should be separate, too but that just my opinion. First step in clean would be using a .lvlib and geting this into project form with public and private VIs. Taking it one step further would be converting this library to a class. David

The last element was removed. I stared to decode the type descriptor. Heres what I found, see attached vi: Starting at the 4th element in the type descriptor: FFFF FFFF = variable size array 8000 xxxx = Fixed array where xxxx is the size elements 0000 xxxx = Bounded array where xxxx is the size in elements Download File:post-319-1161356371.vi

No real question here just that I'm using this fixed array in a VI that has nothing to do with an FPGA target. This is something you to not have access to in array data types in regular Labview. In investigating this hidden feature of arrays, I've been wondering if I can use them in other places, not just FPGA targets.

I'm using a Dell D810 with Labview. It has a nice 15.4 WUXGA LCD that does 1920 X 1200 resolution. It has both trackpoint and touch pad. But the real feature I like the best is a real RS232 serial port on the back, hard to find these days.

In FPGA module, arrays have an option to "Set Dimension Size..." when you right-click on them in the front panel. This brings up a "Set the size of this data item" dialog box. Here you can select fixed or bounded array size and elements. I decide to copy this array and place it into a regular Labview VI to see if it would work, which it did. Then, I wanted to see what would happen if I tried to insert 1 element into a fixed array [16]. The output wire of the insert into array became a bounded-size array [17]. The connected indicator was still a fixed array [16] which was automatically coerced back to a fixed size of 16 with a coersion dot. Attached is the 8.2 VI I've been playing with. I have no idea what will happen if you open this VI and you do not have the FPGA module installed. Download File:post-319-1161266721.vi

The file open function behaves differently when the "operation" input is a control. See attached v8.01 example vi. Not sure if this is a bug or expected behavior. It sure wasn't what I was expecting and is not documented in the help files. The file open function is blocked by the file dialog express vi if a control is used as the operation input. Download File:post-319-1159549716.vi

I would say no, its always a good idea to let the OS pick the local port. I've run into problems when the OS did not close a local port I was trying to use again.

I have not seen this problem before but are you using something other than 0 for local port on TCP open? local port is the local connection port. Some servers only allow connections to clients that use port numbers within a specific range that is dependent on the server. If the value is 0, the operating system selects an unused port.

For your user.lib with Donalds updates. Download File:post-319-1141835467.ctl

The second lock times out after 250ms. So, the "Set Modified Data.vi" should be in a case statement with the timeout boolean. Actually, I've always used this style of semaphore to prevent a race condition but I've never set the timeout to anything but -1. If you did that in your example, the timeout would never occur and the program would wait forever. You example does show something I didn't notice, the "Acquire Semaphore.vi" doesn't return an error when there is a timeout. If it did, then I think your example would work as expected. I too shamelessly stole this kind of protect read/modify/write access from OpenGoop object data store examples. Its not object based anymore and I never decided to take ini files from open/close to create/destroy.

Here is a vi that will get all the control references from a cluster. This vi requires OpenG toolkit and Labview 7.0. Download File:post-319-1138726604.vi