hello ı have an s4c plus controller.
S4C plus I got to work ımages.Images share it with me, I'd appreciate it with friends.
tanks!!
hello ı have an s4c plus controller.
S4C plus I got to work ımages.Images share it with me, I'd appreciate it with friends.
tanks!!
We have a S4C plus controller and we started having a problem on robot boot after doing some stuff.
1- I backed up the image of the disk before starting to do anything.
2- The robot system was corrupt, it was not possible to go into the service or file manager menus.
3- I tried downloading a new system but there was space problem in the disk.
4- To delete the current system I had to go into the service tab for X-Start but it wasnt possible since service tab could not be opened.
5- I restored the disk with the image of another robot and to do X-Start but after that it started stucking at counting on boot.
6- Restored the original hdd image back but still it keeps counting to thousands at boot.
Now I cant do anything, the robot doesn't boot and keeps counting (status led of the cpu is red btw).
Does anyone have any idea ?
Hello,
I have a used S4C Plus, which I have powered on for the first time after It got installed to its new plant. I have powered it before connecting to the manipulator. When I tried going into the service window It freezes with a blank page, It also does the same thing with the file manager window. But it is ok with other options like System Parameters. Since I can't go into the service window, I can't do any backup/restore operation. Does anyone have any clue on the problem?
Oh and in case I will need to reinstall a new system, I will have to establish its profibus connection to the external IO terminal (beckhoff) again. Which is something I don't have the experience or knowledge on. I would be really glad if someone has a manual including profibus configuration for S4C Plus
Actually there are only two modes on the pendant of this VKRC2 there is "auto" and "manual".
Do I need to activate some interrupt with the buttons ive mentioned to do what you have been suggesting btw?
Well I want the operator to be able to pause/halt the execution since there are some long processes and it can be needed to halt it without an emergency protocol. I was able to do that with ABB robots. There used to be 2 buttons conected to the IO board, one to stop the cycle and one to start it. I'm thinking of doing the same with KUKA. Oh btw the controller is VKRC2
Hello,
I've been wondering how I can configure 2 DI signals to act as cycle stop and cycle start. I want to have two signals, one to halt the execution (just a normal halt, not some E-stop) and one signal to make the cycle continue. Is it possible to configure digital inputs for such purpose?
Thank you for the reply I will check again when I go to site
Greetings,
I'm having a problem with the X11 connections of a KRC4 Controller. I don't have any problems at T1 and T2 modes. But on AUT I'm getting an error.
I'm getting this message:
KSS12016 Operator Safety Open
There are some pin connection combinations that I have tinkered with and tried various combinations (some NC and some NO) based on what I have read from the robot forum and the documentations. These combinations are:
6-64 I'm not sure about what to do with these 8 pins
23-24
21-22
3-4
There are other 14 connections on which I don't have much of a doubt. These are all connected with jumpers (I will change these jumpers later with necessary NC safety connections)
108-106 Probably unnecessary on my setup, these pins leads to nowhere in the cabinet
107-105 Probably unnecessary on my setup, these pins leads to nowhere in the cabinet
32-31
14-13
29-30
11-12
27-28
9-10
25-26
7-8
19-55
1-37
2-38
20-56
I think there is something I need to do with the 4 pin pairs I have listed above but I can't figure it out. Is there something I need to do with those pairs?
Thanks in advance,
Thanks a lot for the help.
Actually I want to cancel it because I ran out of free output signal (16 out of 16 are in use). So I want to rename that signal and use it to actuate a valve.
Thanks a lot for the help, in that list I see 2 system outputs
- MOTLMP
- CycleON_DO
It is obvious now that the second one is the one I want to cancel.
Can I just delete that signal? Would it cause any problems?
Thanks a lot, i think i will both use switch and virtual safety. One last thing about the robot:
I am having problems rotating the first axis more than 65 degrees. It says that it is the limit for it. How can I extend that reach for the first axis?
Thanks, I've also thought of a switch for it I might use it then. I don't know about the world zone commands but will read on them.
Hello,
I have 2 IRB2400 robots with S4C controllers. One robot is the master that drives the positioner and the second one is a slave one that sends a feedback that states it is at home position and it is safe to rotate the positioner.
I want to get a digital feedback when the robot is at home (to inform the master robot). At the moment I SET an output after the robot goes to a point that I have named as "HOME".
I have 2 questions:
1- Is there a "home" protocol that I can use to get reliable feedback?
2- I set the output after reaching home and reset it before any motion command. By a very simple operator mistake, that signal can remain SET and the positioner can collide with the slave robot. Can someone suggest a convenient way to overcome that risk?
I don't want the positioner to crash into the robot with incorrect signalling
BTW I know that SM Bus is the bus that lets the main computer supervise dsqc 505 - 506 and 508, the units I have mentioned that I have replaced were the main computer and the battery unit (dsqc 505) Well since the error is regarding the communication with all the units, it was a slim chance that the cause was by the battery unit. But I suppose replacing even the main computer (dsqc540) suggests that is not based by any unit of the bus.
There are some possibilities bugging me:
1- SM Bus wiring:
I have tried checking every cable connected to these 3 units and the MC. To be honest I couldn't get which cables are of the SM Bus exactly. But I see a connector (XP4) on the process power supply labelled as "SMBUS", which is connected to the "power supply" port of the computer unit. If I am not mistaken, all relevant data is gathered on the process power supply and connected to the computer unit with a bus cable to be supervised.
2- DSQC 541
I can't even explain why it may cause a problem but the main computer is mounted on that board. I just wondered if it may be related to the problem. Well even if that is the case I don't have a spare one to check :).
3- Software
I'm not an ABB expert, but I assume the SMBUS drivers should be included with the Baseware, not some code in BIOS (If there is such BIOS on main computer). Maybe I can reinstall the system (If someone can confirm that drivers for SMBUS are not in BIOS).
Hello,
I have this controller which comes up with several errors on start-up:
The Robot:
IRB 2400 M2000 (S4CPlus Controller)
Errors:
It goes into a system shutdown error state whenever I turn the power switch off. There is no "shutdown" option in the current baseware version but there is "restart" and when I restart the controller it doesn't give system shutdown error.
The main error I get on start-up (whether I power off/on or restart):
MC0: alarmts.c 768 ipc err
Unexpected error INTERNAL
An unexpected error has occurred. Report this error with the following code and describe the circumstances. MC0: ipc send error -9 to safcycts
This is followed by 4 more errors within the first 15 seconds after startup
37057 SMBUS unit lost - SMBUS unit at address 33 is not responding.
37057 SMBUS unit lost - SMBUS unit at address 39 is not responding.
37057 SMBUS unit lost - SMBUS unit at address 38 is not responding.
37057 SMBUS unit lost - SMBUS unit at address 35 is not responding.
I get these 5 errors regardless of how I restart the system (powering off or using the "restart" under service tab). BUT if I shutdown by powering off, I both loose the mastering and the system goes into system shutdown error state.
Well I have tried replacing the main computer with another one of the same type (DSQC540).
Also tried to replace the computer battery unit (along with its board)
Nothing changed after these. Does anyone have any idea what might be the problem. Will really appreciate if someone has any clue
Thx, excuse his english, no need for futher explanation :). Didn't know that it was retrieved from a board on the manipulator. We will check that.
Thx Fluke, ive tried searching but what is RDW data, and I have another question:
Is it possible to see the manipulator specs by inspecting the mada file (then we can measure and see if the definitions fit with our robot, when we load a mada in it)
Im someone working on the same robot with Doxar atm.
The thing is, even while we were installing KSS and when it prompted the mada selection during setup it didn't approve the kr150 mada we have selected (guided by the label on the manipulator). Yet surprisingly the installation accepted a random mada file we have tried, which is of a kr200 manipulator. We didn't mind the mismatch untill we realised that the robot can't even rotate around the tip of the 6th axis with world coordinate system orientation. Hence failure in TCP interpretation is just a result of misdefined dimensions.
At one point I've tried entering numbers in TCP declaration to see where the robot thinks that its tip point exist on space. Ive concluded that the dimension definitions of the 3'rd axis arm is longer that it should have been. As if the mada is for a robot with a longer arm (just a rough guess)
Im confused a bit since the robot is a bit picky on the madas, like there is a check done to see if the mada is correct (as in it was denying the other mada types on the installation). But the one mada it accepted during setup seems to be wrong.
Well maybe its something not related with mada, but we havent been able to come up with any solution on this.
Thanks everyone,
Its solved, I have commented everything related with other commnication types and now I can manipulate outputs as well. Im attaching the final version of my iosys.ini in case someone esle has the same problem.
Oh I forgot to mention. I had been getting the error: "1034 Error on writing, driver: INTERBUS" as well.
Unlike the the DSE error, I don't get this just when I try to execute a line to modify OUT, I had always been getting this. It was always there since the day HDD was formatted and we started to work with the current KSS.
I so got used to it i forgot to mention. Maybe it can also give a clue.