Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

RT Motion MK 3.1 - Run/Stop function on Red DSMC2

NJ_CAIN

Member
Joined
Apr 20, 2016
Messages
16
Reaction score
0
Points
0
Has anyone managed to configure the Run/Stop sync between RT Motion MK 3.1 & any Red DSMC2 camera's? I'm plugged into a Red Scarlet W & have been trying to figure it out with RT Motion over the phone but they are a bit stumped. We know that Red has changed so that you need to select Arri rather than Red in the menu of the hand unit but we cannot successfully configure the Red GPIO menu to make it work.
The lights are changing as they should on the receiver & hand unit, but the camera only triggers record when we unplug the sync cable!
 
Mine works fine on magnesium weapon
 
Hey Jake,

that's great to hear! Would you mind sharing exactly how you have set this up please?
 
I'm on a shoot today but not with my camera. Plug into the sync port, not control, select epic in RT menu, then in camera I believe it's just gpio
 
Just got off a feature or used it worked perfectly
 
We've tryed that with various settings but nothing seems to work. Think it may be a Scarlet W issue
 
Here's what I'm looking at in the Menu's if anyone can point me in the correct direction
 

Attachments

  • IMG_0443.jpg
    IMG_0443.jpg
    87.1 KB · Views: 0
  • IMG_0444.jpg
    IMG_0444.jpg
    89.3 KB · Views: 0
Hi! This is actually on our list to investigate so we can give clear guidance,

This is what we know so far;

- RED changed their trigger technique for DSMC2 modules, *except* the base expander which is the same as DSMC1
- The "new" trigger technique is the same as ARRI, so switching the RTMotion trigger type to ARRI should work on non-base-expander DSMC2 modules
- Despite that, our Scalet-W with Jetpack actually doesn't trigger with the lemo cable and set to ARRI as would be expected... but our firmware is ancient so we'll update the cam and do a proper check ASAP

Kris
 
Ah, I have the base expander that's why mine works I suppose
 
Hi Kris,I've forwarded the response I've had from Red to you guys via email but will post it here also:Sorry to hear about the issue you are encountering with the camera. Based on the Brain GPIO settings on the image below, the settings look to be correct.The DSMC2 V-Lock I/O expander is an industry standard close style circuit as opposed to the DSMC2 Base Expander which is Schmitt trigger and requires 3.3v constant voltage. Does the RT Motion MK 3.1, when set to 'Camera - Arri', fit the close style circuit requirements? Just to confirm, have you tried different cables? Do you have access to another DSMC2 V-Lock I/O you can run some tests with?Attached is a screenshot of our WEAPON Operation Guide on Page 172 that goes over in more detail the required specs for Start/Stop

https://redray.zendesk.com/attachments/token/xWNNDkyet7UAiwi6Gs227Q0Fi/?name=Page+172.png
 
Any luck with this? What was the resolution? Having same problem with new rtmotion and epic-w and i/o vlock.
 
Back
Top