Quantcast
Channel: All LabVIEW posts
Viewing all 203752 articles
Browse latest View live

Re: Get Usable Monitor Size

$
0
0

Yup sorry, sometimes terms fail me.  I meant things like the Aero Theme adding that border.  I couldn't remember the name, but I see now they have a Windows 7 Basic, and Windows Classic which looks like Windows 7, and Windows 3.x or Windows 95-ish.


Re: Tekpower 3645A power supply

$
0
0
If the driver does not work, you need to provide more information than that. A picture of the instrument is not at all sufficient. At least provide the error code/message that you get. Are you using an example that comes with the driver? Also, what sort of physical connection are you using?

Re: Size of graphs varies after table insertion.

$
0
0

Similar issues pertaining to sizing variability problems with graphs in the Report Generation Toolkit have been observed. Graph sizing problems caused by changing the zoom level in Word, saving, and generating another report, have been formally documented (CAR# 334924 and CAR# 314027). In those cases the Development team has decided to defer pursuing the fix due to whatever reasons. The issues you are seeing are likely related. 

 

A potential workaround for your issue is to use the "Word Format Picture" function immediately following the "Word Insert Graph" function. Attached is a simple example with that workaround with instructions in the block diagram.

Re: C DLL memory leak?

$
0
0

Rolf what you're saying is so long as you deallocate memory that's allocated then the function is not a memory leak.  That much is painfully obvious and nothing I "learned in school" taught me any different.

 

When I said "static" function call in C perhaps it was a poor choice of words.  What I meant was from the LabVIEW code via the function call node.  It seems to me like a static call of sorts.  My original question was directed at understanding the difference in the relationship of that node calling the function vs calling it from a plain old C main function.  I believe the answer was simpler than I thought.  Allocate/deallocate just like normal (although I still don't understand 100%).

 

You can question my motives for using C but that seems a bit narrow minded.  The simple answer to that question is that in my industry, code re-use is king.  Since I can cross compile this code to just about any platform in existence, it's a lot more re-usable.  Other example reasons could be (but aren't limited to):  Bringing in resources who know C to help on projects, easier source code management, easier separation of modular logic from platform dependent I/Os such as networking, file storage, etc.

 

The complex answer is more a C vs LabVIEW thing.  If it's not obvious by now I definitely prefer C/C++ to LabVIEW.  My coworker and I often joke with each other, with him calling what I do "text programming" and me calling his "box programming".  While I can admit they both have their merits, in general I could have an all day long conversation on why C++ kicks the pants off LabVIEW.  Your comment on the matter is basically the pot calling the kettle black.  You used the standard argument in any debate over software which is "if you know what you're doing then mine's better" which is ultimately pretty self defeating.  If you care to extend the debate on the subject I am fair game, but I think it's ultimately pointless.

 

I hope my comments aren't too annoying, but I can't abide when pointless, generalized assumptions of ignorance get tossed my way.  I very much appreciate the help on this "box programming".

How to speed up VI load time (VIs that calls Control Design Toolkit functions in a Mathscript Node)?

$
0
0
Is there a way to speed up the load time for a VI that calls Control Design Toolkit functions in a Mathscript node? The performance for LabVIEW to load such a VI is pathetically slow. For example, the attached VI ("MS + CDT functions.vi") takes ~145 seconds to load. A similar VI that does basically the same thing but does not use Mathscript ("CDT_only.vi") only takes about 1 second to load. If I need/prefer to use the MS node, is there a way to speed up this load time?

Re: How to speed up VI load time (VIs that calls Control Design Toolkit functions in a Mathscript Node)?

$
0
0

Sorry, upload failed. Here are the files.

Re: Tekpower 3645A power supply

$
0
0

It says that Visa timed out. Yes I am using the example that comes with the drivers. The communication is USB to RS232.The example code I am using is the one below. Also de communication protocol is attached below for this power supply. Thanks!

 

 

Re: Anyone have instrument drivers for MKS PR4000 and/or MKS 647B?

$
0
0

Just in case anyone happens to stumble upon this old thread like I did...

 

There are instrument drivers for the MKS 647C Mass Flow Controller (compatible with the MKS 647B) in LabVIEW.

 

They can be found by clicking Tools >> Instrumentation >> Find Instrument Drivers...

Then choose MKS Instruments as the company and hit search (feel free to leave the "Additional Keywords" blank because there are only 2 different MKS driver sets currently).

 

If you run into any problems with the drivers (I did not), here is a link to the user manual: http://www.mksinst.com/docs/R/647Cman.pdf

There is a full run-down on how to use RS232 communication starting on page 33.

 

Good Luck! Smiley Happy


Re: Tracking Objects with labview and Vision assistant bounding boxes

$
0
0

You need to use the native pattern matching VIs to control bounding box off / on.  Try cascading the image outputs to inputs (see attached image).  Check the output bounding box outputs from the express VI to make sure they contain locations.

 

Cascade Outputs

Re: SMU delay time

$
0
0

Jeff,

 

The 4,200 samples/sec refers to how quickly the SMU can begin trying to reach the next setpoint, and is not actually an indicator of how quickly the output of the device will be able to reach the next setpoint. It does not take into consideration the settling time. If you take a look at page 4 of the PXI 4132 specification sheet, the maximum measure to host measurement speed at 1/64 PLC aperture time is 3490 Hz when operating at 60 Hz and 2900 Hz when operating at 50 Hz. I have included a link to the specification sheet for reference.

 

http://www.ni.com/pdf/manuals/375128b.pdf

Re: timestamps and calendar types for x-axis in graphs

LabViews

$
0
0

Hello all! I'm having issues opening LabView on device:

1. Message: Run-time error '481', Invalid Picture

2. Message: DAQ ERROR!!!, DAQ Error - 10005 Occurred. Do you want to continue?. If I click YES system close program, if I clock No, system close program too.

 

This is a criticla application in EMC Tecnologia Operations, I appreciate all help you can give us.

 

Thanks in advance!Error1.JPGError2.JPG

Re: LabViews

$
0
0

Nothing indicates that this program is even written in LabVIEW.

 

  • What does the program do? Who wrote it? Where did you get it?
  • Did it ever work on that computer? If so, what changed?
  • What happens if you just open plain LabVIEW?
  • What LabVIEW version are you running (probably old, since you are running windows XP)
  • What drivers are installed?
  • What is the "device" you mentioned (...opening LabVIEW on device....).

 

Re: agilent 34461A

$
0
0

I have an issue with this driver also, the flow control property node always errors out regardless of which type I select. Any help is greatly appreciated.

Re: agilent 34461A

$
0
0

BB567 wrote:

I have an issue with this driver also, the flow control property node always errors out regardless of which type I select. Any help is greatly appreciated.


Perhaps there is an error with the driver.

 

Time to start being an engineer and fix it.


Creating Events for Serial Comms + Database activity

$
0
0

Hi guys,

 

I'm writing an application that takes input from four different sources and picks whichever one is best according to a choice algorithm. The first two sources are input manually, when when a user clicks a button (no way to automate these unfortunately), the third source is from a serial comms device, and the fourth source is in an Access Database on the local network.

 

What I'd like to be able to have is an event generated when we get bytes at the port (from the serial source), and also when a new value is added to the database.

 

Is this possible?

 

 

Re: agilent 34461A

$
0
0
Why can't you provide the error code/message? I don't see how your question is related to this thread.

Re: Tekpower 3645A power supply

$
0
0
Please don't attach proprietary file types instead of a VI or snippet.

Your serial configuration is probably wrong but you didn't show that either. There's not enough effort on your part in providing meaningful information.

Re: Disable LabVIEW sub-componenet that causes long boot times

$
0
0

Hi Sam_Sharp,

thanks for the suggestion. I tried it and the batch file is loaded at the end of the installation. However it fails to remove the 32-bit instance of nimdnsNSP and the long boot times still occur (see attached image). Not even running the batch file separately fixes the problem after that. Any other ideas?

Thanks,

Mik.aza

Re: How to use NI 9871 in scan mode?

$
0
0

Hi Sam_Sharp,

 

You are awesome!!! It works when I added the property node of Wire Mode!

Very appreciated to your help Smiley Very Happy

20151202001.png

 

I was confused that I didn't add the property node but it works in the host computer(Laptop or personal computer).

I wonder if it is something about the RS232/485 converter to make this not necessary to implement the property node.

Viewing all 203752 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>