David Wisti

QUOTE (mross @ Aug 21 2008, 12:36 PM) Wires work the same in fpga. But, if you have a situation where dataflow needs to be enforced, creating a wire and a corresponding data type and in/out terminals would take more FPGA space then just the enable string of a sequence structure. In FPGA, you could be trying to implement your code in the smallest footprint. Using sequence structures would allow you to optimize for size.

If your an FPGA programmer, you know sequence structures are not going anywhere. Having a sequence structure to enforce dataflow uses less space on the FPGA.

QUOTE (Phillip Brooks @ Aug 1 2008, 02:16 PM) I can't wait to start using these lossy queues. I've been using Shared Variables as lossy queues but there is no way to preview or know how many elements are in a shared variables queues.

In the upgrade notes I noticed the following: Queue Operations Function The Queue Operations palette includes the following new function: • Lossy Enqueue Element

Sorry if this is bit off-topic... LV_FPGA_SE, STM is fine if the host application is Labview. Modbus TCP is widely know protocol in the automation industry. If I have a cRIO that needs to talk to a PLC or HMI, then STM is not going to work. Modbus TCP is also and easy way to get a cRIO to communicate with an OPC server, like Kepware for example. In all of my LV-RT applications, their is a Modbus TCP server running and any Modbus TCP client can communicate to this device. I have a crude system, much like TCE that is employed to expose the memory map (i.e. CVT) of the Modbus TCP server. David QUOTE (LV_FPGA_SE @ Jun 28 2008, 06:56 PM)

QUOTE (LV_FPGA_SE @ Jun 27 2008, 10:51 AM) I appreciate NI for releasing the source code with CVT. I'm not very fond of STM (Simple TCP Messaging) and I would love to see this converted to a more open protocol like Modbus TCP. Since I have the source code, I guess I could accomplish this myself.

404198 is really address 4198 of the holding registers. 4 = holding registers. Most Modbus servers are one based so 400001 is this first holding register (offset 0). In your picture you going to read 365535 because your trying to read input registers, 3 = input registers.

QUOTE (vestman @ Jun 16 2008, 05:08 AM) Single-Process Shared Variables are just global variables wrapped in an XNode. You can not access globals with datasocket.

Nice article Jim! I hope I'm not thread jacking but I thought that 8.2 would put same namespace vi's inside the exe with mangled names? But in 8.5 this was changed to placing them outside the exe. I wonder why mangled names is not a build option.

Jeff, I was unable to reproduce it in a new project. I tried adding in both a RT targets and a FPGA targets. I saved the project and then make more modifications to it. Also, few combinations of such and still no error message. I wonder if it only happens to projects converted from 8.5 to 8.5.1. On the projects that I do see the error message, the error message will appear without doing anything, it just pop-up by itself. This error message was noticed immediately after I upgraded to 8.5.1 on the first project I opened. If I find out anymore information, I will post it here. David QUOTE (Jeff B @ May 27 2008, 10:01 AM)

My projects are quite large, 1000+ VIs. RT and FPGA targets exist in these projects. There is another unrelated issue with some of my projects. When I open my larger projects, they always open with unsaved changes even if you explicitly save the project before closing.

I'm getting the same error message here too. Seems to happen one time per project. The error does not occur right way. If the project has not been saved and there is a * in the title and I run a VI, the error message will pop up. QUOTE (Skip @ May 27 2008, 07:23 AM)

There is an example up on NI.com here: Programatically Creating Shared Variables in LabVIEW 8.2

QUOTE (Yen @ Apr 15 2008, 11:49 AM) Conditional Disable are project and target based. So you could have symbols just for specific targets or global symbols that effect all targets.

Yes subroutine setting does apply to LabVIEW RT code. However, you got me wondering, what does this setting do in FPGA VIs? QUOTE (FlamingYawn @ Apr 11 2008, 09:54 AM)

QUOTE (Jim Kring @ Apr 1 2008, 02:32 PM) I use it for one-way communication between "non-time critical" to "time critical loops" where the skips are in the time-critical loop. This is one way to prevent priority inversion. Since the creation of RT FIFOs, I barely use this technique anymore.

In deterministic applications (i.e time critical or timed structures) I use subroutine priority for the "skip subroutine call if busy" option.

QUOTE(murkyin08 @ Feb 28 2008, 11:30 AM) This does not answer your question but have you looked at the http://zone.ni.com/devzone/cda/tut/p/id/3937' target="_blank">real-time system replication tools? This library is packed full of VIs for cRIO. Most of them are locked but you can look at the VI Hierarchy to find out whats going on inside.

Is the Modbus I/O Server driver installed?

You could use Modbus TCP for the Ethernet communication. NI has a Modbus library or you could use shared variables with Modbus I/O server. AFAIK, you do not need DSC or RT to use Modbus I/O server in shared variables. Or, you could get LabVIEW talking on Profibus directly without any gateway. QUOTE(eoin @ Jan 23 2008, 07:42 AM)

For anyone who has never used IBA Analyzer, it is a far superior tool to signal express. Their graphing ability makes viewing large amounts of data so simple and easy.

Here's one: While the following is for Win2k, I think it still applies to XP: Performance Considerations for LabVIEW on Windows 2000

I've given up on Virtual PC 2007 for now, it keeps crashing my computer. Not even BSOD, it just crashes hard. VMWare works fine and never crashes. I have Labview 7.0 installed with XP SP2 in VMware. The only issue I have with VMWare is some screen artifacts while editing the block diagrams in Labview. I have to move the window around to force a redraw.

QUOTE(Cloedu @ Oct 1 2007, 08:30 AM) I always though ; was the standard for comments in http://en.wikipedia.org/wiki/INI_file' target="_blank">INI files.

QUOTE(Darren @ Sep 22 2007, 11:43 AM) Yea I know, I was just being a wise guy . I posted about http://forums.lavag.org/Fixed-arrays-t4434.html#' target="_blank">fixed arrays a while back.