Devices support - Revision history

HudecekP: /* Virtual devices */

2025-09-17T13:56:40Z

Virtual devices

← Older revision		Revision as of 15:56, 17 September 2025
Line 29:		Line 29:
	= Virtual devices =		= Virtual devices =
	The Pixet core suppots virtual devices for testing without a hardware present. There are two typed of devices available:		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.		* '''File device''' - Generic frame-based device using selected data file for emulating of the measurement. Primarily intended for the user to see something when starting Pixet without a device connected.
	* '''Dummy device''' - Virtual device emulating selected device type with properties by the config file.		* '''Dummy device''' - Virtual device emulating selected device type with properties by the config file.

HudecekP: /* File device */

2025-09-17T13:53:58Z

File device

← Older revision		Revision as of 15:53, 17 September 2025
Line 39:		Line 39:
	* The device has no hwlib and any config file.		* The device has no hwlib and any config file.
	* The device has the '''currentFrameIndex()''' method in the '''[[Python API]]'''.		* The device has the '''currentFrameIndex()''' method in the '''[[Python API]]'''.
	* API user can use it as solution to prevent errors if device count = 0 or for other ad-hoc emergency workarounds.		* API user can use it as solution to prevent errors if device count = 0 or for other '''ad-hoc emergency workarounds'''.

	== Dummy device ==		== Dummy device ==

HudecekP: /* File device */

2025-09-17T12:45:24Z

File device

← Older revision		Revision as of 14:45, 17 September 2025
Line 39:		Line 39:
	* The device has no hwlib and any config file.		* The device has no hwlib and any config file.
	* The device has the '''currentFrameIndex()''' method in the '''[[Python API]]'''.		* The device has the '''currentFrameIndex()''' method in the '''[[Python API]]'''.
	* ~~User~~ can use it as solution to prevent errors if device count = 0 or for other ad-hoc emergency workarounds.		* API user can use it as solution to prevent errors if device count = 0 or for other ad-hoc emergency workarounds.

	== Dummy device ==		== Dummy device ==

HudecekP: /* File device */

2025-09-17T12:44:32Z

File device

← Older revision		Revision as of 14:44, 17 September 2025
Line 39:		Line 39:
	* The device has no hwlib and any config file.		* The device has no hwlib and any config file.
	* The device has the '''currentFrameIndex()''' method in the '''[[Python API]]'''.		* The device has the '''currentFrameIndex()''' method in the '''[[Python API]]'''.
			* User can use it as solution to prevent errors if device count = 0 or for other ad-hoc emergency workarounds.

	== Dummy device ==		== Dummy device ==

HudecekP: /* Dummy device */

2025-07-15T07:58:09Z

Dummy device

← Older revision		Revision as of 09:58, 15 July 2025
Line 50:		Line 50:
	:* User can simple copy your device config file and set the corresponding type in the dummy.ini		:* 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		:: Example: '''Minipix-I08-W0060.xml''' -> '''Dummy-I08-W0060.xml''', Type=3
	* Instructions video: https://www.youtube.com/watch?v=~~n6XIH0_FOFQ~~		* Instructions video: https://www.youtube.com/watch?v=YTpTZyc2Et8

HudecekP: /* Device not found by Pixet or API */

2025-07-14T15:14:38Z

Device not found by Pixet or API

← Older revision		Revision as of 17:14, 14 July 2025
Line 13:		Line 13:
	::* '''Device firmware files:''' Eq zestwpx.bit, zemtpx3.rbf, ... location from which the program is run (beside the exe 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).		::* '''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\|Files and directories of the Pixet and SDK]]		:* '''See''' [[Files_and_directories_of_the_Pixet_and_SDK\|Files and directories of the Pixet and SDK]]

HudecekP: /* Device not found by Pixet or API */

2025-07-14T12:57:10Z

Device not found by Pixet or API

← Older revision		Revision as of 14:57, 14 July 2025
Line 8:		Line 8:

	== Device not found by Pixet or API ==		== Device not found by Pixet or API ==
	* Some devices need a special file(s) and some file not found in expected location:		* '''Some devices need a special file(s)''' and some file not found in expected location:
	:* In addition to Pixet core needing [[Files_and_directories_of_the_Pixet_and_SDK#pixet.ini_file\|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:		:* In addition to Pixet core needing [[Files_and_directories_of_the_Pixet_and_SDK#pixet.ini_file\|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 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.

HudecekP: /* Device not found by Pixet or API */

2025-07-14T12:52:43Z

Device not found by Pixet or API

← Older revision		Revision as of 14:52, 14 July 2025
Line 12:		Line 12:
	::* '''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 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).		::* '''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).
	:* '''See''' [[Files_and_directories_of_the_Pixet_and_SDK\|Files and directories of the Pixet and SDK]]		:* '''See''' [[Files_and_directories_of_the_Pixet_and_SDK\|Files and directories of the Pixet and SDK]]

HudecekP: /* Device not found by Pixet or API */

2025-07-14T12:49:35Z

Device not found by Pixet or API

← Older revision		Revision as of 14:49, 14 July 2025
Line 12:		Line 12:
	::* '''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 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).		::* '''Device firmware files:''' Eq zestwpx.bit, zemtpx3.rbf, ... location from which the program is run (beside the exe file).
			:* '''See''' [[Files_and_directories_of_the_Pixet_and_SDK\|Files and directories of the Pixet and SDK]]

	= Widepix =		= Widepix =

HudecekP: /* Quick links */

2025-07-14T12:46:08Z

Quick links

← Older revision		Revision as of 14:46, 14 July 2025
Line 4:		Line 4:
	* [[IP address change]]		* [[IP address change]]
	* Manuals and other downloads: https://advacam.com/downloads/		* 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 [[Files_and_directories_of_the_Pixet_and_SDK#pixet.ini_file\|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).

	= Widepix =		= Widepix =