Skip to content

using an Input to trigger a move of a real number.

edited December 2020 in PLCnext Engineer

I am trying to move a real number value into a register, the value changes as we hit different limit switches.

I have done this before in Siemens TIA porta using the move command triggered by my limit switch inputs with a different value when the different limit switches are activated

the move function here does not have a trigger input , how can I preform this function without it?

 

Comments

  • Hi Paul,

    In PLCnext Engineer version 2021.0, you can add an EN (enable) input to any Function, like the MOVE function. From memory, you can right-click on the MOVE block instance and add the EN input from the menu. You can search the Help system for more information on the EN/ENO feature.

    Hope this helps.

  • when will PLCnext Engineer version 2021.0 be available?

     

  • Hi Paul,

    version 2021.0 is available now, and it already has a Hotfix release - so the current version is 2021.0.1.

    You can download the installer from our website:

    https://phoenixcontact.com/product/1046008

    (click on the "Downloads" tab under the picture, then scroll down to the "Software" section)

    ~ Martin.

  • thank you , totally solved my problem.

     

  • You could also solve your issue by using ST code.

    A small function block could be the ticket here. Also a nice way to start working with ST coding.

     

    Peter Paul

  • Hello,

    the EN / ENO functions are now implemented (2021.0.1). Unfortunately, the values ​​are always shifted whether True or False is applied to the EN.

    Does anyone have the same experience?

    Thanks.

    calamario

     

  • Hi calamario,

    The behaviour when EN = FALSE is described in the PLCnext Engineer help system:

    2021 01 29 13 35 53

    Does this explain what you are seeing?

    ~ Martin.

  • Martin / Calamario

     

    I think the issue is that even if the EN input is false, the move function will move the default value for the data type into the output variable (as per what you highlighted). This can lead to the scenario below:

     

    Screenshot 

    As you can see:

    • The EN input on the first move = TRUE, which moves 29 into Value1.
    • However the EN input is FALSE on the second move, so this move actually moves a 0 into Value 1
    • Therefore the end result is the variable Value1 = 0.

    This seems counter intuitive to me, I would expect no logic to be triggered on any output variables, if EN = False and maybe just because that what I've seen in other PLC's. So the original value of the variable would be maintained.

     

    See below:

     

    Screenshot2

     

    Now I must admit, this observation is based on past experience, and not on any knowledge of defined standards. I think it's just something that will catch people out if they are not aware how EN/ ENO is handled by PLC Next.

  • Hi Andrew, I agree with you. In my experience with other IEC progamming software (mostly Simatic Manager and PC WORX), the EN output behaves differently to PLCnext Engineer.

    This is from PC WORX:

    2021 01 29 20 41 52

    I will give this feedback to the relevant product manager.

    ~ Martin.

  • Hi everybody,

    I had the same issue with the EN function, in my opinion this handled of the EN/ENO it´s not so useful. For to conditional manage not bool data type, I usually have to use ST.

    Thanks.

    Simon
  • Please note that the current EN/ENO feature on Functions, introduced in PLCnext Engineer version 2021.0, will not be available in version 2021.3.
    To continue using this feature, it will be necessary to use version 2021.0.x (i.e. version 2021.0 with or without a hotfix).

    (ref: 209518)
  • OK, but will it be impossible to do a move or another conditional operation with a non bool variable on graphic language? Somethig like the examples above.
  • The MOVE function (and all other functions) will remain, but in version 2021.3 it will not be possible to add the EN/ENO feature to the MOVE function (or to other functions).
    It will still be possible to do the equivalent of a conditional MOVE in an LD code sheet the same way as before, e.g. using a SEL block - see attachment.
    Like the MOVE function, that SEL example will work when MyVar and NewValue are the same type.
  • That SEL function would not work for what we want to do, for example, I have three sensors, according to which one is activated, I want to move a value to make a count or comparison or move a time, the sel function that will be last is the one that goes If the value is saved, if it is true, it will move that value(IN0), otherwise it will move the value it has in that last(IN1) SEL function. I do not understand how simple things Phoenix Contact complicates it. I also do not understand how they get the EN / ENO function, if one wants to make an account if a certain logic is given
  • That SEL function would not work for what we want to do, for example, I have three sensors, according to which one is activated, I want to move a value to make a count or comparison or move a time, the sel function that will be last is the one that goes If the value is saved, if it is true, it will move that value(IN0), otherwise it will move the value it has in that last(IN1) SEL function. I do not understand how simple things Phoenix Contact complicates it. I also do not understand how they get the EN / ENO function, if one wants to make an account if a certain logic is given
  • Hi Luciano,

    If you would like to reproduce the logic shown in your picture, and if I am reading that logic correctly, then you do not need to use the EN/ENO feature, or SEL blocks. In your picture, since the EN input on all the EQ blocks is always true, this is identical to the EQ block in PLCnext Engineer without an EN input.
  • Martín,
    I THINK THAT THE EXAMPLE I WAS NOT THE MOST CONVENIENT FOR YOU TO SEE WHAT THE MOVE FUNCTION IS VERY IMPORTANT WITH en / eno. THIS EXAMPLE IS WHAT I WOULD LIKE TO DO. In version 2021.0.1 the MOVE function did not work, in the latest version it does not allow me to use the instruction with EN / ENO
  • Hi Luciano,
    OK, that latest example is a common case where EN/ENO on the MOVE function would be useful.
    As discussed earlier in this thread:
    • The EN/ENO feature in version 2021.0.x did not work as expected.
    • The EN/ENO feature has been removed from version 2021.3.
    • In cases like the one you show, it is possible to use a SEL block to reproduce the behaviour of a MOVE block with EN/ENO, similar to this:
  • Hi Martin,

    I hope it is possible with the next version.
    I would suggest also to remove the help section of future version if it is not implemented or make a notice of it => I was starting out with the starter kit and version 2021.3 and it is really frustrating if the help section tricks you in searching for the checkbox for an hour :-).
  • That is a very good point, seafoxc. That section of the help should have been removed, or at least flagged with a version notice.
    I will raise this with the developers.
    There is currently no timeline for the re-introduction of the EN/ENO feature.
    Sorry for the trouble.
    ~ Martin.
Sign In or Register to comment.