Sapera with IMAQdx

Similar Questions

• How a 14 bit camera does not have a 16-bit image with IMAQdx?

  Hello

  I use camera firewire Guppy Pro F-031.   And I'm the program with IMAQdx.
  This camera AD converter is 14bits, and I expected that the strokes per pixel of this unit should not exceed 2 ^ 14.  In the attached photo, the maximum number allowed for each pixel is 18132, which is larger than the 2 ^ 14  I am not a 16-bit grayscale output.  How a camera 14bits output 16 bit generally?

  My configuration:
  1 ni-IMAQdx to the Microsoft driver.
  2 VideoMode = "Format 7, Mode 0, 656 x 492".
  PixelFormat = "Mono 16".
  BitsPerPixel = "use the value of the material.
  PixelSignedness = "United Nations signed.
  ShiftPixelBits = "false".
  Auto exposure, Gain, brightness, Gamma is ignored

  Thank you very much!

  best,
  Wen

  IMAQdx do not move or stretch the data AFAIK. Change the boutien and see if that makes a difference.

• Invalid XML in matlab with IMAQdx

  I'm trying to interface with a GigE (SVS-Vistek svs4021) in Matlab 2009A camera, but I'm getting InvalidXML errors when I open the camera.  My goal is to create a wrapper dll .NET for IMAQdx controls that will open, enter and close the camera.

  Here's my progress so far:

  -Map of Intel PRO/1000 GT installed.  GigE driver NOT installed.

  -Connected to the camera in MAX.  It worked.  I could acquire images, change the shutter times, etc.

  Written-A a test in c# .NET and program dll.  It worked also.  I was able to acquire images and copy them into a table.  See below.

  -Loading dll .NET in Matlab (using NET.addAssembly).  I couldn't get a picture.  More investigation showed that I was getting 1074360291 error, failed to load the XML of the camera.

  I confess, write wrappers for DLLs .NET .NET is redundant.  I had to do it in the past for a dll not .NET and now my Matlab code expects.  I tried to load NationalInstruments.CWIMAQdx.Interop.dll directly in Matlab, but I got errors running CameraOpen().  I tried to avoid using Image Acquisition Toolbox of Matlab.  It costs $1,000 and I didn't count on the 30 day trial.

  Given that the c# code works, it must be something simple as referring to the incorrect dll or a directory.  Someone at - it ideas?  Is there an example of Matlab code to achieve this?

  Thank you

  Ryan

  ----------------------------------

  Here is an excerpt of my .NET dll c# code:

  public void Connect()
  {
  Status of CWIMAQdx.Error;
  Status = CWIMAQdx.OpenCamera ("cam0", CWIMAQdx.CameraControlMode.Controller, out sId);
  Console.WriteLine ("opening Camera-" + Status.ToString ());
  MessageBox.Show ("opening Camera-" + Status.ToString ());

  Status = CWIMAQdx.ConfigureGrab (sId);
  Console.WriteLine ("Configure Grab-" + Status.ToString ());
  MessageBox.Show ("Configure Grab-" + Status.ToString ());
  }

  (I use the MessageBox that I can see what is happening in Matlab).

  Hi Ryan,

  Ah, that's the problem... If you upgrade to a later version of IMAQdx it should solve your problem. Basically, we use a common component of GenICam (all GigE Vision publishers share this component) itself is based on Xerces. Old versions of GenICam used a not-so-unique-named version of Xerces and so he had the potential for conflict with other copies loaded in the same process that have been compiled with different compilers/settings. New versions of IMAQdx use a newer version of GenICam that uses particularly aptly named copies of Xerces that must not come into conflict.

  I updated to version 3.2 here:

  http://Joule.NI.com/nidu/CDs/view/p/ID/1099/lang/en

  Eric

