Skip to content

Programming in PLCNext Engineer feedback

dpionkdpionk
edited February 2021 in PLCnext Engineer

This is my first project with using PLCNext and I selected it for that fact that I could use the datalogger or code with it to create my own sort of SCADA system and store data.  My trouble is that I am using the PLCNext to program the actual functions of the machine using ladder logic.  It's painful. 

When you copy a chunk of rungs to duplicate in the same networks to reuse the "Code_Networks" do not declare them selves as a unique identifier. Am I missing something with this just because I do not know the software well enough?

When you change the variables in the table being used in the declaration the code does not update with the change and you have to manually go to the code and change it everywhere it is used. 

The view from left rung to right rung does not fit without having to scroll unless you zoom out to a helicopter view.  Is there a way to change this? 

I have tried to circumvent the code network problem, and view by creating a new code section.  However the additional code pages added have a completely different layout, feel, and display than that of the original.  

I am just feeling like everything is way more difficult than it needs to be, meaning that it is taking me more time.  I am familiar with programming in many different PLC programs and manufactures, ie. Allen Bradley, Siemens, Automation Direct, Omron, Mitsubishi, Fanuc, I could go on.

 

Are my struggles due to ignorance?  Any help would be appreciated.

 

Thank you.

 

Comments

  • Rob HRob H

    I share your views about the NOLD editor. I find it frustrating and usually avoid using it which is unfortunate because that style of logic is most familiar to me and easiest to debug. 

    Have you given ST and LD a chance? I find it much easier to write programs in those styles, but will admit it's a paradigm shift coming from traditional ladder. It's also harder to debug online because it doesn't highlight the true logic paths in LD like it does in NOLD. 

    There is a new refactor option in 2021.0 that allows you to rename a variable and all its references. That is a much appreciated new feature. 

     

  • Carsten PLCnext TeamCarsten PLCnext Team

    Dear dpionk, dear Rob,

    thanks a lot for your open feedback. 
    Some of your points are not new to us and we try to put more convenience to the PLCnext Engineer by offering such functionalities like "refactoring".
    The refactoring feature is developed further for future versions, so you’re not restricted to rename the instances, we will also offer to refacture the datatype, comments and every other property.

    Another example is, that we will implement the automatic creation of new instances of copied code in graphical editors. So one of your major topics should be solved with that. 

    But also I can feel that some of your points are more related to knowledge and I think you need a short introduction for some of the really good editor features we have. 
    I hope one of the colleagues from the US have already tried to contact you to guide you a little bit.

    Only to give an example for some points which are solved already:
    The width of the Network oriented Editor can be adjusted in the options of the PLCnext Engineer. There you can switch between an unlimited width, or a fixed width with an amount of objects. 

     

    If you have further questions or feedback, don’t hesitate to contact us directly or share it here in the forum and we will notice it and take care of it.

    Best regards

    Carsten Weber. 

    Product Management - Software

Sign In or Register to comment.