collinsd70

MrPLC Member
  • Content count

    221
  • Joined

  • Last visited

Community Reputation

21 Excellent

1 Follower

About collinsd70

  • Rank
    Sparky

Profile Information

  • Country United Kingdom

Recent Profile Visitors

672 profile views
  1. Mitsubishi 2401 File set error Q2ASH

    Your very welcome. I find this normally happens for me during testing and changing of parameters, possible something is not deleted or cleared.   Regards Daniel.
  2. Sercos not connecting to Ultra3000

    Hi derrickjp7. Firstly welcome to the forum. SERCOS Phase 3 normally indicates a configuration error between your SERCOS Controller (Master) and the actual Slave configuration as you quite rightly stated. I would double check the configurations between configured and actual, I have attached a SERCOS Diagnostic PDF that was written for the 6000 Series; however the SERCOS Phasing is standard across all Modules. Check your firmware versions match- or atleast the "compatible" keyring section is chosen. If everything looks good- make sure all the configurations are downloaded and maybe give everything a power-cycle. Then see how far your phasing gets afterwards.   Regards Daniel SERCOS Troubleshooting.pdf
  3. faulted processor

    Because you are using the 300-Series I am going to assume you are using STEP 7. If you go to file --> open and choose your standard libraries, you can import OB121 from the Organization Blocks folder and paste into your blocks folder in your project tree. Once you have done this, you can highlight block (or in the block-view, type "OB121") then click the download icon to load the OB into your PLCs memory; this will prevent the PLC from "crashing". You then need the analyze the cause of the programming error using the diagnostic buffer you have mentioned previously.  If you want me to have a look at your program- please "archive" and attach via here or via PM. Regards Daniel.
  4. Mitsubishi 2401 File set error Q2ASH

    Have you tried a memory format? Then download again... Regards   Daniel
  5. faulted processor

    Hi Rompot. It looks like your PLC has crashed because of a programming error, to prevent the PLC going to stop mode- you need to insert OB121 (this is the called OB on the rising edge of a programming error). Then you will have a system error- but PLC is able to run as normal. The most recent error indicates an area length error when reading/ writing to DB262. This could be because of a pointer or something changing during runtime. In your diagnostic buffer you should be able to navigate to the problem with the button 'go to', hope this helps.     Regards Daniel
  6. IEC Developer and the AS-i interface

    Hi Colin. I have had brief experience with this module- and yes, it was programmed with the IEC Developer Package. I also have the A Series- Module on my test bench which I believe is very similar in terms of setup but haven't had time to test yet You will need the configuration package Configurator-AS, do you have this? Here is the link to the manual if you don't have it already....  http://dl.mitsubishielectric.com/dl/fa/document/manual/plc/sh080291e/sh080291eg.pdf   Regards   Daniel.  
  7. Allen Bradley

    Welcome Karthikeyan_cmps Im assuming here that your using RSLogix 5000/Studio 5000? If so, once you have configured your Input/ Output Device in the Controller Organiser- you simply need to follow the structure defined by the Slot Number. So lets say you have an Input Card in Slot 1. In your controller tags you will find a structure called (Local:1:I.Data) inside this all bits will be mapped and updated every scan. If you need to Monitor Input 0 On Slot 1 ---> Local:1:I.Data.0 is the tag you need.       Regards Daniel        
  8. comms Error

    Have you tried swapping the cables between HMIs to see if the fault moves? If your happy your software and configuration is correct, you need to try substituting components to try and narrow down the cause of the fault.     Regards Daniel
  9. comms Error

    Are you running through an ethernet switch? If so- connect to the switch with your laptop and ensure you can ping both the PLC and the HMI. If this is all good, might be worth a power cycle incase one of the ethernet ports has been closed.   Regards Daniel
  10. Hi Joe. Have done this on the 'bay', all other items are USA-based but everytine I list automation parts like these, they never sell or get any interest. Have also tried selling some Mitsy stuff and some Siemens Failsafe Modules (all as far as im aware; heavily underpriced). Never seem to get any bites.   Regards Daniel
  11. Can any one help me

    Hi mshifa. Firstly welcome to the forum. My initial guess is that you have the wrong Input Address in your program? Can you double check the input address matches your physically wired input? If this is all OK maybe check your voltage supply, it may be sufficient to illuminate the LED but not necessarily enough to close the input relay. Otherwise please attach your code and maybe a photo of your wiring..   Regards Daniel
  12. Hi Olyn. See attached a 6 Element FIFO for the REAL Data Type. Instructions 1. Import the AOI into your Project. 2. Create an Instance in either Global or Local Memory. 3. Load the AOI into your Selected Routine, Connect the Clearall Boolean and the REAL which will load to the FIFO.(the REAL is loaded when it changes value). Note the Clearall is an IO Parameter so will be passed through the AOI and reset once all buffers are emptied. 4. oFIFO_Pos will tell you the location of the most recent Variable (to be used for an Arrow on a HMI for example) I have confirmed operation on Emulate5000 and all seems to work correctly. This AOI will load and store 6 Variables only, do not attempt to change the array sizes, if you do; you may crash the PLC.     Regards   Daniel. AOI_6FIFO_REAL.L5X
  13. How many REALs do you wish to store in this FIFO? What version of RSLogix500/Studio5000 are you using? I will have to customise the AOI to your requirement.     Regards   Daniel
  14. Exceed maximum step size

    Hi Arnoldzw   It seems you are in a very difficult position. At this point in time; I would consider which is most cost effective 1. The time it will take you reengineer this code, test and debug or 2. Bite the bullet and buy a PLC with suitable step size. You will have to play around with languages to work out which translates into less steps.   Regards   Daniel
  15. Exceed maximum step size

    Hi Arnoldzw. Unfortunatley there is no simple way to reduce this significantly; you may be able to use different instructions/ functions to reduce your step size, however the only significant way to reduce this is to use a different language such as simple/ structured ladder etc. Normally with a Mitsubishi system; the code would be designed and coded before buying the necessary hardware- this way you can approximate the number of steps so that you can then choose an appropriate CPU. You also should ensure you have a spare number of steps to accommodate the online change facility if this is something you wish to do during your comissioning stages. Ultimatley; your most cost effective measure will probably be to buy a bigger CPU.   Regards Daniel