Posts by mortoch

    We looked at servo grippers and determined that they were so big and bulky that they were not feasible for what we do.
    That being said they are powerful if that is the goal.

    There are also driver chips on the mother board that can be blown by a short in your EE plug. They are very easily found if they are blown.
    The driver-chips are two Toshiba TD62107 drivers.
    They are located right behind the blue CRM10 and CRS1 connectors, and they sit in sockets, so they are very easy replaceble.
    (Kudos to RacerMike for this fix when I needed it.)

    Where your cables all enter the controller there is a bunch of grounding clamps that bite down on the cable shields. In RJ2 it is the lower left corner of the cabinet. Make sure they are all tight. I cleared this alarm once merely by tightening those clamps.

    Hey I300I300
    I am going to be checking landing zones for pickup and drop off. Picking from a supply rack, feeding to a robot feed table. Picking from the same table and returning to either the same rack or a finished rack, (still thinking on that one.
    I think I will use the "kiss" rule until it proves inadequate.
    Thanks for the info.

    Hey Guys.
    I am considering using vision to "see" wax molds for an automated investment mold dipping project.
    I know the variables must be huge but could someone give me a ballpark figure for a descent vision system.
    Basically I am comparing the price between individual laser sensors and vision.
    Thanks in advance.
    Mortoch

    Here is what I have on the svro-57 etc. These are collected from this forum so maybe run a search for the subject. Good Luck.


    Fanuc srvo 057 and 058 and 036 alarms keep coming back
    I keep getting a srvo 057 1-6 and 036 1-6, goes away sometimes right away and sometimes it takes 20 mins or so after disconnecting and reconnection optic, power, servo cable ect. any suggestions on what the issues is? cables all seem fine.


    Reply #1
    What robot model and controller type?

    Reply #2
    Replace the fiber-cable.


    Although it may look ok, it is pretty fragile and may be internaly damaged.


    Reply #3
    I would say examine the servo amp LEDs when this occurs I doubt it's the fiber cable but the fssb is the connection from server amp to access control card on the main board. You can also unhook this fiber cable and you will see a red light emitting from one side and and on the other end of the connection that red light on the opposite side.


    Reply #4
    fanuc RJ-3 M16i , I have replaced the optic cable multiple times.


    Reply #5
    This is a common problem with the Fanuc RJ-3.
    You need to replace the Back Plane PCB.



    FSSB Faults SRVO-057
    Hello All,


    Fanuc S-430iW with RJ3 controller.


    We're having SRVO-057 FSSB Disconnect fault on all 6 axis. I've replaced the fiber optic cables, the main control card on the amplifier. At this point I want to swap the main controller, but I can't get a full backup. It get's all 12 FROM backups, but fails to get the last image,which is SRAM.


    We can cycle power and keep going without having to do anything else.


    Now all of a sudden, we have 2 other robots faulting for the same thing. Really weird. It was discovered on one robot while someone was doing a PM on the E-stops and just checking to make sure they function correctly.



    Let me know your thoughts. Thanks.


    Reply #1
    What model controller?


    Reply #2


    Rj3 and a S-430iW robot.


    Reply #3
    Check FS1 on the servo amplifier. Once cleared you have to reboot the controller.
    Reply #4
    Check FS1 on the servo amplifier. Once cleared you have to reboot the controller.


    Sent from my SM-G930P using Tapatalk


    Thanks, I'll check, but this is a Rj3 controller. Not sure if it has those fuses and resistors.


    Reply #5
    RJ3 has had problems with FSSB alarms. The real culprit, according to Fanuc, is the printed circuit board on the backplane. I have not replaced one for this fault.
    The problem will happen when power is cycled.
    To test the FSSB, with the controller on, unplug the fiber cable at the Servo amp and look at the connector end. There should be a light on one of the fibers. Plug it back in and then unplug the fiber cable from the axis control card on the CPU. The light should now be on the other fiber. If the light is not on in either case then the suspected component will need to further testing trouble shooting. I have never seen the servo amp fail this way. I have seen a couple of bad axis control cards though.
    If the lights work properly and you still have the alarm Fanuc suggests this;
    unplug the fiber cable from the servo amp and from the main board and power on the controller and let the controller boot up.
    Power down the controller and plug them both back in and turn the controller back on.
    This should temporarily "fix" the problem allowing you to run.
    Reply #6
    Thanks for the help.


    I hate to speak too soon, but it looks like the main CPU board was the culprit. I replaced it and restored an original image that came with the robot. I had to restore all my .TP, .IO and register programs separate. It would not let me backup sysvar.vr nor take an image of the problem CPU.


    Hope this helps someone in the future.

    I use a dedicated laptop with an 232 port and a homemade cable. I hook to the 25 pin out of the robot and the 9 pin D on the laptop.
    Using Kfloppy it takes about an hour or less to create a backup.

    I would say it always the same fileS as it is more than one. To me it acts like a delay that the kfloppy sees and doesn't like because it pops up and then the file starts it save. This is more of a curiosity because the files work.

    During the save routine I get errors that report error reading file but when I check the upload status it is uploading that file. Is this an update issue between the computer and the controller?
    I am uploading from RJ2 through a 25 pin to 9 pin into an old windows xp laptop.
    This doesn't seem to effect anything, just an annoyance.
    Thank you.

Advertising from our partners