Zetav is a tool for verification of systems specified in RT-Logic language.
Verif is a tool for verification and computation trace analysis of systems described using the Modechart formalism. It can also generate a set of restricted RT-Logic formulae from a Modechart specification which can be used in Zetav.
With default configuration file write the system specification (SP) to the sp-formulas.in file and the checked property (security assertion, SA) to the sa-formulas.in file. Launch zetav-verifier.exe to begin the verification.
With the default configuration example files and outputs are load/stored to archive root directory. But using file-browser you are free to select any needed location. To begin launch run.bat (windows) or run.sh (linux / unix). Select Modechart designer and create Modechart model or load it from file.
: You flashed firmware intended for a Full-Chip interface onto a cheap Lite/Revision B clone.
Open the utility and click "Activate."
If the version is lower or unstable, you can use the option to browse the APPLI folder (within the checker's folder) and select the 4.4.0 file to flash, then click "Downloading" to update. Troubleshooting: When "440 Verified" Fails psa interface checker 440 verified
Different software versions require tightly matched firmware variants to execute deep commands like BSI configuration, key programming, and injector coding. The table below outlines how the 4.4.0 verified package fits within the diagnostic ecosystem: Firmware Version Compatible DiagBox Software Range Target Vehicle Eras Lexia 348 / Peugeot Planet 2000 standalone Pre-2007 vehicles v4.3.0 DiagBox v6.11 to v7.39 2008 – 2014 vehicles v4.3.7 DiagBox v9.12 to v9.68 2015 – 2020 vehicles v4.4.0 (Verified) DiagBox v9.91 and higher Modern Euro 6.d / CAN-Matrix vehicles
Even with a decent interface, you may fail the verification. Here are the most frequent culprits: : You flashed firmware intended for a Full-Chip
Whether you are a professional mechanic serving Peugeot, Citroën, and DS customers or a passionate DIY enthusiast maintaining your own vehicles, taking the time to properly verify your diagnostic interface using the PSA Interface Checker will save countless hours of frustration and ensure that your diagnostic sessions proceed smoothly every time.
One of the first reasons someone searches for "psa interface checker 440 verified" is to confirm if their VCI is authentic (or a high-quality clone) and fully functional. While the term "440 verified" is not an official status, it strongly relates to the tool's ability to confirm your interface is a "full chip" unit that can handle modern DiagBox versions, including those requiring firmware 4.4.0. The table below outlines how the 4
If your interface is not showing as "440" or "Revision C," you may experience: when opening Diagbox.
It contains all the necessary optocouplers and relays (usually 12 or more) required for stable communication.
For any technician working on modern Peugeot, Citroen, or DS vehicles, achieving "440 Verified" status on your interface is not optional—it is essential for proper module scanning, programming, and telecoding. By following the guide above, you can ensure your Lexia 3 interface is fully optimized, stable, and ready to tackle the most complex diagnostic tasks with DiagBox 9.149 and beyond.
| PSA DTC | Likely cause | Tool 440 finding | |---------|--------------|------------------| | U0019 | CAN bus off | CAN-H to CAN-L resistance < 20 Ω | | U1213 | LIN slave missing | LIN mode: no flash, or red LED | | P0115 | ECT circuit | Continuity fail in sensor wires | | P2122 | Pedal position low | Short to ground on 5V reference | | C1320 | ABS sensor | Resistance > 1.5 kΩ (should be 1–1.2 kΩ) | | B1805 | Airbag igniter | Diode mode: junction fail or short |
The Zetav verifier expects the input RRTL formulae to be in the following form:
<rrtlformula> : <formula> [ CONNECTIVE <formula> ] ... <formula> : <predicate> | NOT <formula> | <quantifiedvars> <formula> | ( <formula> ) <predicate> : <function> PRED_SYMB <function> <function> : <function> FUNC_SYMB <function> | @( ACTION_TYPE ACTION , term ) | CONSTANT <quantifiedvars> : QUANTIFIER VARIABLE [ QUANTIFIER VARIABLE ] ...Where predicate symbols (PRED_SYMB) could be inequality operators <, =<, =, >=, >, function symbols (FUNC_SYMB) could be basic + and - operators, action type (ACTION_TYPE) could be starting action (^), stop action ($), transition action (%) and external action (#). Quantifier symbols (QUANTIFIER) could be either an universal quantifier (forall, V) or an existential quantifier (exists, E). Connectives (CONNECTIVE) could be conjunction (and, &, /\), disjunction (or, |, \/), or implication (imply, ->). All variables (VARIABLE) must start with a lower case letter and all actions (ACTION) with an upper case letter. Constants (CONSTANT) could be positive or negative number. RRTL formulae in the input file must be separated using semicolon (;).
V t V u (
( @(% TrainApproach, t) + 45 =< @(% Crossing, u) /\
@(% Crossing, u) < @(% TrainApproach, t) + 60
)
->
( @($ Downgate, t) =< @(% Crossing, u) /\
@(% Crossing, u) =< @($ Downgate, t) + 45
)
)
Verif tool does not deal with direct input. Examples are load from files with extension MCH. Those files are in XML and describes model modes structure and transition between modes. There is no need to directly modify those files. But in some cases it is possible to make some small changes manualy or generate Modechart models in another tool.
If you have further questions, do not hesitate to contact authors ( Jan Fiedor and Marek Gach ).
This work is supported by the Czech Science Foundation (projects GD102/09/H042 and P103/10/0306), the Czech Ministry of Education (projects COST OC10009 and MSM 0021630528), the European Commission (project IC0901), and the Brno University of Technology (project FIT-S-10-1).