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 :)

Camera self rebooting...

Looks like it does happen on Build 16.

PaulClements said:
Our other camera went on the last beta build of build 17 (About a day before the release build came out) and it hasn't had the same problem. Maybe something changed between the last beta and release? Or maybe it's just something that happens to certain cameras for whatever reason?
Click to expand...

Paul, still no problems with BETA Build 17?

If so, can someone please upload the BETA build 17 that came out right before the Release Build 17?

That one seemed to be more reliable than Release Build 16, Release Build 17, and BETA 18.


Chris Oben said:
Using a build 16 RED. Same thing as reported above . . . automatically restarts itself and LCD goes blue.
Click to expand...

Dave Edsall said:
I've had this issue on both B16 and B17.
Click to expand...

sandro de frino said:
The same problem happened to me while nobody was touching it, 2 or 3 times.
It was with the cradle and the battery, with the build 16.
Happened again after upgrade to 17.
Click to expand...
 
Brent@RED said:
All fair enough, Steve. Not to get into a philosophical debate - but there is no such thing as "random" :) If some people (some very frustrated people, I know) are seeing this issue, there has to be a root cause. So, we want to do what you are doing here at RED to try to get the reboot issue induced. Tell us temperature, tell us what project settings, tell us firmware, tell us accessories hooked up to gear (both RED and third party), tell us power sources, etc.

And, yes, you are right - it could be that no "one thing" is the trigger of an issue. It could be four things in combination that cause an effect. In fact, with something as relatively low in quantity as reported with this issue, it means there are a lot of factors involved.

So, if you are getting this issue, please file an incident ticket with the above information. Right now, we are only going to be able to tell you "we are working on it". But the more data we have, the more we can zero in.

Hope that helps clarify and, rest assured, we have our top guys looking into this.

BC
Click to expand...

hello Brent

Spoke to sean today i have 2 bodies doing this as well down here in Argentina. We are testing everything happened on 17 switched to 18beta still happening and reversed it to 16 and its still happening. re format drives off the camera each time to take the drive thru clean sorta speak. It has even happen without any media on the camera...but heres the best of all it happen during build re-install... im in contact with sean but i think its going to crawl up to you...cameras are virtually brand new... one body has been on one job and the other is going out for the first time this weekend comming up.

what are we thinking at this point??
 
JanneJansson said:
Reading this thread it seems to be different levels of problem.

1) Invironment: heat, coold, dust, vibrations.
2) Configutation: lose cables, wrong voltage, too big power drain, faulty accesory.
3) Firmware: bugs, memory issues, leaking memory, using up all working memory.
4) Internal connections: Lose cables, lose slot-in boards, movement among boards.
5) Hardware construction problem: Component change from old to new series camera. New component not behaving exactly as old, but enough to look "ok". Example could be some small power regulator is over heating and is changing main voltage, forcing reboot.

..or any combinations of this.
Click to expand...

Are you sure you didnt miss anything?
 
sergue, I PM'ed you. Sean filled me in.

All, we are still trying to track this down. Don't take the relative silence on this one issue as a lack of effort. As soon as I have news, we will let you know.

BC
 
Brent@RED said:
All, we are still trying to track this down.
Click to expand...

Brent, how about putting the BETA build 17 (the one that came right before the Release build) on red,com/support? Someone who is having problems with the firmware that is currently available may want to give it a try.

sergue said:
question for all...1. is this happening to anyone without the factory upgrades?
Click to expand...

Yes

Cail Young said:
#1295 predates the shipping upgraded units and (at the time) had not gone back for upgrade.
Click to expand...

Mike Prevette said:
I really think this is a Firmware issue. I have never had rebooting problems before release build 17 ... Also my camera has not been updated yet. #1686
Click to expand...
 
I'm in the same boat as Cail and Mike.

Mine hasn't been updated and NEVER did it before 17.
 
Well, #1295 is on its way back from upgrade and (hopefully) repair. We shall see on Monday...

Here's the list of updates from 3.3.9 to 3.4.1 (Beta 17 to Release 17)

Significant changes since Build 17 v.3.3.9

