1. DIY-Robotics (Help Center)
  2. Community
  3. Troubleshooting — FANUC

Teach Pendant Black Screen following a cable failure

Avatar
Isaak Labelle

Hey!

We've recently had a robot tear its TP cable by moving on its rail with the TP cable hanging loose. We've replaced the cable and fuses and got the robot to turn back on and clear all the faults. The next morning the TP would boot and show the booting sequence, but then it would blackscreen and be unresponsive. The only response we could get is by pressing F1 which brings up a windows xp era explorer page with many japanese hyperlinks. 

We've tried a different TP and same thing happened to it, and also tried the original TP on a different robot and got it to boot.

I am at a loss for the next step and would very much appreciate some help if anyone has experienced this!

Thanks in advance,

Isaak

Didn't find what you were looking for?

New post

Comments

5 comments

Sort by Date Votes
  • Avatar
    Gabriel Hallée
    Comment actions Permalink

    Hi Isaak,

     

    It sounds like your software may have become corrupted. I’d suggest forcing a Controlled Start by holding F1 and F5 during startup. This should open the Controlled Start menu, where you can load either:

    • An image backup, or

    • The original core software from the USB key associated with the robot.

    After restoring the core software, be sure to also load backups of your TP programs, variables, I/O configuration, and any other files that have been modified for the robot’s environment.

     

    Don’t hesitate to reach out if you need more guidance!

     

    Gabriel

    0
  • Avatar
    Isaak Labelle
    Comment actions Permalink

    Hey Gabriel,

    The controller opens, I can even access it with a virtual teach pendant. The robot boots, the TP does not. I have tried to get it to boot in Controlled start but the TP stays unresponsive.

    0
  • Avatar
    Gabriel Hallée
    Comment actions Permalink

    Hi Isaak,

     

    Assuming that your TP and cable both work on another robot, we can likely rule those out as the source of the problem. This points toward an issue inside the controller itself. The incident may have damaged the TP cable connector or the TP interface circuitry inside the controller.

     

    I’d suggest inspecting the controller’s TP port and internal connections closely for bent pins, loose wiring, or damaged boards.

     

    Also, if you can translate any of the Japanese hyperlinks or messages that appear, they might give valuable clues about what’s failing during boot.

    0
  • Avatar
    Isaak Labelle
    Comment actions Permalink

    Alright, maintenance will test connectivity of all the pins of the cable and inspect the TP port. 

    The japanese simply explains that the version of windows explorer that pops up is the same as the PC windows explorer.

    0
  • Avatar
    Gabriel Hallée
    Comment actions Permalink

    Sounds good, will be waiting on your feedback.

    0

Please sign in to leave a comment.