|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: Recording Two Video Streams via Labview Dashboard
The way I had implemented it was to duplicate the "WPI_CameraRead MJPG For Dashboard" VI and give it a separate IP corresponding to the other camera. In order to use more than one camera, you have to assign them unique IPs and explicitly address them in the Dashboard code; you cannot use the "Camera IP" local variable, as it will only return one IP (not sure which though).
It's funny that you mention this though, because I am currently trying to fix a problem where when one camera is disconnected, waiting when opening one TCP port causes pausing in the reading of the image in the other. I am currently working on this problem. Will post when I figure anything out. |
|
#2
|
|||
|
|||
|
Re: Recording Two Video Streams via Labview Dashboard
With regards to the pausing, I'm guessing you're reading them both in the same while loop. That VI blocks until it reads in an image. To solve this, move one to a separate loop.
|
|
#3
|
|||
|
|||
|
Re: Recording Two Video Streams via Labview Dashboard
Quote:
While the one camera is waiting on a connection to open (TCP Open), it blocks the TCP Read operation of the other camera used to get the image. I have "solved" this problem by limiting the number of times a camera can attempt to connect (in case one is unplugged). Then, I decide when to try again based upon what the robot is doing. In my case, it will retry the vision camera when shooting, and retry the intake camera when driving around (robot tells the Dashboard what to do via NetworkTables). I have still not solved the problem of being able to record both at once, although I assume it may have something to do with a conflict in resources (access to file system, encoding, etc.). |
|
#4
|
|||
|
|||
|
Re: Recording Two Video Streams via Labview Dashboard
I think that the solution is to make a second call to the Dashboard_Create AVI vi. Pass in the name you want for the second camera. Oh, and you'll want to make the Dashboard Create VI be reentrant. The Preallocated clone will compile such that the feedback node inside the VI is unique per call and will correctly manage more than one file refnum.
Greg McKaskle |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|