Welcome to Ubiqua Support

This page contains a list of questions and answers pertaining to particular topics. Please choose among the listed options to find your answer.


There are two versions available: "Standard" and "Evaluation".

The Standard version requires a subscription (monthly and annual options available), which also entitles you to receive software updates and online support.

The Evaluation version of Ubiqua is fully functional, but it is limited to 1,000 packet captures per session. The Evaluation version is valid for 7 days, after after which you may acquire a Standard version. Only one Evaluation license may be redeemed per user account.


Ubiqua Protocol Analyzer (or Ubiqua PA) is a monitoring and analysis tool created to help developers in the design and creation of wireless sensor networks. It provides a swift visualization, and a robust, efficient and reliable decoder for the most widely adopted protocols based on the IEEE 802.15.4 standard. Ubiqua PA provides analysis for several kinds of networks regardless of the number of devices operating; it supports multiple devices and capturing on multiple channels at the same time.

Please refer to the User Guide here to get the updated hardware and software requirements for Ubiqua.

If you have problems trying to start the installation process try this:

  • Make sure you are logged as an administrator.
  • Make sure the source and target directory aren't encrypted.
  • Make sure the installer is located in the local hard drive and not in a network drive.
  • If the Documents folder is located in a mapped drive, make sure the drive is online at the time of the installation.
  • Try installing the application with a different user.

After following the instructions above, if you still have problems installing Ubiqua, as a last resource please follow these steps.

  • Uninstall any previous version of Ubiqua (if any) by accessing Add/Remove Programs on the Windows Control Panel.
  • Download the latest version of Ubiqua installer.
  • Open the command prompt and change directory ("CD [download_path]") to where you have the Ubiqua Installer file.
  • In the command prompt, type (with the quotes):

msiexec /i "[installer_name].msi" /lvx "Ubiqua_Install.log"

Replace [installer_name] for the real name of the installation file. A log file will be written in the same directory where you have the Ubiqua Installer file.

Ubiqua communicates with most of the sniffer devices connected to the pc via serial port communication. Many other programs in the computer interact with the peripherals connected to the computer using serial port communication as well.

In some rare cases Ubiqua won’t detect or operate the device because another program in the computer is using the same COM port of the device. For example, the PCCompanion application which is installed to interact with a Sony Ericsson device continuously opens and closes the serial port assigned to the installed sniffers.

The solution for this issue is to close those type of programs, or disable them from the automatic startup in Windows.

How to use

Add extra security to your Ubilogix account by setting up the multi factor authentication. Please read this blog post which describes how to activate and disable the TOTP in your account, and everything related to this process.

When a device is set as sniffer on the Device window, we can select it with the mouse, then, do a right click over it and on the pop-up menu select the option "Remove Device".

On the Graphic View use the toolbar button named "Load Background Image…" (first button on the toolbox from left to right).

The configuration files are located in

  • XP: C:\Documents and Settings\All Users\Application Data\Ubilogix\Ubiqua\
  • Vista/7: C:\ProgramData\Ubilogix\Ubiqua\

Folder might be hidden, if so, copy and paste the path to the address bar.

Currently Ubiqua does not offers an option to add freely any protocol into the decoders list, to do so, please contact us

  • Make sure the key you need to decrypt the packets is in your key bank.
  • Make sure the key has been enter in the same order as it appears over the air.
  • Make sure you don't have another key that matches the criteria and might interfere in the selection of the correct key for the packet (e.g., the correct key might be a DefaultNetworkKey but a regular NetworkKey matches the criteria for that packet and PAN ID, the NetworkKey has preference over the DefaultNetworkKey).

The colors of the nodes indicate:

  • Gray, a normal node.
  • Red, for a coordinator. Which is any node with the short address 0x000 in a Zigbee network.
  • Green, for an end-device. This color is only assigned after its type has been read from a Device Announce packet.
  • Blue, for a router. Any node that is not a coordinator and has children. The type might also be assigned from a Device Announce packet.

The Association Request/Response packet must be caught by Ubiqua in order to show the topology of the network, otherwise the nodes will be shown as orphans.

When a sniffer device is connected it must appear on the Devices window as "Unassigned", select the desired device and do right click over it, then, choose the option "Setup device as…" and in the next submenu select the sniffer type.

If the device does not appears at all on the Devices window then, contact Ubiqua's technical support for help, send and email to: **support@ubilogix.com**

To be able to capture more than one protocol at the same time (same channel or another channel), more than one sniffer hardware is needed. When a device is setup as sniffer we just change one of its configuration properties named "Protocol" to be the needed one. This is by clicking over the current protocol name shown on the column showing the protocol.

