ProbitBench FAQ

ProbitBench might not run on East Asian versions of Windows operating systems. Please use an English or European version. Also make sure you have installed the .NET 2.0 framework with SP2 when using ProbitBench V2.0.6.0 or lower. Higher versions of ProbitBench require the .NET 4 framework.

For ProbitBench V2.0.6.0 and lower, please run the program with administrator privileges. From V3.0.0.0 onwards, no administrator rights are required on Windows 7 and later.

The ProbitBench package including test sequences is reserved for members of the DiiA (DALI Alliance) only. It must be downloaded from a restricted location on the DiiA organisation website. For login details please contact the DiiA directly.

If you downloaded the free version of ProbitBench, the test sequences are not part of this software. If you downloaded the ProbitBench package including the test sequences, this can happen on Windows 7 or later: Windows marks all downloads from the internet as unsafe, and even the content inside a downloaded zip file inherits this mark when uncompressing. Solution: Right-click the zip file and check the file properties, you will see a message such as 'This file came from another computer and might be blocked to help protect this computer'. Use the Unblock button to remove this restriction. After unblocking you should be able to decompress the zip file and run the application. If you merged new test sequence DLL files with previous ones, older test sequences may no longer appear because they have become incompatible with the newer ProbitBench version.

When in Ed2 mode, the Sniffer and Bitscope highlight problematic frames according to the Ed2 interframe and bit timings. Frames are marked yellow when they violate Ed2 transmitter timings. Such frames are non-conformant from the transmitter's perspective, but they have to be accepted by the most restrictive Ed2 receiver. Additionally a '*' mark appears at the time and/or frame information indicating an interframe and/or bit timing violation. Frames are marked red when they violate Ed2 receiver timings. Such frames are non-conformant and will be rejected by the most restrictive Ed2 receiver. A successful reception depends on specific receiver thresholds but is not guaranteed. Additionally a '**' mark appears at the time and/or frame information indicating an interframe and/or bit timing violation.

When in Ed1 mode, the Sniffer and Bitscope highlight problematic frames according to the Ed1 interframe and bit timings. Due to the lack of differences between Ed1 transmitter and Ed1 receiver timings, any violation is marked red. Such frames are non-conformant and will be rejected by the most restrictive Ed1 receiver. A successful reception depends on specific receiver thresholds but is not guaranteed. Additionally a '**' mark appears at the time and/or frame information indicating an interframe and/or bit timing violation.

Each ProbitBench release specifies the minimum required firmware version of the Probit hardware (ProbitLab, ProbitLab2, ProbitGears, ProbitSite). Always update ProbitBench first, then update the corresponding device firmware. Check the changelog on the ProbitBench downloads page for the exact version dependencies of your release.

Yes. ProbitBench works offline with all its analysis features, for example reviewing previously recorded sniffer logs, inspecting bus signal timings in Bitscope, browsing test result files in Navigator, or working with the Simulator in offline mode. A connection to a Probit device is only required for live measurements and test execution.