I don’t know if it has any connection, but I’ll share my experience.
After updating to version 6.8, the visualization didn’t want to be displayed at all, even though everything else worked (SDM and webserver). I couldn’t find anything in the log that would be related to it. Since AR version 6.7, logging into SDM is new. I skipped 6.7 because there was a problem with auditing. But after changing the version, it doesn’t display an error (I didn’t see if there was a warning), but because it wasn’t filled in, mappView apparently didn’t load at all. PS: I only changed this and visu work now.
Please notice: SDM is not related to mapp View … SDM is a feature of Automation Runtime.
I know that they have implemented some sort of authentication, but I have no further details here.
It’s not problem of mappView, but the SDM is runtime thing. The problem is, when the SDM is opened in web browser on PC (I think, thats the main usage) and switch the tab (or I think, that’s problem with another window - so unactive webbrosing), the SDM logged me out. For example: when I want try to click on some winget in visu opened on PC and watch CPU usage, I change the tab, do the click and return to SDM, I am logged out and it need new log in (it’s take 30s and logout time is set to 30 min).
PS: I am using Firefox, Edge and Chrome
I did a quick test and this is caused by the browsers performance saving features.
If I disable “sleeping tabs” functionality, either by excluding the server address or completely turning off the “sleeping tabs” functionality I am not logged out of the SDM.
Here is an example from the relevant settings in Edge.
Here I have edited “https://localhost” to “https://localhost_aaaa” to allow the “https://localhost/SDM” tab to sleep and after 30 seconds it enters a sleeping state and logs me out of SDM.
If I exclude “https://localhost” the browser tab does not sleep and SDM does not log me out. Same functionality if I disable the putting tabs to sleep functionality completely.
Sleeping browser tabs can also cause mapp View to reload the page if the tab has been sleeping.
I can confirm this.
This leaves us with edge as the only viable option for SDM as the settings can be adjusted per URL?
I don’t know a single website that ends the session when the tab is paused / in background - therefore this sounds more like a problem B&R should solve and not the customer / enduser.
Has somebody opened a ticket?
To avoid a site from being deactivated, add it to your “Always keep these sites active” exclusion list.
On your computer, open Chrome.
At the top right, select More > Settings.
On the left, select Performance.
To the right of “Always keep these sites active,” select Add.
From here there are 2 options:
Add current sites: Select from available sites that are currently open in a tab.
Select the box to the left of the site you want to add, and click Add.
To go back, select Cancel.
Add sites manually
Enter the web address.
Select Add.
To go back, select Cancel.
Tip: The web address format for the manual site exclusion policy is: [scheme://][.]host[:port][/path][@query].
Here are some examples of how to add sites manually if you want to create an exclusion for:
Entire domains and subdomains: Exclude the URL scheme. For example, google.com matches and prevents deactivation of subdomains like drive.google.com and calendar.google.com.
Specific domains, but not any subdomains: Include a dot (.) before the URL host. For example, .google.com won’t match and prevent deactivation of subdomains like www.google.com, drive.google.com, and calendar.google.com.
Specific subdirectory: Include the URL path. For example, www.google.com/finance matches and prevents deactivation of all Google Finance pages, but won’t prevent deactivation of the www.google.com main pages.
URL host and query components: Asterisks (*) can be used as wildcards. For example, https://* matches and prevents deactivation of all https sites and youtube.com/watch?v=* matches and prevents deactivation of YouTube videos.
Wildcards for prefix, suffix, or substring matches of the URL host component aren’t supported. For example, *oogle.com or google.com/* won’t match and prevent deactivation.
