LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Trying to use a simple property node from Imaq1394 Init

Hello
 
I am trying to configure my PGR 1394 DragonFly Express Camera.  The company sent me a vi that another customer said worked and was able get the serial number from the camera.  When I opened the vi, I was dissapointed to see it is broken!
 
The brokern arrow comes from the wire from the MAQ1394 Init vi session output to the input of the property node reference input.  The mouse over the broken wire says:
 
"You have connected terminals of two different types.
The type of the source is datalog file refenerce of.
The type of the sink is IMAQ1394."
 
What is strange is that the property node has the IMAQ1394 class written in the top section.  When I drop down my own property node on my own vi it says App.  Somehow, I assume, this vi worked somewhere in order to get the class name to read IMAQ1394. Yet now it does not work on my machine.
 
Ultimately I am simply trying to place the camera in trigger mode yet I cannot get the vi to build.  If I use the IMAQ1394 read or write sensors it blows LabView out of the water.  (Labview is corrupted and must be restarted message)  The failure of that attempt led me to asking PGR for help and they said a customer had some success with the above vi.  Which does not work for me.
 
So how do I use a property node using a reference from a 1394Session out?
 
Why would this vi be broken on my machine and not on another?
 
I have 2 attachements.  The Vi in question.  You need IMAQ vision and 1394 installed and the screen shot of how the vi looks on my PC.
 
Any advice would be appreciated!
 
 
Tinman
 
 
 
Download All
0 Kudos
Message 1 of 3
(2,637 Views)

Sorry, looks fine on mine.  LV 8.0 and Vison 8.0.

Matt

Matthew Fitzsimons

Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison
0 Kudos
Message 2 of 3
(2,631 Views)
Hi Tinman -

The VI opens properly on my system, in all current versions of LV and with IMAQ1394 v2.0.2.  This sounds like a simple corruption in your driver installation.  Try uninstalling the driver, rebooting the system, and then installing the latest version of the driver you own a license for.  (there are three types of licenses -- v1.0, v1.5-2.0.1, and v2.0.2+).
David Staab, CLA
Staff Systems Engineer
National Instruments
0 Kudos
Message 3 of 3
(2,617 Views)