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

Epic has "Error: 0x0000001d"

How is the camera being powered? Looks like it is from the mains.

Have you tried starting it up from another power source? Or from a different outlet?

Battistella
 
Many, many thanks to Callum at Red Europe. He has promised to sort me out with a replacement camera for our shoot, whilst my is repaired.

Which is great, because our temporary stand-in camera, a BlackMagic, is no fun at all :-)
 
How is the camera being powered? Looks like it is from the mains.

Have you tried starting it up from another power source? Or from a different outlet?

Battistella

Hi David,

Yes, I tried batteries instead.

And Callum also suggested trying it without the lens mount and without the side SSD module. But still the same error.
 
Needs to go to RED...most likely main board related. Did anything physical happen to the camera that could have jarred something loose?

Thank you very much

Fury

Hi Nick,

Yes, it is being couriered to Red tomorrow morning.
No, the camera is always protected in foam in a Pelicase, and well looked after.
 
Hi Nick,

Yes, it is being couriered to Red tomorrow morning.
No, the camera is always protected in foam in a Pelicase, and well looked after.

Having said that... it just occurred to me that when it was sent back to me from Red, the FedEx couriers may have played rugby with it!!!
 
I got the same error, ever figure out what caused the error?


I got this error yesterday once at random. I shut it down and powered it right back up with no problems. Not sure what to make of this.. anybody ever figure out what the deal is? Do I still need to send in the camera if it's working right now?
 
Mine had a bad board that needed to be replaced.

Were you getting the error regularly? How much did it cost?

I have only seen the error once, yesterday, then not again since then. A little hesitant to send it in when the camera seems to be working normally and I have shoots coming up and not a ton to spend on repairs.
 
I just started getting this today randomly. Most of the time hitting record. First day with the current firmware installed also.
 
I am currently going through this. Sent a log to Red. They told me to bring the camera in for servicing. I did, took them 3 days to diagnose the problem. Apparently, bad board on camera. I upgraded to Dragon this past April. Luckily they kept me under warranty even though it's been over 90 days since upgrading and gave me a loaner camera. Thanks Red! Still disheartening to go through this so soon after upgrading. I know this error can be triggered by multiple different factors, best thing to do is just contact Red and rule out anything major.
 
Hello everyone.. has anyone found a solution for this? I rented an Epic, and got this error message when i turned on the camera : ''Error: 0x0000001d''.
For some reason the message disappears and doesn't show up anymore when I am restarting the camera.
 
Hi,
Im getting this same error any resolution to it? happens once in a while? guess i need to just contact support if not
 
Hi,
Im getting this same error any resolution to it? happens once in a while? guess i need to just contact support if not

I've found it randomly pops up if I have a mini-mag (120gb) in the mini SSD module when powering the camera up. I let the camera shut down, take out the mag, then power the camera back up. Once back on, I pop the mag in and don't experience issues.

I've also only had this running on redvolt or v-mount power - haven't run into it on AC power.
 
Hi,
Im getting this same error any resolution to it? happens once in a while? guess i need to just contact support if not

Hey francisco, have you had any problems with the camera other than the random error code? I have had this message 2 times in the past month but it seems the camera boots back up and works fine afterwards. I contacted red and they told me to send it in - the problem is I am leaving for a month long gig on Jan 27 with the camera. I'm wondering if it is a minor issue or a major one. Is it something that I can have fixed when I come home or do I have to get it done now?
 
Hey francisco, have you had any problems with the camera other than the random error code? I have had this message 2 times in the past month but it seems the camera boots back up and works fine afterwards. I contacted red and they told me to send it in - the problem is I am leaving for a month long gig on Jan 27 with the camera. I'm wondering if it is a minor issue or a major one. Is it something that I can have fixed when I come home or do I have to get it done now?
Your camera will eventually have more errors pop up to the point it's happening all the time, as you have a bad board in camera. Talk to red about a lonor camera before sending it in. That repair usually takes a week to do.
 
Your camera will eventually have more errors pop up to the point it's happening all the time, as you have a bad board in camera. Talk to red about a lonor camera before sending it in. That repair usually takes a week to do.

I guess there is no way to know how serious a problem it is. I only have 14 shoot days scheduled over the next month, but they are all on the road in various countries, no time to send or receive a new camera body...... such bad timing for this to happen.
 
I sourced the issue I was having with our RED Epic Mysterium-x.

While playing around with setups on the Ronin I directly mounted our Teradek Bolt 300 Transmitter to the top of the camera(to limit cable movement). I noticed that even without the BNC plugged in and the power source was different to the Epic and Bolt 300, each time I turned on the transmitter the error appeared about 10 seconds later.

I'm assuming that the radio waves was messing with the camera.

Moving the transmitter further away from the camera seams to have fixed it for us.
 
I got this a couple of weeks back and now today I got it again. sent in a ticket to support and though it was solved with a new firmware install. But apparently not. So guess need to try to replciate and send new support ticket.
 
Back
Top