LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

ERROR 1074360293

Hello to all the colleagues on the forum, I have a problem with a code in LABVIEW which consists of the error ¨1074360293¨ TIME OUT. I am doing a simple project and for this I have the tools required for video acquisition (NI MAQ, NI MAQ DX etc) 

When connecting a USB camera to my laptop, it works wonderfully and that makes me realize that the NIMAQ tools are working correctly; However, my goal is to make it work with the integrated web cam of my laptop, and it is at that moment that the program stops working.

In the session in it allows me to select the camera that my laptop recognizes, the integrated camera says to recognize it in ¨cam 0¨ and the USB camera in ¨cam 1¨. I reiterate on cam1, which is the USB camera, the program recognizes it, but when I stop the program and want to put the laptop's integrated camera (cam0), I get the error "1074360293" TIME OUT. The error occurs when passing the GRAB.vi,

I already checked on my laptop and Labview has permission to enter the camera, I have seen in various forums about possible solutions, but they have not worked for me, please if anyone can help me.

Enclosed PSDT I send the V.I, in advance thank you.

Download All
0 Kudos
Message 1 of 9
(3,773 Views)

Hola a todos los compañeros del foro, tengo un problema con un código en LABVIEW el cual consiste en el error ¨1074360293¨ TIME OUT. Estoy realizando un proyecto sencillo y para ello tengo las herramientas requeridas para la adquisición de video (NI MAQ, NI MAQ DX etc )

Joehendrix1723_0-1588531827960.png

Al conectar a una cámara USB a mi laptop, funciona de maravilla y eso me hace recapacitar que las herramientas de NIMAQ están funcionando correctamente; sin embargo, mi objetivo es hacerla funcionar con la web cam integrada de mi laptop, y es en ese momento que el programa deja de funcionar.

En el session in me permite seleccionar la cámara que reconozca mi laptop, la cámara integrada dice reconocerla en la ¨cam 0¨ y la cámara USB en la ¨cam 1¨. Reitero en la cam1, que es la cámara USB el programa la reconoce, pero cuando detengo el programa y quiero poner la cámara integrada de la laptop (cam0) me aparece el error ¨1074360293¨ TIME OUT.

El error ocurre al pasar del GRAB.vi, ya verifique en mi laptop y Labview tiene el permiso de ingresar a la cámara, he visto en varios foros sobre posibles soluciones, pero no me han dado resultado, por favor si alguien me puede ayudar.

PSDT adjunto envio el V.I, de ante mano gracias.

 
 
 
 
 
 
 
 
 
 
 

 

Download All
0 Kudos
Message 2 of 9
(3,779 Views)

I downloaded your VI (camera otra.vi) and ran it on my Dell Laptop (whose camera is "cam0", and is the only camera currently plugged in to this PC.  When I ran it, I saw a video of a homely guy sitting in a chair -- couldn't tell what he was doing, but he really needed a haircut, looked like it was almost two months of frizzy stuff (maybe he's trying for an Afro) ...

 

Unsure why the same code (which looks OK to me) didn't work for you ...

 

Bob Schor

0 Kudos
Message 3 of 9
(3,717 Views)

Wow, I can't believe what you're saying, maybe some image of me was saved, I don't know how to tell you. I apologize beforehand.
I don't know why it doesn't work on my laptop, and only the integrated webcam.
maybe it's the computer spec, but I use one with:
Windows 10 operating system
.intel Corei3 2.1GHz
.4 gb of RAM
HD 4 pro camera
Intel HD Graphics 3000 video card
.Labview2017, Vision 2017
It is strange because the camera works with other applications such as "Zoom", "meets", etc.
At the moment of executing the program, the camera turns on, but in the block diagram of the Grab.VI the error 1074360293 appears, at the moment I put the focus that helps me to see the operation of the program, as you can see in the image error.jpg
I hope to find the solution, thanks for your help friend.


Attached I upload another V.i similar to that one, waiting to see if it is a failure of this other one.

In the code that I send attached, the integrated camera of the laptop does not work either.

