Posts by frederiksensome

    Hi, thanks for the responses, my team tried what u suggested and its possible to boot up the controller with teach pendant from other robot,but when using its teach pendant on another robot the same error occurs. And no, its not even possible to boot BMON, otherwise it would possibly be an easy fix from the start. Seems to me like the teach pendant automatic update when doing the firmware update got screwed and now the files are corrupted somehow. Do u know if there is any way to get the pendant into default state as it is when shipped we can do on-site?

    gTpsMVpHi guys,

    as seen in attachment,we are having issue with this message after the cpu battery was removed before robot got installed and powered up. We are trying to install the firmware USB on a brand new robot and this is preventing us from even booting into bios. The controller is R-30iB and has never been booted before, but as I said, the cpu battery was removed while controller was off. Normally we just boot into bios and recover image from other identical controllers, but as my team informs me, for some reason it's not possible in this case. Anyone can advise how to proceed or at least saw this message pop up before?


    thanks in advance

    for the most obvious errors as in SRVO-007/037/280 the remedy is to use jumpers on the EES and SVOFF connector to get rid of external emergency and SVOFF error and for IMSTP MENU>NEXT>SYSTEM>CONFIG and disable UI signals...since ur controller is not specifying which fuse is blown u have to check them all to find broken one... and to recover from SRVO-062 u do the reset pulse coder procedure as MENU>NEXT>SYSTEM>MASTER>CAL,press F3 RES_PCA,F4 YES and after reset do a cold start

    To start with clean but mastered robot after INIT START find file SYSMAST.SV in ur ALL OF ABOVE backup and copy to a USB or compact flash card,as robot does controlled start mode after INIT START go to MENU>FILE>F5 UTILITY and set which medium u are using,then F3 to load mastering data and after that FCTN>COLD START.

    Hi guys,


    for 2 days now im trying to figure out how to get rid of this alarm. I know from both this forum and from experience that it should be piece of cake to clear it by rotating each affected axis in joint,but that is not the case now. Robot just wont move, keeping the message system is in error status. Affected were axis 3-6. Controller is R-30iA and arm is R-2000iB.


    Now since i started working on it i already tried RES_PCA/turn off,init start,image restore,changed both cables between controller and arm,exchanged servo amplifier still with no success. Maybe its going to be obvious to someone when i say that after i press deadman and circuit breaker clicks normally i hear no sound from brakes,thus no sound from encoders powering up. Running out of options i even tried to open cover on batteries with power turned off just to see that now instead of 3-6 all axis are having the pulse not established alarm,without me being able to joint any of it. Just to add, im pretty sure this robot must have been running few months ago because it was refurbished and remastered in other customer's plant with fanuc support. So any help how to get rid of this problem will be appreciated, maybe im missing something and u can point me some direction.

Advertising from our partners