• Integration of SAP with ERPI overview

  Hello

  I've done the integration of hyperion with EBS. Here are the basic steps I've done.

  1. install ERPI.

  2 - has given the Apps schema and initialized.

  3 - Select the general ledgers.

  4. define mappings according to EBS.

  5 create the rule.

  6 import data from BSE-> hyperion.

  My questions are,

  1 - How to achieve this in SAP?

  2 - steps are almost the same? or different?

  3. how the participation of functional person is necessary?

  4. how knowledge of SAP is necessary?

  5. how many types of cards is there for the integration of the EPRI-SAP?

  6 it is recommended by oracle?

  7 - What other ways I have move given sap in hyperion? can I use informatica?

  Concerning

  What is ERPI or FDMEE?

  (1) integration SAP is documented in the FDMEE Administrator's guide and the Guide of the adapter you can download from the site of bristlecone pines

  (2) integration SAP is completely different. It has different configuration of the side steps ODI. There are also some spots on the side AS creating a user for ODI (JCo connection)

  (3) the FDMEE-SAP adapter configuration is usually performed by a technician because it requires some knowledge of ODI. A functional person would act as soon as the adapter is configured so that it can configure FDMEE with respect to any other source

  (4) generally the core SAP team will configure SAP as required for integration and you don't need really SAP kwnoledge

  5) there are 6 predefined maps (documented in the Administrator's guide). That's FDMEE, to ERPI you will need to go to the latest patch for the 6 I guess

  (6) oracle cannot recommend an adapter because it depends on what you are going to integrate. If you want NEW GL balances, then use the NEWGL adapter.

  (7) Informatica does not hyperion support > = 11.1.2.3 I guess that if you would be able to use it, but you'll have to customize adapter for Hyperion, if you have the version 11.1.2.3 +. This can be done using APIs (for example: HFM API)

  If you are in the previous version you can use but I recommend not to use because it is not supported.

  Another option would be to use autonomous ODI that uses the same approach as adapter FDMEE-SAP from the technical point of view. In deed the SAP-FDMEE adapter uses the KMs ODI - SAP

• Performance issue of SAP with Oracle 10 on Sun SPARC T5240 server

  Dear friends,
  
  We have a performance issue after the migration of our basic system of SAP ERP 6.0. To new servers, we moved a month ago.
  The report of EarlyWatchAlert SAP response time of CPU is too high, although the CPU utilization is never more than 5%,
  
  The current system is:
  
  Database server: Sun SPARC Enterprise T5240 Server - 2 CPU´s with 6 core wire 8, 1.2 Ghz 32 GB RAM
  and we use a different identical server configured as an application server.
  
  Database is Oracle 10.2.0 and Solaris 10 operating system.
  
  The problem is CPU average response time is 450 ms and maximum CPU load is 5% percent.
  
  Configuration prior to migration with the old servers, we got the answer of CPU: 150 ms and max CPU load: 50%.
  Old configuration: 2 X HP rp3440, 2 X PA 8800 (2 core, 1.0 GHz) CPU.
  
  You have experience with a similar situation, setting that could be bad for server CPU´s not making full use?
  or you know any similar configuration for benchmark?
  
  Thanks in advance
  
  Uzan

  The new server's processors in Niagara? If so you could run in the known performance issue identified in MOS Doc 781763.1 (Migration of fast single machine threaded CPU to CMT UltraSPARC T1 and T2 causes an increase in the CPU reports)

  HTH
  Srini

• medium-sized images of the camera with IMAQdx

  Hello

  I need through the images acquisition of a camera and subtract the average of an acquisition of background image.

  Although I use an ethernet connection, the program is REALLY slow.

  I'm new with Labview so any suggestions is very welcome... I have attached the program

  This is not my best work, but take a look a this.  The same code acquires the two images, you just choose what image control stores the updated average image.  the Analyze button then processes what is in control of the two images (reference and absolute).

  Your problem is that you initialize constantly every time as an image.  Just do it once.

• To end a Subvi after the break (with IMAQdx)

  Hello!

  So, I need to display a grid on a projector and take a picture of him with a camera. My problem is that I want the program to run as quickly as possible and at the moment I can only show the grid a certain amount of time.

  So I would like to confirm that the photo was taken and stop the vi poster sub grille. I thought that by replacing the tempo by a certain time structure

  and send the message 'stop' after taking the picture might work but it doesn't.

  So my idea was to make a sequence and then send the message to "kill".

  I read about the events, but I don't know how to use it and even if it is not too complicated.

  The first picture is the main vi and the second, that I want to end.

  

  Hello

  Sorry, I don't have that the VI grid is actually a Subvi from the mainVI. You can use a global variable to pass your stop request to the Subvi.

  The question is: do you want to stop the Subvi after loop iteration for all four? Or do you want to start and stop the Subvi in each iteration of the loop for?

  Here is an example for the second option:

  

  

  now, it should work. in the first image is set to false - the Subvi 'Grid' will continue to run the shutdown command. After the image was taken at the 'grid' Subvi is hollow arrested the last image.

  See you soon,.

  Cheggers

• Unibrain Fire-i with IMAQdx color camera

  Hi all

  I'm considering buying a color of Unibrain Fire-i 785 camera. It is possible to purchase this camera uses OR-IMAQdx (I don't have any NOR-VISION). The sales rep told me to a quite expensive third-party SDK. But all I want to do is wink images to a file, so this seems like an exaggeration...

  Can someone advise?

  Thank you very much

  David

  Just to take pictures, you need the IMAQdx (Image Acquisition pilots), which is a few hundred dollars.  This should be all you need if you're not processes images.  If it is not available without NI Vision to save the Image, you can convert the image into a table, and then save it using the tools of image control.  It takes more than a few steps and probably a little more time, but the price is right.

  Bruce

