Welcome to our community

Be a part of something great, join today!

Register Log in
  • 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 :)

Tilta nano, what setting to trigger Komodo.

Björn Benckert

Björn Benckert

Well-known member
Joined
Dec 5, 2007
Messages
7,423
Reaction score
74
Points
48
Age
52
Website
www.syndicate.se
Have had my tilta nanos for a while but when I updated the firmware in camera a while back I can't find the setting to activate the triggering. Any clues. GPI setting somewhere. As I remember it was in system settings and set it to GPI but I must be mistaken as I can't find it. Also can´t find a single note about this on the web strangly. Anyone know?
 
There is no setting in the camera for this, just the R/S cable from the FF motor to the Ext port. Should work out of the box.
 
Alex Zeder said:
There is no setting in the camera for this, just the R/S cable from the FF motor to the Ext port. Should work out of the box.
Click to expand...

Hmm. Worked before, now the hand control hums but the camera does not start record... Might be me having shitty batteries in the hand control.


I have two of them and I got the same problem on the one sitting on my Monstro... Think I got the settings right but it simply does not make the camera record when hitting the button on the hand unit.
 
Alex Zeder said:
But you can control focus with it?
Click to expand...

Yes that's the thing. All else works on both of the kits I have but not triggering camera... and it did work before on the Komodo. For Monstro tilta first sent me the wrong cable, not suited for I/o module then now when I updated Komodo and got the new cable for monstro the triggering does not work on any of them. Frustrating as F. I really like these little motors but without the record function it kind of sucks.
 
Related- I couldn't get R/S to work with the Tilta Nucleus / 4-pin out of the extension unit- Red seemed to blame Tilta, Tilta blamed Red.
 
Duncan de Young said:
Related- I couldn't get R/S to work with the Tilta Nucleus / 4-pin out of the extension unit- Red seemed to blame Tilta, Tilta blamed Red.
Click to expand...

On the DSMC2 cameras there are two different protocols depending on what module your using. V lock I/o has one protocol with a closure and then other modules use power
 
YES,

What's going on? it worked in the previous firmware and now, can't seem to get it to run stop????? Anyone have the fix?
 
Mestizo Devon said:
YES,

What's going on? it worked in the previous firmware and now, can't seem to get it to run stop????? Anyone have the fix?
Click to expand...

Hmm, So at least I'm not alone. Something odd with Komodo firmware?
 
Did you save the old firmware files and can roll back for a test now? FWIW, I'm using the cable to the ext port, not 4-pin, and this still works with 1.6.5.
 
Alex Zeder said:
Did you save the old firmware files and can roll back for a test now? FWIW, I'm using the cable to the ext port, not 4-pin, and this still works with 1.6.5.
Click to expand...

I'm not sure its worth the hassle, I guess if the latest iteration of firmware does not do the triggering part correctly then RED will crack down on it in the next update.
 
I opened a support case with red will se what they say...

I also have the same problem with my other camera Monstro with I/O vlock module bought two cables from tilta... Shit does not work. Think I did all the needed settings in communication but still no go. Tested with both my nano systems.

Had it working before so not sure what it can be.
 
I'll check my Dragon 6K. It was working on both Komodo and 6K..... I put in a ticket also, I have gotten no response....
 
Got this reply from red. Anyone knows if there is a special setting that needs to be applied fir GPI triggering? As I remember when I first got the nanos, I went into the communication setting and change something but I don't remember what, and then it worked... Now when I go in there I don't find anything GPI related... Any clues?

Will film a little clip for John and send the log file.


John (RED Digital Cinema)

Mar 31, 2022, 2:47 PM PDT

Hello Bjorn,

Thank you for contacting RED Support.

I'm not aware of any changes in recent firmware that would affect camera triggering, via any of the available methods including via EXT, GPI, or CTRL. We'd recommend brief troubleshooting to ensure that we have all the necessary information regarding your symptom(s). Please copy the questions below to your reply email and include your answers to each, if applicable:
  • Does rolling firmware back to the previous working version resolve the issue or does it persist?
  • Is your triggering cable feeding into camera EXT, expander module GPI, expander module CTRL, or something else?
  • Can you please provide a photo or short video of your camera set-up, including the cable configuration, and the symptom you're experiencing?
  • Please send a log file for further analysis. The log file can be saved by going to MENU > MAINTENANCE > SAVE LOG. This will write a text document to your RED media that is about 5MB in size, ending in the word "log." This may help us to pinpoint the root cause of this symptom.
Thank you, I look forward to hearing from you.

Best Regards,

John | Technical Support
Phone: +1-949-206-7900 Option 3
 
You must log in or register to reply here.
Back
Top