Okee, so i have an application were i need to run 3 Visca cameras on my Atem and it just won´t get it to work..
For the answer how to get your Visca cameras connected see this post!! viewtopic.php?f=4&t=61265&p=352368#p352368
Note: I have never seen anyone report that they got the Visca up and running on the Atem while this feature is in there for a good 2 years now!!
But for this function to work you need the official 1/2M/E hardware panel to get it to function. This is function is not available in the software
What it does (or not does) You connect the camera to the Atem on the 422 port. (in my case for testing i use a Sony D70 at the moment. But i have BRC300 and other HD Visca cameras in my Rental so i could get them too for testing. Anyway for testing purposes this model does fine.)
I wired the camera up with a Salea logic analyser to the Atem. Making sure i follow the connections like they say in the manual.
After setting the Baudrate and connecting it all up. Pushing "Detect" will send out an Address Set message on the 422 bus. ( 0x88 0x30 0x01 0xFF ) Which is in HEX and exactly what we needed on the Visca bus.
The camera reacts with sending the Adres back + 1 ( 0x88 0x30 0x02 0xFF ) (Exactrly as the VISCA protocol descibes it!! ** This is for other cameras on the line that are daisy chained to get an address and do +1 until the last camera has his address. The loop back will ensure that last address is send back to the controller (Atem) and he will know that and how many cameras are connected! The last message -1 will be the total amount of cameras connected.. But in this setup it is just 1 camera.
Unfortunatly the Atem keeps reporting there are "0 VISCA devices connected" So it seems that the Atem does not see the message that the camera send out, or does not handle this like it should be!!
And yes i crossed the return wires to the atem a few times to make sure they did not ran inverted..
I made 1 mistake by turning the wires on my logic analyser.. So it turned up right in the software.. But whoops the connection to the atem did not turn with that
Later this week i will make a capture of the visca camera and Sony visca remote to show what it should look like.
So yes i got it to work after some wire twists.. I will make a piece of documentation on how to wire exactly from pin to pin from the atem to the camera's upcoming week.!! For futher reference to anybody that wants to use this function in the future..
![:-/ :roll:](./images/smilies/icon_rolleyes.gif)
For the answer how to get your Visca cameras connected see this post!! viewtopic.php?f=4&t=61265&p=352368#p352368
![;-) ;)](./images/smilies/icon_e_wink.gif)
Note: I have never seen anyone report that they got the Visca up and running on the Atem while this feature is in there for a good 2 years now!!
![:-( :(](./images/smilies/icon_e_sad.gif)
But for this function to work you need the official 1/2M/E hardware panel to get it to function. This is function is not available in the software
![:-| :|](./images/smilies/icon_neutral.gif)
What it does (or not does) You connect the camera to the Atem on the 422 port. (in my case for testing i use a Sony D70 at the moment. But i have BRC300 and other HD Visca cameras in my Rental so i could get them too for testing. Anyway for testing purposes this model does fine.)
I wired the camera up with a Salea logic analyser to the Atem. Making sure i follow the connections like they say in the manual.
After setting the Baudrate and connecting it all up. Pushing "Detect" will send out an Address Set message on the 422 bus. ( 0x88 0x30 0x01 0xFF ) Which is in HEX and exactly what we needed on the Visca bus.
![:-) :)](./images/smilies/icon_e_smile.gif)
The camera reacts with sending the Adres back + 1 ( 0x88 0x30 0x02 0xFF ) (Exactrly as the VISCA protocol descibes it!! ** This is for other cameras on the line that are daisy chained to get an address and do +1 until the last camera has his address. The loop back will ensure that last address is send back to the controller (Atem) and he will know that and how many cameras are connected! The last message -1 will be the total amount of cameras connected.. But in this setup it is just 1 camera.
Unfortunatly the Atem keeps reporting there are "0 VISCA devices connected" So it seems that the Atem does not see the message that the camera send out, or does not handle this like it should be!!
- Atem Visca data capture.png (122.46 KiB) Viewed 76386 times
And yes i crossed the return wires to the atem a few times to make sure they did not ran inverted..
I made 1 mistake by turning the wires on my logic analyser.. So it turned up right in the software.. But whoops the connection to the atem did not turn with that
![:-D :lol:](./images/smilies/icon_lol.gif)
Later this week i will make a capture of the visca camera and Sony visca remote to show what it should look like.
So yes i got it to work after some wire twists.. I will make a piece of documentation on how to wire exactly from pin to pin from the atem to the camera's upcoming week.!! For futher reference to anybody that wants to use this function in the future..
![;-) ;)](./images/smilies/icon_e_wink.gif)
Last edited by Xtreemtec on Wed Jul 26, 2017 10:08 am, edited 2 times in total.
Daniel Wittenaar .:: Xtreemtec Media Productions ::. -= www.xtreemtec.nl =-
4K OBV Trailer, ATEM TVS HD, 4M/E Broadcast Studio 4K, Constelation 8K, Hyperdeck Studio 12G, Ursa Broadcast 4K, 4K fiber converters with Sony Control
4K OBV Trailer, ATEM TVS HD, 4M/E Broadcast Studio 4K, Constelation 8K, Hyperdeck Studio 12G, Ursa Broadcast 4K, 4K fiber converters with Sony Control