Kodak i640 Path-Through Scanner Logo
Arsalan Tariq Posted on Feb 08, 2007

Kodak i640 communication Error

(Kodak I640 Scanner's Service Log) (Solution Require) [Log] [01/26/2007 00:22 docs=2572997] id=212 HALT data=0x00000000(0) Pod door opened [01/26/2007 00:22 docs=2572997] id=180 ERROR data=0x00000000(0) CPU detected IPB fault or Communication error [01/26/2007 00:22 docs=2572997] id=193 ERROR data=0x00000000(0) CPU-IPB communication failure [01/26/2007 00:21 docs=2572997] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 22:56 docs=2572591] id=180 ERROR data=0x00000000(0) CPU detected IPB fault or Communication error [01/25/2007 22:56 docs=2572591] id=193 ERROR data=0x00000000(0) CPU-IPB communication failure [01/25/2007 22:55 docs=2572591] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 22:55 docs=2572591] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 22:55 docs=2572511] id=030 HALT data=0x00000005(5) Jam in transport [01/25/2007 22:48 docs=2572180] id=260 CLEAR STOP data=0x00000002(2) No paper in elevator tray [01/25/2007 21:32 docs=2567815] id=260 CLEAR STOP data=0x00000002(2) No paper in elevator tray [01/25/2007 21:28 docs=2567727] id=193 ERROR data=0x00000000(0) CPU-IPB communication failure [01/25/2007 21:27 docs=2567727] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 21:27 docs=2567438] id=030 HALT data=0x00000001(1) Jam in transport [01/25/2007 21:19 docs=2567438] id=193 ERROR data=0x00000000(0) CPU-IPB communication failure [01/25/2007 21:18 docs=2567438] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 21:18 docs=2567434] id=030 HALT data=0x00000005(5) Jam in transport [01/25/2007 21:11 docs=2567434] id=180 ERROR data=0x00000000(0) CPU detected IPB fault or Communication error [01/25/2007 21:11 docs=2567434] id=193 ERROR data=0x00000000(0) CPU-IPB communication failure [01/25/2007 21:10 docs=2567434] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 21:10 docs=2567434] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 21:03 docs=2567420] id=030 HALT data=0x00000005(5) Jam in transport [01/25/2007 20:58 docs=2567420] id=193 ERROR data=0x00000000(0) CPU-IPB communication failure [01/25/2007 20:57 docs=2567420] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 20:57 docs=2567394] id=030 HALT data=0x00000005(5) Jam in transport [01/25/2007 20:44 docs=2567378] id=193 ERROR data=0x00000000(0) CPU-IPB communication failure [01/25/2007 20:42 docs=2567378] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 20:38 docs=2567378] id=193 ERROR data=0x00000000(0) CPU-IPB communication failure [01/25/2007 20:38 docs=2567378] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 20:38 docs=2567366] id=030 HALT data=0x00000005(5) Jam in transport [01/25/2007 20:30 docs=2567366] id=193 ERROR data=0x00000000(0) CPU-IPB communication failure [01/25/2007 20:29 docs=2567366] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 20:29 docs=2567342] id=030 HALT data=0x00000001(1) Jam in transport [01/25/2007 20:23 docs=2567342] id=180 ERROR data=0x00000000(0) CPU detected IPB fault or Communication error [01/25/2007 20:23 docs=2567342] id=193 ERROR data=0x00000000(0) CPU-IPB communication failure [01/25/2007 20:23 docs=2567342] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 20:22 docs=2567342] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 20:22 docs=2567338] id=030 HALT data=0x00000005(5) Jam in transport [01/25/2007 20:04 docs=2567338] id=180 ERROR data=0x00000000(0) CPU detected IPB fault or Communication error [01/25/2007 20:04 docs=2567338] id=193 ERROR data=0x00000000(0) CPU-IPB communication failure [01/25/2007 20:03 docs=2567338] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 20:03 docs=2567338] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 20:03 docs=2567310] id=030 HALT data=0x00000005(5) Jam in transport [01/25/2007 18:59 docs=2567310] id=180 ERROR data=0x00000000(0) CPU detected IPB fault or Communication error [01/25/2007 18:59 docs=2567310] id=193 ERROR data=0x00000000(0) CPU-IPB communication failure [01/25/2007 18:36 docs=2567310] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 15:36 docs=2565940] id=694 CLEAR STOP data=0x02940345(43254597) Lower imaging guide dirty or document in transport [01/25/2007 15:36 docs=2565771] id=030 HALT data=0x00000005(5) Jam in transport [01/25/2007 15:32 docs=2565771] id=180 ERROR data=0x00000000(0) CPU detected IPB fault or Communication error [01/25/2007 15:32 docs=2565771] id=193 ERROR data=0x00000000(0) CPU-IPB communication failure [01/25/2007 15:32 docs=2565771] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 15:32 docs=2565771] id=030 HALT data=0x00000008(8) Jam in transport [01/25/2007 15:31 docs=2565768] id=030 HALT data=0x00000001(1) Jam in transport [01/25/2007 15:31 docs=2565768] id=694 CLEAR STOP data=0x02E402E4(48497380) Lower imaging guide dirty or document in transport [01/25/2007 15:31 docs=2565761] id=030 HALT data=0x00000005(5) Jam in transport [01/25/2007 13:05 docs=2564265] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 13:04 docs=2564265] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 13:04 docs=2564265] id=180 ERROR data=0x00000000(0) CPU detected IPB fault or Communication error [01/25/2007 13:04 docs=2564265] id=193 ERROR data=0x00000000(0) CPU-IPB communication failure [01/25/2007 13:02 docs=2564265] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 12:33 docs=2563382] id=180 ERROR data=0x00000000(0) CPU detected IPB fault or Communication error [01/25/2007 12:33 docs=2563382] id=193 ERROR data=0x00000000(0) CPU-IPB communication failure [01/25/2007 12:33 docs=2563382] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 12:33 docs=2563382] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 12:32 docs=2563349] id=030 HALT data=0x00000001(1) Jam in transport [01/25/2007 12:27 docs=2563349] id=180 ERROR data=0x00000000(0) CPU detected IPB fault or Communication error [01/25/2007 12:27 docs=2563349] id=193 ERROR data=0x00000000(0) CPU-IPB communication failure [01/25/2007 12:26 docs=2563349] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 12:02 docs=2562419] id=180 ERROR data=0x00000000(0) CPU detected IPB fault or Communication error [01/25/2007 12:02 docs=2562419] id=193 ERROR data=0x00000000(0) CPU-IPB communication failure [01/25/2007 12:02 docs=2562419] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 12:02 docs=2562419] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 12:02 docs=2562419] id=030 HALT data=0x00000008(8) Jam in transport [01/25/2007 12:02 docs=2562418] id=030 HALT data=0x00000001(1) Jam in transport [01/25/2007 11:58 docs=2562418] id=180 ERROR data=0x00000000(0) CPU detected IPB fault or Communication error [01/25/2007 11:58 docs=2562418] id=193 ERROR data=0x00000000(0) CPU-IPB communication failure [01/25/2007 11:57 docs=2562418] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 11:57 docs=2562418] id=030 HALT data=0x00000008(8) Jam in transport [01/25/2007 11:57 docs=2562418] id=030 HALT data=0x00000008(8) Jam in transport [01/25/2007 11:56 docs=2562367] id=030 HALT data=0x00000001(1) Jam in transport [01/25/2007 11:46 docs=2562159] id=180 ERROR data=0x00000000(0) CPU detected IPB fault or Communication error [01/25/2007 11:46 docs=2562159] id=193 ERROR data=0x00000000(0) CPU-IPB communication failure [01/25/2007 11:46 docs=2562159] id=212 HALT data=0x00000000(0) Pod door opened [01/25/2007 11:46 docs=2562159] id=030 HALT data=0x00000008(8) Jam in transport [01/25/2007 11:45 docs=2562159] id=030 HALT data=0x00000008(8) Jam in transport [01/25/2007 11:45 docs=2562134] id=030 HALT data=0x00000001(1) Jam in transport [01/25/2007 11:33 docs=2561818] id=030 HALT data=0x00000005(5) Jam in transport

  • Anonymous Mar 12, 2012

    We buy, sell and trade; new, used and refurbished scanners. Call me about the Kodak i640. Andre 855-420-8273 ThirdWindTechnologies.com

×

1 Answer

Anonymous

Level 1:

An expert who has achieved level 1.

  • Contributor 3 Answers
  • Posted on Aug 08, 2008
Anonymous
Contributor
Level 1:

An expert who has achieved level 1.

Joined: Aug 08, 2008
Answers
3
Questions
0
Helped
2103
Points
3

I Have had the same problem. I changed the power supply an the error was never detected

Add Your Answer

×

Uploading: 0%

my-video-file.mp4

Complete. Click "Add" to insert your video. Add

×

Loading...
Loading...

Related Questions:

0helpful
1answer

"cycle error" - scanner powers up ok but will not scan due to this error ID=055

Error 55: "Lamp I2C error reading from DAC". Operator log message: "Cycle power, if problem persists, call service.". This error is involves communication errors between the LED AY and the DAC. A couple things can be done to alleviate this issue but unfortunately, as a user, you can only perform the first step. The other steps require a Kodak Field Engineer to complete. First step, upgrade your Firmware. Firmware updates can be found at the following web page: http://graphics.kodak.com/DocImaging/US/en/Support_Center/Document_Scanners/Production/i5200_Scanner/Support/Drivers_And_Downloads/i5000_Series_Scanner_Firmware/index.htm. If you still experience issues following the firmware upgrade, call Kodak Service & Support to schedule a field engineer to be dispatched to your site.
0helpful
1answer

Forgot the phone lock key of samsung SGH i640V

Type the code below on your mobile main screen after you remove the sim card:
*2767*3855#
0helpful
1answer

Display

do u mean u have problem on display
0helpful
1answer

Major alarm code 827.9055

Is this a Inter-tel INT4000 phone? Not a Spectralink?
1helpful
1answer

Cant run videos on wm6

Install latest wm6 version and rinstall it will solve your problem
0helpful
1answer

Can only get GSM on unlocked Samsung i640v

need a network unlock code for my samsung i640v please help imei 350012546857556
0helpful
1answer
0helpful
1answer

Check kds.log -this is my massage error when i press scan option at canner kodak i 260 "check KDS log" messge error appears when scan option chosen on i40 Kodak Scanner.

Try Calibration routine. If it fails check optics are clean and not scratched. If it still fails change the lamps.The KDS.log is encrypted and can only be accessed via a license key. This is only Available to Kodak reps or through RTS ltd service calls.
WWW.Responsets.co.uk.
1helpful
1answer

Orange led on

Ok. You can start the Scan Val. Tool. There is a File with the Error Codes. Please let me know the Code.
Not finding what you are looking for?

1,619 views

Ask a Question

Usually answered in minutes!

Top Kodak Office Equipment & Supplies Experts

Cindy Wells

Level 3 Expert

6688 Answers

Grand Canyon Tech
Grand Canyon Tech

Level 3 Expert

3867 Answers

ZJ Limited
ZJ Limited

Level 3 Expert

17989 Answers

Are you a Kodak Office Equipment and Supply Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides

Loading...