Jobbe9000

MrPLC Member
  • Content count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Jobbe9000

  • Rank
    Newbie

Profile Information

  • Country Denmark
  1. 1756-EN2F

    Hi, There should be 3 rotarty switches in the top of the module to determine the IP address. if they are set between 001..254 the module will use 192.168.1.xxx (rotary switch address). If you wish to use an address outside the 192.168.1.xxx range, then the switches needs to be set outside that area (and also not 888). Use the BootP or RSLinx to configure and disable the BOOTP/DHCP mode, otherwise the module will not save the assigned address.
  2. Removing Coordinated Motion Task

    Hi Dan,   It is hard to tell without having seen the program, but the motion instructions for coordinated motion, usually takes the "cordinate system" as a parameter. If you make a backup of the project and delete the coordinate system, you should be able to compile the whole project and you will get an error from the compiler everwhere the coordinate system is used.    
  3. Kinetix 6000 registration input using existing sensor

    Not beeing an expert on the 6000 series, but you should be able to just connect the common (pin15) on the Kinetix 6000 with the 24VDC power supply common for your CLX inputs. Then pull a wire from where the sensor is currently connected to the CLX input and to the IO registration Pin on the Kinetix 6000. If its just for testing purposes then that should do it...
  4. Kinetex 5500 Servo Drive Vertical Load

    The "MechanicalBrakeEngageDelay" parameter determins the amount of time that the servo drive should keep torque on the motor while the mechanical brake engages. It does not determin how much time the mechanical brake actually uses to engage. You should raise the time, ive heard somewhere that most mechanical brakes in AB servoes uses about 200-250ms to engage. Try to raise the engage delay time.  
  5. MATC_recovery

    Hi, First of all you have to remember that working with cam profiles is always done incremental, and that is why it always seem to start from zero. I suspect that you use the MAS or MSO to "Pause" the axis? And that you use the STO (Safe torque off) either with CIPSafety or hardwired? When the STO is activated the drive issues a MSO by itsself, which is simalar to issuing an MAS instruction to stop all movements, gearings, cams etc. and this brakes the link between the time master and your axis.   There are 2 ways to solve this problem: If you want to continue using a time cam, you will have to do some math and scale your time cam before starting it after an E-stop. This can however be very tricky if the axis is working together with other axes.   The (in my oppinion) better and more safe way to do this, is by looking into virtual axis and position cam. A virtual axis is not affected directly by STO because it as the name suggests, does only exist in virtually and cant cause any danger in the real World. The way that you would handle this, is to create a virtual master, and a virtual axis excatly matching your physical axis in settings, scaling etc. Then use a MAG instruction to gear the physical axis to the virtual axis. before excecuting the cam profile. In case of an E-stop, you will stop the virtual master and the other virtual axis and the physical axis will stop together with the master axis. Once the axes are stopped by a controlled stop, you can activate the STO function on the physical axis, which will only brake the gearing to the virtual axis.. the virtual axis is still linked in a cam profile with the virtual master axis. Once the E-stop has been reestablished, you are able to gear the physical axis back to the virtual axis and start the virtual master again.   I hope it makes sense and that you will figure it out.