collinsd70

MrPLC Member
  • Content count

    264
  • Joined

  • Last visited

Everything posted by collinsd70

  1. 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).  
  2. 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.  
  3. 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?
  4. 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.
  5. 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).
  6. 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.  
  7. 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 .
  8. 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.
  9. Thanks Ken- very useful to know.
  10. Hi All. Im currently developing a machine program from 2 previous machines- this means im integrating routines from both projects including standard and motion logic. My question however is- 1 program is scanning its motion tasks on a preset cyclical value- whereas the other motion program is not set with any priority. I have worked on programs before (mainly Mitsubishi) where we used fixed priority and scan times to ensure no high speed signals werent missed (like encoders for example). Would anyone be able to give me some advice with regards to the motion tasks? What are the advantages/ disadvantages?
  11. Latch Data of PLC Mitsubishi Q03UDE

    When powering off the PLC without a battery- you have approximatley 3 minutes before the standard ROM capactors will completley discharge..
  12. SERCOS II ---> Ethernet/IP.

    Innoloe.   I completely agree with you- however it does list with some variables; what the evuivalent is in the Ethernet/IP Protocol. There are some variables used in the CIP_Drive that do not have an equivalent in the other protocol and vice versa.
  13. Hi All. I have been tasked with engineering a new PLC program urgently. My employer has given me a week to convert an original piece of code that ran Motion Control across SERCOS II- now onto the Kinetix 2000 Series via Ethernet/ IP (also a pneumatic drill will now be an additional servo axis) Having a quick look through the code- my main concern is the conversion of the variables that were originally on the SERCOS II DUT ("AXIS_SERVO_DRIVE") and now are using the variables in the "AXIS_CIP_DRIVE" DUT (Ethernet/IP). The variables between these 2 are not identical so this leaves a lot of uncompiled tags. The main tags that do not compile include configuration words, actual velocity and other important tags that currently handle the motion logic in the main routines. My main question is- Is there an official conversion manual or guide on which variables can be used as a replacement between the 2 data unit types?, I have seen on the AB forum that similar questions are being asked but doesnt seem to be any straight forward replies. Considering I have "1 week" to convert all these tags, create a new motion group with necessary logic for another servo, adjust the IO tags and complete the HMI develpment for this machine- this seems like a lot to take on.   Thanks in advance.     Dan.          
  14. TIA Portal V13 Assign Profinet Device name

    bagged2drag. If you have the MAC-Address you can use the PST Too from Siemens Automation (Primary Set up tool). This is the tool I use to initially configure all nodes on my Profinet networks. Confirm you have the correct MAC Address before applying an IP Address and node name. If you have an issue with the AnyBus card- you may need to restore factory defaults before carrying out the method above.
  15. SERCOS II ---> Ethernet/IP.

    See attached file if anyone needs this info. AXIS_SERVO to CIP_DRIVE.pdf
  16. Retentive DATA for Mitsubishi Q00J

    I have tested this on the Q00JCPU before and can confirm it works- In GX Developer/ IEC Developer proceed as follows. -Double click on your CPU. -Locate the 'Device' tab. -Look for the data type you require (in your case the D Registers). -Across the row there will be a 'start' and 'end', so in your situation you would start with '0' and complete the end of your range as required. There are 2 fields you can adjust (the later CPUs can clear the 2nd range with the Latch Clear switch). So you can use either. -Complete the form- 'check' then 'end'. -Download the parameters to the PLC. -To test this works- open your data entry monitor and write a value into D0. -Reboot the PLC (either powercycle or PLC Reset). -Check the contents of the Register D0 have been retained.   An alternative to setting these static ranges- Is to use 'R' registers or 'ZR' Registers (increased memory range and may not be available for the Q00J).
  17. Hi Joe. Yes I did but didnt realise I could do this- I had AB on the phone earlier and they supplied a pack of add-on profiles which cured my revision issue. Many Thanks.
  18. Hi All. Does anyone has a copy of this EDS file?. Ive been into AB's EDS Database  but it doesn't exist (latest revision is 10.001). Unfortunately when I roll back the EDS in my configuration to 10.001- I get a load of errors in my code as the UDT structure changes. (43 errors). Drive P/N is: 20BC015A0AYNANC0   Thanks in advance.  
  19. Protecting Source- GX IEC

    Does anyone know if it is possible to protect source FB's (ST and Ladder) in GX IEC Developer 7.01/7.04? I have spent a lot of time engineering FB's that will be used in multiple instances and I would like to protect this code from being modified/adjusted.
  20. Q06H CPU Failure

    Bought a new Q33B rack today and went to test operation with one of my spare CPUs. Unfortunatley it seems my CPU no longer works (I tested the rack with another CPU after and all OK). The CPU was working fine last time I used it. Has anyone attempted to repair/ fault find on these units? I think theres is a problem with the main 5v circuit as there is no indication on the unit at all (no lights etc). 
  21. Start Ladder Logic Test

    You need to install 'GX-Simulator'
  22. Running out of memory on the Q03UDE

    Skidbladnir. Just a thought- might be worth formatting your standard memory then reloading your program. I've had memory problems before where I've overwritten 'parts' of code during different projects instead of starting fresh.
  23. Problem with ET200M on PROFINET network

    As Jimmy mentioned..try clearing your system data blocks, then recompile all.
  24. Just a side note- as per Crossbows comment, MODSOFT is Dos Based and can only run on anything previous to Windows XP.  I used Serial cables in ProWorx NXT without any issues.
  25. Regarding the software..you should be able to open this via MODSOFT or ProWorxNXT. There is a application in the ProWorx directory that will convert your code from a number of file extensions. Accessing the CPU could be done via Modbus or Modbus Plus- I built a serial cable myself that I used to engineer code on the 484 and Quantum platforms. If you want me to take a look at opening/ converting your code. Feel free to give me a PM.