• How can I keep my images retrieved with IMAQdx Grab.vi of twinkle?

  I collect pictures of a firewire camera. I get the pictures I want, but the image flickers out periodically. Images must be stable in my application. I slowed down the speed using "Wait (ms)" inside the "While" loop but still have the same problem. It seems that this is caused by the buffering at different times. This seems to be a common problem, although I couldn't find good instructions to ni.com. Anyone had similar problems before, or is it just me?

  Thanks in advance.

  You have a few problems of sequencing.  For example, you view 1 Image at the same time you are copy and extract a color plan that changes the image.  These three events are in parallel.  Who knows what happens first?  You may be copying the plan excerpt, or the original color image.  Similarly, either can be displayed.

  As a general rule, whenever I use an operator that modifies the image type, I have input an image of the new type as the destination image.  This allows to maintain the type of each image unchanged.

  If you use an image in two places (in parallel), any operator who changes it should have a new image that the destination image.  If this isn't the case, the error line should be directed so that no variable processes occur before the process of mutation.

  Bruce

• IMAQdx with 10, 12, 14-bit and the display Conversion

  Hello

  I ran into a problem when you use a 12-bit with IMAQdx firewire camera.

  When you take a 12-bit image in an IMAQ I16 display Conversion method not working anymore. Vision sometimes gets unstable one can freeze my LabView. (Labview8.6, Dev.8.6.4 of Vision).

  In the attached screenshot, you can see for example that it is bringing dynamic scaling of 90%.

  Maybe is a problem with the camera data format? Or 12 bit images are fixed scaled?

  I have a fix using 16-bit only a little changing.

  Chris

  Hi, zabotage,

  His "documented bug" that has been discussed here somwhere.

  Thus, mapping works with 16-bit images only! Its documented. Even you have 16-bit type, but bit depth that lies inside IMAQdx is not 16-bit.

  Also use the depth of Bit Image IMAQ with 16 bits before function mapping (or with the depth of bit = 0, I do not remember) and everything will be OK.

  Andrey.

