If your device block displays a symbol or icon in Network view, hover over the icon to view the message. 

Firmware upgrade versions
Xilica Firmware upgrades use a numbering scheme of X.Y.Z (like 4.0.1)
is a major version which means a significant modification on compatibility on different communication protocol. If Xilica Designer and the device(s) have different major versions, they will not work together and will cause trouble.
is a minor version which means there are functionality changes, however the communication protocol will remain compatible. Only specific new features will not function properly but in general, older features will still work fine.
is the build number. The build number is used when a bug fix version is available.

Red circle with backslash
The major version expected by Xilica Designer is different from the device. This will cause communication breakdown and you must upgrade the device Firmware before it will work with Xilica Designer.

Yellow triangle with exclamation mark
The detected device has a lower minor version as compared to the recommend minor version stored in Xilica Designer. In this situation, some new features provided in Xilica Designer (i.e. new DSP modules) will not function in the device. We recommend upgrading the device Firmware, but if the user is not using any new features and does not want to upgrade, it still works.

The device clock is not synchronized
Xilica Designer provides a function to allow you to synchronize your host computer clock to the device real-time clock. In Network view, a Clock icon will be displayed in the lower left of the device block. When online, the device clock will check and confirm that it is the same as your host computer.
If the clock is correct, it will display a normal clock icon. Under this situation, you do not need to do anything as the clock in the device is correct.
If the clock is different from your host computer, the clock will display a question mark on top of the icon.
Sync one device: Right click the device block > Synchronize Device clock.  
Sync all devices at once: At the top right of the software > Sync clock to all devices
(Note: After the clock is synchronized, the device will automatically reboot). 

No project file is stored in the device.
There is no design in the device. Create a new design or import a design.

No data
The processor needs a design to be loaded into the device. If the same error message persists even after loading a design to the device, please restart the device and reboot the software.  

DSP Processing Error (1)

A bad pre-designed project was loaded into the device. Try reloading the pre-designed DSP file into the device. If there is no change, restart the device, reboot Xilica Designer and reload the file.

DSP Processing Error (2)
The pop up message shown will print out an error code. Please retry the Firmware Upgrade. 

IP Issue error
TCP error
There is a connection issue with the device. When a device is detected, a TCP connection is trying to be made from Xilica Designer to the device to obtain device information. If it fails to obtain the device information, this TCP error message will be displayed.

When communication is sent through TCP, Xilica Designer sends a message then waits for the device to respond. This wait will have a timeout of 1 minute. If the network is not set up properly and the message cannot get to the device, Xilica Designer will keep waiting until it timeouts (after approx. 1 minute). After this message timeout, it will retry with the message or the next message.
If there was a temporary network issue that caused the TCP message to drop, it may take up to 1 minute before it can retry and recovery itself.
However if the network issue is persistent, the retry will never succeed and the TCP error icon will be displayed.

If you see the TCP error, please wait for approximately 1 minute to see whether the TCP error goes away.
If the system can recover itself, that may just mean a temporary issue on your network. If the TCP error icon persistently displayed, that means there is something wrong with the network. 

1. If it will not self connect, right click the device block > Remote Reset Device.

2. You can test the connection. In Xilica Designer's Network View, right click the device block > Device Setup. In the Network tab, in the Connectivity Test section, select TCP Test. The results will display.

3. Check the firewall on your host computer. Disable the firewall on your host computer and see if it resolves the problem. 

4. Check the IP address range of your host computer to see whether it is consistent with your device IP range.
At the top left of Network view, it will display the IP address of your host computer. notice that in the example, there are multiple IP addresses. This is because the computer has multiple network interfaces (such as, Wi-Fi, Bluetooth connection, etc.)

5. Make sure the device IP address is within the same subnet of your host computer (or use a router to route the network traffic to the appropriate subnet).

6. We also recommend keeping your host computer network interface to the minimal. If you can disable some of the unused network interfaces, that will reduce the confusion of network traffic.

7. If that still does not work, the issue must be isolated by reducing the network components. Doing so, can determine whether the device and host computer is working properly.

  • Setup the device and host computer to DHCP mode.

  • Connect a LAN cable directly between the device and host computer.

  • As there is NO DHCP server available, the device and computer will revert to zero configuration. The device IP address will be 168.254.x.x, and the computer IP address will be 169.254.x.x. Check if this works. 

UDP Error:
Xilica Devices rely on UDP broadcast mechanism to broadcast a device heartbeat message. In order for the system to work, the network must be able to support UDP broadcast. In normal LAN environments, UDP broadcast is supported. However, if you are setting up a more complex network with different sub-nets, you must enable your routers to support UDP broadcast from one network to the other.
We recommend keeping your network simple and to run everything under a single sub-net.

To verify whether UDP is working. you can use the UDP test function.
In Xilica Designer's Network View, right click the device block > Device Setup. In the Network tab, in the Connectivity Test section, select UDP Test. The results will display.


Flickering ON/OFF status
If the device status is flickering from ON to OFF repeatedly, that means the device is detected in the network, however, it cannot consistently receive the heartbeat message from the device properly. Once Xilica Designer receives a heartbeat message (UDP broadcast message) from a device, the device is expected to keep sending it's heartbeat broadcast every second. If the detected heartbeat is not received for 3 seconds (missing 3 heartbeats in a row), the device will be considered OFFLINE. When the next heartbeat message is received, the device will switch to ONLINE again. 

The flickering status is likely caused by a bad network setup or bad Wi-Fi reception (Especially when you run your Xilica Designer on a Wi-Fi connected host computer). We recommend to always run your equipment on a wired network.

To assist in this situation, a Network Condition setting option is available in System Preferences. At the top of the software, select Settings > Preferences.
Set the Network Condition.  

Excellent - Wired network with no packet lost
The device is considered as OFFLINE when the heartbeat is missed for 3 seconds.

Acceptable - WiFi network with no packet lost
The device is considered OFFLINE when the heartbeat is missed for 6 seconds.

Poor - WiFi network with some packet lost
The device is considered OFFLINE when the heartbeat is missed for 12 seconds.

Xilica Designer Crashing
If Xilica Designer is crashing before it opens Network View, there is a high chance that one of the system files is corrupted. Click here for recovery instructions.

Heartbeat Monitor and Network Capture
In Xilica Designer, there are two features listed under the Troubleshooting tab. These features should only be used under Xilica Support direction. Users should avoid using these features themselves. 

Did this answer your question?