ProbitBench V4.6.0.0.zip (2024-12-06)
Changes related to LVE Developer V0.7.0.0 test sequences:
Changes related to ProbitBench V4.5.0.0:
· Requires ProbitLab V4.12 or ProbitLab2 V4.14 or ProbitGears V4.6 firmware
· Fixing minor issues
· Fixing an issue with the MacroInterface
· Added support link for DALI Alliance members
· Added interface support for 34x
· Added test parameter: overvoltage protection
· 103 feature addressing updated
Changes related to LVE Developer V0.6.2.0 test sequences:
· Adaptions to revised interface
Changes related to ProbitBench V4.4.0.0:
· Requires ProbitLab V4.12 or ProbitLab2 V4.13 or ProbitGears V4.5 firmware
· GUI & internal optimizations
· Simulator: Several optimizations & bug fixing
Changes related to ProbitBench V4.3.3.0:
· Fixing sporadic reboots of ProbitLab2 devices when Gigahertz Optik DLL is used
· MacroInterface extended for ProbitGears usage
· GUI optimizations
· Internal optimizations
· Mediator: 105 and 332 commands added
· Navigator: Fixing storing last selected folder
· Navigator: Sort elements in view by clicking on columns header
· Sequences: Revised bus communication handling for multi master testing
· Sequences: Time column shows clock time instead of timestamp
· Sequences: Fixing line double click handling
· Sequences: Improving options dialog
· Sniffer: Toggle format for time and idle time by clicking on columns header
· Sniffer: Recording as text file removed
· Sniffer: Record pause removed
· Sniffer/Sequences: Multiline select and copy function added (with standard shortcuts), e.g. which can be pasted in Excel
Changes related to LVE Developer V0.6.1.0 test sequences:
· Adaptions to revised interface
Changes related to ProbitBench V4.3.2.0:
· Requires ProbitLab V4.12 or ProbitLab2 V4.12 or ProbitGears V4.5 firmware
· Mediator: Fixing wrong 209 Tc enumeration
· Navigator: Fixing detection of test result in xml files
· Sequences: Fixing long file name issue
· Sequences: Improving options dialog
Changes related to LVE Developer V0.6.0.0 test sequences:
· Adaptions to revised interface
Changes related to ProbitBench V4.3.1.0:
· Requires ProbitLab V4.12 or ProbitLab2 V4.12 or ProbitGears V4.5 firmware
· Fixing crash issue of Visual Studio when using ProbitConstants.dll in a macro code project
Changes related to ProbitBench V4.3.0.0:
· Requires ProbitLab V4.12 or ProbitLab2 V4.12 or ProbitGears V4.5 firmware
· Automatic memory scale for internal buffers. This allows to increase the number of elements in views dependently of the computers RAM.
· Colour meter support added for Gigahertz Optik devices BTS256, MSC15, CSS-45. The required external files need to be obtained separately and placed in a folder named “External” of the ProbitBench application path.
· Fixing basic macro code project thread handling
· Fixing minor issues
· Fixing special character issue
· Fixing big file loading issue
· Sequences: “Search for” function added
Changes related to ProbitBench V4.2.8.0:
· Requires ProbitLab V4.11 or ProbitLab2 V4.11 or ProbitGears V4.4 firmware
· GUI updates
· Low disk space notification
· Sequences: Abort dialogue allows to keep output states of used Probit device
· Mediator: 102, 103, 202, 207, 209 updates
· Simulator: Fixing loading issue
Changes related to LVE Developer V0.5.9.0 test sequences:
· Adaptions to revised interface
Changes related to ProbitBench V4.2.7.0:
· Requires ProbitLab V4.9 or ProbitLab2 V4.10 or ProbitGears V4.3 firmware
· Extension for 209 update
· Minor internal optimizations
Changes related to LVE Developer V0.5.8.0 test sequences:
· Adaptions to revised communication protocol
Changes related to ProbitBench V4.2.6.0:
· Requires ProbitLab V4.9 or ProbitLab2 V4.10 or ProbitGears V4.3 firmware
· Sequences: GUI optimized
Changes related to LVE Developer V0.5.7.0 test sequences:
· Adaptions to revised communication protocol
Changes related to ProbitBench V4.2.5.0:
· Requires ProbitLab V4.9 or ProbitLab2 V4.10 or ProbitGears V4.3 firmware
· Adaptions to revised communication protocol
· File reading optimized
· Fixing character encoding
· Fixing issues with command exception handling
· Bitscope: Ed1 logical bit error indication
· Sequences: Fixing text wording
Changes related to ProbitBench V4.2.3.0:
· Requires ProbitLab V4.8 or ProbitLab2 V4.9 or ProbitGears V4.3 firmware
· Sniffer/Sequences: Fixing table view issue when reaching the maximium number of lines
· Navigator: Fixing registration file creation issue for protocol files containing special characters
Changes related to LVE Developer V0.5.6.0 test sequences:
· B.3 test cases extended
· B.3, B.4 optimized
· Physical layer and bit layer tests: Checking DTR0 before modifying
Changes related to ProbitBench V4.2.2.0:
· Requires ProbitLab V4.8 or ProbitLab2 V4.9 or ProbitGears V4.3 firmware
· Mediator: Fixing crash when reading a memory bank
Changes related to ProbitBench V4.2.1.0:
· Requires ProbitLab V4.8 or ProbitLab2 V4.9 or ProbitGears V4.3 firmware
· GUI optimized
· Storing last used AC or DC power supply mode
· Logical unit handling at test start optimized to skip unnecessary tests
· Fixing issues with command exception handling
· Fixing crash issue in case of connection loss
· Fixing crash issue in case of connection loss
· Mediator: Default settling time optimized according the priority levels
· Sniffer/Sequences: Fixing printing issues for long protocols
· Simulator: Fixing GUI updates
Changes related to ProbitBench V4.2.0.0:
· Requires ProbitLab V4.7 or ProbitLab2 V4.7 or ProbitGears V4.3 firmware
· Adaptions to revised communication protocol
· GUI layout optimized for smaller screen size
· External trigger port link configuration available
· Duplicate profile function
· New messages and hints to fix commonly known issues with ProbitBench
· Support links added in help menu
· ProbitGears feature report in information window
· Bitscope: GUI optimized
· Sniffer: Column resizing fixed
· Sequences: DLL hash issue in case of file lock fixed
· Sequences: Column resizing fixed
· Sequences: 5 second extended recording in case of test sequence halt
· Navigator: Signature proof while browsing removed (signature is still proofed when “Check content” is used)
· Mediator: Memory bank write backward compatibility to Ed1
· Mediator: Global address selection moved from “Mediator Developer” to new tab “Mediator Address”
· Mediator: Answer detail report fixed
· Mediator: Minor GUI issues fixed
· Macro interface: Sniffer functionality added (see example project)
· Macro interface: “SetOuput” function added, replacing the former “SetSwitch” function (it remains for legacy purpose, but it is not recommended to use it anymore)
Changes related to LVE Developer V0.5.4.0 test sequences:
· Minor output issues fixed
· Internal changes without changing test flow or content
Changes related to ProbitBench V4.1.1.0:
· Requires ProbitLab V4.6 or ProbitLab2 V4.6 or ProbitGears V4.2 firmware
· Mediator: Command “WRITE MEMORY LOCATION – NO REPLY” replaced by “WRITE MEMORY LOCATION” for writing to a memory location to become compatible with Ed1 devices
· Sequences: Report, warning and error references in the xml protocol files contain more detailed information about the test step
· Navigator: Comparison of test sequences with non-ASCII characters fixed
Changes related to LVE Developer V0.5.3.0 test sequences:
· New test sequences C.5.1 and C.5.2 added
· Test output of few test sequences adapted
Changes related to ProbitBench V4.1.0.0:
· Requires ProbitLab V4.6 or ProbitLab2 V4.6 or ProbitGears V4.2 firmware
· 103 command set and handling implemented
· General GUI adapted and optimized
· Start screen is movable
· Connection state button is clickable to connect and disconnect with Probit device
· Tool tips added for the ribbon bar control elements
· Bitscope: Unused control elements removed
· Bitscope: Output text revised
· Bitscope: F5 can be used for refresh
· Bitscope: Bit time measurement while pressing CTRL key and moving the mouse cursor over the bit timings
· Sniffer: Unused control elements removed
· Sniffer: Output text revised
· Sniffer: Print function added
· Sequences: Print function added
· Sequences: Warning message adapted to the connected hardware
· Sequences: Long waits (> 60s) will show the start clock time as reference
· Sequences: Option “Do not save low level information” removed
· Sequences: Option “Break on error?” added
· Sequences: Option parameter for DALI bus short circuit added
· Sequences: Some option parameters renamed
· Sequences: Switch mapping function for relevant option parameters added
· Navigator: F5 can be used for refresh
· Navigator: File name parsing fixed
· Navigator: Button for creating registration files for DIIA added
· Simulator: 202 optimized
· Simulator: Load and store fixed
Changes related to ProbitBench V4.0.0.5:
· Requires ProbitLab V4.5 or ProbitLab2 V4.5 or ProbitGears V4.1 firmware
· Fixing an issue where in Ed1 mode the ProbitBench remains checking according Ed2 timings.
Changes related to ProbitBench V4.0.0.4:
· Requires ProbitLab V4.5 or ProbitLab2 V4.5 or ProbitGears V4.1 firmware
· Revised communication protocol for future needs
· Revised DALI frame detection
· Revised macro interface (including example) adding blocking/non-blocking transmission of macros and capabilities for switching
· Fixing minor issues in ProbitBench and its modules Navigator, Bitscope, KNX, Simulator, Sniffer
· Simulator: 209 colour standard capabilities
· Sniffer: Revised presentation of bus events/telegrams
Changes related to ProbitBench V4.0.0.3:
· Requires ProbitLab V4.4 or ProbitLab2 V4.4 or ProbitGears V4.0 firmware
· Revised communication protocol for future needs
· GUI layout optimizations
· Ed1/Ed2 selection in offline mode
· Bitscope: Transmitter timing check of highlighted halfbit
· Navigator: Failed and missing test sequence report generation
· Sequences: Storage of last selected test sequence set
· Sequences: Error step through functions
· Simulator: Memory bank access
Changes related to ProbitBench V4.0.0.2:
· Requires ProbitLab V4.3 or ProbitLab2 V4.2 or V4.3 firmware
· Revised communication protocol for future needs
· Simulator: Fixing load configuration in offline mode
· Simulator: Fixing load configuration when ProbitGears has 201 configuration only
· Mediator: New design with focus on functionality for Edition 2. Divided in Developer and Toolbox tab
· Mediator Developer: Have access to all defined commands
· Mediator Developer: Macro functionality introduced for creating, storing, loading and executing your own commmand sequences
· Mediator Toolbox: Develop and use your own tools (see example project) with simple and easy macro based bus access
· Mediator Toolbox: Basic tool collection for accessing the most common 102 functionalities
Changes related to LVE Developer V0.5.1.0 test sequences:
· Adaptions to interface changes
Changes related to ProbitBench V4.0.0.1:
· Requires ProbitLab V4.1 or V4.2 or ProbitLab2 V4.0 or V4.1 firmware
· Revised communication protocol for future needs and new devices
· Bus high voltage is limited from 0V to 22.5V
· Simulator: Fixing crash when storing a simulator configuration
Changes related to LVE Developer V0.5.0.1 test sequences:
· Test sequence B-2 checks now the range from 0V to 16V to find out the receiver voltage threshold level
· Test sequences renamed
for C-3.1, C-3.2, C-4, D-1.1, D-1.2
· Test sequences restructured
for C-1
Changes related to ProbitBench V4.0.0.0:
· Requires ProbitLab V4.0 firmware
· Revised communication protocol for future needs and new devices
· Bus high voltage is limited from 9.5V to 22.5V
· Selected profile name displayed in window title
· Test protocol files are secured against modifications
· Edition mode compatibility check for test sequences
· Introduction of Edition 2 developer test sequences from Lichtvision. They will help and support to develop devices according Edition 2. The test scope is focused on differences between Edition 1 and Edition 2 specifications and features. These test sequences will be extended and updated steadily in the future.
Changes related to ProbitBench V3.0.0.5:
· Requires ProbitLab V3.4 firmware
· Adaptions for new DLL version handling
· Fixing crash issue when importing file while in offline mode
· Optimizations in displaying of problematic frames regarding transmitter and receiver timings (timing quality level)
· Bitscope: Highlighting of problematic frames regarding transmitter and receiver timings (timing quality level)
Changes related to ProbitBench V3.0.0.4:
· Requires ProbitLab V3.4 firmware
· Probit devices detected as offline will not be shown in the selection box
· Integrated bus power supply and bus terminal connection of Probit devices can be switched seperatly
· Optimization of IEC62386 Ed1 bit and frame analyzation and handling
· Mediator: Optimization of addressing algorithm used in “Installation Commands”
· Mediator: Bugfxing of DALI transceiving behaviour
· Sequences: Tab options revised
· Several minor bugfixes, optimizations and changed wording
· Internet update checking for new versions
· User profile can be created to store individual configurations
· Automatic light measurement with Extech SDL400 light meter
· IEC62386 Ed2 bit and frame analyzation and handling
· Sniffer: Highlighting of problematic frames regarding transmitter and receiver timings (timing quality level)
· Mediator: New “Application Ext. Commands” tab for sending device type specific application extended commands
Changes related to ProbitBench V3.0.0.2:
· Requires ProbitLab V3.2 firmware
· When double clicking on a line in the “Sniffer” tab the “Bitscope” tab centers the full frame including the stopbits.
· “Address selection” tab removed and replaced by a control on the top of the main tab panel.
· Bugfix of display errors in “Sniffer” and “Sequences” tabs
· Several minor bugfixes, optimizations and changed wording
· “Sequences” tab options allows the selection of automatic or manual mains supply connect behaviour.
· Textboxes for displaying answer frames (for example used in “Query Commands” tab) shows content updates by a green background flash.
· New “Installation Commands” tab allows to transmit often used command sequences on installation level like assignment of short addresses.
· “Simulator” tab can be used when a ProbitLab is connected to readout an installation with query commands. The queried values are displayed in a virtual composition of control gears. This composition can be stored for later use with a ProbitGear device.
Changes related to ProbitBench V3.0.0.1:
· Requires ProbitLab V3.1 firmware
· Bugfix for “Sniffer” tab when double clicking on a line
· Gear symbol changed in “Simulator” tab
Changes related to ProbitBench V3.0.0.0:
· Requires ProbitLab V3.0 firmware
· Requires at least .NET4 framework
· Windows XP is not supported any more.
· No more administrator privileges required with Windows 7 and Windows 8 operation systems to connect to a Probit device.
· Revised communication protocol for future needs and new devices.
· “Verify content” function added in Navigator tab. This function allows you to compare a folder with test results against the test sequences DLL’s. As a result you get an overview which tests are missing, failed or passed.
· “Bus supply” button added to the ProbitBench. This button shows you if the internal bus supply is connected to the bus data terminals.
· New “Simulator” tab added to the ProbitBench.
Changes related to ProbitBench V2.0.6.0:
· Requires ProbitLab V1.9 firmware
· The test sequences are seperated from the ProbitBench and are loaded from DLLs when the ProbitBench starts.
· The frame detection tolerances are set to 20% for a half bit (1 TE) and 10% for a full bit (2 TE).
Why ProbitBench does not start?
Answer: ProbitBench might not run on East Asian version of Windows operating systems. Please use an English or European version.
Answer: Please make sure you have installed the .NET2.0 framework with SP2 when using ProbitBench version V2.0.6.0 and lower. Higher versions of ProbitBench will need .NET4 framework.
Why ProbitBench V2.0.6.0 cannot find any Probit device?
Answer: For ProbitBench version V2.0.6.0 and lower please run the program with administrator previleges.
Why I cannot download ProbitBench with test sequences?
Answer: The ProbitBench (with test sequences included) is for members of the DIIA only. It has to be downloaded from a restricted download location from the organization website.
For login details please contact the DIIA directly.
Why ProbitBench cannot find any test sequences?
Answer: If you downloaded the free version of the ProbitBench then the test sequences are not part of this software.
Answer: If you downloaded the ProbitBench including the test sequences then this can happen on Windows 7 operating systems or above. Windows marks all downloads from the internet as unsafe. Even the content inside of a downloaded zip file inherits this mark when uncompressing.
Solution: If you right click on the zip file and check the file properties you will see a message like this:
This file came from another computer and might be blocked to help protect this computer
An unblock button should be available to remove this security issue. If not it might be that you have not sufficient user privileges. After unblocking you should be able to decompress the zip file and run the application.
Answer: If you downloaded the ProbitBench including the test sequences and merged the new test sequences DLL files with previous ones then it might be that the older test sequences does not appear because they become incompatible with the new ProbitBench version.
What is the meaning of the timing quality level (color and text marking of frames) shown in Sniffer and Bitscope?
Answer: When in Ed2 mode the Sniffer and Bitscope highlights problematic frames according the Ed2 interfame and bit timings.
Frames will be marked as yellow when violating Ed2 transmitter timings. Such frames are non-conformant from transmitter perspective but they have to be accepted by the most restrictive Ed2 receiver.
Additionally there will be a “*” mark at the time and/or the frame information indicating an interframe and/or bit timing violation.
Frames will be marked as red when violating Ed2 receiver timings. Such frames are non-conformant and will be rejected by the most restrictive Ed2 receiver. A successful receiving depends on specific receiver thresholds but is not guaranteed.
Additionally there will be a “**” mark at the time and/or the frame information indicating an interframe timing and/or bit timing violation.
Answer: When in Ed1 mode the Sniffer and Bitscope highlights problematic frames according the Ed1 interfame and bit timings.
Due to the lack of differences between Ed1 transmitter and Ed1 receiver timings any violation will be marked as red. Such frames are non-conformant and will be rejected by the most restrictive Ed1 receiver. A successful receiving depends on specific receiver thresholds but is not guaranteed.
Additionally there will be a “**” mark at the time and/or the frame information indicating an interframe and/or bit timing violation.
© 2025 Lichtvision Engineering GmbH - All rights reserved
Imprint | Cookie Policy | Declaration of data protection | Privacy Statement
