Devices support

This page contains hints for using and troubleshooting of our devices.

Quick links

• IP address change
• Manuals and other downloads: https://advacam.com/downloads/

General troubleshooting

Device not found by Pixet or API

• Some devices need a special file(s) and some file not found in expected location:

• In addition to Pixet core needing pixet.ini, device needing hwlib located by the [Hwlibs] section of the pixet.ini, device's own XML config file located by the [configs] section of the pixet.ini file, more devices often need special files. Their location follows different rules:

• Device ini files: Eq dummy.ini, zest.ini, ... this is device-type specific files and can be located either in the location from which the program is run (beside the exe file), or in the user settings directory. Location is selected by the UseAppDataDir and AppDataDir values in the [Settings] section of the pixet.ini file.
• Device firmware files: Eq zestwpx.bit, zemtpx3.rbf, ... location from which the program is run (beside the exe file).
• Other device-type specific files: Eq ftd2xx64.dll, okFrontPanel.dll, ... location from which the program is run (beside the exe file).
• Note: Be careful that "beside exe" may not apply when running from a programming IDE. For example, in Visual Studio, the default state of a C# project is that "beside exe" is really "beside exe", but the by-default of a C++ project is that the files can be located in the root of the project.

• See Files and directories of the Pixet and SDK

Widepix

Widepix L

• WidePIX -L user manual

Widepix PoE

• WidePix POE Quick Start Guide

Widepix PoE v2

• WidePix POE v2 Quick Start Guide

Virtual devices

The Pixet core suppots virtual devices for testing without a hardware present. There are two typed of devices available:

• File device - Generic frame-based device using selected data file for emulating of the measurement.
• Dummy device - Virtual device emulating selected device type with properties by the config file.

File device

• Default virtual device if no physical devices found.
• User can disable it using the FileDeviceWhenNoDevs=false in the [Settings] section of the pixet.ini file
• User can force it using the FileDevice=true in the [Settings] section of the pixet.ini file
• In the Pixet program can be selected some predefined data set or a custom data file. The file must be frame-based.
• The device has no hwlib and any config file.
• The device has the currentFrameIndex() method in the Python API.

Dummy device

• Virtual device emulating presence of specific device type and generating noise while "measuring".
• Need the dummy.dll/dummy.so hwlib file, enabled in the [Hwlibs] section of the pixet.ini file
• Using the dummy.ini configuration file in the Pixet directory or AppData directory (The file can be in both places, find out which one is used).

• Count > 0 must be set
• Set the ChipCount, ChipIDs list and Type in the [0] section (or next section numbers if Count > 1).

• Every dummy device need it's own XML config file

• File name must be Dummy-CHIPID.xml, Dummy-I08-W0060.xml for example.
• User can simple copy your device config file and set the corresponding type in the dummy.ini

Example: Minipix-I08-W0060.xml -> Dummy-I08-W0060.xml, Type=3

• Instructions video: https://www.youtube.com/watch?v=YTpTZyc2Et8