Hi
Please instruct me for connect IRC5 with cp1616 profinet to siemens s7 -1200
My robot has this option 888-1 ProfiNet IO M/S and CP1616 card
RobotWare Version: 5.15.9157.15
Many thanks
hi
did you solved this problem
Hi
Please instruct me for connect IRC5 with cp1616 profinet to siemens s7 -1200
My robot has this option 888-1 ProfiNet IO M/S and CP1616 card
RobotWare Version: 5.15.9157.15
Many thanks
hi
did you solved this problem
Can you explain exactly what you want and why?
Joystick devre dışı hatası nasıl düzeltilir?
robot açılırken test esnasında joystick orta konumda olmasına rağmen bu hatayı veriyorsa, joystick sökülüp yaylar ve yüzeyler temizlenebilir. daha önceden benim de başıma gelmişti ve düzeldi. denemekte fayda var..
no, robot multi-tasking and plc are unfortunately not used..
My aim in this study is, as I said before, when the robot is not working, the robot should not stay in motor_on. I will either use CYCLE_ON = 0 as it is not working, or I will use DO_HOME = 1. otherwise the robot is already either manual or in the AUTO_STOP state because the door is open.
The first line has an issue, it is this: IF DOutput(doCycleOn) = 0
For that to be true then the program cannot be running, If the program is not running, then the code does not get executed. If you could put that in a background task then it might work.
I counted the time when the robot was not workink anyway and wrote it to be MOTOR_OFF, after 15 minutes. If the robot is waiting at HOMEPOINT, it is already in RUN mode. Already my problem is that, when the operator isnot working, the robot stays on MOTOR_ON.
I can also use HOME signal instaed of CYCLEON.
I tried it before, at the end of time (MOTOR_ON: = false MOTOR_OFF: = true), but I guess it was wrong and it didn't work
The motors do not actually turn off, they remain on, but the brakes engage, and the hour meter stops running. But actually, as far as SIS counter running still, I have to say I am not sure how that behavior is affected.
If I write a program like this, and add it into WARNING MODULE like air presence control in MAIN proc, I think the system will stop after 15 minutes. say what?
IF DOutput(doCycleOn)=0 AND DOutput(doAutoOn)=1 AND DOutput(doMotorOnState)=1 THEN
MotorOffTime:=TRUE;
ClkStart mtime{4};
nmtime{4}:=ClkRead(mtime{4});
IF nmtime{4}>=900 THEN
ClkStop mtime{4};
ErrWrite mfundament{1}, mmy_message{1}\RL2:=my_message{3}\RL3:=my_message{5};
SystemStopAction\Halt;
ENDIF
ELSEIF diLS1PrgStart = 1 OR diLS2PrgStart = 1 OR diLS3PrgStart = 1 OR diLS4PrgStart = 1 OR diLS5PrgStart = 1 OR diLS6PrgStart = 1 THEN
ClkReset mtime{4};
nmtime{4}:=0;
MotorOffTime:=FALSE;
ENDIF
You could then try to update your robotware. Do you know if it came with that version or has it been updated to the current version from earlier version?
the robot version hasnt been changed. same system same version since istalled..
Have you tried using the reset on the back of the pendant?
yes, i have tired. but sometimes it gets reset, sometimes i have to turn it off and on
The motors do not actually turn off, they remain on, but the brakes engage, and the hour meter stops running. But actually, as far as SIS counter running still, I have to say I am not sure how that behavior is affected.
Hello;
In our 6700 robot (IRC5) that we use ARO3G servogun, the servogun does not move without any error. For example, I am modifying the point, when I run the same point, the servo goes to a certain point and does not do the welding process. When I use the INDGUNMOVE RESET command for a solution, it fixes. TR.ABB's advice is to establish a new system, but they cannot say anything clearly about the solution. This problem has occurred twice in the last 6 months.
Is there such a problem other than me?
thanks for your helps
I will chech it again. In this case, will motors switch to motor_off position after 120 minutes?
Look for it in motion planner via the pendant.
unfortunatelu ı couldn't find an option related to duration in the MOTION tab..
No, not there. It might be in the motion planner, or it might be one of those things that you only see in the pendant.
I guess there are irrelevant values there too:
#
MOTION_PLANNER:
-name "motion_planner_1" -std_servo_queue_time 0.193536\
-linear_max_speed 9.7 -use_motion_sup "rob1"\
-use_jog_parameters "motion_planner_1" -use_for_jogging -repos_installed \
-use_spline_parameters "motion_planner_1" -restricted_circlepoint
-name "motion_planner_2"
-name "motion_planner_3"
-name "motion_planner_4"
-name "motion_planner_5"
-name "motion_planner_6"
It is available in all of them, in the MOC.cfg. In the older ones, by default, it was set to 3,600,000 seconds. Newer baseware default is like 9 minutes, 900 seconds? Somewhere in that range, much more reasonable.
writes in MOC file:
#
BRAKE:
-name "SERVOGUN" -control_off_speed_limit 1 -control_off_delay_time 0.4\
-brake_control_on_delay_time 0.4 -brake_ramp_speed_limit 0.4\
-initial_brake_dec_time 0 -use_brake_type "SERVOGUN"
There is no need for that. There is a system parameter, "Brake On Time" that will allow you to set when the brakes should engage. The servos remain on and ready, but the hour meter should stop as the brakes are on.