• State Not Answered
  • Replies 4 replies
  • Subscribers 583 subscribers
  • Views 2391 views
  • Users 0 members are here
Options
Related

Lock page functions in secondary screen using multi monitor.

Fredric Johansson

Hi, ive upgraded a project to 2023R2 and it uses multimonitor, previously its popolated ith Cicode and display pages on the main screen and alarm list on the secondary screen.

So i created screen profiles and configurated it the same, it opens as expected but, when i use "go to page" in the alarm list its displayed on the alarm screen wich i dont want. Is it possible to redirect so all page functions appears in the "main screen"?

  • 0

    Hi  

    It's possible to redirect page navigation so that all page functions (like "go to page" from the alarm list) display on the main screen while keeping the alarm list on the secondary screen. Since you're using screen profiles in 2023R2, the default behavior allows independent navigation per window/monitor, which is why pages now open on the active screen (the secondary one in this case). To override this and force pages to open on the main screen, you'll need to customize the Cicode behind the navigation trigger using window control functions. This is probably a bit too involved to answer within a forum post, but you could reach out to AVEVA Technical Support for further assistance if you get stuck.

    Here is some psuedo cicode which could work, but I have not tested:

    FUNCTION MyPageDisplay(STRING sPage)
    INT iCurrentWin = WinNumber(); // Save current active window (e.g., secondary/alarm)
    INT iMainWin = 1; // Or WinNumber("Main") if you named it
    WinGoto(iMainWin); // Activate main window
    PageDisplay(sPage); // Display the page on now-active main window
    WinGoto(iCurrentWin); // Optional: Return focus to original window (alarm screen)
    END
    So you would replace the existing "PageDisplay" calls in your template or page navigation, with this custom page "MyPageDisplay" function.
    Let us know how you get on.
    Kind regards
    Olivier
  • 0

    Hi Frederic,

    If your migrated project is using equipment, and you took advantage of the Workspace as well as screen profiles, then this can be achieved quite easily:

    • Master Page 1 -> Has a Content Pane (default one does). Make sure it supports all the Content Types you want: Content Types
    • Make sure all your content pages (mimics) have been assigned a content type: Assign a Content Type to a Page
    • Make sure all your equipment, that trigger alarms, have been assigned a home page in the Page field of the equipment: Add Equipment Using Equipment Editor
    • Master Page 2 -> Design this as your dedicated Alarm Page.
    • Assign each Master page to a screen in your screen profile.

    When the user selects to "Navigate" from an Alarm in the Alarm Page, it will use an internal navigate function to work out what equipment the alarm belongs to, then what the "home" page is of that equipment, and then it will display it automatically in a pane of your master page(s) that supports its Content Type. In this case the Content pane of Master Page 1. See Autofill.

  • 0 in reply to Bradley

    Hi Bradley, thanks for your help, but unfortunately we hanvent implemented equipments, and its a quite large project with about 8000 pages or so.

  • 0 in reply to Olivier

    Hi Olivier, yes i suspected it would come to someting like that, its similar to how it was built in teh previous version, i will give it a try.