No idea what was going on. The error came suddenly. After a reinstallation, everything runs without errors again.
Posts by Roland Keller
-
-
The only thing that helped was uninstalling, installing the previous version and then updating to V5.5.3.
-
I will check it.
I just checked into the hotel.
Take a look and I'll get back to you.
-
-
PVTR=(P_Zero divided by PWKPOS)
* add an offset in tool coordinates included in variable PTEACH to PVTR after the division
-
-
Goto is suboptimal. Make a local subroutine and use GoSub.
When the subroutine is finished, the program pointer jumps back to the place where it was called.
Code
Display More'Mainroutin M1 = 1 While M1 = 1 If M_In(11) = 1 Then GoSub *Box1 Break ElseIf M_In(12) = 1 Then GoSub *Box2 Break ElseIf M_In(13) = 1 Then GoSub *Box3 Break Else 'Do nothing EndIf WEnd END '*********************** 'Local subroutine '*********************** *Box2 'insert your code RETURN '************************ *Box1 'insert your code RETURN '************************ *Box3 'insert your code RETURN '************************
-
A hardware (for example Siemens ET200 or similar) must be available for the communication between the robot and the PLC. How else are the signals to be transmitted? But this is not available in RobotStudio. Virtual signals cannot be transmitted. But I would be happy to be convinced of the opposite.
-
As far as I know it is not possible
-
And please don't always dig up the old posts. This Post is 6 year old. It´s better open a new one.
-
Check the Robotstudio help. Keyword Clk. This could be your friend.
-
-
-
Hello Skooter,
thank you very much, the error messages are gone.
It is running now.
-
According to ABB service, only a jumper from pin1 to pin2 on connector X8 is required.
-
ABB IRB 4600 with RW 6.13.
The system is prepared to control a 7th axis. But it is no longer needed and should be removed from the system.
Actually no problem.
Remove the drive unit in the installation manager and you are done. The drive unit is also no longer displayed under Configuration Motion.
However, it is still present in the Motion Planner and reports an overheated motor.
Removed the axis from the moc, loaded moc and restarted. And it is still in the Motion Planner.
Hardware completely disconnected. Created a new system. Nothing changes.
Has anything changed in the newer RW states?
-
Workobject?
-
The robot guides a plasma cutter. This is ignited with high frequency. As far as I can tell, everything is cleanly shielded.
What seems strange to me, but I have no idea where it could come from, is that a resistance of about 2 ohms is measurable on the table on which the cutting is done. But there should be no current at all. Perhaps it is due to incorrect earthing.
-
Unfortunately, I can't say too much about it at the moment. I got the information from the machine manufacturer who quit due to illness. According to him, it was always this board. I was able to have a brief look at the robot itself on Friday. However, it was switched off. I have only received a few photos so far.
-
Robot RA010LA. Defective 1HA board has been replaced. After 20 minutes in teach mode, the new board was defective again. and was replaced again. Same phenomenon again. Kawasaki then replaced the power block. After that, the error reappeared after a few minutes without the robot being moved. Does anyone know this phenomenon and could possibly help me?
Thanks in advance
Roland