Master/Slave on Weapon is there a wireless Mode?

[Mike Finegan]

OK once again I see conflicting information even from RED support (posting here).
I was told by RED tech support that only with GigE between identical DSCM2 cameras - you could get frame level sync between master and slave suitable for top production 3D stereo rig.
But then I see statement from RED support in this forum that no it just duplicates settings. Which RED support statement is correct?
Also I see Mika statement that you can do without GigE - using even wireless - but I do not see frame sync statement anywhere (which is not same as using deneke to gen lock cameras).
Any production 3D stereographers using DSMC2 and care to weigh in?

 

[Mikael Lubtchansky]

OK once again I see conflicting information even from RED support (posting here).
I was told by RED tech support that only with GigE between identical DSCM2 cameras - you could get frame level sync between master and slave suitable for top production 3D stereo rig.
But then I see statement from RED support in this forum that no it just duplicates settings. Which RED support statement is correct?
Also I see Mika statement that you can do without GigE - using even wireless - but I do not see frame sync statement anywhere (which is not same as using deneke to gen lock cameras).
Any production 3D stereographers using DSMC2 and care to weigh in?

As far as I know only tri-level sync from a generator via sync port can provide accurate sensor sync.
For remote control / master slave, you can use GIG-E or CTRL port (only for 2 cameras as it is a direct RX-TX connection). Via wifi it is not really possible for now, and the RTmotion multiplexer will allow multiple cameras via CTRL port so you can built rigs without GIG-E connectors and router.

The only way I can think of avoiding the tri-level box (for a 2 camera rig) would be to feed one camera SDI out to the other's camera GENLOCK in but I have never tested this on RED and not sure it is supported.

FYI Dave Winder is not part of RED support team but is from the engineer team so I think he can be trusted as a very good source of info on those tech questions ...

 

[Inge Wegge]

I tried to set up two cameras using the rs232-to-rs232 cable on the ctrl ports yesterday, but I could not get it to work. The manual says "camera-to-camera
communication is possible only via GIG-E" on page 106 (v6.3)... Has anyone got this to work?

 

[Mikael Lubtchansky]

I tried to set up two cameras using the rs232-to-rs232 cable on the ctrl ports yesterday, but I could not get it to work. The manual says "camera-to-camera
communication is possible only via GIG-E" on page 106 (v6.3)... Has anyone got this to work?

Which cable did you use ?

There was one for sale on RED.com few months ago that was not wired correctly for this application and required 2 wires to be reversed sonthat TX talks to RC and vice versa...

Also make sure communication menu is set to camera to camera on the SERIAL tab...

 

[Inge Wegge]

So I guess I have to open the cable and change TX and RC on it... Anyone knows the colours on the cables and which is which?

 

[Mikael Lubtchansky]

So I guess I have to open the cable and change TX and RC on it... Anyone knows the colours on the cables and which is which?

there should be 3 wires needed, check the pins for CTRL port in the RED DSMC manual.
to work it needs to be :

GND <-> GND
RX <-> TX
TX <-> RX

 

[Inge Wegge]

I think I got it, but I'm not 100% sure if the black mark on top is the top looking at the camera, or if it is where the red mark is. Anyone?
It's like this if the top is the top: 1=red, 2=white, 3=yellow 4=blue, -on the RED rs232-to-rs323 cable.

 

[Kwan Khan]

there should be 3 wires needed, check the pins for CTRL port in the RED DSMC manual.
to work it needs to be :

GND <-> GND
RX <-> TX
TX <-> RX

Planing to have RTMotion CTRL port multiplexer for sure, however just wanted to confirm if this setup will work on Multiple Ravens (with DSMC2 V-lock I/O expander and Jetpack (HDMI) together)

 

[Mikael Lubtchansky]

Planing to have RTMotion CTRL port multiplexer for sure, however just wanted to confirm if this setup will work on Multiple Ravens (with DSMC2 V-lock I/O expander and Jetpack (HDMI) together)

This works great but without the RT multiplexer you can only connect 2 cameras together via CTRL

I think I got it, but I'm not 100% sure if the black mark on top is the top looking at the camera, or if it is where the red mark is. Anyone?
It's like this if the top is the top: 1=red, 2=white, 3=yellow 4=blue, -on the RED rs232-to-rs323 cable.

Yes it should be the red mark looking at the camera connector (orientation can differ depending in the module etc)
If the color you indicate are similar on both ends you will need to cross the RX and TX ones to make it work.

 

[PatrickFaith]

for what is worth, RTMotion is finalising a CTRL port multiplexer that will allow master slave (RCP only, no tri-level genlock sync as this requires separate wiring as explained by Dave above) over CTRL port so you can make camera rigs with more than 2 cameras without going GIG-E... it will also allow other interesting stuff... more info here :

http://us10.campaign-archive2.com/?u=5f16a41cde25b426e17690d67&id=8de5b4226c&e=21d33e1544

PS : this product was created out of necessity since some of use had a real need for this, and altho the market is limited for such a specialised product, Kris said he should be able to keep the price affordable.
And FWIW (disclaimer) RTMotion products are super foolcontrol friendly and I personally love their stuff but I do not have any direct benefit or interest in RTMotion sales whatsoever.

This looks excellent, integration to fool control another benefit. VR productions can get super expensive really quick. I also like the concept that these can link multiple systems, I can't afford having all the camera's in a vr setup to be dsmc2 so I also need to figure out how to integrate with the 8 to 10 other cameras.