• IMAQdx nidaq

  Hello

  I am a newbie of LV, your patience is appreciated

  I posted in the Councils of labview, but because I work a lot with imaqdx I thought I should post here also.

  I work with a gigabit Prosilica GE 680 camera connected to my computer via Intel PRO 1000 G/T and I also work with a M NI USB 6212 BNC series. Connected to the nor-daq is a source of light on each of the AnalogOut0 and AnalogOut1, as well as 3 analog: read analog two of the three outputs, the other entrance is a signal of the camera by saying that it is imaging or not.

  I was debugging the code from someone who is no longer around to help. The code basically allows the user to synchronize two things: 1) capture and recording of a number of specified length avi, which in my hands, is typically movies of 2 sec to 200 images per second AND 2) to turn off the two sources of light at times during the movie and specified. The problem is in the precise timing of the light sources with the camera exposure period.

  From now the lights turn on and off in my movies, which is good. The problem is that the camera lights late compared to the signal of departure as evidenced by the output signal "imaging" sent by the camera in one of the analog inputs. The result is that the lights seem to lights at the beginning of the avi saved since the movie begins later that it is specified. It's not ideal.

  What changes should I make to the labview code to make sure that the camera is precisely synchronized with the analog?

  Thanks and let me know what information you need from me.

  -Alex

  Hello again,

  I solved the problem. It was a hardware problem. Using SyncOut2 instead of SyncOut1 on my camera Prosilica 680 GE gave me the schedule that I specify. No major code changes was necessary, other than changes to support the change of equipment.

  The question remains as to why works SyncOut2 and SyncOut1 does not. After consulting the technical manual for the camera, I realized that the use of SyncOut1 requires that I use the ground isolated on 12 IO pins my camera. Although I am a novice to the electronics, it seems to me that this would require a line that goes from the isolated ground my mass of the external circuit DAQ. I didn't get it, even if I did when I tried SyncOut2. This missing connection can have an impact on power SyncOut1 send a trigger to the acquisition of data.

  The reason why I started with SyncOut1 that is an SMB connection to BNC, which seemed to be a convenient way to get the camera to trigger the acquisition of data. Yes, I was lazy. If it turns out that I still need to connect an isoground on the 12pin to the DAQ extground convenience then disappears.

  I understood what the analog input wavegraphs look like now that the timing is good.

  Two additional questions that I have for those of you who have followed this thread. I supplied the information that could have led to this solution? I'm missing something in my introduction and ups tracking?

  Despite the outstanding issues I will mark this as resolved issue. Kudos to Bruce for helping me to think about it.

• Cannot create an installer containing IMAQdx in 2014 of LabVIEW

  I have a strange question in the generation of installers with a function IMAQdx in LV Application Builder 2014.

  When I was building an installer for an executable file using IMAQdx in 2013 LV, Application Builder automatically selected additional installers needed and IMAQdx drivers (Vision Acquisition) were one of them. Now I'm trying to build the project even in 2014, but in the additional installers, I see only NOR-IMAQdx DURATION 14.0. When I build the installer in 2014 LV, the size of the file is about 300MB opposed to 900MB of the installer which has been built in 2013 of LV.

  When I run the installation program from 2014 on a 'clean' Windows, install and run any application that uses IMAQdx, I do not see the cameras connected. This problem is fixed after manual installation Vision Acquisition software of DVD drivers for the device OR. After that, I can see all the cameras in the application and in MAX.

  I tried to manually add additional installers in 2014 LV, but nothing helped. It seems to me that there is no way drivers IMAQdx bundle in LV Application Builder.

  I found a post related to this and I wonder if someone can reproduce this behavior before dropping off a CAR. I have attached a simple project with a simple VI and installers of the sample in for testing. The VI allows you to select a camera (e.g. a webcam) and video image.

  Hi martin.zmrhal,

  What you see with only the Vision Acquisition Software runtimes (VAS) available in the list of installers extra is expected with the latest behavior.

  Before Vision Acquisition Software (VAS) August 2014, programs additional installation to after-sales Service, namely OR-IMAQ, e/s NOR-IMAQ and NOR-IMAQdx not only includes the runtime components but also for LabVIEW application development support. GO August 2014 and later, now only allow us the deployment of runtime components. This gives the advantage of a substantially reduced Installer size, but you can include more support development (ADE) LabVIEW applications is in the installation program.

  This change aligns Vision with LabVIEW behavior and most of the other products OR you cannot deploy generally support the complete development of a product, but rather only the runtime components. If you need to install GO with ADE on your deployment machine, you will need to distribute the complete Installer GOING on this machine in addition to LabVIEW (to make use of the SAV ADE support). To do this automatically, you will need to write a batch file to run the installer for LabVIEW, then IMAQdx.

  With respect to the second issue of not being able to see the camera, I think that what you are experiencing is that the drop of the control Session is dimmed and you cannot click on it to see a list of the cameras on the system. It is also the expected behavior for the runtimes are going TO. This does not mean that the driver is not well that discovery of cameras, and you can test this by typing the name of the camera in the Session control (for example "cam0" for the first discovery of camera on the system).

  What we are looking for with this behavior, is for vision applications deployed to abstract the end-users camera selection process. Ideally, your code must list programmatically cameras with IMAQdx list Cameras.VI and then determine what device (based on the type of bus, serial number, model number, etc.) to the target. We are working on an application note paper that clearly explain with some examples, but the idea is similar to this example of community for NI-DAQmx devices: https://decibel.ni.com/content/docs/DOC-10014.

  I'm sorry for the current lack of documentation on these features, but without a doubt, we are working to provide examples useful and other items in the knowledge base at this address. I'll post a link to the content as soon as it is available.

  In addition, Vision Acquisition Software August 2014 f1 went live yesterday: http://www.ni.com/download/ni-vision-acquisition-software-august-2014-f1/4974/en/. The patch is also available through the Update Service, and it is strongly recommended that you upgrade if you still use drivers of August 2014.

  Kind regards

  Joseph

