Posts by Skooter


    Ill check the battery before powering it in. Its been unpowerd for at least 10 years so they probably need to be replaced.


    I would snip the battery leads or desolder if you have very good soldering skills. I would not spend much money till this old girl at least jogs.


    You may need help with the run-chain jumpers to get it to jog. Looking at the back wall inside the controller, you should see the System Terminal Unit that should be a DSQC124 or a DSQC138. Can you verify which one?

    If it's the same as the M91 IRB90s, it should have the early S3 power supplies.
    You may want to make sure the 2.4V NiCad batteries on the DSMB127 Memory board(s) are not shorted before turning it on.
    You'll need DSDD (720K) 3.5" floppy disks to save parameters and any programs you write.
    I've already posted all the S2 PDFs I have to the manuals section.
    Keep us posted.

    .


    Where do I enter the calibration data?


    Parameters Menu, Topic: Manipulator, Type: Motor Calib
    Select IRB1, and then you should see the calibration number listed as Calibration Offset.
    As Lemster68 said, the number should match the number on the stick on the back of the robot arm




    Iv created a MoveAbsJ and axis 3 is out by -0.3 Deg axis 5 is out by 0.2 Deg and axis 6 is out by -0.7 Deg.


    The position you said you created for the MoveAbsJ. If it is a named position, it is a jointtarget. You can view/Edit this data by going to View, select Data Types, select Jointtarget and then select the named position you used. Verify each joint of this position is 0.0

    The 'Welcome ABB' only comes up when the controller boots up without errors. The S4C & S4C+ take a very long time to boot when there are system errors.
    Are there any other errors that happen before the Internal errors?
    Focusing on why the teach pendant does not respond to key presses:
    Could be the teach pendant is receiving but transmitting - try another teach pendant.
    Could be an issue with the Panel Unit - try another.
    Unplug the backplane X10 & X16 CAN bus connections and try again. Perhaps something is loading the CAN bus after a while.
    Could be a fatal error in the system that requires a software reload. The errors are on the screen are not encouraging. I hope you have a recent backup and software just in case.
    You could monitor the output of the serial port on the front of the Main Computer board. Search the ABB & ABB manuals board for "PC as service tool" for more info.


    Ok, but where should I place the file sio.cfg ? On the floppy disk (small pendrive on the front of the controller)? I tried to open it on a laptop, but it did not detect it.


    Do you have a floppy disk or a USB floppy emulator?
    Save your parameters to whichever you have. One of the parameter files will be SIO.cfg. You can open it with Notepad, WordPad, Notepad++, Brackets, etc
    These values can also be entered in the Parameters window of the teach pendant under the topic "Communication".
    The User Manual for BW3.1 or 3.2 will also have more information in the Parameters section. Can upload it if you don't have it, just let me know if you have BW3.1 or BW3.2.


    Lemster68 is right. You must fix this issue first. Possible causes: Bad SMB or bad axis 4 motor or the wiring between the SMB & axis 4 motor. I would reseat the connections on the SMB and motor first. Make sure exposed shielding on the cables going to the SMB are cable tied to the SMB metal frame to give them proper grounding. If it's a 2400/10 or /16, you can swap axis 4 resolver connectors with axis 5 or 6 and see if the problem moves. If it doesn't, suspect the SMB or cable harness. If you have a 2400L, use a spare motor to connect to axis 4 motor connections to verify. DO NOT move the resolver or remove it from the motor. Doing so will change the commutation and open up a whole new set of problems.

    Check the logs. A system error can keep you from seeing the programs. Get the robot to the point where you can jog it and update the rev. counters. I'll guess you should be able to see your programs then.

    Regarding S4C robot computer boards:


    3.1 -> 3.2 = :top:


    3.2 -> 3.1 = :down:


    I was told years ago that the larger 3.2 BIOS overwrites the smaller 3.1 BIOS. When you load the smaller 3.1 back in, it doesn't completely overwrite the 3.2. The lack of deleting the BIOS memory area before loading and lack of an EOF (End-Of-File) marker allows what is left of the 3.2 BIOS to append to and corrupt the 3.1 BIOS. Since there is no provision for clearing the flash ROM, the IC is usually removed, cleared on a programmer and reinstalled.


    ı have s4c ırb 6400 robot. this robot smb is not working good . orginal smb is DSQC 313 3HAB 2213-1/3.
    Can ı replace it with DSQC 313 3HAB 2213-1/2 ? I found ıt from my friend ? ı am not sure about working . please help


    The DSQC313 is actually the circuit board and is used in several SMB with different mounting configurations. Make sure the SMB your friend has is the same mounting configuration. The IRB6400 part # should be 3HAB4259-001 or the newer 3HAC14506-001. The SMB part number is usually found on the frame underneath the battery pack.


    The /2 and /3 at the end of the part # is the revision number. The /2 should work.

    Regarding your questions:
    1) The BIOS is stored on the Robot CPU board in a flash RAM IC. It updates when loading software of a newer revision of the same software or when updating to a version, 3.1 -> 3.2. DO NOT go backwards in software versions as it will corrupt the BIOS.
    2) I assume you mean a flash drive type hard drive? No. That is the S4C+ and newer.
    3) Memory in the teach pendant is used internally for the operation of the pendant.
    4) The S4C does not use images. That is done by the S4C+ and newer. The service port information is also for the S4C+ and newer.
    5) It means they are in an error state.
    6) If the reason you don't have communications with the controller is a bad teach pendant, then changing the teach pendant will help.
    7) If you have a corrupt Robot CPU, then change it. Just be very aware that going backwards in software versions will likely corrupt the memory in it. BW3.0->BW3.1=YES and BW3.1->BW3.2=YES. BW 3.2->BW3.1=NO and BW3.1->BW3.0=NO

    15+ years ago, had an M94A IRB6400-2.8 that came out of GM Arlington with 2 fixed torches on the EOAT that were used simultaneously to give 2 welds on parallel paths. The tight tolerances in parts & fixturing gave it successful results. It had 2 Miller Deltawelds and had put in years of welding on the assembly line. Was weird to see ArcWare on a 6400, too bad I lost the backup to a hard drive crash years ago.


    I've used the tandem setup that Tyler posted. It was needed for a big controllable puddle to fix terrible part fit up issues. Lincoln was extremely helpful with the software updates in the i400s used. The torch cleaner was funky looking and expensive.

    The computer picture shows an S4C computer rack with a DSQC336 ethernet board, not an S4C+. You are using a procedure to connect to an S4C+ which will not work on the S4C. The software will need the Ethernet Services option installed. The IP address is specified in the SIO.cfg parameters. Here is an example:


    SIO:CFG_1.0:3:1::
    #
    COM_PHY_CHANNEL:


    -Name "sio1:" -Type "sio"


    -Name "sio2:" -Type "sio" -Channel 2


    -Name "ENET" -Type "ethernet" -Channel 3
    #
    COM_TRP:


    -Name "Enet" -Type "TCP/IP" -PhyChannel "ENET" -LocalAdress "192.168.0.50"
    #
    COM_APP:


    -Name "EneT" -Type "NFS" -Trp "Enet" -SpSysEvent 1\
    -ServerAddress "192.168.0.23" -LocalPath "pc:"\
    -ServerPath "/C/ABB_S4C_PROG/" -UserID 1 -GroupID 1 -PortNo 4

    There are several different USB floppy replacements units along with different versions of (sometimes sketchy) PC software.
    Not sure where to start unless you have another setup that works where you can swap places with a working unit.
    Perhaps posting pictures of the front and back of the unit you're using will make it more relevant to someone.
    When you plug the formatted USB into a computer, does it report it as "FLPPY0" approx 1.38MB in size?

Advertising from our partners