Incorrect checksum of B & R module when downloading program and DIAG mode

Ask Questions
,
4

Hi Sergei,

According to the online help, 6405 is entered if the precalculated checksum of the B&R module is not corrected, i.e. the file of the module is corrupt. This is detected during start-up.
This error cannot be ‘repaired’ unless the file is rewritten (e.g. by writing to the flash).

https://help.br-automation.com/#/en/6/diagnostics_support%2Fsys_error%2Ffiles%2Fsyserror_br2000_6405.htm

In contrast to that, there is error 6403, which is entered if the module in DRAM was destroyed during runtime.

https://help.br-automation.com/#/en/6/diagnostics_support%2Fsys_error%2Ffiles%2Fsyserror_br2000_6403.htm

In this respect, it can be assumed that ‘something’ destroys your file system during or directly after the download.

In both cases, a page fault could be the cause.

Possible remedy:

  • Use the ‘safe file system’
  • Use IEC Check / AdvIecCheck library

Do not hesitate to contact the local B&R support. Further questions may arise:

  • are always the same module(s) affected
  • which module types are affected
  • are the affected modules created during runtime (e.g. data objects)
  • are there some more logger entries

btw:

Do you already know ‘AdvIECcheck’ library ? (unfortunately not helpful when using C/C++)