<< to CrossControl homepage

Support & Service Center

VNC server on CC displays

Printer-friendly versionPrinter-friendly versionPDF versionPDF version

Virtual Network Computing (VNC) allows someone to remotely view and control a computer, or in this case a display. Each of our CCpilot displays can be extended with a VNC server which means you may remotely connect and control the display from a VNC Client. The VNC server has been developed to be a standalone service, without use of Qt or other services.

Attached to this article are installation archives for each of our units. The ZIP-files contains the following:

  • Installation instructions (README)
  • Documentation (WORD)
  • Archive for installation on target

The different display units use the same general SW but needs some specific options to be able to handle the difference in screen sizes. The following options are available:

  • single-touch = only valid for our iMX5 units as they can only use single touch
  • touch-device = touch device to be used (Default: /dev/input/touchscreen0)
  • port = port number to connect to (Default: 5900)
  • passwd = password to view server data (Default: No passwd used)
  • viewonly = no input to server possible
  • verbose = turn on VNC server logging
  • x-scale = x-scaling for the unit (Default: 125)
  • y-scale = y-scaling for the unit (Default: 125)
  • invert = invert x/y scaling (only needed for CCP VC)
  • fps = number of fps (Default: 2)

To connect to the VNC server in the CC display you will need to start a VNC client/viewer on your remote device and connect to the CC display with the IP address. You should see the display screen mirrored on your VNC client and be able to control the display from the VNC client. The documentation shows how to use the VNC viewer in our virtual machine (LinX SW Suite v4).

Known limitations:

Startup delay

When auto starting the VNC viewer at reboot/power up, the touch drivers are not ready to be used. There is a need to add a delay to the startup script. Add the line "sleep 3" before starting the VNC server!


The VNC viewer used in our VM environment will show the screen contents of the VI2 rotated. And as the VI2 has no touch, it is not possible to control the screen contents.


The VNC viewer used in our VM environment will not show the screen contents of the X900, but the mouse presses will be translated as correct touches on the target. But you can’t see what changes on screen. This is due to some configuration in the X900.
Information about this will be added later.


For the iMX8-platform you need to use the vivante-driver (eglfs_viv) that uses the framebuffer to get "our" VNC server to work correctly. The document included in the ZIP will described this in more detail.


The XM2 Linux OS installation contains the service "x11vnc". The service works ok, if it is started from the command line in a terminal. If the service is added to autostart, the first connection from a VNC client works fine. But there is a problem to reconnect, if the client is closed and restarted. The session will then not reconnect.
Information about how to solve this will be added later.

Environment and Versions: 
LinX SW Suite v4