0 Kudos
Message 4 of 9
(3,706 Views)

Sorry, I didn't even try to run your second code -- much worse (from a LabVIEW "Style" viewpoint) than the first.  So excuse me for a moment while I put on my "Professor" hat ... (I actually folded a "Printer's Hat" from an article in yesterday's Newspaper, and have just put it on my head).

 

We are going to write a 6-function program that should work the first time.  We will go slowly, and you should "do all of the steps".  The assumption is that (a) you have NI's Vision Development Module and Vision Acquisition Software installed, (b) MAX can show you a Camera on its "Devices and Interfaces" tab, and (c) using MAX, you can "see" and "Grab" with a Camera.  You need to be able to see the Vision Palette on the Front Panel, and the Viision and Motion Palette on the Block Diagram, where you should see the sub-Palettes IMAQdx and Vision Utilities.

  1. Open a New VI.
  2. On the Front Panel, from the Vision Palette, drop an Image Display.
  3. Go to the Block Diagram.  Drop the following Functions from the Vision and Motion Palettes in the following (left-to-right) order:
    • IMAQ Create (from Vision Utilities, Image Management).
    • IMAQdx Open Camera.
    • IMAQdx Configure Grab.
    • IMAQdx Grab (might be called Grab2).
    • IMAQdx Close Camera
    • Simple Error Handler
  4. Turn on Help (Ctrl-H), click on each of these functions, and read the Help description.  Read the Detailed Description of the IMAQ/IMAQdx functions.
  5. Connect the Error Lines (Create to Open Camera, Open Camera to Configure Grab, ... Close Camera to Error Handler).
  6. Create a name for the Image (the "Session In" input to IMAQ Create).  Right-click the Image Type input (bottom) and Create Constant.  Change the Constant (an Enum) to RGB (U32) (as that is almost certainly the format for your Integrated WebCam).  Leave a little space between this function and the next.
  7. Right-click the Session In terminal of Open Camera and create a Constant.  Right-click the "selector" indicator (the little triangle) and choose "cam0", your WebCam.  Wire "Session Out" to the Session In terminal of Configure Grab.
  8. Skip to the Grab function,  Wire Image Out to the Image indicator from the Front Panel's Image Display.  Position this indicator so its lower edge is above the upper edge of the Grab Function.
  9. Draw a While Loop around Grab and Image, leaving Close Camera and the Error Handler outside the loop.  Wire Stop to the Stop Indicator.
  10. Connect Session Out from Configure Grab to the Session In input of Grab.  Wire the Session Out of Grab to Close Camera.  Wire New Image from IMAQ Create (Step 6) into the While Loop to Image In of Grab (I route the wire down below Open Camera and Configure Grab, then up to make a straight shot to Grab -- neat and as straight as practical, with only 4 bends).
  11. Run your code.  It should work.

I am deliberately not posting a Snippet, nor the code itself, and urge other readers of this Reply to honor this request.  I am trying to teach, which means I'm trying to get someone to learn, which doesn't happen by "giving them the answer", but by helping them to "discover the answer with a minimum of frustration".

 

Bob Schor

0 Kudos
Message 5 of 9
(3,665 Views)

Well, I really followed all your steps but it still doesn't work for me. As you well say in ¨ MAX¨ in the same way my integrated camera does not work, something strange because I connect the USB camera and it works both in the code that you taught me and in NI MAX. I think that I should update VISION to the closest version, well I don't know how much benefit I have from updating.
I upload the code that you taught me in the steps, maybe I am wrong and you can correct me, only if I do not interrupt you.
Additional I upload images of how it looks when I run the code from my laptop and an image of the error that I get when I test it in NI MAX.
Thanks for your help, friend. I really appreciate it.

0 Kudos
Message 6 of 9
(3,645 Views)

