Maloperation of baseChannel methods in the ApplicationTemplate (corrected from V3.9)

Corrected from:
PLC Designer V3.9
L_EATP_ApplicationTemplate library V3.9
 
Response of the new version:
The removal of the function restriction, which has already been implemented with the library attached to this AKB contribution, is now part of the latest library version delivered with PLC Designer V3.9.
 
What happens?
  • PLC processing stops with an exception.
  • Variable values change unintentionally.
  • baseChannel methods do not work.
When does this behaviour occur?
  • If one of the methods baseChannelDisableQSPFollowing, baseChannelSetErrorQuit, and baseChannelSetNominalState is not called with its own module address (MM_Address unequal L_EATP_CONST.OWNID), the PLC memory may be corrupted as a result. This may lead to an unintended change of variable values up to a stop of PLC processing with an exception.
  • All baseChannel methods which have a module address (MM_Address) as first parameter do not work if their own module (L_EATP_CONST.OWNID) is not assigned as module address.  
Which products are affected?
PLC Designer from V3.8
L_EATP_ApplicationTemplate library V3.8.0.7
 
Short-term measures/recommendations:
Go to the library manager of your PLC project and check if L_EATP_ApplicationTemplate library V3.8.0.7 is used. If so, replace the library in the PLC project as described in the attached update description by the L_EATP_ApplicationTemplate V3.8.2.7 library attached to this contribution.
  
Evaluation:
The function restriction may occur if the ApplicationTemplate is used in a PLC project and L_EATP_ApplicationTemplate library V3.8.0.7 is used. This library version is delivered with PLC Designer V3.8. Lenze recommends to replace this library version in the PLC project by the library attached to this AKB contribution.
The function restriction does not concern the ApplicationTemplate PackML.

URL for linking this AKB article: https://www.lenze.com/en-de/go/akb/201400254/1/
Contact form