Here are some tips that might help solve your problem.

  • Make sure you have a windows account with administrator privileges.
  • Make sure you have the .NET Framework 4.0 (Full , not just the "Client Profile").
  • (This fixes most of the problems) Make sure you have the .NET Framework 3.5 (We're currently updating the application with new components, but some components still use the .net 3.5, this framework is not included in .net 4.0) http://www.microsoft.com/download/en/details.aspx?id=22
  • Restart the computer and execute the application.

If none of the above solves your issue, then you'll need to provide more information about the issue.

Please follow these steps:

  • Click on the Windows Start button and enter "evetnvwr" (no quotes) and press Enter.
  • Navigate to the Windows Logs > Application, sort the event by "Date and Time" and find the error(s) (it should have the same time stamp when you executed Ubiqua).
  • Double click on the error and click on the "Copy" button and paste all the errors in to this email.

Follow Step 2 and 3, but now for the "Windows Logs > System" section.

To be able to capture in more than one channel at the same time more than one sniffer hardware is needed.

This is, one sniffer per channel. When a devices is set or added as sniffer, we can adjust its parameters on the Device window and set the channel we wish to capture. For more info about this please consult the Ubiqua User's Guide

Ubiqua supports opening captures from Daintree's SNA and NXP/Freescale analyzer and Wireshark. Just by doing click with the mouse over the file menu and choosing the option "Open"

Ubiqua PA supports Zigbee-2006, Zigbee-2007, Zigbee-Pro and PopNet2.0


  • IEEE 802.15.4
  • Zigbee
  • Thread
  • PopNet
  • IETF 6LowPan
  • Zigbee Light Link
  • Zigbee Green Power
  • JenNet-IP

Here we have listed the protocols and profiles supported by Ubiqua according to the most stable specifications:

  • IEEE 802.15.4 - 802.15.4-2003 (No security supported)
  • Zigbee – 053474r18ZB_CSG-Zigbee-Specification
    • ZCL - 075123r02ZB_AFG-Zigbee_Cluster_Library_Specification
    • ZDP - 053474r18ZB_CSG-Zigbee-Specification
    • HA - 053520r26ZB_HA_PTG-Home-Automation-Profile
    • CBA - 053516r11ZB_AFG-Commercial-Building-Automation_Profile
    • HC - 075360r13ZB_ZHC_PTG-PHHC-Profile
    • SE - 075356r15ZB_ZSE-ZSE-AMI_Profile_Specification
  • TP2 - 064166r01ZB_AFG-Test-Profile-2
  • Synkro RF - SYNKRORM Rev. 1.2
  • PopNet 1.0 - SJS 110-300-03
  • PopNet 2.0 - SJS 115-300-05
  • Zigbee IP
  • Zigbee RF4CE - 094945r00ZB_RF4CE-Specification
  • IETF-6LoWPAN - rfc4944 and Draft-IETF-6lowpan-hc-06

Ubiqua PA is capable of handling Zigbee-2006 Network security, on Zigbee-2007 and Zigbee-Pro Network and APS security. Also, PopNet1.2 and PopNet2.0 as well, on lite and AES128.

For a complete list of supported devices please see section Supported Sniffer Hardware in the Ubiqua Documentation Pages.

By doing click on the file menu, and choosing the option "Save Environment" (File > Save Environment).

In earlier versions of Windows, processes running under the same user account shared the same basic security privileges. Starting with Windows Vista, a new attribute, Privilege Level, is attached to each process. A process cannot send a message to another process with a higher privilege level, although they both may be running under the same user account.

UIPI (User Interface Privilege Isolation, a variant of UAC, User Account Control) disables drag and drop from medium integrity processes to high integrity processes by filtering out most window messages.

In essence, Ubiqua works with elevated privileges preventing the ability of drag-and-drop from the desktop.

Topology connections.

A topology edge is created in the Graphic View based in the information of the Association Request/Response messages of MAC 2003 and 2006. After receiving these two messages, Ubiqua gets the parent-child topology relationship needed to generate the edge, an edge is added from son to parent. The parent node is obtained from the Source Address of the Association Request message, and the child node from the Short Address field of the Association Response message.

Routing connections.

When Ubiqua captures a Zigbee Network Link Status message, it uses the data inside this message to generate the edges (A,B). More specifically, the beginning the edge (A) is the Network Source Address field of the packet, then for each item in the Link Status List generates an edge where the end (B) is the Neighbor Network Address of each list item.

To apply a filter you must first create it. You can create them in two ways. The first one is through the Packets View, select a field on the tree, right click on the node and select the "Create Filter" menu item. You will be prompted with options to create a quick filter according to conditionals applied to the targeted field values. The other option to create a filter is to use the Filter Editor, click the Add Filter toolbar button on top of the Traffic View. Follow the instructions on screen. To finally apply a filter, click the "Apply Filter" toolbar button.

Internally Ubiqua handles all timestamps as Universal Coordinated Time (UTC). When displayed in the user interface these values are converted to the timezone set in your operating system. If you wish to view timestamps as UTC, you can change this preference on your computer.

You still have a question?

Couldn't find what you needed in the frequently asked questions section?
Please visit your personal Ubilogix dashboard; you may create and review support tickets via the support tab.

Visit your Dashboard