Kyocera ECOSYS P6235cdn - Beep after potential water damage - no error?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • M.Ant
    Junior Member
    • Feb 2020
    • 8

    [Electrical] Kyocera ECOSYS P6235cdn - Beep after potential water damage - no error?

    Kyocera ECOSYS P6235cdn was removed from a room and left to dry due to a leak (heavy storms over the last few weeks and a dodgy roof) over the weekend that may have let water into the printer. We've removed it and dried it out (no visible water or damage to the internal components, just the outside) for over 4 days. Turning it on today, it prints fine but after every print job it lets out a loud long beep and when it was first turned on it let out several.

    Nothing on the error log.
    The buzzer option on Job Finish and Ready are disabled.
    No notifications on the display.

    I can't locate a service manual for this printer, so I'm unsure if it's a notification of water damage or just something odd that maybe a factory reset will resolve.
  • bsm2
    IT Manager

    25,000+ Posts
    • Feb 2008
    • 27450

    #2
    Re: Kyocera ECOSYS P6235cdn - Beep after potential water damage - no error?

    When you web in any error messages ?

    Comment

    • M.Ant
      Junior Member
      • Feb 2020
      • 8

      #3
      Re: Kyocera ECOSYS P6235cdn - Beep after potential water damage - no error?

      Originally posted by bsm2
      When you web in any error messages ?

      https://cdn.kyostatics.net/dlc/za/do...635cidn_EN.pdf
      Nothing. It's about a 10 second long constant beep when it starts up or wakes up, a shorter beep after every job and sometimes randomly just a beep out of nowhere. No errors anywhere.

      Comment

      • M.Ant
        Junior Member
        • Feb 2020
        • 8

        #4
        Re: Kyocera ECOSYS P6235cdn - Beep after potential water damage - no error?

        A little update:

        We think this may not be damaged at all now, but depending on what the user returning (was on sick leave, coming back this week) says about whether or not it beeped before we think this will be an issue with newer firmware that nobody else on-site noticed until we pulled it into the office to dry it out.

        We purchased this printer in November and Kyocera accidentally sent us two. We offered to buy the second one for a heavy discount, so to test this I pulled it out. The same beeps. These printers are on firmware version 2TW_S000.002.123 (2019.06.20). The other 3 we have on-site are all on 2TW_S000.001.421 (2018.09.11).

        1st line tech Kyocera support couldn't even tell me where to get the firmware from to update it using the Net Viewer software, so I'll be waiting for the print engineers to contact back.

        Comment

        • HenryT2
          Senior Tech

          500+ Posts
          • Apr 2010
          • 962

          #5
          Re: Kyocera ECOSYS P6235cdn - Beep after potential water damage - no error?

          The little speakers on these machines are not very loud . We did have a call once that the tech said that there was a loud beep when powering on , so we had him check the incoming power . The customer had this printer plugged into a UPS . When they plugged the printer correctly into a wall outlet --- the beeping stopped . Check the incoming power to be sure it is not plugged into a UPS or a power-strip .
          "The Serenity Prayer" . . .
          God grant me the serenity to accept stupid people , the courage to not waste my time and energy on them , and the wisdom to know that I cannot fix STUPID .

          Comment

          • blackcat4866
            Master Of The Obvious

            Site Contributor
            10,000+ Posts
            • Jul 2007
            • 22702

            #6
            Re: Kyocera ECOSYS P6235cdn - Beep after potential water damage - no error?

            Originally posted by HenryT2
            The little speakers on these machines are not very loud . We did have a call once that the tech said that there was a loud beep when powering on , so we had him check the incoming power . The customer had this printer plugged into a UPS . When they plugged the printer correctly into a wall outlet --- the beeping stopped . Check the incoming power to be sure it is not plugged into a UPS or a power-strip .
            Funny you should mention that. I've had two calls like this: one was a Toshiba eS455 the other was an Oki rebadged as Toshiba eS477. On each occasion the machine was plugged into an uninterruptable power supply rated 1000 watts (~8.3A load rated). Every time they tried to use the copier the UPS would screech at them. =^..^=
            If you'd like a serious answer to your request:
            1) demonstrate that you've read the manual
            2) demonstrate that you made some attempt to fix it.
            3) if you're going to ask about jams include the jam code.
            4) if you're going to ask about an error code include the error code.
            5) You are the person onsite. Only you can make observations.

            blackcat: Master Of The Obvious =^..^=

            Comment

            • JR2ALTA
              Service Manager

              Site Contributor
              1,000+ Posts
              • Feb 2010
              • 2017

              #7
              Re: Kyocera ECOSYS P6235cdn - Beep after potential water damage - no error?

              Originally posted by HenryT2
              The little speakers on these machines are not very loud.
              My thoughts exactly. I had a customer at a busy pharmacy who wanted the Job Complete beep LOUDER and I soon realized there's no volume option. It's quiet and I can't see how it would be any louder -- water damage or not.

              Comment

              • copier tech
                Field Supervisor

                5,000+ Posts
                • Jan 2014
                • 7933

                #8
                Re: Kyocera ECOSYS P6235cdn - Beep after potential water damage - no error?

                Originally posted by M.Ant
                Nothing. It's about a 10 second long constant beep when it starts up or wakes up, a shorter beep after every job and sometimes randomly just a beep out of nowhere. No errors anywhere.
                Let us eat, drink, and be merry, because tomorrow we may die!

                For all your firmware & service manual needs please visit us at:

                www.copierfirmware.co.uk - www.printerfirmware.co.uk

                Comment

                • M.Ant
                  Junior Member
                  • Feb 2020
                  • 8

                  #9
                  Re: Kyocera ECOSYS P6235cdn - Beep after potential water damage - no error?

                  So, bit of an update.

                  Kyocera sent an engineer (without booking it or letting us know in any way, bit of a surprise).

                  After unpacking and looking at the second printer from the batch straight out of the box, we've determined this is nothing to do with water damage. The other printer does this straight out of the box as well.

                  The engineer went away confused - he agrees it's strange (and annoying). He filmed it to show the problems and said he was going to have to look into it.

                  These two printers were purchased in oct/nov separate from the other ones in the school which do not have the same issue. He thinks it's not firmware, but may be a hardware/part issue and it could be that since both of them are from the same batch that they have the same issue.

                  Kyocera haven't been the best at keeping us up to date (no contact from them at all except for sending an unannounced engineer) so I'm going to have to contact them again and chase any updates.

                  Comment

                  • blackcat4866
                    Master Of The Obvious

                    Site Contributor
                    10,000+ Posts
                    • Jul 2007
                    • 22702

                    #10
                    Re: Kyocera ECOSYS P6235cdn - Beep after potential water damage - no error?

                    If it truly is firmware, downgrading the firmware would be a simple way to narrow it down. =^..^=
                    If you'd like a serious answer to your request:
                    1) demonstrate that you've read the manual
                    2) demonstrate that you made some attempt to fix it.
                    3) if you're going to ask about jams include the jam code.
                    4) if you're going to ask about an error code include the error code.
                    5) You are the person onsite. Only you can make observations.

                    blackcat: Master Of The Obvious =^..^=

                    Comment

                    • M.Ant
                      Junior Member
                      • Feb 2020
                      • 8

                      #11
                      Re: Kyocera ECOSYS P6235cdn - Beep after potential water damage - no error?

                      Bizarrely, I've had a brainwave post-corona lockdown and cracked the case which seems obvious afterwards.

                      When this was in the room and no beeps were reported, it was plugged straight into the socket.
                      When we pulled it back to test it after water splashed on it, it was plugged in either on an extension or a UPS socket.
                      When the first Kyocera engineer saw it, it was plugged in on the same UPS socket and he also heard the beeps (he didn't link it to the power).
                      During lockdown, a second Kyocera engineer came. Due to restrictions, we moved the printer into a separate room for him to look at and it was plugged straight into the wall socket. No beeps.

                      Just pulled out a separate printer of the same model, and my coworker reported it as having the same error. Thought to myself I wonder if it's the power, plugged it straight into the wall and no beeps.

                      So it doesn't like being on a UPS most likely, which isn't surprising. No visual errors and the Kyocera engineer didn't recognise it either.

                      Comment

                      Working...