1. Home
    1. Dashboard
    2. Search
  2. Forum
    1. Unresolved Threads
    2. Members
      1. Recent Activities
      2. Users Online
      3. Team Members
      4. Search Members
      5. Trophys
  3. Articles
  4. Blog
  5. Videos
  6. Jobs
  7. Shop
    1. Orders
  • Login or register
  • Search
Everywhere
  • Everywhere
  • Articles
  • Pages
  • Forum
  • Blog Articles
  • Products
  • More Options
  1. Robotforum - Support and discussion community for industrial robots and cobots
  2. Members
  3. rib

Posts by rib

  • ABB S4 + IRB2400 startup problem: Diag: Illegal instruction.

    • rib
    • February 6, 2021 at 11:58 PM

    A few days ago I have replaced the contactors, this did not solve the problem in the servo however was necesary because of the smoke,

    Today I made a temporary cable from the encoder to the SMB. This is a sub-d 15 (encoder) -> IDC (SMB), which currently does not go through the bearing but is going from the outside to the SMB. This did solve the problem.

    This week I will replace the connector from the original cable as the above is only temporary. Hopefully this will solve the problem because replacing the complete cable will be dificult.

  • ABB S4 + IRB2400 startup problem: Diag: Illegal instruction.

    • rib
    • January 31, 2021 at 7:40 PM

    The burned contactors is K1 or k2 indeed. But I will replace all 4 contactors. I will also check the shielding of the encoder cable.

    Do you know how the cable is going through from axis 1 to the SMB. Is there a drag contact or something else? I see a cable carrier for the motor cables but for the encoder cables it looks like it’s going just through the bearing. But I cannot see everything.

  • ABB S4 + IRB2400 startup problem: Diag: Illegal instruction.

    • rib
    • January 29, 2021 at 10:54 PM

    And then there was grey smoke.


    Today I replaced the encoder and now the noise is far less then it the beginning, although it is still there. Then I placed the robot in the position with the biggest amount of noise and I noticed that by pulling on the encoder cable the amount of noise was changing. From that point of time I got the feeling that the problem is maybe related to the encoder cable.


    But in the mean time I did something else and then there was a strange smell and grey smoke in the S4 cabinet. The smell came from the relays which switch the power to the motor board. After measuring these the resistance was also high for a relays. Then I hoped that this was maybe the problem and found a temporary solution with a relays which can only switch the 3 phases for the motor supply so the other signals are still switched with the old relays. Unfortunately the same amount of noise is still present with this temporary solution. So for this I also have to find a more permanent solution.


    So currently I am searching in the direction of the encoder cable. I am thinking of creating a temporary cable directly to the board. If this solves the problem: how is the cable going through the robot from the base to axis 2? It looks like the motor cables are going through a cable sleeve but these encoder cables are going through the middle joint directly.

  • ABB S4 + IRB2400 startup problem: Diag: Illegal instruction.

    • rib
    • January 28, 2021 at 7:34 PM

    Thanks for your reply.

    I also bought now an additional encoder which I will get tomorrow. I will also try your points tomorrow if replacing the encoder does not solve the problem.

  • ABB S4 + IRB2400 startup problem: Diag: Illegal instruction.

    • rib
    • January 27, 2021 at 10:32 PM

    I have now replaced the motor to an used one from ebay, but unfortunately still the same noise. The pins of the XP1 connector looks nice also the inside. Also the connector is not getting warm, which I would expect with an loose contact.

  • ABB S4 + IRB2400 startup problem: Diag: Illegal instruction.

    • rib
    • January 25, 2021 at 9:29 PM

    I did both tests:

    1) Pressed brake 1 axis and turned manually: i could turn the motor nice and smoothly.

    2) While in jog window watched the amount of degree of each axis: nice and steady.
    3) Previously I already interchanged the motor boards.

    4) Also checked the resistance of the motor by uncoupling the big harting multiconnector from the control cabinet. Between all phases was almost the same resistance.

    P.s. the check with the megger I did not do yet because the motor connector is difficult to reach.

    So from my perspective:

    It's not the brake (test 1), not the encoder (test 2), not the electronics (test 3, or it should be the backplane). So remains for me: cabling (most of it tested with test 4, but not all) or the servo (altough the resistance looks okay in test 4).

    Some other ideas?

  • ABB S4 + IRB2400 startup problem: Diag: Illegal instruction.

    • rib
    • January 25, 2021 at 10:50 AM

    I already tried something similar to check the brake, but your method is more efficient. I will perform your tests this evening.

    I also think to try to megger (isolation test) the coils of the motor. I am thinking if maybe the insulation of on of the coils is not okay anymore and therefore are leaking to the ground.

  • ABB S4 + IRB2400 startup problem: Diag: Illegal instruction.

    • rib
    • January 24, 2021 at 5:16 PM

    Small update:

    Today I did the procedure to commutate the motor of first axis, see attached picture. I placed the motor in this posistion and then selected commute axis 1 in the service menu. Unfortunately this did not solve the strange noise.

    Edit: also now swapped the servo amplifier boards inside the s4 controller but still the same noise on the same axis.

    Images

    • 65F82CDC-2DCB-4B2E-A72A-30FA6EECE69C_autoscaled.jpg
      • 566.68 kB
      • 1,200 × 1,600
      • 10
  • ABB S4 + IRB2400 startup problem: Diag: Illegal instruction.

    • rib
    • January 24, 2021 at 9:33 AM

    I can move the robot now :smiling_face:

    Only thing is that the motor of the first axis is making a strange noise it looks I sound a little bit as electricity flow or how you want to describe it. When not moving this is constant and when moving its pulsates with the speed of the movement.

    Can it be that for this axis maybe the commutator values are wrong? And therefore the motor is not

    Powered correctly?

  • ABB S4 + IRB2400 startup problem: Diag: Illegal instruction.

    • rib
    • January 23, 2021 at 12:34 PM

    I did now manage to get the right Baseware version for an IRB1400 during setup you can then choose for the IRB2400. This is now completely installed, and the system now at least start up again. But now the following problem arises:

    - Battery of the robot itself is also empty.


    Therefore, commutation also has to be done again probably. The only disk which I had was a boot disk so also no MOC.cfg file but I did found the encoder values, but only two times. Any tips?

    Images

    • DA45E386-69EC-451D-BA29-729831574877_autoscaled.jpg
      • 624.11 kB
      • 1,200 × 1,600
      • 14
  • ABB S4 + IRB2400 startup problem: Diag: Illegal instruction.

    • rib
    • January 21, 2021 at 9:40 PM

    I think it is "Boot discette label text:Basic 2.0". I did found BaseWare 3.0 on the forum: boot disks for S4 will it be possible to use this one and therefore to upgrade?

    Br Rene

    Edit: just checked but this is not possible. Probably I have the BaseWare basic 2.0 version. Hopefully somebody still have these disks :smiling_face:

  • ABB S4 + IRB2400 startup problem: Diag: Illegal instruction.

    • rib
    • January 21, 2021 at 8:52 PM

    Hi,

    I have just replaced the battery now the warning is gone, but the error is still there. Also tried to connect with the com port but no output. Therefore removed both batteries and now the system is at least performing the test (it didnt do that) and is then performing a cold boot. Now it is asking for the disks (as expected).

    I inserted disk 1 which was okay and then asked for disk 2 which I did not have. Attached the disc.id file.

    Does somebody has the boot disks?

    Files

    DISC.zip 635 Byte – 25 Downloads
  • ABB S4 + IRB2400 startup problem: Diag: Illegal instruction.

    • rib
    • January 21, 2021 at 8:14 AM

    Hi,

    Thanks for your reply.

    Attached the photo of the teachpendant with the warning (batterij) and error (diag). First I get the warning then the error. I managed yesterday to have boot disk 1 working again, the other ones I do not have. ABB_MC file was corrupt and could be repaired by windows. The disc.id file still looks okay.

    Update: also disconnected to robot cables, but still the same error.

    Images

    • error_both_autoscaled.jpg
      • 149.36 kB
      • 1,919 × 745
      • 25
  • ABB S4 + IRB2400 startup problem: Diag: Illegal instruction.

    • rib
    • January 20, 2021 at 10:58 PM

    Thanks for the reply, I also do not think that by replacing the battery it will be solved, but I just have to be sure because when going for a cold boot definitely everything will be lost. Currently I am still waiting on the new batteries, so unfortunately no update. I did check the boot disks but unfortunately these are corrupt. What will be the best way to get these disks again?

    ABB S4, IRB 2400 M94

  • ABB S4 + IRB2400 startup problem: Diag: Illegal instruction.

    • rib
    • January 17, 2021 at 1:02 PM

    Hi,


    I have a ABB S4 + IRB2400M94A which will not start-up anymore after some years of no use. It gets an error: "Diag: Illegal Instruction, SR: 2014 PC: 0004C6A6". This happens during booting. What happens:

    - Power on

    - Boot screen will be shown: "Welcome to the S4 robot-controller"

    - Warning. 03:01501 Battery 1 low voltage

    - Warm start in progress.

    - Then after a few seconds only It gets an error in only text: "Diag: Illegal Instruction, SR: 2014 PC: 0004C6A6".


    I already tried searching on the internet but I cannot find anything regarding this error also not in the manual. Off course I also get an warning for the battery so I already ordered new batteries which I will getting a few days, but normally I would say a warning should not prevent that the robot will not start-up. Also a warm boot is performed so the memory is not empty. At least that is what I think.


    The red LEDs on all expansion cards are red, according the manual this happens when the controller is not initialized, I think because it did not start-up currently.


    Did somebody has got a similar problem? Or maybe an idea to solve it?


    Currently my approach would be: I replace the batteries, to be sure. If this does not solve it I would clear the memory by removing the batteries and try to do a cold boot. The problem there is only I do have some disks for this but if these are the rights ones and still working..., I am doubting at least. Therefore I would like to use this as a last solution.

Advertising from our partners

IRBCAM
Robotics Channel
Robotics Training
Advertise in robotics
Advertise in Robotics
Advertise in Robotics
  1. Privacy Policy
  2. Legal Notice
Powered by WoltLab Suite™
As a registered Member:
* You will see no Google advertising
* You can translate posts into your local language
* You can ask questions or help the community with your knowledge
* You can thank the authors for their help
* You can receive notifications of replies or new topics on request
* We do not sell your data - we promise

JOIN OUR GREAT ROBOTICS COMMUNITY.
Don’t have an account yet? Register yourself now and be a part of our community!
Register Yourself Lost Password
Robotforum - Support and discussion community for industrial robots and cobots in the WSC-Connect App on Google Play
Robotforum - Support and discussion community for industrial robots and cobots in the WSC-Connect App on the App Store
Download