Veganic

MrPLC Member
  • Content count

    471
  • Joined

  • Last visited

Posts posted by Veganic


  1. The counter method might not be looping because you are not resetting it?

    There are internal pulses at 1sec and 1 min, M8013 and M8014 respectively.

    Use C1 to display time accumulated in seconds
    
      M1   M8013
    --| |--|^|---------------------------[C1 K3600]--
    
      C1
    --| |----------------------------+---[ALT M2]---
                                     |
                                     +---[RST C1]--
    
      M1     M2
    --| |-+-| |----------------------------(Motor 1)-
          | M2
          +-|\|----------------------------(Motor 2)-

     

    OR

    Use C1 to display time accumulated in Minutes
    
      M1   M8014
    --| |--|^|---------------------------[C1 K60]--
    
      C1
    --| |----------------------------+---[ALT M2]---
                                     |
                                     +---[RST C1]--
    
      M1     M2
    --| |-+-| |----------------------------(Motor 1)-
          | M2
          +-|\|----------------------------(Motor 2)-

     

    I don't know what the accuracy will be over time and also worth checking it is not 59 or 61 minutes.

     


  2. I know you have a solution but there is a different way:

    You can use a "Part" - Select a word part display after creating your parts.  Hopefully it is then fairly simple but let us know if you have any questions.

     


  3. @MarkusR   Thanks for the tips, I will try them when I get to site.

     

    @Gambit    That demo program seems to be out of date but it does seem to work better than the "improved" version.

    I have finally got something working in the simulator. I had to add a unicode text input box on the screen and the operator had to enter the new name before pressing the rename button.

    All obvious to anyone who has actually written the code - the rest of the world not so much.  I don't have this kind a problem with those Beijers units.


  4. I'll certainly give it a try. Thanks.

     

     

    Edit: scanning the pdf, that version seems to use scripts and window screens none of which are created in my version.  I thought all this was in the operating system now? 

    I'll have a look later.


  5. I an testing the GOT built in recipe funtion to see if the recent improvements make it useable.

     

    My first problem is that I have created a "recipe record list" but the "rename record" button does nothing. Also I can delete the record but then it forever remains nameless.

    Where did I go wrong?


  6. My understanding s the -P502 the same module but with access to port 502 for modbus communication.

    I don't know if the -P502 will work in place of the standard unit but if you have one there is no harm in giving it a go.

     

    Edit: All the details are in the help file with the function blocks - it used the MC protocol.


  7. Ethernet:

    FX3u-ENET units.

    Search for the  EthernetFX3MC_GW2_V100 function blocks in MyMitsubishi for all the information.

     

    Other options:

    CC link - limited to 32 words I think but expandable if you send in batches.  CC link is rock solid and easy to program.

    Use data exchange in an HMI.  Slow but simple and adds other functionality - you may have one already.

     

    Edit: I will say that the Mitsubishi approach to Ethernet on the older stuff can seem overly complicated - I sometimes just strip out the couple of lines of code that will do the job for testing or for non-critical operations.


  8. 6 hours ago, Gambit said:

    I always found the iX series to be kinda slow. But I tried the first few versions so that might be it.

    What is better about them in your opinion? 

     

    @Gambit  the answer to that is a whole new thread.    There are pros and cons for each.

    @PeteW1959   The first questions that come to me are:

    1. How many messages do you need to display at once?

    2. Look at the alarm function and see if that is of use.  It seems to be just what you need.

    There other options but you'll find them once you get started.

     


  9. There are lots of trick to reduce your program size but I would suggest changing the CPU as already recommended.

    The problem is too general to give any meaningful help.

    Hints would be:

    - look at the program structure -  use "for next" loops for example.

    - Load the program into the plc, or at least half of it. Upload a raw ladder - see how the function block bloat the program.

    - Look at your addressing and see if index registers can help.

    -You can then go deeper and look for repeated snippets of code.

    Your program will probably end up being completely unreadable and if it does fit in the plc it will leave no room for expansion.

     

     

    1 person likes this