I'm on a show with 3x Alexa35's. The original "A" Camera body was constantly flashing the orange/yellow "Temperature Increase Warning." Always orange/yellow, never red (so no actual error code, just the warning flash).
It would flash on and off for a second all day once every 1-2 minutes.
We exchanged the body for a new one. The new body is doing the exact same thing. Enabling "Hide Messages" does not get rid of it. Turning "Side Info Left" to off does not get rid of it.
Our "B" and "C" camera bodies do not do this. The "B" and "C" bodies are on SUP 1.2.0. Both the original "A" body as well as the new replacement are on SUP 1.2.1.
I noticed yesterday (May 2) a new SUP 1.2.3 became available, but the temperature increase warning is not mentioned in the release notes as something patched or as a known error.
Has anyone else experienced this? It's really annoying, especially because the error also appears over SDI to everyone at our video villages and offsite streaming.
Temperature Increase Warning
-
- Posts: 2
- Joined: Fri May 03, 2024 10:06 pm
Adding some more information to this:
- All of our cameras are set to "Rec Low" fan setting.
- Both the "A" Body (that displays this warning 1000 times per day) and the "B" Body (that has never shown this warning) are hovering at a sensor temperature between 38-40°C. This is while shooting on stage where the ambient temperature is roughly 10°C.
- All of our cameras are set to "Rec Low" fan setting.
- Both the "A" Body (that displays this warning 1000 times per day) and the "B" Body (that has never shown this warning) are hovering at a sensor temperature between 38-40°C. This is while shooting on stage where the ambient temperature is roughly 10°C.
-
- Posts: 559
- Joined: Wed Aug 13, 2014 3:15 pm
- Location: Munich, Germany
- Contact:
Hi Wade,
a late reply, it seems nobody has experienced the same issue. Did you get in touch with ARRI Service at that time? You can always drop them a mail with the log files attached, Sometimes the logfiles can give a hint on what is triggering a certain behavior.
It is strange that the very same behavior showed up once you've exchanged bodies. This feels like the issue is connected to the overall configuration/rigging of the camera. What was different to B or C camera?
Cheers,
Jan
a late reply, it seems nobody has experienced the same issue. Did you get in touch with ARRI Service at that time? You can always drop them a mail with the log files attached, Sometimes the logfiles can give a hint on what is triggering a certain behavior.
It is strange that the very same behavior showed up once you've exchanged bodies. This feels like the issue is connected to the overall configuration/rigging of the camera. What was different to B or C camera?
Cheers,
Jan
Jan Heugel
Application Engineer
Application Engineer