First Steps. After the successful installation, the following Window appears: The MicroBrowser is able to display - All Web-HMI which are designed with SpiderControl PC HMI Editor or an OEM version of it - CODESYS WebVisu V2.3 - CODESYS WebVisu V3.x For all other content, the AutomationBrowser will use the integrated Chromium HTML5 Web-Client. When opening an URL, the AutomationBrowser will first analyze the HTML page and then open automatically either the MicroBrowser or Chromium (when in Auto Mode). Older SpiderControl HMI projects as well as the CODESYS Webvisu V2.3 used Java Applets, which are no longer supported in any Browser. The MicroBrowser is able to display these HMI without a Java VM by using a native implementation. CODESYS Webvisu V3.x can be visualized both with the MicroBrowser as well as with Chromium HTML5. The MicroBrowser offers better performance as well as other possibilities, so for this type of HMI the AutomationBrowser will open Chromium when in Auto-Mode or the MicroBrowser when forced to MicroBrowser Mode. When you display a newer HTML5 based SpiderControl HMI, the Auto mode will open the MicroBrowser, but you can force it to use Chromium by selecting the HTML5 mode. Enter Android Settings to modify IP Address and other network related parameters. This is useful when the AutomationBrowser is in Home Screen mode and the user has no access to other Apps. Full-screen is only used to remove the status bar in the top of the screen Immersive-Mode is used to remove both status bar and the task bar in the bottom of the screen (restore task bar with a swipe up from the bottom of the screen) This is only used in HTML 5 mode to show a control bar in the top of the screen, to navigate with previous and next buttons, to refresh the view or to come back in the home view - MicroBrowser: The view will automatically de re-scaled to fit the screen (isotropic, keep width/height ratio) - HTML 5: It's not really re-scaled on the view, since it depends on the HTML page. But it will activate an option of the WebView control to fit the screen. - MicroBrowser: enable/disable panning and zooming of the view. - HMTL 5: Unused, this option is handled in the HTML code - MicroBrowser: Improve the rendering with anti-alias if the device does not already support this feature in hardware accelerator. In most devices we don't need to activate this option. - HTML 5: Unused - MicroBrowser: Either show the Android Keypad to edit a value or use the Keypad/alphapad TEQ files - HTML 5: Unused Export station list in the into the Download/AutomationBrowser/MB_STATION.xml Scroll the menu list for more… Import station list from Download/AutomationBrowser/MB_STATION.xml PIN code is used to prevent any modification from operator user. The password is needed to change anything. This feature allows for locking up the operator panel to avoid a user to modify settings or to exit the App (‘Kiosk Mode) Close the menu The version that you have installed so far covers the basic functionality. If you need a customized behaviour, the AutomationBrowser can be extended with the SpiderPLC components. In the following, we present two examples of such extensions. If you have an application which could be solved using this approach, please contact us. The SpiderControl AutomationBrowser allows for a seamless navigation from a HTML5 Webvisu on a PLC to a web-cam which is linked directly with its H264 / rtsp:// URL (which is supported by almost any webcam). A fully customized user interface in the control panel offers the option of providing a self-contained, consistent operation. ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇.▇▇▇/watch?v=ohQA5tI2A8E The SpiderControl AutomationBrowser can be programmed with an integrated functional block logic to force a jump to a specific URL, to block the touch screen or to switch on/off the back light. The integrated SpiderPLC can be programmed with any standard Browser and connects to external PLC using standard protocols like OPC UA, Modbus, ISO-on-TCP and more. Like this, a Web-Panel can be used to display several Web-HMI's, but still be controlled by a connected PLC. ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇.▇▇▇/watch?v=2kIVhjvNuk8 Following questions are being asked often concerning the MicroBrowser CoDeSys. This most often has 2 possible causes:
Appears in 1 contract
Sources: License Agreement
First Steps. After the successful installation, the following Window appears: The MicroBrowser is able to display - All Web-HMI which are designed with SpiderControl PC HMI Editor or an OEM version of it - CODESYS WebVisu V2.3 - CODESYS WebVisu V3.x For all other content, the AutomationBrowser will use the integrated Chromium HTML5 Web-Client. When opening an URL, the AutomationBrowser will first analyze the HTML page and then open automatically either the MicroBrowser or Chromium (when in Auto Mode). Older SpiderControl HMI projects as well as the CODESYS Webvisu V2.3 used Java Applets, which are no longer supported in any Browser. The MicroBrowser is able to display these HMI without a Java VM by using a native implementation. CODESYS Webvisu V3.x can be visualized both with the MicroBrowser as well as with Chromium HTML5. The MicroBrowser offers better performance as well as other possibilities, so for this type of HMI the AutomationBrowser will open Chromium when in Auto-Mode or the MicroBrowser when forced to MicroBrowser Mode. When you display a newer HTML5 based SpiderControl HMI, the Auto mode will open the MicroBrowser, but you can force it to use Chromium by selecting the HTML5 mode. Enter Android Settings to modify IP Address and other network related parameters. This is useful when the AutomationBrowser is in Home Screen mode and the user has no access to other Apps. Full-screen is only used to remove the status bar in the top of the screen Immersive-Mode is used to remove both status bar and the task bar in the bottom of the screen (restore task bar with a swipe up from the bottom of the screen) This is only used in HTML 5 mode to show a control bar in the top of the screen, to navigate with previous and next buttons, to refresh the view or to come back in the home view - MicroBrowser: The view will automatically de re-scaled to fit the screen (isotropic, keep width/height ratio) - HTML 5: It's not really re-scaled on the view, since it depends on the HTML page. But it will activate an option of the WebView control to fit the screen. - MicroBrowser: enable/disable panning and zooming of the view. - HMTL 5: Unused, this option is handled in the HTML code - MicroBrowser: Improve the rendering with anti-alias if the device does not already support this feature in hardware accelerator. In most devices we don't need to activate this option. - HTML 5: Unused - MicroBrowser: Either show the Android Keypad to edit a value or use the Keypad/alphapad TEQ files - HTML 5: Unused Export station list in the into the Download/AutomationBrowser/MB_STATION.xml Scroll the menu list for more… Import station list from Download/AutomationBrowser/MB_STATION.xml PIN code is used to prevent any modification from operator user. The password is needed to change anything. This feature allows for locking up the operator panel to avoid a user to modify settings or to exit the App (‘Kiosk Mode) Close the menu The version that you have installed so far covers the basic functionality. If you need a customized behaviour, the AutomationBrowser can be extended with the SpiderPLC components. In the following, we present two examples of such extensions. If you have an application which could be solved using this approach, please contact us. The SpiderControl AutomationBrowser allows for a seamless navigation from a HTML5 Webvisu on a PLC to a web-cam which is linked directly with its H264 / rtsp:// URL (which is supported by almost any webcam). A fully customized user interface in the control panel offers the option of providing a self-contained, consistent operation. ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇.▇▇▇/watch?v=ohQA5tI2A8E The SpiderControl AutomationBrowser can be programmed with an integrated functional block logic to force a jump to a specific URL, to block the touch screen or to switch on/off the back light. The integrated SpiderPLC can be programmed with any standard Browser and connects to external PLC using standard protocols like OPC UA, Modbus, ISO-on-TCP and more. Like this, a Web-Panel can be used to display several Web-HMI's, but still be controlled by a connected PLC. ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇.▇▇▇/watch?v=2kIVhjvNuk8 Following questions The Automation Browser supports both http and https URL, with or without credentials. http://[user:password@]hostname/... https://[user:password@]hostname/... If credentials are being asked often concerning not specified in the URL and the server prompts for HTTP authentication, it will show an authentication dialog, to enter the username and password. If you choose "Save Password" in this dialog, it will still show the authentication dialog the next time, to allow the user to use the stored information or enter another username/password. If credentials are specified in the URL, the HTTP authentication dialog will not be displayed, unless the credentials are wrong. In that case, you will have to update or clear the credentials from the URL. If the server uses as untrusted SSL certificate or self-made certificate, the user will be prompted to accept it and continue loading the page, or not. Press YES (ALWAYS) to permanently save your choice. Press CLEAR DATA in the Android Settings of the app, to restore the default settings and clear all stored credentials. VNC URL is something like vnc://▇▇▇.▇▇▇.▇.▇▇▇/ vnc://hostname[:port]/[bpp[.depth]]/[password] Optional parameters: - port, default is 5900 - bpp is either 8, 16 (565) or 32 (888), 0 use default parameter from server - depth is optional and depends on the bpp. Supported values are 16.15 (555), 8.6 (64 colors) or 8.3 (8 colors) - password if need must be defined after the pixel format, to use default pixel format, use bpp 0 - If supported on the VNC server side, the best choice is 16 bpp (565), for example vnc://▇▇▇.▇▇▇.▇.▇/▇▇/▇▇▇▇▇▇▇▇ Notes: - A Floating Button is used to open and close the Android Keypad, - The Floating Button is visible only if Android Keypad option is enabled in the menu. - A long press on the Floating Button moves the button. - The Auto-Start in MicroBrowser CoDeSys. This most often has 2 possible causesmode is recommended to be used instead of Auto detection - If the connection is lost and the Auto Start is defined with a delay (3s or more), it will return to the countdown page rtsp://[user:password@]hostname/[live0][?caching=MILLISECONDS] Depending on the camera you will have to specify /live0, /live1, ... or something like that, after the hostname The optional network caching parameter in the rtsp URL, allows you to reduce the latency from the live stream, but may cause artifacts or refresh issues if the parameter is too short The default value is 200 ms, for example, to set 50 ms rtsp://▇▇▇.▇▇▇.▇.▇▇▇/▇▇▇▇▇?▇▇▇▇▇▇▇=▇▇ * Without countdown (start immediately)
Appears in 1 contract
Sources: License Agreement