Hello,
I updated C80 with:
- Linux image : 1.8.0
- Firmware : 1.4.0
With this firmware, there is a new section in PhysicalView CPU Configuration:
What is it for?
I didn’t find any information in Automation Studio Help.
Thank you
Hi @simone.lonardoni ,
I see the description of that Remote Access, under T80 section: AS Help 6 - Remote Access
What is it for?
You have, for example, mappView HMI running on C80 and you need to view the same visualization on your laptop for service purpose.
Ciao
Valerio
1 Like
Hi Valerio!
I had seen the description under T80 section.
I tried to configure it in both mode (WebGL and VNC), but I can’t connect.
Are there any other parameters to enable/configure?
Thank you
Hi @simone.lonardoni ,
unfortunately I don’t have a C80 with me so I can’t make any test, maybe someone else in the community can do that when they have time.
Let’s try to collect more information on your case and focus for example on WebGL.
-
Please tell us your ARs version:
Example:
-
C80 HW file, I think you already wrote 1.4.0.0 and I see it’s the latest one
- Which is your terminal firmware version? You can see that on SDM
-
Linux Image: you already told us is 1.8.0
-
Could you upload SystemDump and attach it to the post? Do you see some warnings/errors on the connection?
-
Could you make a screenshot of your ethernet configuration:
- C80 configuration:
- Screenshot of your mapp View Configuration: you should have at least 2 as “Maximal client connections“
9) Are there any other parameters to enable/configure?
I guess you have to enable the remote access, but unfortunately in the Help in one picture the access is enabled,
but in the note below the default settings is disabled, so please check on the service page which is your settings.
Thanks
Ciao
Valerio
Hi Valerio,
- ARs version:
- C80 HW file:
3. Terminal fw version:
4. Linux Image: 1.8.0
-
ETH config:
7. C80 config:
8. mappView config:
9. Enable remote access:
I didn’t find this page in the C80. I think this page is only for “T” series, right?
Thanks!
You are right, in the configuration view on T80 I see that option available:
so we are in the point where the documentation is not clear and we have to jump on scientific approach “try and see“, unfortunately I don’t have C80 with me I can’t help you.
In case you don’t have an update from the community in couple of days please call Support in Italy (Milano/Brescia/Padova/Bologna) and share with them the link of this post so they will not ask the same questions.
Ciao
Valerio
Thanks so much for your time!
Hi Simone,
unfortunately I can’t download your SystemDump, we can’t access to google drive:
Ciao
Valerio
Hi Valerio,
is it possible to upload files here?
Is there another recommended method?
Thanks
yes it’s possible, I see in other posts customers/colleagues did that
Thanks
Ciao
Valerio
1 Like
Hi @simone.lonardoni , unfortunately I can’t help you without a C80 and I don’t see comment from the community.
I called Support in Italy and they are waiting your call, please give them the link to this post so they see all data you already have provided.
Please update us when you find the cause of the problem.
I hope next time I’ll be more helpful.
Ciao
Valerio
Thanks so much Valerio! I’ll let you know.
unfortunately no solution from my side, nevertheless I would share my infos, maybe the’re interesting for the local support team.
I took your post as an opportunity for some self-learning, picked a C80 panel and setted it up (just an empty project, no mappView visu, updated it to the same versions as you use → TerminalOS 1.8.0, AR 6.5.1, HW upgrade 1.4.0.0, AS 6.5.0.306) and tried to get the remote access running.
But until now I fail, too.
I’m absolutely unsure if the following is really correct, but:
from my basic (network) understanding, if enabling the remote access you need additionally to set up a Destination NAT configuration to forward the remote access data packets into the Linux based TerminalOS (as the physical ETH interface is always assigned to AR).
So I tried to configure the ports 8080 (WebGL) and 8081 (websocket) via Destination NAT from “incoming at IF2 → forward to 192.168.37.2” (which is the ETHinternal TerminalOS IP address).
I tried similar with VNC remote access instead of WebGL (using the right ports there), and additionally with the developer tools port 9222 when using Web visu mode (this is used for remote debugging of the browsers content) as described in the PPC80 manual … unfortunately I failed in all three variants.
And as there’s no terminal configuration page in a C-panel (at least as I know), the only setup parameters are the ones in the AS project.
As I’ve done my basic tests inside the company LAN and with my company notebook (were some security restrictions are active in the network itself and on the device), I’m not sure if this has also an impact to my test setup, so I’ll try the setup again outside of the company infrastructure to be sure.
But right now, it looks like that it’s not that easy, and, for example, I’m missing some more settings I’m not aware of (most probably security settings, for example the by default disabled IP forwarding between the different ETH interfaces inside the PLC - I already tried there some different setup, but haven’t seen a difference, and from my understanding IP forwarding is only neccessary if doing IP routing, but I tried to use NAT which does not need IP routing as I know).
Long story short: I’m also struggling and have no more idea right now.
Please keep us updated with the findings of the local support team, many thanks in advance!
Best regards!
2 Likes
Thanks @alexander.hefner
I am waiting for answers from local support.
I’ll update you as soon as I have news.
1 Like
Hi,
I was able to make it work by enabling the NAT for Port 8080 and 8081 as well as activating IpForwarding on IF2 and IF3 of the C80.
After searching the web and using AI is seems like the NAT only resolves the adresses but is not able to forward the traffic. For that the IpForwarding is necessary.
Also the RemoteControl must be enabled by using the functionblock ArScreenEnableRemoteControl.
BR Fabian
2 Likes
Hi,
great, thanks!
I think in my case the missing function block call was the reason (I’ll test it but I’m confident it works then).
BG
Alex
Update: I can confirm that the function block call did the trick and it works now also on my side in all variants, of course for VNC remote access and remote debugging the appropriate destination NAT settings are additionally needed.
@simone.lonardoni, please see Fabians post above, he shared everything needed to get it running!
1 Like
I’m sure there is a reason (that I don’t know now) why on T80 we have on the configuration view in AS the option to enable/disable the Remote Access feature, and on C80 we have to call a Function block to do same.
Thanks so much Alex and Fabian for your help, please Simone update our local Support about the successful test made by Fabian.
Ciao
Valerio
@valerio.manenti, I think the additional function block call is mandatory for cyber security reasons, so that the operator of the machine can enable/disable it, not only the owner of the project source code.
BG Alex
PS: happy to meet you (again), even if it’s just in the forum 
1 Like
Hi,
it works!
My configuration is for VNC access.
- enable Remote Access with function “ArScreenEnableRemoteControl”:
- CPU Configuration:
NAT Configuration (with Terminal IP address of ETHInternal) and Terminal/Remote Access (put yours User and Password)
- ETH configuration:
enable “IpForwarding”
- ETHInternal configuration:
enable “IpForwarding”
And in the end:
Thank you so much at all of you for your time!
2 Likes