# Display SICK on TP600

**URL:** <https://www.wago.community/t/display-sick-on-tp600/966>\
**Category:** Hardware and Linux\
**Tags:** tp600\
**Created:** [May 17, 2024, 9:21am UTC](https://www.wago.community/t/display-sick-on-tp600/966 "2024-05-17T09:21:32Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Damkjaer](https://avatars.discourse-cdn.com/v4/letter/d/e9c0ed/32.png) [@Damkjaer](https://www.wago.community/u/Damkjaer)\
**Post date:** [May 17, 2024, 9:21am UTC](https://www.wago.community/t/display-sick-on-tp600/966/1 "2024-05-17T09:21:32Z")

</div>

Hi, I am currently working on trying to get a TP600 to display the GUI from a SICK visionary t mini.  
When trying to open the GUI it keeps loading forever as if some javascript or other part of the GUI requires more than the TP600 is capable of providing.  
I’ve also tried to open the GUI through a PLC using the browser element, but this results in a message saying that the request was blocked by the server.

My question is if anyone has experienced something similar and know a workaround to this problem.

 ![Blocked](https://us1.discourse-cdn.com/flex016/uploads/wago/original/1X/b340d5c8fd9455fd922842db556431b8e04752ac.jpeg)

---

<div class="post-metadata">

**Author:** ![quenorha](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/quenorha/32/429_2.png) [@quenorha](https://www.wago.community/u/quenorha)\
**Post date:** [May 17, 2024, 9:57am UTC](https://www.wago.community/t/display-sick-on-tp600/966/2 "2024-05-17T09:57:54Z")

</div>

You can display the Touch Panels 600 web browser development tools in order to find what’s wrong.

To activate debug mode on the Touch Panels 600 integrated browser, it must be started with the “ **-remote-debugging-port** ” option.  
To do this, connect to the screen via SSH (e.g. Putty).  
Edit the “ **/etc/script/start\_webbrowser.sh** ” file using the nano editor (make a backup copy beforehand)

> cp /etc/script/start\_webbrowser.sh /etc/script/start\_webbrowser.sh.save

> nano /etc/script/start\_webbrowser.sh

Replace the line

> /usr/bin/webenginebrowser $URL &

with the following content:

> /usr/bin/webenginebrowser $URL --remote-debugging-port=1080 &

It is also necessary to be able to view the various tabs in order to switch from the development tab to the page to be analyzed.  
Edit the “ **/etc/specific/webengine/webengine.conf** ” file using the nano editor (make a backup copy beforehand)

> cp /etc/specific/webengine/webengine.conf etc/specific/webengine/webengine.conf.save

> nano /etc/specific/webengine/webengine.conf

And edit the various properties as follows:

> tabbar=1  
> zoom=0  
> navbar=1  
> menubar=0

After these changes, reboot the screen

> sync reboot

It is now possible to execute the following command to display the development tools tab.

> echo newtab=[http://127.0.0.1:1080](http://127.0.0.1:1080) \> /dev/webenginebrowser

In the development tab, select the page to be analyzed.  
You might check the console.

---

<div class="post-metadata">

**Author:** ![Damkjaer](https://avatars.discourse-cdn.com/v4/letter/d/e9c0ed/32.png) [@Damkjaer](https://www.wago.community/u/Damkjaer)\
**Post date:** [May 17, 2024, 11:07am UTC](https://www.wago.community/t/display-sick-on-tp600/966/3 "2024-05-17T11:07:06Z")

</div>

Thank you for your reply.

Trying to open the page directly from the TP doesnt provide much as far as i understand. But using the browser element within a 750-8212 PFC200 gives a security violations. Do you know if it is possible to ignore the security policy or use a different method to show the GUI?

 ![PLCConsole](https://us1.discourse-cdn.com/flex016/uploads/wago/original/1X/918af7c2898bbca4b969cf6dceb26b49033cd927.jpeg)

---

<div class="post-metadata">

**Author:** ![quenorha](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/quenorha/32/429_2.png) [@quenorha](https://www.wago.community/u/quenorha)\
**Post date:** [May 17, 2024, 11:18am UTC](https://www.wago.community/t/display-sick-on-tp600/966/4 "2024-05-17T11:18:35Z")

</div>

Is the page you’re trying to open a CODESYS webvisu ?

Could you show the configuration you have made in the browser favorites of the TP600 ?

---

<div class="post-metadata">

**Author:** ![Damkjaer](https://avatars.discourse-cdn.com/v4/letter/d/e9c0ed/32.png) [@Damkjaer](https://www.wago.community/u/Damkjaer)\
**Post date:** [May 17, 2024, 11:24am UTC](https://www.wago.community/t/display-sick-on-tp600/966/5 "2024-05-17T11:24:40Z")

</div>

Yes, it is webvisu. The PFC has a browser element pointing towards the webserver of the camera.

 ![Favorites](https://us1.discourse-cdn.com/flex016/uploads/wago/original/1X/4cfec8711656e4bcc7368807473dbec7ad20c9a8.png)

---

<div class="post-metadata">

**Author:** ![quenorha](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/quenorha/32/429_2.png) [@quenorha](https://www.wago.community/u/quenorha)\
**Post date:** [May 17, 2024, 11:26am UTC](https://www.wago.community/t/display-sick-on-tp600/966/6 "2024-05-17T11:26:36Z")

</div>

OK understood, didn’t read properly your first question.  
You’ll find some hints how to change the security policy of the lighttpd webserver (not really good for security)  
You might try to add a favorite to the camera itself first to see if it worksfine.

> [@Display grafana-web-page inside webvisu](https://www.wago.community/t/display-grafana-web-page-inside-webvisu/346/2):
>
> Hi @schweichichi, For security reason embedding webpage in another is by default disabled. To allow embedding, you can modify the grafana config file, but it looks more convenient to do it using an environment variable, so you can add the following parameter to your docker run command : -e "GF\_SECURITY\_ALLOW\_EMBEDDING=true" -e "GF\_AUTH\_ANONYMOUS\_ENABLED=true" The first allow embedding and the second disable the authentication, this is probably what you want to consider. Also you …
