• State Not Answered
  • Replies 5 replies
  • Subscribers 584 subscribers
  • Views 354 views
  • Users 0 members are here
Options
Related

Writing values to devices using Modbus issue, roles and profile issue

Mohamed Almansy

Hello all, I have an issue when writing to devices using MODBUS, if I am using my configured profile and not citect.ini profile and the user that is signed in runtime was not the admin, runtime do not write values to devices on the network, but if I just signed in using the admin user in runtime, everything works fine and the values are being written to devices on network, but if I use the default citect.ini file, all users write values to Modbus devices and everything works fine.

note that, 1- I am not using any privileges, 2- I have no write roles on the tags I am trying to write on, 3- I had compared the citect.ini profile parameters and my profile parameters, the two are having some differences of course, but nothing seems to affect the writing on devices operation or role settings.

Parents Reply Children
  • 0 in reply to Mohamed Almansy

     Hi  ,

    It appears to be configuration related. 

    • Windows or Plant SCADA authentication is used in your system?
    • How the profile is created? (should be created via Topology | Profiles in Plant SCADA Studio).
    • Have you used Configurator to set up the target machine?
    • Are you using Deployment?

    Take a look at [Client] section of the profile where it should have the following parameters

    • Clusters = [your clusters separated by comma]
    • ComputerRole = 1 (for control client and 2 for view only client)
    • PartOfTrustedNetwork = 1

    Hope the info here is helpful.

    ~Jacky

  • 0 in reply to Jacky Lang

     

    - I am using plant SCADA Authentication, Plant SCADA Authentication is  my issue (should be signed in in runtime with any user ,[not necessarily  admin user], to be able to write values to Modbus).

    - The profile is created using the topology yes.

    - yes I have used the configurator and configured my settings.

    - yes I am using the machine as a deployment server.

    - the client parameters are all configured as you described, but we are still facing the issue.

    I will attach photos for settings that are related to my issue, I wish this will help you troubleshoot.

  • 0 in reply to Mohamed Almansy

    Take a look at the messages logging in syslog of the client process after you use the admin user and non-admin user respectively. Hope the log would report some useful info to narrow down the issue.

© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.