What are possible reason for having custom logic faults on TeSysT that has not been detected by SoMove compiler?
SoMove software with TeSysT DTM is not able to simulate complete TeSysT behavior. It can detect syntax errors, but writing a wrong value to an LTMR register is not implemented in a custom logic compiler. For example, if the new TEsysT few version allows a wider range for certain TEsysT parameters, the extended range can be easily implemented into DTM evolution (new DTM version) and so the configuration seen in SOmove will be consistent with TEsysT parameters. But the custom logic compiler is an extra package and does not often pass evolution (The last evolution was done together with TEsysT fw 2.5 when CALL_EOM instruction was implemented).
Based on experience, 99% of errors where the compiler says OK but TEsysT shows custom logic fault is caused by:
- missing "TMP" or "NV" text in the instruction
- wrong value (out of range) is written into LTMR register.
The rest of the errors shown are detected by SOmove compiler.
Based on experience, 99% of errors where the compiler says OK but TEsysT shows custom logic fault is caused by:
- missing "TMP" or "NV" text in the instruction
- wrong value (out of range) is written into LTMR register.
The rest of the errors shown are detected by SOmove compiler.
Gepubliceerd voor: Schneider Electric Belgium
Hulp nodig?
Selecteer zelf het juiste product
Vind snel en eenvoudig de juiste producten en toebehoren voor uw toepassingen.
Offerte aanvragen
Dien uw aanvraag online in en een expert zal contact met u opnemen.
Verkooppunten
Vind eenvoudig de dichtstbijzijnde distributeur van Schneider Electric op uw locatie.
Help Center
Vind de antwoorden die u nodig heeft via bladeren door veelgestelde vragen over onderwerpen.