Cameralink triggering

[Adam_H]

Hi bestbier,

You can force the trigger line low programmatically by using the CWIMAQSignalActions object.  Set it to Unasserted and it will drive the trigger low for you.  There is no way to configure its state at startup.

[bestbier]

Any ideas why I can't add a pulse train?

[Adam_H]

Hi bestbier,

I am not exactly sure why this is happening.  One thing to try would be to delete all your references to IMAQ and then re-add them just in case something was not added correctly.  Also do you think you could attach a screen shot of it just so I can take a look at it.

[bestbier]

Hi Adam

See attached screenshot. I created a new project in VB and added an IMAQ control and then opened it's properties window.

Best regards

Bestbier

[seVEMes]

Hi Bestbier,

You said in an earlier post that if you try the programmatic approach there is no pulse. What does your line of code look like? I've interpreted what Andrey Dmitriev posted and using the NI-IMAQ Function Reference Help under Signal I/O Functions » imgPulseCreate2 and this is similar to what his code would have looked like if it were in a text based language. I just copied and pasted the Usage section of the help document and added in parenthesis what was input in the LabVIEW code:

rval imgPulseCreate2(uInt32 timebase(PULSE_TIMEBASE_PIXELCLK), uInt32 delay(0.03), uInt32 width(0.1), IMG_SIGNAL_TYPE signalType(IMG_SIGNAL_STATUS), uInt32 signalIdentifier(IMG_IMEDIATE), uInt32 signalPolarity(IMG_TRIG_POLAR_ACTIVEH), IMG_SIGNAL_TYPE outputType(IMG_SIGNAL_EXTERNAL), uInt32 outputNumber(0), uInt32 outputPolarity(IMG_PULSE_POLAR_ACTIVEH), uInt32 pulseMode(PULSE_MODE_TRAIN), PULSE_ID* plsID);

Please post how similar this code is to what you implemented.

[bestbier]

Hi

Code I used is as follows (VB2005):

        Dim Pulse1 As NationalInstruments.CWIMAQControls.CWIMAQPulse

        Dim Signal1 As NationalInstruments.CWIMAQControls.CWIMAQSignal

        Pulse1 = AxCWIMAQ1.Pulses.Add

        Pulse1.Action = NationalInstruments.CWIMAQControls.CWIMAQPulseActions.cwimaqTrain

        Pulse1.Delay = 1

        Pulse1.SignalLineNumber = 0

        Pulse1.SignalPolarity = NationalInstruments.CWIMAQControls.CWIMAQSignalPolarities.cwimaqActiveHigh

        Pulse1.SignalSource = NationalInstruments.CWIMAQControls.CWIMAQSignalSources.cwimaqImmediate

        Pulse1.Units = NationalInstruments.CWIMAQControls.CWIMAQPulseUnits.cwimaqPulseUnitSeconds

        Pulse1.Width = 1

        Signal1 = AxCWIMAQ1.Signals.Add

        Signal1.Action = NationalInstruments.CWIMAQControls.CWIMAQSignalActions.cwimaqGeneratePulse

        Signal1.Line = NationalInstruments.CWIMAQControls.CWIMAQSignalLines.cwimaqExternal

        Signal1.LineNumber = 0

        Signal1.Pulse = Pulse1

Regards

Bestbier

[Adam_H]

Hi BestBier,

It is kind of a strange problem.  Are you placing down the .NET control?  What version of the IMAQ driver are you using?  I think it might be a good idea to try and reinstall the IMAQ driver.  If you are not using the latest IMAQ driver (the latest is 4.1) I would also suggest trying a newer version.  You can find the newest version here.  NI Vision Acquisition Software 8.6

Message Edited by Adam_H on 01-19-2009 03:03 PM

[bestbier]

Hi Adam

Yes, I have IMAQ 4.1 with Vision Development Module 8.6 and Vision Acquisition 8.6.

I got the PC I am planning to give to my customer - brand new unused, installed Windows XP,IMAQ, Vision and VB2005 and the same NI-1427 from my developement PC -Same problem!.

Could it be that my camera file is not correct?

I do not currently have a camera connected, could that be a problem?

Could it be the 1427's firmware(card is about 12 months old)? - Where can I get the latest firmware? (PCs with card installed is not connected to internet).

Best regards,

Bestbier

[Adam_H]

Hi bestbier,

I know it is a fresh install but could try uninstalling and reinstalling IMAQ.  It is possible that something went bad on the install and is causing this problem.  You should not need to have a camera connected to tell it to add a pulse.  I have no problem with that on my end.  I am 99.9999999% sure it is not the camera file but there is an easy test to be 100% sure.  Set the camera file to a camera file that ships with the driver and see if this changes anything.  You can do this by right clicking on the camera in Measurement & Automation Explorer and a different selecting camera.  Pick one from the list that is the result of this menu.  Let me know how it goes.

[bestbier]

Hi Adam

I removed the card and uninstalled all NI software, reinstalled required software and reinstalled card, Windows detected new hardware and installed drivers. No luck.

Tried one of the included camera files - No luck.

Changed the card's firmware to the version that does not include 64bit support and still no luck.

I need to order another card, but want to sort this out before I do that.

Best regards

Bestbier