1. Set a register to the outputvalue (See above for possible values)
2. Transfer the register to the port (Port21 / 22)
Posts by sjx
-
-
This is the AC Drive version of the manipulator. This is not the same like your version. Came up with S3M92 (IRB1500) systems and works via the 7th internal drive unit with Common Drive switching (One drive for 3 axis, 10, 11, 12). Your S3 System is version M87 - M90A.
Needs 3 AC-motors, 1 drive unit, 1 SMB Board, 1 Switching Board with safety Interface from ESAB, lots of cables..........
Much cheaper to buy the complete system and sell your robot.
-
The old ESAB Orbit 160R positioners use DC drive technology with Labod Drives in a separate control cabinet. These could be operated up to the S4 generation (DSQC208A Board). S4C no longer supported this. Converting the manipulator to S4C drive technology is too complex and too expensive. The safety concept with activation/deactivation of the drives would also have to be integrated. ESAB provided special circuit boards for this purpose. It is almost impossible to get all this together and ultimately adapt the parameters of the S4C.
-
If I remember correct, the Serial Link RAP option disk that came with a lot of software was the key. Been about 25 years since played with the S4 RS232.
It's been 20 years for me too.
With Advanced Functions you can also read/write serial channels. RAP protocol also required special basic software (Basic Commware, BaseWare OS RAP) -
Connector X5 on AP80:
You also need the right software option to use it.
-
Do you have connect 24VDC/0V to the I/O groups ?
-
-
The option includes the documentation
-
There is any wiring diagram for A1/X23 ?
-
Do I need this disc ID file for all the other software discs also or just for this cold start?
Boot discs and option discs require these disc.id files. Discs that you need after the boot process do not.
Can you read/copy the discs on a PC ? Do the discs have "scratches" ? Is the floppy of the controller really ok ? -
The disc.id file always has a readable text portion at the beginning of the file that has disk #, part #, serial # & copyright stuff. If it's not there then someone has deleted it.
Do not think that this has been deleted.
Original update disks from ABB do not have a serial number as standard. The disc.id file code had to be generated using a software tool. This normally required the original set that was supplied with the robot. The disc.id of the update set could be generated from the disc.id of the old set.Today I tried to start it up again after I did check the D62 and D63.
I got a new error message at startup.
What exactly did you do?
Did you just remove the board or did you really remove the e-proms ?
What do the red LEDs on the computer boards do ?
Do they go away after a certain time or are they still on after an hour ? -
Is it possible to insert my serial no. in disc.id files with notepad?
No, not possible with Notepad.The serial number is also part of the encrypted code. But your disc.id file contains a serial number?
And if so is it the robot serial no or the electical cabinet serial no I should use?
The standard at ABB was that the mechanics and control cabinet had the same serial number on delivery. In the automotive industry, however, they were then exchanged at random.
If you want to have a matching serial number, I would use that of the control cabinet. -
Think you have the A32 welding interface from ESAB used together with the S2 controller / LAH 500.
controller parameters analog ports:
Port 25 Voltage Port
Port 26 current Port depends on which wire diameter you use
-
It's krc1, are you sure the newer driver exist on krc1? Don't think so.
It has nothing to do with KRC1. It has to do with KSS. He has written in Post #1 "running KSS 4.1.7 SP05".
KSS V4.1.x has version 2 driver.
-
In Telnet, it shows baudrate 125kBaud.
Photos shows DIP-Switch for 500kBaud ?
Changed any DIP Switch configuration? Switched OFF / ON the modul after changing?
Is this really a standard-version from Wago 750-306 ?
Think is the version used in old ABB S4C (+) Systems. (004-Version)
In IOSYS.ini, you can use also the new DeviceNet driver dn2drv.o and zhe new mapping system.
Change to:
[DRIVERS]
DEVNET=2,dnInit,dn2drv.o
[DEVNET]
INB0=5,0,x1 ;$IN[1-8]
OUTB0=5,0,x1 ;$OUT[1-8]
-
In RW3.2, on disc 8, you have normally your model:
Use Scan to go to the second submenu
-
...How is the SBM Kuka replacement procedure going,
-
The master of the safety circuit is in the KCP.
That's the reason, why safety circuit works only with the pendant.
Which KSS version is installed ?
Have you done the installation by yourself ?
What's the history of this robot?
Can you post the files progress.ini and the hw_inf.ini files?
-
You have not only a problem with "Emercency stop".
You have a problem with the complete ESC-circuit.
Look here the "?" :
That's the reason why I asked for information about connectors X5, X4, S2.
-
Whats about connectors X5, X4 and the position from "S2 Voltage Two way switch" ?
Some pictures from the back from the controller and your wiring are surely helpful for us.
Advertising from our partners