Completed optimization for RED 16GB CF cards.
Addition of embedded time code in HD-SDI outputs.
Addition of CROSS JAM (creation of 23.98 fps from 29.97 timecode)
Addition of CROSS GEN (creation of 29.97 fps from 23.98 timecode)
Added USER KEY function – Record
Changed method of writing camera LOG file – access via SETUP menu.
Changed location of PRE-RECORD – access via MEDIA menu.
Selection of lens Distance data reporting in Feet or Meters
Addition of Audio LINE input gain control 0dB / 10 dB.
FALSE COLOR exposure meter tracks VIEW selection – REC709 / REDspace
Corrected operation of Shutter PHASE control.
Added USER programmable Safe Action / Title guides.
Changed MAGNIFY to display 1:1 native sensor resolution.
Added selection to playback clips using CLIP or CAMERA LOOK values.
Added USER PREFERENCE file.
Click to expand...

Perhaps it is TC embed in HDSDI? Perhaps it's a /i data thing?
 
I really do appreciate all the feedback and thought that you guys are putting into this. Believe it or not, I am forwarding your feedback to the engineering team who is evaluating this issue. The biggest problem is how rare this occurrence is. Out of thousands of cameras in the field, only a very small handful are experiencing it. For those that are, I know it is a total pain in the ass. But, the fact is that it is so rare, it is very hard for us to repeatedly replicate to diagnose.

That being said, I can say from feedback from you guys, it does not seem to be a Build 17-specific issue.

Thanks again for everyone's patience,
BC
 
Still happening

Still happening

I thought that maybe it was a drive issue because it seemed limited to one of our Red drives. We sent the drive in for evaluation at Red and they found no problems.

We've been shooting commercials with the other drive for the past few weeks with no problems until last friday. It rebooted once during playback, but no problems since then. The whole scenario--reboot, blue LCD.

We were running a fairly light config with only an LCD and Red drive connected. Fresh battery. So far, we have only experienced it during playback.

My warranty is expiring this week, so I'm fairly concerned.

Rob Powell
High Point, NC
 
I have seen self rebooting on the 4 Red I have seen, in Paris. All of them were 17, or 18.

Mine was working well on 17 beta until I got the Red-drive. Then it started to reboot. Now it's rebooting even when I'm on CF, but less often (about two time a day). I switched to 18, but it's the same.

That doesn't bother me. There is always something to tweak in the meantime.
but some clients finds it difficult to deal with, and then always try to find someone to yell at (the chain of screaming you know), usually the Dit or Red Inc itself. I can't say they are wrong. But it's not like it was a deal-breaker, they are always happy in the end.
 
Sorry Curran, Haven't been back to this post for a little while, I don't have a copy of the beta build 17 anymore. The camera got updated to release build when it was upgraded. I'll have a dig about though it might be kicking about somewhere.

Paul
 
Paul, never mind about the beta build 17. It was just that I hadn't heard of any reboots on 17 beta until the post by Bérenger above. Weird that it only started to reboot after he started using the Red-Drive.
 
I guess i'm one of the few cams with trouble... (but i doesn't matter, soon we will get epic-x)

off topic now.... it's weird, but I kinda like it :

My personnal projects with people that loves red are always troubleless (i mean, it reboot, but as I said one or two times, and it's not a big deal, and fast). But with red hater or assimilated, it freezes and reboots regulary, like 10 times a day.

Sometimes, it's like the RedOne knows the feeling of those who are using it... I've met an AC, who hated computer. I mean the guy touch the mouse a second and the computer was down for 30 minutes... and it was the same with Red, after all, it's a big computer.
 
My Lucy (#4248 built 16) came back yesterday from a rental job after a week, and the guys reported the same issue on their last day of shooting, they said it happened 3 or 4 times that day after around 20 minutes of shooting. Screen turning blue and then the camera powered down. They left the camera off for a few minutes and booted up again and everything worked. They were using a RED drive.

I left the camera running last night for around 40 minutes and I had no problems, however i was using CF cards, will try the same thing with a red drive connected tomorrow.
 
You must log in or register to reply here.
Back
Top