Leaderboard

A most excellent description of the sometimes arcane Front Panel dimensions can be found here. All credit belongs with the original author, David Staab. I put this here so I can find it easier next time I need it, which seems to happen every couple of years or so :-)

View File Plasmionique Modbus Master This package contains the Plasmionique Modbus Master library for LabVIEW. It supports RTU, ASCII and TCP modes with the following function codes: 0x01 - Read Coils 0x02 - Read Discrete Inputs 0x03 - Read Holding Registers 0x04 - Read Input Registers 0x05 - Write Single Coil 0x06 - Write Single Register 0x07 - Read Exception Status 0x0F - Write Multiple Coils 0x10 - Write Multiple Registers 0x16 - Mask Write Register 0x17 - Read/Write Multiple Registers 0x2B/0x0E - Read Device Identification Other features include: - Sharing a COM port across multiple Modbus sessions using VISA locks (10 second timeout). - Sharing a Modbus session across multiple communication loops. - TCP transaction ID handling to ensure that requests and responses are matched up correctly in case responses are received out of order. - Modbus Comm Tester, available through the "Tools->Plasmionique" menu, for testing communication with a slave device without writing any code. - Detailed help document available through the "Help->Plasmionique" menu. Examples are included in "<LabVIEW>\examples\Plasmionique\MB Master\": MB_Master Comm Tester.vi: Demonstrates usage of API to open/close connection and communicate with a Modbus slave device. MB_Master Multiple Sessions.vi: Demonstrates usage of API to open concurrent Modbus sessions. MB_Master Simple Serial.vi: Demonstrates polling of a single input register over serial line. Download a copy of the user guide here: MB_Master - User Guide.pdf Note that Version 1.3.4 of this library has been certified compatible with LabVIEW and has been released on the LabVIEW Tools Network: http://sine.ni.com/nips/cds/view/p/lang/en/nid/214230 The most recent version of this library will always be released on LAVA first before going through NI's certification process. ***This project is now available on GitHub: https://github.com/rfporter/Modbus-Master Submitter Porter Submitted 04/01/2016 Category LabVIEW Tools Network Certified License Type BSD (Most common)  

Very interesting, please see if you can find a simplified example that can be submitted to NI. Storing a variant in a shift register is something I'm sure I've done plenty of times. Also I don't know if it makes things easier, but I've been moving away from OpenG functions for cluster manipulation, and choose to use the NI functions, and the Variant to Data trick. Attached is an example where a cluster is turned into an array of variants, manipulated, and then turned back into the cluster. Notice that the Get Type Information also returns the data name. Oh and if you update the cluster you need to set the Cluster size in the Array to Cluster to the right number of elements, the wire will be broken if it doesn't match. I made and XNode to do this but didn't want to add another unknown into debugging this. Of course if this is a bug in LabVIEW this won't, help. If this is a bug in LabVIEW, I'd bet adding an Always Copy inside the loop will probably fix it.

Download it from Customize Property Pages: http://webspace.webring.com/people/og/gtoolbox/CustomizePropertyPages.html

found getUserAppReference.vi in LabVIEW 2011\vi.lib\Utility\allVisInMemory.llb

The closest I think you can come is using nested subpanels. Top level VI is simply one with two subpanels. It hosts one of your dynamic UIs in one and a clone of itself in the other, which in turn hosts another UI and another clone. Keep going until done. You then would need to manage the scrollbar on the top level VI, along with the size of all the nested panels. In theory doable, but very messy. I have an app I'd like to do this in, bit the kludginess of it all has turned me off even trying. The good news is that this should be doable in a fairly extensible way, but I agree dynamic control creation would be way better.

OK, I got piping/redirection to work. The key was some code/info posted on this C# thread. There are a couple more kernel32 dll calls now, so it's even farther from pure .NET. However, it works pretty good, both from console and System Exec. Next up: Develop similar method to allow a LabVIEW program to accept input from StdIn. -Scott Write Std Out with Redirection.vi