iowa

QUOTE (sam @ Sep 10 2008, 10:09 PM)

The problem resides in the Driver that you are using. You should ask the creator of the driver. Another thing I can think of is playing the bit count, 8, 16, 14, 24 ....

if you can not change the driver, you can rearrange the array yourself as I can see that you are getting the image array and saving it to file. Remember the Array is in RGB. and use ArrayInterleave and ArrayDecimate.

Nice ideas.. Thank you.

http://lavag.org/old_files/monthly_09_2008/post-12065-1221083262.jpg' target="_blank">

QUOTE (sam @ Sep 10 2008, 05:25 PM)

You are not parsing the [Rows] in [image Array] correctly if my memory serves correctly. From the picture it seems that you are for example taking every other pixel,which will give you a compressed stubby image.

How do I fix it?

Thank you,

Alex

Using Logitech QuickCamPro 9000 -- have problem with quality of the outputted pictures

1) Using Logitech QuickCamPro 9000

2) Created VIs (attached as QCP9000.ScreenCapture.zip)

SMU_Driver.zip

3) Take a look on: "QCP9000 Snapshot.vi"

-- When using this VI the outputted picture are of corrupted quality See attached: "QCP9000 - picture.from.VI.JPG"

-- while actual WebCam picture is crystal clear. See attached: "QCP9000 - picture.from.WebCam.JPG"

I don't know what I have done wrong in my "QCP9000 Snapshot.vi".

Please let me have your expert feedback or ideas for improvement.

Thank you,

Alex

By the way this camera is Low cost and of amazing quality (for the price):

Logitech QuickCam® Pro 9000 -- <http://www.logitech.com/index.cfm/webcam_c...56&cl=us,en#>

The one with image-perfect detail and clarity. Carl Zeiss® optics and autofocus keep images razor-sharp, even in extreme close-ups.

Technical Specifications

Carl Zeiss® lens - German Optics!

Autofocus system

Ultra-high resolution 2-megapixel sensor with RightLight™2 Technology

Color depth: 24-bit true color

Video capture: Up to 1600 x 1200 pixels (HD quality) (HD Video 960 x 720 pixels)

Frame rate: Up to 30 frames per second

Still image capture: 8 million pixels (with software enhancement)

Built-in microphone with RightSound™ Technology

Keep receiving "Sorry, some required files are missing, if you intended to view a topic, it's possible that it's been moved or deleted. Please go back and try again" when attempt to download VIs from posts 1 & 2 or open pictures..

Would like to have these VIs.. looks soo interesting.

Thanks,

Alex

QUOTE (atyab @ Aug 26 2008, 11:59 AM)

I'm using LabVIEW 8.6 with Vision Development Module 8.6. I have to use a USB and/or Firwire camera to take snaps triggered by an external singnal and then do some processing on the captured snaps. Then wait for the next tirgger singal and repeat the process.

Things I've done:-

1. I've been able to receive the external singal via a SCB-68 in LabVIEW.

2. I've been able to do the required image processing in NI Visison Assistant 8.6 on an already captued image.

What I need to do:-

1. I need to combine the two things in LabVIEW and make the processing sensative to the external singal.

Troubles:-

1. I can't find the IMAQ USB and IMAQ IEEE 1394 VI's in my Function Pallet for LabVIEW 8.6.

2. How do I trigger a camera to take a snap and then ask it to do the same on the next trigger signal.

Please let me know if you were able to find these VIs Examples.

I have similar chalanges of trying to incorporate WebCam into LabView.

Have a need for: 1) Taking Pictures; 2) Processing pictures with OCR for texts extraction outputed as string.

Thank you,

Alex

http://energyray.com

Test Stand 4.0 -- Better Reporting question

Have LabView & Test Stand sequenced project where I have to deal with 100K of tests results.

Native Test STand reporting is not really friendly or helpful in analyzing such huge volumes of tests results.

Question: Has anyone had any experience with Test Stand reporting -- what type of Test Stand reporting do you use? Any examples would be helpful.

Wonder if anyone has SQL DB Reporting repository with IIS WebPortal & Crystal Report Web AcrtiveX for letting anyone in intranet visit Webpages and query any flavor of the tests results reports. I am looking for examples or anything related to better Test Stand reporting.

Thank you,

Alex

http://energyray.com

QUOTE (mballa @ Aug 1 2008, 08:14 PM)

Exe scripts are not the only way to use AutoIT!!! If you look on their webpage.

it says they have DLL and COM (ActiveX) control.

After AutoIT is installed you can access the functions using the Active-X Open and Invoke nodes

Here is how to use AutoIT in LabVIEW

Here are some vis to get you started.

This is super nice.. Thank you !!!!

http://energyray.com

QUOTE (rolfk @ Aug 1 2008, 09:19 AM)

I'm doubt you find it. Automating user interface testing on a Windows API level is absolutely not trivial (hence contradicts your requirement of simple LabVIEW examples) and is the reason there exist software packages like AutoIt.

If you really hope to build an extensive UI testing framework for non-LabVIEW applications don't go and try to use LabVIEW for it. Of course it can be done as there is virtually nothing that couldn't be done in LabVIEW if it can be done in a program at all, but it is going to be a major pain in the ######. Feel free to research the Windows API on MSDN and proof me wrong but asking for simple examples here is not likely to give you anything useful.

Rolf Kalbermatter

