Posts by panic mode

    i do not miss it all, this is dangerous. i remember returning from lunch and not checking the mode. colleague was using T2 and did not change it back. after casually enabling drives and trying to jog, robot moved suddenly and nearly crashed into some equipment there. if it moved the other way, i could be hit before having time to react.

    I have 3 robots where the gates need to be closed to move in T2.

    That is implementation detail. Default is that robot does not care about state of operator safety input while in manual mode (T1/T2). Also older KSS even allowed jogging while in T2. Newer KSS do not allow that so in T2 one can only test programs while operator safety doors are open - jogging is no longer possible.

    Integrator may choose to disallow use of T2. Common option is to simply turn off T2 mode. In older KSS if selecting T2 is still possible (since all hardware is still there, just the option is disabled in software), robot would simply display T1 and act accordingly.

    sounds like a user to me... :D

    either the KRC did not finish writing files (files not closed properly or usb stick was not ejected properly before removal)


    there is something on your computer that removes the file(s), perhaps antivirus...

    and if you want to program robots, do not just look AT file icons. look INSIDE files if you want to see what is going on. use another machine to verify that files are there and in correct format. for example after you remove USB stick from KRC... you COULD connect the stick right back to that same KRC and look inside files. if all ok then you know that files disappear WHEN you connect USB drive to your computer.

    you can also confirm that by generating new program module on the robot. in fact that is what you should definitely do first to establish baseline for your robot programs. they contain other things (based on installed options) that are on your robot. those things end up in both SRC and DAT files (check INI fold for example)

    SRC file has structure

    DEF program_name()
    ; blah blah

    DAT file structure is

    DEFDAT program_name
    ; blah blah

    notice that DEF/END are used in SRC, while DEFDAT/ENDDAT are used in the DAT file

    also notice that after module name there are parenthesis but - only in SRC file...!

    sorry, i was distracted and missed the part about program selection.

    i am not sure what is going on there. if you are using EXT mode then all control need to be external. if you press stop on smartPad, you will stop the robot but this is abnormal and will require recovery.

    you did not clarify the key issues:

    1. how is the CELL program selected? according to your SPS, there is no related logic inside LOOP. there is a default AUTOEXT INIT before LOOP but this only works once the SPS is started if robot is in EXT mode. that means most likely case (and still unconfirmed) is that CELL is selected manually by operator.

    2. where is your code? i see nothing that uses stop button. at which line is program when you need to press STOP button on the smartpad?

    CELL.SRC is just a name of the program module. you can call it CEL666.SRC if you like or DELETE_ME.SRC or WHATEVER.SRC.

    question is how the program module is selected. if this is done by code in submit (rather than by operator), then you just need to adapt submit to match actual file name of so called "cell" module.

    to answer any program code related questions, program code should be made available.

    They don't....

    Ratio does not change, it is a fixed gearbox, not automatic transmission. Axis is sized so that max torque, max speed and max power are never exceeded. You always work with less than axis is capabke of, it is just that at some times you may approach one of the limits. And if you not only approach but actually reach or exceed it, something is supposed to sense it and respond. Usually with a fault message.

    Motor can reach some max speed... Or max torque... Or max power. But not all at the same time...!

    Max speed is possible when there is no load. Great but not very useful. We need robot to move some load

    Adding load reduces possible acceleration rate. Also may also reduce max speed as a consequence of limited motor power.

    And when said load is sufficiently large, axis will no longer be able to move at all. This is stall condition. In this case motor produces the maximum torque and the speed is - zero. Also bot useful to waste energy to not move. We want robot to move, not act as a statue.

    How you want axis to behave will determine type of control. This could be position control, or speed control or torque control..

    You can control one thing only. Others are limits at best...

    You cannot control both positions and speed for example as they are contradictory.

    In most cases axis is using position control. If you tell axis m to some position, it will do so... If possible.

    Motion planner generates setpoints that axis follows. Or at least tries ...

    To ensure desired response PID loop is used. Actually it is often only PI loop - this may not be as capable as PID but it us inherently stable.

    So motion planner tells drive what speed limit and target position are, the drive does the rest.