Joe,

     You've convinced me that "Something is Screwy in the Computer of Joe Hendrix" (for extra credit, from which play that you should have read in High School is this quote not quite lifted?).

     I'm attaching my code, along with a picture (not a Snippet!) of my Block Diagram to illustrate a curiousity that had me scratching my head for a few minutes (I'll explain).  But I also attached the VI, itself, written in LabVIEW 2017, so you can try it (I already predict it won't work ...).

WebCam Grab BD.png

As you can see, our Block Diagrams are essentially identical, except I connected the Error Line everywhere first, as I asked you to do, so that it continued into and out of the Grab inside the While Loop.  And my wires were straighter.  And I didn't use Icons for Controls and Indicators (more compact, neater "look").

 

And the feature of your code that threw me for a loop, as it was a feature I don't think I'd ever used.  Your Block Diagram had a red "rim" around it that "hugged" the edge of the Frame.  ???  Could it be a Breakpoint?  But if I right-clicked on blank space (or looked through the menus, Breakpoint never appeared.  Aha!  If I click on, say, an Error Line, Breakpoint appears, and I can select the Breakpoint Manager, and see you have put a Breakpoint on the entire Diagram.  I have no idea how you did this, and even less why you did this, except that you probably don't know how to use the Single Step and Highlight Execution tools on the Menu Bar (but I did learn something).

 

Anyway, do try my code, which will probably fail, as well.  I'm going to focus on your statement "I think that I should update VISION to the closest version, well I don't know how much benefit I have from updating", which suggests, to me, that you may well have a Vision Version Probllem.

 

Before making changes to your system, please do the following:

  1. Open NI MAX.
  2. Under My System, expand the Software Tab.
  3. Attach a Screen Shot of the Software Tab contents.

Once I see this, I'll try to make some recommendations that I hope will fix this problem (which should not be occurring).

 

Bob Schor

0 Kudos
Message 7 of 9
(3,620 Views)


To be honest, I don't know how I put the single stepping option and what the function is exactly, I don't know much about the program, but I'm very interested in learning from it. It is a very powerful and interactive Program for programming and I like that. I learned it in the University and today I want to give it more use.
But in turn I know the basics and you could say that a little more than the basics.
It is exactly as you say friend, our codes are the same but mine does not work with the integrated camera. I can even assure you that at the beginning my code was exactly like the image you uploaded. The ´´Shift Register´´ was added in the While Loop.
I hope that updating I don't lose the Vi's of NI MAQ and Vision since a friend told me that that had happened to him, I suppose that he had it cracked.
Attached is the NI MAX screenshot as requested.
Always thanking you for helping me on this issue and I really appreciate your help, thanks friend.

0 Kudos
Message 8 of 9
(3,609 Views)

Hello, Joe.  Thanks for the Attachment.

 

I think that what you call the "Single Stepping Option" is what I call a "Breakpoint".  When you open your Block Diagram, does the Window showing the Diagram have a red border around it?  That's a "Breakpoint", meaning "Stop Here".  I don't know how you turned it on, but I'm going to show you how to turn it off.

  1. Open the Block Diagram.  Notice the red border.
  2. Right-click any Wire in the Diagram.  From the Drop-down, click "Breakpoint", then "Breakpoint Manager".
  3. You should get a picture like this:Breakpoint Manager.png  This shows an Active Breakpoint (Big Red Dot) on the entire Diagram.  You can Clear it or (what I recommend) Remove it.
  4. To Remove, click the line with the Breakpoint to Select it, click the Red X to delete it, then click Close.
  5. Done.

I don't see anything too terrible in your Software list that you attached.  The major difference between our systems (besides my having multiple LabVIEW versions and a few more drivers) is that you have installed 64-bit LabVIEW, whereas every one of the hundreds of LabVIEW installations I've done for myself, my colleagues, and my students has always been 32-bit LabVIEW.  I understand that more and more tools and Devices are becoming 64-bit "safe", but unless you are working with very large sets of data, you are safer with 32-bit LabVIEW.

 

     See how your system works when you "unlock" your code, or when you run mine (which has no Breakpoints).

 

Bob Schor

0 Kudos
Message 9 of 9
(3,599 Views)