PDA

View Full Version : konica minolta c3110 with an fbob code


Custom Search


brent
03-07-2018, 05:36 PM
weird code. but the manual said it was an abort code this machine has been problematic
from the beginning.. when it had any code on it. we had to unplug it let it sit and it would come back
on usually with no lights on the display any thoughts on this or the fbob code?

thanks guys very much

brent

tech51
03-07-2018, 07:23 PM
Update the firmware to the latest. That should cure it.

blackcat4866
03-08-2018, 02:48 AM
Firmware is at release 1 controller (A6DT30G0116-999) and scan (A6DT23G0101-999), or release 2 controller (A6DT30G0204-999) and scan (A6DT23G0101-999).

The bug is fixed in firmware to release 3 controller (A6DT30G0304-999) and scan (A6DT23G0300). Firmware is currently at release version 8, sub controller (A6DT30G0803-899), main controller (A6DT30G0C02-999), engine (A6DT0Y00050G001200_A), and scan (A6DT23G0402-999).

If you've never done firmware on a bizhub C3100, It's a little different than the majority of bizhubs, and different from the Lexmark based printers. It does some unexpected things. I recommend that you read the README file that I put together before you do it. And please don't ask for the firmware. =^..^=

B0265
03-08-2018, 09:03 AM
I've had this once. I tried the setting below but that only changed the indication from an error code to a jam. The solution for us was to change the ADF unit.

SoftSW No.291
= 0: Indicate FB0B as before.(Default)
= 32: JAM is indicated instead of FB0B

copier tech
03-02-2020, 12:45 PM
Firmware is at release 1 controller (A6DT30G0116-999) and scan (A6DT23G0101-999), or release 2 controller (A6DT30G0204-999) and scan (A6DT23G0101-999).

The bug is fixed in firmware to release 3 controller (A6DT30G0304-999) and scan (A6DT23G0300). Firmware is currently at release version 8, sub controller (A6DT30G0803-899), main controller (A6DT30G0C02-999), engine (A6DT0Y00050G001200_A), and scan (A6DT23G0402-999).

If you've never done firmware on a bizhub C3100, It's a little different than the majority of bizhubs, and different from the Lexmark based printers. It does some unexpected things. I recommend that you read the README file that I put together before you do it. And please don't ask for the firmware. =^..^=

Thanks for the word doc very hady to read while waiting!

Out of interest does it matter what order I update the files? I have just done them in the order saved to usb.

blackcat4866
03-03-2020, 02:18 AM
It's most important during the transition from a single controller file to the main controller and sub controller files.

jwai
03-03-2020, 06:13 PM
Firmware is at release 1 controller (A6DT30G0116-999) and scan (A6DT23G0101-999), or release 2 controller (A6DT30G0204-999) and scan (A6DT23G0101-999).

The bug is fixed in firmware to release 3 controller (A6DT30G0304-999) and scan (A6DT23G0300). Firmware is currently at release version 8, sub controller (A6DT30G0803-899), main controller (A6DT30G0C02-999), engine (A6DT0Y00050G001200_A), and scan (A6DT23G0402-999).

If you've never done firmware on a bizhub C3100, It's a little different than the majority of bizhubs, and different from the Lexmark based printers. It does some unexpected things. I recommend that you read the README file that I put together before you do it. And please don't ask for the firmware. =^..^=

I have one machine with version 8 F/W, it displayed this code and reset it with power off/on main switch.

Custom Search