Bizhub 364e "This is invalid External Memory"

[Madnhain]

So this is interesting...
On boot up, the machine automatically goes into Firmware update mode with the "Firmware Update / This is invalid External Memory / Please make sure the external memory" message.
However, the metal service cover is Down, blocking the sensor.
It boots up normally if I lift the metal service cover (unblocking the sensor).

I cannot seem to find a reference anywhere to what state this sensor needs to be in for Firmware to be initiated. Anyone recall?

My best guess is that someone at some time removed the plate that the sensor is mounted on and installed it wrong... (if that is even possible). I'll look into that when I go back as it just occurred to me as I write this.

[copyman]

So this is interesting...
On boot up, the machine automatically goes into Firmware update mode with the "Firmware Update / This is invalid External Memory / Please make sure the external memory" message.
However, the metal service cover is Down, blocking the sensor.
It boots up normally if I lift the metal service cover (unblocking the sensor).

I cannot seem to find a reference anywhere to what state this sensor needs to be in for Firmware to be initiated. Anyone recall?

My best guess is that someone at some time removed the plate that the sensor is mounted on and installed it wrong... (if that is even possible). I'll look into that when I go back as it just occurred to me as I write this.

I've seen this before but it's been a long time and can't remember how I fixed it? Will see if I can find my notes on it. Might as well bring firmware with you and try to update or if already up to date just reinstall latest F/W.

[tsbservice]

Definitely problem with sensor. Remove back cover and position it properly.

[Markks]

So this is interesting...
On boot up, the machine automatically goes into Firmware update mode with the "Firmware Update / This is invalid External Memory / Please make sure the external memory" message.
However, the metal service cover is Down, blocking the sensor.
It boots up normally if I lift the metal service cover (unblocking the sensor).

I cannot seem to find a reference anywhere to what state this sensor needs to be in for Firmware to be initiated. Anyone recall?

My best guess is that someone at some time removed the plate that the sensor is mounted on and installed it wrong... (if that is even possible). I'll look into that when I go back as it just occurred to me as I write this.

Have you tried updating firmware?

[derrekflo]

The problem is the MFP there is a bulletin where it indicates that the battery in some equipment arrived defective, it is necessary to change the MFP or otherwise change the battery and update the firmware.

[Hansoon]

Definitely problem with sensor. Remove back cover and position it properly.

Another machine, but I had a whole bunch of BH-C-284e coming from a wholesaler where they removed the hard drive. In the process of doing that, they removed the little hook-up cable from the sensor to the board too. Idiots.

Hans

[Madnhain]

Have you tried updating firmware?

I know you had to ask lol... but yes, that's the thing... It updates firmware as expected. I'm telling you, this thing is possessed.

[Madnhain]

Definitely problem with sensor. Remove back cover and position it properly.

As soon as I make it back over there I'm going to give this a go. Seems odd that Firmware DID update as expected (with cover in up position). But when booting normally (cover down) it still goes into FW mode.

[Synthohol]

then that sensor is NFG right?
have you checked it with a meter blocked and unblocked?
this is basic man, check the sensor in both states, if no change sensor bad right?

[femaster]

So this is interesting...
On boot up, the machine automatically goes into Firmware update mode with the "Firmware Update / This is invalid External Memory / Please make sure the external memory" message.
However, the metal service cover is Down, blocking the sensor.
It boots up normally if I lift the metal service cover (unblocking the sensor).

I cannot seem to find a reference anywhere to what state this sensor needs to be in for Firmware to be initiated. Anyone recall?

My best guess is that someone at some time removed the plate that the sensor is mounted on and installed it wrong... (if that is even possible). I'll look into that when I go back as it just occurred to me as I write this.

The typical state of the sensor for normal booting should be the sensor blocked. When the sensor is unblocked is when it should boot into firmware update mode. If it boots to firmware in either position, I'm thinking either a bad sensor or a shorted harness. The harness issue seems like a stretch though. It's so short that I can't see how it could get shorted, but if untrained hands were in it, who knows.

At this point, I'd borrow the sensor and harness from another copier and test.