Menu

Snap7: Exception: CLI : function refused by CPU after TIA PORTAL update

GloriaG
2020-11-19
2020-11-20
  • GloriaG

    GloriaG - 2020-11-19

    We have an application with a Raspberry pi using SNAP7 and a S7-1214. The
    application was workin smoothly but the PLC was programmed in TIA PORTAL
    V13.0 (wich is not compatible with new versions of TIA PORTAL). So we have
    proceed to update this using the following steps:
    1-We've created a new proyect with the PLC in TIA PORTAL V13 and uploaded
    the software from the PLC
    2- Upload the TIA PORTAL from V13 to V13 SP2 and then to V16.
    3-We reseted the PLC to factory settings and downloaded the software from
    TIA PORTAL V16.
    4- We checked the I/O addresses configuration to ensure they hadn't changed.

    (this worked almost smoothly just describing the process for your better
    understanding)
    The rest of the system is working smoothly, but after this the raspberry pi
    is not working and returning: Snap7: Exception: CLI : function refused by
    CPU.
    The main solutions given to this problems in different forums are:
    -Check access level to "full" and allow GET/PUT communication check. This is
    propperly setted up.
    -It might be a firmware incompatibility. The firmware has not change during
    this operation, so I guess if it was working before, it should work now.
    Can you offer any other bit of information about what might be the problem
    here?
    Any advice will be wellcome.
    Regards

    Gloria García
    Ingeniera de Software

    Ctra. de Córdoba, Km 429
    Complejo El Rey
    E-18230 Atarfe GRANADA - SPAIN
    Tel.: +34 958 439 200
    Ext:1241
    ggarcia@atarfil.com
    www.atarfil.com
    Responsabilidad Medioambiental: No lo imprimas si no lo necesitas
    Environmental Awareness: Do not print it if you do not need to
    Aviso Legal: Este mensaje y sus anexos pueden contener información
    confidencial, por lo que se informa de que su uso no autorizado está
    prohibido por la ley. Si usted no es el destinatario pretendido por el
    remitente, por favor póngalo en su conocimiento por esta misma vía o por
    cualquier otro medio y elimine esta comunicación y los anexos de su
    sistema, sin copiar, remitir o revelar los contenidos del mismo a cualquier
    otra persona. Cualquier información, opinión, conclusión, recomendación,
    etc. contenida en el presente mensaje no relacionada con la actividad
    empresarial Atarfil S.L. y/o emitida por persona sin capacidad para ello,
    deberá considerarse como no proporcionada ni aprobada por la empresa.
    Atarfil S.L. pone los medios a su alcance para garantizar la seguridad y
    ausencia de errores en la correspondencia electrónica, pero no puede
    asegurar la inexistencia de virus o la no alteración de los documentos
    transmitidos electrónicamente, por lo que declina cualquier responsabilidad
    a este respecto.
    Disclaimer: This message and its contents may contain confidential
    information and its non-authorised use is prohibited by law. If you are not
    the intended recipient of this email, please advise the sender of the fact
    using the same, or other, means and delete this message and its contents
    from your system without copying, forwarding or revealing the contents of
    the message to any other person. Any information, opinion, conclusion,
    recommendation, etc. contained in this message and which is unrelated to the
    business activity of Atarfil S.L. and/or issued by unauthorised personnel,
    shall be considered unapproved by the company. Atarfil S.L. implements
    control measures to ensure, as far as possible, the security and reliability
    of all its electronic correspondence. However, the company does not
    guarantee that emails are virus-free or that documents have not be altered
    and takes no responsibility in this respect.

     
  • Davide Nardella

    Davide Nardella - 2020-11-19

    The only reasons for the CLI : function refused are the permissiond and the optimized DBs.
    We use Snap7 currently with TIA 16 without problems.

    1 - Set the priviledges and the GET/PUT permission and then DOWNLOAD THE HW CONFIGURATION into the CPU.
    2- Set the DB as not optimized and DOWNLOAD IT into the PLC.

    Let me know.

     
  • GloriaG

    GloriaG - 2020-11-20

    This was properly configured when we were having the problem.
    However, We are not using a DB for the Tags that need to be read or write, we are using the PLC tag s table. So, they have a fixed memory addresses and we are accesing them from the snap 7 referencing them as DB0.

     
  • Davide Nardella

    Davide Nardella - 2020-11-20

    Sounds strange to me that you want to read DB0.
    I just tried with a small CPU (1511F) and it answers Function refused.
    I dont' know CPU 1214 but, are you sure that it worked before ?

    To read PLC TAGs you should use ReadArea passing S7AreaMK (0x83) as Area.

     
  • GloriaG

    GloriaG - 2020-11-20

    Yes, I am certain that it was fully working before,
    We are trying to use the PLC TAGs because we are reading the inputs from an I/O card wich have addreses such as (%I0.0). And it made sense to have all the variables gruped in the same place.

    We are using the read_area with differents Areas acording to the memory type (0x81 to read inputs (%I)), (0x82 to read outputs %Q) and (0x83 for directions that are %M)

     
  • GloriaG

    GloriaG - 2020-11-20

    Yes, I am certain that it was fully working before,
    We are trying to use the PLC TAGs because we are reading the inputs from an I/O card wich have addreses such as (%I0.0). And it made sense to have all the variables gruped in the same place.

    We are using the read_area with differents Areas acording to the memory type (0x81 to read inputs (%I)), (0x82 to read outputs %Q) and (0x83 for directions that are %M)

     
  • GloriaG

    GloriaG - 2020-11-20

    Solved the issue, (apparently) I unchecked the GET PUT bit, downloaded the configuration and then checked the GET PUT bit again, then it started working.

    Thank you.

     

Log in to post a comment.