Posts by byrol

    I am reading all the written answers one by one and I am really reading a lot of useful information. I have no choice but to extend the mode selector switch on the cabinet to the operator. Thank you very much to everyone thanks to you I have read many useful shares.

    Since the robot's cabin is away from the user operator, the operator can move from the control at any time, even if the cabin is in the auto position. I want this.

    Sergei Troizky,

    Yes, you're right, I may not be able to express exactly what I want. When the key on the cab of the robot is in the Auto position, the Pendant does not move to the robot. If the key on the robot's cabinet is T1/T2, then the Pendant allows the robot to move. "Jog in Auto Mode"



    The value you wrote down looked like "0", I made it "1", but again the situation has not changed the robot does not move from the controller in the Auto position.

    If the Auto Mode switch on the cabinet is selected, I cannot move manually through the robot control. I want to do this. No matter where the switch on the cabinet is located, I can make a manual movement via the robot control.

    I'm probably asking a very simple question, but I don't understand why I can't solve the problem. Robot: M710IC Cabin: R30IB. If the switch on the robot cabinet is in the auto position, I cannot move the robot even if the control is on. If I take the key on the cabin T1/T2 to one of the two, I can only move. With which variable can I also give movement to the robot in the Auto position.

    My idea, This problem does not necessarily mean that the engine or pulse coder is faulty. There may also be a problem with the CRM1 or engine cables. Or there may be a problem with the EM Card. There are problems with the cable itself, and the robot only has problems when it comes to certain angles. Over time, when he makes more movements, he begins to make this mistake more often.

    If it were me, I'd prefer Fronius. Your friend recommended a new generation machine, it's good. I have installed this series before, it is really light and has a very low power consumption, such as 35A of the machine. But I think the two most important features are that you can disassemble and install everything on the machine without needing any extra equipment, and the 100Mbit communication speed is very good.

    I think you need to choose this entirely based on which brand in your area can support you better. Fronius machines are more affordable than Lincoln, and Fronius equipment becomes lighter. I think both are the same in terms of robustness. Cloos is not a brand I know of. According to Lincoln Fronius, there is more electricity consumption. However, because Lincoln is an older and more experienced company, their resource options are much greater.

    To date, we have performed memory upgrades on 3 different robots. In the first one, we bought the memory from Fanuc and without doing anything, we just inserted it into the card and it worked smoothly. In the second one, the plug didn't work and a staff member from Fanuc probably did "Control Start", didn't let me follow it and started the memory. On the third, Fanuc's own staff was also unable to promote the memory. He took a complete backup and sent it to headquarters, they did something about the memory in the backup, sent it back, and when we restored it, the memory worked. So I'm wondering if I understand what kind of promotion is being done. When the robot memory will be added, I will take popcorn and coke with me and say, "How will it be this time?"so I'm watching that. ;(

    "SLC2-SST-CLX-RLL-PFB-Profibus" this entire communication is already defined as "RSLink". In other words, they all provide communication via the "RS-232" port that we know of. In order for you to configure a card similar to this in the robot, you need to read the card's documentation well. There it is already described in detail which decimal code is divided into how many parts and how it turns into an input/output signal.

    One of our customers has a "RJ2 M16i" robot that I installed 4 years ago, and the robot is welding laser CW to stainless material. The robot is as shown in figure 1.axis is forced to work quite close to ground zero. The weight on the robot head is about 7-8 kg. Since we installed the robot, our customer is not convinced of the maintenance, and the robot welds almost 16 hours a day. Now there has been a problem like this for a few months now, there are no problems with the robot's welding points or operation, but when it finishes its work and goes to standby 3.the axis motor visibly releases itself somewhat towards Z-. I have almost no mechanical knowledge of robots. Do I need to get some reasonable support from outside or can I fix this problem by reading the document myself? The robot has not been maintained for 4 years, except for battery replacement at the beginning of each year only. It seems to be a mechanical problem, I am waiting for ideas from my masters.

    Note:The picture shows the normal working position, not the position where the motor is released. I took a picture to show that you work in this position all the time.


    The card whose picture you are sending with the error code on the screen is not the same card. The Fanuc motherboard in the picture. If this card did not work, only your screen light would come on, but no text would appear on the screen. The motherboard, which is written in the error code, talks about the "DeviceNet" communication card. It is also known as an I/O card. That card is located in a different place from the motherboard. Depending on the type of card, it may vary in some cabins, it happens during its rack unit in some cabins, and it may be on the cabin cover externally in some cabins.


    Thank you for your answer, but how is the expert entry that you wrote done? Could the person who built the robot have set any password for expert login?

    A friend of mine got a job at a new factory in a city far from me. There's a Kuka VKRC2 robot. there is a 7th axis, and it moves on a sled. This sled wants to lengthen its length, it has no mechanical problems, but how to make a change in the robot software "limit and so on", it does not know. Since the robots I'm dealing with are always Fanuc, I don't even have a single idea about it. For me, what is difficult is probably very easy for Puppet masters...