Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

acquire at 800 mbps with avt pike on 64-bit windows vista

Solved!
Go to solution

Hello forum,

     I'm using labview 2010 (32-bit), on a 64-bit windows vista system (yea, I will upgrade my labview soon) and i have an AVT pike f023b camera connected via a 1394b firewire.  

 

Before, on a 32-bit system, i was able to acquire at the 800mbps using the AVT buspackage, but it does not work with 64-bit systems.

 

does anyone know how to get  800mbps with the pike camera using labview??

 

thank you.

veritas

 

0 Kudos
Message 1 of 11
(4,944 Views)
Solution
Accepted by topic author veritas

If you are using a 3rd-party bus driver along with IMAQdx (presumably so things like 800Mbit operation will work on Vista) you will need to contact that vendor to see if they have a 64-bit version available. Otherwise IMAQdx will use the native OS-provided drivers for the bus interface. The OS-provided drivers do not support 800Mbit on Vista, but they do on Windows 7.


Eric

Message 2 of 11
(4,937 Views)

saw both your posts.

 

windows 7, here I come!

 

thanx!

 

0 Kudos
Message 3 of 11
(4,934 Views)

hello

      So, currently, for testing, i have a 32-bit system with windows 7 installed, and am using labview 2009 32-bit.  I'm trying too acquire at 800s using a 1394b firewire using the AVT pike F032b camera (i've successful gotten 800 on a 32-bit vista using the AVT bus package).  

 

I get a drop down that goes to 800, but it gives a timeout error  0xbff6901b.  If i  run it at 400mbps, it works fine...but, of course, acquires at a slower frame rate.  Does anyone know how I can fix this error?

 

thanks!

veritas

 

0 Kudos
Message 4 of 11
(4,886 Views)

Hello,

 

Let's have you run the Camera Validator (http://digital.ni.com/public.nsf/allkb/EBE3BBBEF4FEA92786257225006FF242) to see if we can extrapolate anything from the report. When you do this, be sure to set it to the 800Mbps setting. Perhaps this could be something with frame rate/image size/packet size.

 

-Zach

Message 5 of 11
(4,866 Views)

Hi there. thanks for the quick reply.

 

So i ran what you requested (both when i had it at 400, and then at 800)

 

It just keep running for a very long time (>1 hour)...so i just stopped it.  hope it's sufficient.

 

Not really sure how to interpret it...but definitely see more timeouts with the 800s

 

notably, here's the pack information for 400 and 800 from the measurement and automation GUI:

400: 4096

800: 5424

 

Download All
0 Kudos
Message 6 of 11
(4,861 Views)

here's images of the screen (it's not connected to internet) for which it works(400s), and for which it errors (800s)

 

Download All
0 Kudos
Message 7 of 11
(4,860 Views)

Just another thing, I see that the failures occurred at larger frame sizes, but previously, on a veryyyy similar computer, using the avt bus package (32-bit vista), i'm able to get 314fps, at 800.  If windows 7 solves the previous 1394b issues, I'm assuming that it should perform at around the bus package?

 

0 Kudos
Message 8 of 11
(4,856 Views)

Hello,

 

They are completely different driver offerings but I would think that they should not be significantly different. From the look of your report, this seems to be following a pattern with the larger image and packet sizes but it is odd that at a 400Mbps setting you don't get a timeout with a packter size of 4096 and you do get a timeout on 800Mbps at a packet size of 4040. We will have to look at this further.

 

-Zach

0 Kudos
Message 9 of 11
(4,811 Views)

yea...i noticed that...and I'm really not sure why that is the case.

 

is there anything else I can report to you to help?

 

thank you again,

veritas

 

0 Kudos
Message 10 of 11
(4,789 Views)