Tim_S

Hmm... My first inclination would be to use an occurrence instead, but that doesn't change the functionality.

Tim

That's an extremely broad question. Are the devices PCI cards or connected through a communication port? What type of communication (e.g., RS232, GPIB, Ethernet, USB)? What type of devices? You are going to need to provide some information about these for people to have an answer.

Tim

Appreciate the update.

Tim

You will want to check out the examples that ship with LabVIEW; there are good instrument/RS232 examples included. As for installing the driver... if there isn't an installer or if it's not a package (see VIPM) then you will just put the driver in "C:\Program Files\National Instruments\LabVIEW xxxx\instr.lib".

Tim

It really shouldn't matter that much. LabVIEW code is compiled regardless of whether you're in the development environment or the run-time environment. Are you trying to determine differences between different machines?

Executables typically do not have their block diagrams; this speeds up performance and can give you slightly different timing.

Here's an update on this. I recreated the base object and plugins from scratch and, I thought, identically. The recreated code worked without issue. Tech support's response was:

The GNU Image Manipulation Package (GIMP) is a freeware Photoshop-like program. It's not always intuitive, but has layering and quite a few features.

Changing font size doesn't automatically happen; you'll need to use a resize event to go through all the controls and change the font.

Tim

Ah, got it.

I've got a calibration object with name, physical channel, scaling, etc... The object has methods to save to and load from XML file. I've coded the serialization into the object. (Hope I'm using the terms right.) Wouldn't this be the appropriate place?

Tim

To flaunt my ignorance, can you explain "object serialization tools"?

Tim

Since you are breaking up your data into chunks, are you breaking them into powers of two? (4096 bytes and the like.) TCP is optimized for transferring data in powers of two.

I'm not sure why you would get that error. Have you tried following the directions in the message and reinstall the MathScript RT module?

You'd be better off asking NI if NI has a utility for porting things over. I'm not aware of any, but then I've not used CIN.

Tim

NI tech support has filed a CAR on this; I'll post it when they send it to me. The CAR is about the breaking after execution and not what is causing the breaking; we're still working on the root cause.

I've been trying to convert some working LV2011 code to a plugin structure using the method found at http://lavag.org/topic/14212-how-to-call-a-plug-in-object-from-an-executable/page__p__85600#entry85600. The code can execute once during which loading the plugins produces errors. The code terminates and is now broken. All of the plugins are now in memory with no way to unload them except to close the project and open it up again.

I pulled out the load portion of the code and had no problems loading a plugin and converting it to a more specific class. I added a VI from the base class after the conversion and ran into the same break-after-execution.

I don't have a version of the code I can post here, however would appreciate any ideas that could help us figure this out. The plugins are to perform analyses (max, min, span, kurtosis, etc.) on waveforms.

Tim

Using all caps is going to cause people to not read your post.

It entirely depends on what you are calibrating and how to determine what hardware you need.

Tim

Are you looking to highlight for editing or highlight to make it stand out?

HI all,

I am Having NI cRIO and i dont know,

How to call Dynamiv VI On FPGA RT Target

Plsease Help.

Are you trying to call a dynamic VI on a RT or FPGA? I've not tried it with RT, but I assume it's the same as Windows. Dynamic loading is not available on FPGA.

Do you have code? Have you tried or looked at examples?

Tim

I've had a few calls into NI tech support lately and had to send them my entire user.lib, including (and mainly because of) the OpenG libraries. Zipping up something in the vi.lib as well as the user.lib is not a big deal to me, however it may be for a more novice LabVIEW user trying to get tech support.

If it connects to the serial port then you need to look at the serial communication pallet. There may be a device driver that does the interface you need. Have you looked at NI's website or the manufacture's website for such?

Tim

You will need the gamepad interface specification or will have to play around with some test equipment. Have you tried a google search?

Tim

Have you done a paper design yet? You may be quite surprised what is appropriate when you start breaking a large design into smaller components.

Hi,

Another question, how do you measure the "CPU-usage" in a VI?

Task manager gives a general idea. The Tools->Profile->Performance and Memory menu option gives a good idea of where that CPU time is going.

Tim

I've used functional globals, however I've used and read good argument for using global variables. Global variables can contain constants kept in controls with the value set as the default. You then have one VI to go to for all of your constant values. I would recommend the FG over the global if you are going to access the value frequently, but if it's something that you are going to read once during initialization and never again (e.g., IP address of target system) then a global would be appropriate.

If it's a value that never changes and you don't load, a VI with a constant in it could be set to inline, thus providing the same (similar?) overhead as a constant with the benefit of changing the value one place.

Tim

Have you tried rebooting (has worked for me when some memory issues occur)? Is this something you can reproduce? If so, I'd recommend calling NI as they will want to look at your code.

Tim

Can someone please help me understand "friends"

People would be more able to help if you posted your project rather than the snippet.

The concept of friends is along the lines of such... Say I have a drill and know two people "Person A" and "Person B". Both people want to borrow the drill. Person A is a friend, so I say sure, go ahead and borrow the drill. Person B is unknown to me, so I tell him to bugger off and don't let him have access to the drill. Person A may or may not consider me a friend, but that doesn't matter as I believe he is one and will grant him access to my drill.

Tim