collinsd70

MrPLC Member
  • Content count

    40
  • Joined

  • Last visited

Community Reputation

1 Neutral

About collinsd70

  • Rank
    Sparky

Profile Information

  • Country United Kingdom
  1. Removing Coordinated Motion Task

    Thanks Jobbe9000. I have had a better look now- removing the globals COORDINATE_SYSTEM and followed through errors. I now need to instruct the motion axes individually and reassign all calculated "angles" that the Cartesian was driving to.
  2. Removing Coordinated Motion Task

    Hi All. I have been given a new program to engineer- the original code used 2 axis in a Cartesian co-ordinate system to allow for different angles of drilling. All done via Kinetix 2K on SERCOS II These axis are now to be individually isolated- and the angle is adjusted by the operator now. I need to remove the coordinated motion group- if I just simply "delete" this- do I need to be weary of anything else? Are there any dedicated coordinated motion instructions that need removing/ adjusting?     Thanks   Dan.
  3. qj71mb91

    Babyblue10   According to the QJ71MB91 User Manual- your start request is sent via Bit 5 so at starting X/Y 0000- your address will be Y4. See the attached diagram which shows your process flow and signals to analyse.       Cheers.
  4. Kinetix 300 Hard Limits

    I am using Kinetix 350’s... The firmwae version is very low (v2.xx I believe) so may explain why I dont have the functionality to disable/ enable these. The machine is being shipped Friday wired as is- but thanks to everyone for their feedback.
  5. Debugging Local O: Data

    This problem was caused by logic in different cyclic priorities handling the same Boolean.....was very hard to find (thanks to the Trending facility for helping me debug this).  
  6. Debugging Local O: Data

    Hi Joe. Yes I completely agree that it was most likely being controlled from another part of the program- however the system is now fully commissioned and this problem no longer seems to exist This project was developed from a "standard" piece of code (I use the word "standard" very loosely)- and thus; have spent about 80% of my time (roughly 4 weeks) debugging lots of different problems in this piece of code rather than improving my motion logic; written for drilling control.  
  7. Extended File Registers

    In GX IEC Developer there is the option in ‘Device Edit’ to export any range of MELSEC variables to a .csv file. You could do this (export)..make the parameter change- then write back in?
  8. Q02H USB DRIVER

    Korona. I have had this issue before- are you installing on 64bit OS? I have 2 different copies of the MELSEC USB driver and sometimes I have to switch between them when installing in different VMs. Sometimes I have also had to go through the ‘have disk’ option and install that way.
  9. qj71mb91

    If you are referring to ‘starting’ the Modbus TCP card after a powercycle... This can be started via the utility or via the User Program. I dont know about the Modbus cards but normally the start request in an Intelligent Module (32 bit) is the first output bit of the slot number- so for example if your card is in slot 0- then your start request signal will be Y0 (you can also analyse the inputs X0-X1F for module state before sending the start request).
  10. Debugging Local O: Data

    Joe E. Thanks for your response- I had a theory that the output bit may at some point have been latched before the logic was shuffled/ deleted. So I simply toggled the bit and now it stays in a low state. The flickering output however; I will have to do some tracing with the trend graphs.  
  11. q03ude and shifting lots of bits

    From memory in GX IEC developer- there is SHL_E and SHR_E, both of which can shift a 16-bit word or integer .
  12. Kinetix 300 Hard Limits

    Hi Ken. Thanks for your response- I tried both settings and both seem to stop the drive completley- ie no MSO can be executed. I have been unable to find any further information on this- so I think the hard limits will just be permanently wired high.
  13. Debugging Local O: Data

    Hi All. I have a wierd bug in my program, my logic includes 2 routines that pass a tagname directly to and from Input and Output addresses (ie the "Local Data") The problem I have is 2 of these outputs are being set- even though the logic doesnt appear to ve driving them. I have cross checked these and also checked there are no other tags using the same aliases. 1 output is permanently high, whilst the other is flashing so fast I have had to disconnect it from a spare solenoid. Does anyone have any further ideas what could be driving these?
  14. Kinetix 300 Hard Limits

    Hi All. Does anyone know if the Hardware Overtravel Limits on the Kinetix 300 can be disabled? The only option I have in Studio/RS Logix 5000 is to generate alarm only or Stop Drive. For now I have bridged the signals high permanently and I have soft limits configured in my parameters. I was able to disable hard limits for the Kinetix 2000 but this option doesn’t seem to be available for the 300’s
  15. Fixed Cyclic Execution of Motion Tasks

    Thanks Ken- very useful to know.