As posted before, already found some of the basic Windows API examples from NI.com.

The AutoIt is useless when someone have to deal with 100s of different interactions... would you really prefer to fire array of 100s of executables created in AutoIt instead of robust LLB with VIs using actual Windows API "hooks" controlling 3rd party application?

As for not using LabView statement:

In scope of any complex LabView implementation there is a BIG benefit from using 3rd party applications to supplement LabView coverage. In my case I implemented hooks into 3rd party GUI and it is working.. not perfect but working.. When time permits will be expanding my LLB by adding new "hooks".

Thanks to all who responded to my questions with actual answers & ideas. It helped to get started on this.

QUOTE (JDave @ Jul 31 2008, 10:45 PM)

Is there some reason you have to do all the Windows API work yourself? I thought the suggestion of using compiled AutoIt scripts was quite nice. AutoIt does all the API work and you just run the exe from your VI. Is there a reason this doesn't work for you?

Yes there is a reason..

The LabView project I work with executes millions of the software / hardware tests and adding Windows API interfacing ability to "hook" into another 3rd party (C++) application will let me enhance already existing test coverage by reusing another application's functionality... Using AutoIt will not be as elegant or as fast because of the big number of buttons I will have to interact with ... expect on average to click 1-3 million of buttons every 24 hours.. Direct interfacing from LabView by the use of Windows API will let me do it directly and faster without the need for huge library of AutoIt executables.

BTW -- found some working Windows API examples on NI.com (library of VIs for opening applications, resizing, moving, clicking etc..)

QUOTE (westjlittle @ Jul 31 2008, 10:16 PM)

Some of these actions can be done by using a GUI test program like TestComplete. We use it to verify our software products

Jim

The question was HOW to interact with 3rd party application's Front-End GUI directly from LabView (from VI file) by the use of Windows API..

TestComplete is another test automation tool similar to AutoIt or QTP..

This is not what I was looking for...

QUOTE (iowa @ Jul 22 2008, 04:21 AM)

Found this:

Windows API Function Utilities (32-bit) for LabVIEW[/size][/size] These VIs make calls to the Windows Application Programming Interface (API) for managing and controlling windows (minimize, maximize, move, resize, rename, close, etc); managing applications (run application, quit application, print file, etc); adding and removing network resources; keyboard filtering; and system utilities (mouse cursor position, windows path, screen resolution, system path, etc). These VIs are intended for use only on 32-bit Windows platforms.

And this: http://zone.ni.com/reference/en-XX/help/37..._the_win32_api/

Thanks,

Alex

Any news or new feedback/ideas for this thread?

I could really use working VI example which uses Windows API to control Windows Calculator..

Please ???

QUOTE (mballa @ Jul 22 2008, 04:50 AM)

I also use Auto It and love it. Mostly because it has Active X Drivers which make it work well with LabVIEW. I am planning to submit my AutoIt Vis to the CR sometime this year. I like the Idea of using the windows calculator as a demo example.

I have posted my Win API set of keyboard emulation vis Here

. There might also be some useful info Here.

If you do come up with a usable set of Windows API vis please post them or put them in the CR. I know that many members would appreciate a good Windows API library.

Found this:

Windows API Function Utilities (32-bit) for LabVIEW[/size]http://zone.ni.com/devzone/cda/epd/p/id/4935 These VIs make calls to the Windows Application Programming Interface (API) for managing and controlling windows (minimize, maximize, move, resize, rename, close, etc); managing applications (run application, quit application, print file, etc); adding and removing network resources; keyboard filtering; and system utilities (mouse cursor position, windows path, screen resolution, system path, etc). These VIs are intended for use only on 32-bit Windows platforms.

And this:

Thanks,

Alex

[/size]

QUOTE (MikaelH @ Jul 21 2008, 10:52 PM)

I'm using AutoIT-scripts compiled into exe-files that I run from LabVIEW.

http://www.autoitscript.com/

//Mikael

I tried it already BUT it is balky and consumes run time.

I would like to have more elegant solution of using Windows API to emulate Clicks/Keyboard thus driving C++ test application directly from LabView.

Still hope for Simple LabView WinAPI Example: such as code example of working with Calculator from LabView..

Thank you,

Alex

http://energyray.com - my collection of QA Tools

QUOTE (Omar Mussa @ Jul 21 2008, 07:24 PM)

Anything's possible... I know you can simulate clicks/keyboard presses but am not sure about reading visible text without serious effort.

Here's a http://zone.ni.com/reference/en-XX/help/371361D-01/lvexcodeconcepts/ex_3_call_the_win32_api/' target="_blank">link with an example to calling Windows API functions. Someone's probably got a library with mouse/keyboard API calls for LabVIEW somewhere...

I seen this NI.com article before..

I am looking for actual VI examples..

Used QTP to automate my testing before (same idea of using 3rd party applications to do the actual testing and all controlled from QTP).. Now trying to convert to using LabView and interfacing with 3rd party C++ applications by faking user actions (clicks/keyboard) is critical.

Looking for examples..

Thank you!

Question: Is it possible to control applications run in windows XP from LabView, by emulating buttons clicks, reading visible text etc.. is it at all possible? I have our own C++ application used in embedded testing, instead of rewriting all functionality in LabView wanted to use originally created C++ application by hooking to Windows API and simulating buttons clicks driven by LabView as well as reading data from this C++ application (by LabView). Please help. Thank you,Alex[/size]