My Requests

Qinsy

How-to Remote Display Client

General

A Remote Display Client (Client Controller) process receives settings (computations, current line, steered node, etc.), raw data and positioning results over a TCP/IP network from a Socket Server running under the Controller on an online pc.
This document will give an explanation on how to set up the connection between a Socket Server and Remote Display Clients.

A Remote Display Client can set up independent displays, but cannot change online settings without special permission.

For detailed information about certain settings please check the inline Help by pressing the F1 button on your keyboard.

On this page:

Network setup

Important

This document presumes that the TCP/IP protocol is properly installed and a suitable IP addresses are defined.
Computers must belong to the same subnet mask and must be communicating with each other over the network.

Make sure that all PC's are logged into the domain or that they are all part of the same work group to prevent problems with file sharing. 

When the PC's are all part of the same work group please make sure that the user profiles are present on all the PC's.

Set the IP address and Subnet mask; for example…

The IP addresses of the remote QINSy computers on the bridge, ROV, client, etc. are all set in the same way.
By setting the submask 255.255.255.0 the IP addresses on these computers can be 192.168.1.X.
X must be a different number ranging between 1 - 254.

Qinsy

The Socket Server is part of the Qinsy Controller, and is automatically installed with Qinsy.

Remote Display Client Add-on

The Socket Server option is only available for use if the Qinsy Remote Display Client Add-on module has been purchased and enabled on the current dongle being used on the Server PC.

  • This can be checked in the License Manager
  • The number of clients is unlimited

The Remote Display Computers do not need a dongle in order to visualize the data sent from the Socket Server.

Install Qinsy on all the concerning computers and add the "Remote Display Controller" icon to the Qinsy Console.

  • Since 8.18.2 you'll get a popup for the License Manager which you can ignore
  • You might get another popup, but this only appears when you have never made a dongle selection on that PC before.
    You can close this one as well.
    • In 8.18.2 you can do this by right clicking on the Console icon in the Windows Taskbar:
    • From 8.18.3 you can close it as shown below:


  • Create a New local project or copy a project onto the remote PC and open it.

Important

Do not use a mapped (network) drive of the project on the Online PC and do not select the project on the Qinsy Online PC, both will cause problems with the project file and can corrupt your Template Database.

All computers should have the same Qinsy version installed as installed on the Qinsy Socket Server computer.
Computers with a different version installed will not work as Remote Display Computer.

Check the Qinsy Console to see which version is installed by selecting "Help" from the menu bar and then "About Console".
The version is displayed as "Version 9.xx.x".


Communication

The communication is protocol TCP for the socket server and the socket clients.

The listening Ports you select in the socket server are split into Port and Port+1 (Yellow Rx and Tx). On these ports Socket Server will listen and the initial connection will be established and then they will be offloaded to individual Rx and Tx ports per client, selected by the operating system. The selected ports cannot be influenced by the QINSy Socket Server. The operating system will automatically select free available ports.    

Please make sure that the selected Port and Port+1 have access through your firewall for the selected IP range and that all ports created by the SocketServer.exe will have access through the firewall.  


Setting up the Socket Server

  1. The Socket Server is started from the computer that acts as server.
    Start an online session by opening the Qinsy Controller.
    Go to "Options" on the menu bar and select "Socket Server".



  2. Select "Settings" on the menu bar of the Socket Server and then "Socket Server".
    In this dialog the listening port for the remote computers is set, the Default value is 2010.

  3. Select "Settings" from the menu bar and then "Output Settings".
    In this dialog a selection can be made of items that will be sent to the Remote Display Clients. 


    Shared Folders

    Even when the 'Share project folder with clients' check box is checked, it is advisable to follow the steps below to manually create a share.

    Remote access

    When the Remote Display Client needs to have the ability to control Qinsy from his computer, make sure that the Qinsy project folder on the Socket Server computer is shared and that it can be accessed via the network using Windows Explorer.


    When running Windows 8 / 8.1 and up you need to share your project folder to allow the Remote PC's to use the Online used Active Sounding Grid file:



    Remote access

    When the Remote Display Client needs to have the ability to control Qinsy from his computer, make sure that the Qinsy project folder on the Socket Server computer is shared and that it can be accessed via the network using Windows Explorer.


When everything is set up correctly and users are connected to the Socket Server it may look like this:

The Socket Server shows useful information of the clients that are connected, for instance the IP address and host name and the Qinsy version that is used by the client.

Setting up the Remote Display Client

  1. As mentioned before, on the Remote Display Client it is not necessary to have a Qinsy dongle inserted in the computer. 
  2. The PC requires a copy of your Qinsy project and should contain:
    1. Template Database file used on the Host PC (running the Socket Server).
    2. Background data required (DXF, QXF, QGF, ECW, etc.)
  3. Select the "Remote Display Controller" icon from the Qinsy Console.
    If the Icon is not available as shown before it must be added to the Console.
    Do this by right-clicking in the lower pane and selecting "Add/Remove QPS Programs".
  4. From the Remote Display Controller go to "Settings" on the menu bar and select "IP Address".
    In this dialog the IP address of the Socket Server Computer must be entered as well as the "Listening Port".
    Instead of an IP Address it is also possible to enter the Host Name. The Listening Port is also the same number as entered in the Socket Server.
    Enable the option "Enable Remote Control" in order to start and stop the recording from the Remote Client computer.
    This can only be enabled if it is enabled on the Socket Server.



  5. The Remote Display Controller should now show "Connected to server", but it will also show "Status", Fix number, Steered node, etc.
    When this is the case the connection is successful.

The user can now set up displays or open existing ones and, if enabled, line changes can be made as well as starting and stopping the recording.

The Remote Display Controller also shows useful information of the Socket Server, for instance the server IP address and the Qinsy version.

Questions & Answers


TopicAnswer/info
1Display options are grayed outIn case the display options are grayed out, it means that no "Steered node" data is sent. As soon as you are back in your MWLM, the options will be available again.
2No connection

In case the connection is not started it is most likely that there is a network problem.
Try to ping the Socket Server computer and see if there is a reply.
If not, please contact your network specialist.

Use off the shelf network cables to prevent strange network behavior due to wrong wiring.

3No grid data on remotes

Everything is working and you can reach the folders on the server PC, but you cannot see the sounding grid on the remotes.

It might be worth checking you network profile and if is set to:

  • Public
  • Private
  • Domain (Enterprise workplaces only)

Try setting it to Private, meaning that you are in a private network and PCs are easily discovered by other PCs.
For changes to take effect, Socket Server needs to be restarted.