In this section you can find Support resources of Ubiquity that may be useful to newbie or expert programmers when looking for answers to commonly asked questions or specific Downloads available from the section at the bottom of the page.

FAQ - Download

Quick search FAQ

Show all answers
Hide all answers
  • Is there an Ubiquity getting started guide?

    Yes, certainly!

    You can get the quick guide from the following link.


  • Which are the minimum connectivity requirements for Ubiquity Control Center and Ubiquity Runtime?

    Both Control Center and Runtime components use outgoing Internet connections, they never use incoming ones.


    You need at least one TCP port 80 or 443 open, or as an alternative the TCP port 5935.

    In case the IT manager requires to block the internet browsing, the HTTP (80) and HTTPs (443) ports may be closed, while Ubiquity connectivity is ensured throught the outgoing TCP port 5935.

    When available the use of outgoing UDP ports (80, 443 or 5935) this can improve performances. Availability check of UDP ports is automatically done. In case no UDP ports are available, the condition is reported in Control Center with a sign (warning triangle) where the condition is located (Control Center o Runtime side).

    Please note that missing UDP connectivity does not introduce any functional limitation.

  • The network bridge did not succeed to be created. How can I fix it?

    You could occasionally get the following error when trying to bridge two Ethernet adapters.

    This could be related to several reasons: 

    Make sure the Ethernet adapters you want to bridge are not shared. 

    Make sure you have the netbrdgm.inf under c:\windows\INF.

    If you cannot find it, download it here

    Additionally, the WMI component (Windows Management Instrumentation) could be corrupted or missing. This can cause the advanced settings panel to look like this:

    First check that the “Windows Management Instrumentation”' service is running.

    To do the diagnostic, run the WMI diagnostic tool, you can get from Microsoft here: www.microsoft.com/download/en/details.aspx. 

    If the tool detects problems, you can try and repair the WMI component: 

    open a command window (start > cmd.exe) 

    type "net stop winmgmt" 

    type "cd %windir%\system32\wbem" 

    type "ren repository repository.old" (or alternatively delete it) 

    type "net start winmgmt"

    For some Win32 systems with embedded operating systems, it may happen that the problems in creating bridge are due to missing network layer components from the original image of the operating system.

    The cases analyzed where solved by technical support using some additional files.

    Download the files, un zip them and copy the contents to the following folders:

    inf => c:\windows\inf

    sys => c:\windows\system32\drivers

    Restart the system and try to create the bridge again.

    Note: the use of the suggested files is at your own risk. ASEM is not being responsible for the proper use of the above procedure. This FAQ just shares the results of some success intervention done on some 3rd part systems, but it cannot be in any way assumed as general solution valid for any case.

  • How much is the data traffic generated by Ubiquity to keep the connection with the server infrastructure?

    When Ubiquity Control Center, Ubiquity Runtime or Ubiquity Router are connected to the server infrastructure without ANY active assistance session, they use about 60KB/hour (1,4MB/day) for the keep alive activity.

  • I have a system with just one Ethernet interface. How do I configure Ubiquity Runtime to get Internet access and VPN access to the autoamtion sub-network?

    Ubiquity Runtime fully supports the case in which the host system has only one single Ethernet interface.

    In this case the interface will be used for both Internet access and VPN access to the automation sub-network.

    The two sub-networks, Internet access and LAN, could be logically separated, but this is not a requirement.

    All the information about how to configure the VPN are reported in the Control Center on-line manual in the following chapters:

    Runtime\Configuring the VPN\ VPN to the entire remote subnet with 1 Ethernet adapter

    Note: Ubiquity Control Center can be downloaded from the following page on the asem.it web site:


  • Si veda la FAQ "Come posso cambiare il Dominio di appartenenza di un dispositivo?" per informazioni su come cambiare l'associazione tra un dispositivo ed un Dominio.

    At the first time Ubiquity Runtime connects to the Server Infrastructure, it shows on its interface, a device ID and a password.

    The code shown is unique for the device (related to the hardware).

    The association between the device and the Domain is done from Control Center.

    From Control Center, in the “Devices” view click on the icon at the bottom called “Add new device”.

    Enter in the proper fields the codes shown on the Runtime and click “Add”.

    Once the link between the device and the Domain has been established, the codes will disappear from the Runtime interface.

    The new device is added to the Domain with the name “<No name>” and can be renamed at any time by an Administrator user.

    See the FAQ “How to move a device from a Domain to another one” for additional information about how to change the Domain to which a certain device has been associated to.


  • How can I change the Domain to which I have associated a Device?

    Each Ubiquity Runtime device requires being associated to a Domain in order to be reached for assistance.

    To associate a Device to a Domain, please see the FAQ “How do I associate a Device with Ubiquity Runtime to my Domain?”.

    The association between a device and a Domain can be changed freely at any time by the user.

    To remove a device from a Domain is enough you log-on to the Domain with an “Administrator” type user, identify the device to remove and use the “Remove from Domain” command accessible form the icon just above the tree view, or the “Delete” command accessible from the mouse right click context menu, or the “Del” button of the keyboard after you have selected with a single click the device you want to remove.


    Once removed, the Runtime interface will show again the ID and password required for a new association to a different Domain. 

  • Which is the differnece between the "association" of a device to a Domain and the Runtime license registration?

    The association (link) between the Ubiquity Runtime and the Domain is a “link” required to get access to the device for the remote assistance activity.

    The association between the device and the Domain can be freely changed at any time. See the FAQ “How can I change the Domain to which I have associated a Device?” for further information.

    The registration of the Ubiquity License (25 chars code) corresponds to the activation of a “link” between the software license (“token”) and a certain specific physical device.

    The “token” can be moved from one device to another one a limited number of times (two) using the proper procedure form Control Center. See the FAQ “Is it possible to move the Ubiquity Runtime License from one device to an other one?” for further information.

  • Is it possible to move the Ubiquity Runtime License from one device to an other one?

    Ubiquity Runtime is the platform component that stays on the remote device to which you connect for the assistance and the VPN.

    Depending on the license type, you may get access to different features. 

    Ubiquity Runtime is subject to activation by means of a software license code (25 characters).

    The activation of a certain license code is valid for a certain device and it can be moved to another one a limited number of times (two). The Ubiquity Server Infrastructure keeps track of the licenses movements.

    You can think the Ubiquity Runtime license as a “token” which is saved on a certain device and can be moved to another one, not more than two times.

    The license registration procedure is explained in the Control Center on-line help in the following chapter:

    Note: Ubiquity Control Center can be downloaded from the following page on the asem.it web site:


    Note: all ASEM systems delivered with Ubiquity pre-loaded (because of ordering or because included by default) are pre-configured and the license is already activated.

    To move the license is first required to execute the “Unregister”.

    The “Unregister” command is available in the details screen on the right side of the device view once you have highlighted the device name from the tree.

    Note: before executing the “Unregister” it is suggested to keep note of the License number so you can use it later for the new registration. It is possible to select the number and copy to clipboard directly from the details view:


  • How do I configure the SMS alarms' notification on the RM routers?

    The Ubiquity Routers of the RM family include the Premium HMI Runtime, hence the configuration of the alarms and related notification shall be made using Premium HMI Studio by making an HMI project with desired features.

    The SMS notification upon Alarms' events are supported ONLY by RM11 systems (devices with integrated modem). The RM10 systems only support the email notification.

    The RM11 systems are pre-configured for the use of the integrated modem to delivery SMS and no additional configuration through Alarm Dispatecher is required. The "Gsm modem SMS" plug-in is already properly configured.

    The Premium HMI project shall simply include the users configuration with mobile telephone number associated.

    For each threshold that should be notfied ou will need to specify the user (or users) to which the notification should be delivered and the status change to be notified.

    For additional information please refer to the Premium HMI user manual, chapter "Alarm Threshold Event Notification Properties".

  • How can I configure the RM Routers to manage an incoming SMS and provide an answer to the sender?

    The RM Ubiquity routers are able to manage the reception and interpretation of an SMS content sent to the SIM cards used by the modem, when these messages do not contain the keywords used by Ubiquity for connection management.

    In order to notify the PHMI application of the arrival of a text message and later allowing the extraction of its contents, you can use the the following system variables:

    SmsTimeStamp - SmsMsgText - SmsPhoneNumber


    The description of each single variable is available in the PHMI documentation in the "System variable" chapter.

    An example of how to use the variables is available from the following link.

    The sample project uses an event to notify the PHMI application upon SMS arrival and a script to extract the text information from the message.

    Note: the incoming SMS managing is supported starting from Ubiquity 6 and Premium HMI v4.0.1152.16





Download - FAQ

User login

Enter your username and password here in order to log in on the website: