Toggle between two cameras

[DominickC]

I've just wired the value of the joystick being unflattened to the value Vision, which created an orange wire. Will this work for me?

[NeatNit]

Originally Posted by DominickC

I've just wired the value of the joystick being unflattened to the value Vision, which created an orange wire. Will this work for me?

Probably not. Instead, right-click the Value input and create a constant to it. Create another copy of this constant, and then make sure that each one is set to the tab you want. Then, you can use use the Select function (or case structure, or any other way you want) to choose between the constants.

Hope this helps!

[DominickC]

Ah, NOW I get it! Thanks Alan, Greg and NeatNit!

[Greg McKaskle]

I have never tried to open a joystick connection in multiple apps using DirectInput, which is what the DS uses.

I'm leaving town in an hour, so I'll describe it and I look forward to hearing the results.

In the LV dashboard project code, try using the Connectivity>>Input Device functions to open a joystick and read back the buttons. Please note that these VIs aren't quite as flexible as the stuff used for the DS, so once you open a connection, it is not possible to reposition the USB port of the joystick until the DLL leaves memory. This shouldn't be an issue except during development when it causes head-scratching.

Greg McKaskle

[4085]

Hey i found this intresting i just programmed a second camera in and got it within the tabs, Dominick, can you please show me how you programmed in the toggle between the two cameras. With pictures please :/ help please and THANK YOU. Pm me if you can

[DominickC]

I'm going to run with the assumption that you've got a second camera running in an additional "Camera" tab.

First, you'll need to pass a boolean from a joystick or some other input to the DS. This is done via "High Priority User Data".

Then, on the block diagram, right click on each of your "Viewer" icons, then navigate to Create>>Property Node>>Value. You'll have to change each of these property nodes to write by right clicking on them.

Take the boolean you received and create a case structure. In the true case, wire the "Camera Image" enum to the first viewer property node. In the false case, wire the remaining enum to the second viewer property node.

[4085]

Thanks for your help!

[MAldridge]

Originally Posted by Greg McKaskle

In the LV dashboard project code, try using the Connectivity>>Input Device functions to open a joystick and read back the buttons. Please note that these VIs aren't quite as flexible as the stuff used for the DS, so once you open a connection, it is not possible to reposition the USB port of the joystick until the DLL leaves memory. This shouldn't be an issue except during development when it causes head-scratching.

Greg McKaskle

I actually tried that back during the competition season when I needed to halt vision output while the robot had the shooter spun up, when I did it, I got a slew of errors. The first of which was the lack of an 'lvinput.dll' (or similar, can't remember what it was beyond that it was accompanied by an error code). At the time, I attributed this to two pieces of software wanting the same hardware, and a slightly foggy mentor (who was recovering from a head injury) agreed. We scrapped it and reworked the dashboard to have a key binding that could toggle vision on and off.

I would say that the easiest would be to get some kind of proxy driver that would let you make two software joysticks out of one software joystick, but that's me. I am firing up labview now, and I will give it a try using this method again.