• Replies 4 replies
  • Subscribers 585 subscribers
  • Views 191 views
  • Users 0 members are here
Options
Related

Offline tags show as online

Vin

I am converting an old V6.1 Citect application to 2018R2 and have a few questions which are probably all related.  When I run the converted application on the server while it is not connected to the PLC, objects on the screen initially show in red with the flashing grid pattern indicating that the server is offline from the PLC.  This behavior makes sense.  However, after about 15 seconds they all go green and the offline grid pattern disappears the way it should if the server was connected and communicating fine with the PLC.  However, there is no PLC connected and I am trying to figure out why this is happening.  Under Topology/I/O Devices, Memory is not set to true. 

If I run the Citect Kernel and view Drivers, it says no drivers configured. If I view I/O devices, it says no unit statistics available as this is not an IO server.  The 2 drivers that the application uses are MODNET and UNITE.  If I connect a Modbus simulator, then the data shows correctly in the application so it is communicating using the configured MODNET driver.  Is there something that perhaps did not get converted over during the migration that is causing this behavior? 

Is there something else one needs to do in 2018R2 to show tags as being bad in runtime when offline from the PLC?  Would appreciate and help or suggestions.

 Thanks.

Parents

  • It sounds like you are running in multi-process mode (selected in the Computer Setup Wizard). That is fine, however, it means that each process (client, alarm, report, trend, I/O, etc) runs in a separate Windows process and has its own Kernel window. If you open the Kernel from the graphics page in the runtime, then you're only viewing the client's kernel. Go to the Runtime Manager in the system tray (by the clock). You can right-click the I/O Server process and choose Kernel to see the communications pages you wanted.

    Also, make sure you run the Computer Setup Wizard and verify that the computer is set to run as a server, connected to the cluster you created when you upgraded the project.

Reply

  • It sounds like you are running in multi-process mode (selected in the Computer Setup Wizard). That is fine, however, it means that each process (client, alarm, report, trend, I/O, etc) runs in a separate Windows process and has its own Kernel window. If you open the Kernel from the graphics page in the runtime, then you're only viewing the client's kernel. Go to the Runtime Manager in the system tray (by the clock). You can right-click the I/O Server process and choose Kernel to see the communications pages you wanted.

    Also, make sure you run the Computer Setup Wizard and verify that the computer is set to run as a server, connected to the cluster you created when you upgraded the project.

Children
  • in reply to Eric Black

    Thanks Eric. I am starting the Kernel using Kernel=1 under [debug] in Citect.ini.  When I right click on any of the tasks including IOServer1 n runtime manager. the only options I get are Restart. Stop and Dump Kernel.  Dump kernel dumps the contents of the kernel some place but does not show me the Kernel with details on the I/O devices.  What am I missing?

  • in reply to Vin

    [Debug]Menu=1 adds the kernel to the Alt-Spacebar menu in the runtime and to the right-click menu in the Runtime Manager. That parameter is set automatically if you select 'Kernel on menu' in the Computer Setup Wizard (custom mode).

    If you dump the kernel with the DumpKernel() or ServerDumpKernel() command, you can specify what things to dump and whether to use verbose mode. I believe there's also a parameter to control how many items from each table to dump (max). However, viewing the kernel pages from the Kernel window is probably easier.

  • in reply to Eric Black

    Thanks, adding it via the setup wizard and also selecting the menu option which by default was off seems to have done the trick.  Now I do get the Kernel option when I right click on the IOServer task in runtime and can pull up details on the I/O device comms.

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