• IMAQdx and Mightex USB Camera

  Hello

  I cannot get my Mightex USB device to work with Labview 2010 and IMAQdx.  Previously, I installed the DirectShow drivers and has been using Labview 8.5 with the IMAQ for package USB and everything worked fine.  Now I try to operate the camera with Labview 2010, however any execution of the sample programs, such as Grab.vi in Labview 2010, IMAQdx throws an unidentified error.  To help out, I tried to see if I could operate the device using the measurement and Automation Explorer version 5.0.0f1.  The list of the ' devices OR-IMAQdx "fills with two entries:
  -cam1: filter Mightex_BufferSource
  Mightex - CCD camera: Mightex_BufferCCDSource filter
  When I click on one of these to try to access the camera, I get the following error: "Error 0x8007007E the quadrant beetle number is not valid" which returns 0 results in google!

  I contacted Mightex. Don't use Labview 2010, they believe their DirectShow drivers are very good, and I know that they are installed correctly, because everything works with IMAQ for USB in Labview 8.5.

  Can anyone offer any suggestions or clues as to where would be the problem?  Should their drivers be updated specially for IMAQdx, or if the drivers of DirectShow who worked with IMAQ for USB will do work with IMAQdx?

  Thanks for your help!

  OK nevermind, I'm a fool.  A mod can delete this thread, or maybe let upward if you think it might be useful to someone someday.

  I had changed the name of the folder where the drivers and the software on my local computer after installing everything and that's what all went wrong.  I reinstalled the drivers of DirectShow and now everything works fine.

• Crash with Matrox camera mvBlueFox

  Hello

  I'm trying to interface with a camera mvBlueFox of Matrox.  It is a USB 2.0 camera, and the driver supports DirectShow interface which means that it should be usable with IMAQdx.  I downloaded the latest version of the Matrox driver and registered the DirectShow interface by their instructions.  The camera now presents itself as a device of NOR-IMAQdx NOR-MAX, but the problem I have is that as soon as I click on the camera in MAX, MAX crashes immediately.  Any ideas on that?

  Here is the configuration that I use:

  Windows 7 Pro 32 bit

  IMAQ 4.6.1

  IMAQdx 3.9.1

  IMAQ I/O 2.5

  MAX 5.6.0f0

  I also tried an old Windows XP computer that has earlier versions of the IMAQ and MAX installed with a similar result.  I have attached to the crash report if that helps too.

  Thank you!

  The accident is the (misnamed) 'DirectShow_acquire.ax' binary, which is an element that is the seller of the camera Matrix Vision, not Microsoft delivered.

  IMAQdx tries to query the IAMVideoProcAmp interface on the capture device and this call blocks. I think you'd have to ask Matrix Vision to debug this problem because they have symbols for their own dll and that you can see why it crashes.

  Eric

• Several acquisitions of IMAQdx USB camera simultaneously

  Hello

  I am trying to acquire 2 or more focused on the USB webcams at the same time, but one of the cameras always error. I replaced IMAQdx ENTER with IMAQdx SNAP and that seems to work to capture frames. But I would really like live food to webcams both (or several) if possible. The idea is to consult the live wire of two cameras and make necessary adjustments in the rest of the material to my system and then begin to capture images every 10 seconds approximately (from two or several webcams).

  Attached, multicamera_op_v1 = VI to get two webcams live food.

  multicamera_op_v2 = VI to get direct feed from two webcams and then captures frames from two cameras.

  I would like suggestions.

  Thank you