Address on bad boundry error in praviously compiled citect project

Hello All,

We have citect project compiled and running in version 5.42.

We do a small change in graphics screen, no additional variable were added, then on compilation we are receiving errors like "Äddress on bad boundry".

Communication driver is S7 NT and in ini file settings to avoid above error keys is already configured.

 [GENERAL]
CheckAddressBoundary=0

We pack project, then do a full compilation but still citect copiler keep on giving same error.

Kindly advice.

regards

Hemant JADHAV

Parents
  • In your version of Citect, it kept citect.ini in c:\windows. Make sure you are editing the correct file.

    I noticed that if you go to the Citect Explorer | View menu | Configuration File, it may display the citect.ini from your project instead of the one in the Windows folder.

    There were also issues in Citect v5 where it could use some parameters from citect.ini in your project folder and some from c:\windows\citect.ini. Make sure to delete citect.ini from your project folder.

    When you make project backups using the 'Save System Files' option, it copies c:\windows\citect.ini into the project backup, and when you restore the backup, you end up with an old copy of citect.ini in the project. In newer versions of Citect that doesn't hurt anything, but in v5 it can be a problem.

Reply
  • In your version of Citect, it kept citect.ini in c:\windows. Make sure you are editing the correct file.

    I noticed that if you go to the Citect Explorer | View menu | Configuration File, it may display the citect.ini from your project instead of the one in the Windows folder.

    There were also issues in Citect v5 where it could use some parameters from citect.ini in your project folder and some from c:\windows\citect.ini. Make sure to delete citect.ini from your project folder.

    When you make project backups using the 'Save System Files' option, it copies c:\windows\citect.ini into the project backup, and when you restore the backup, you end up with an old copy of citect.ini in the project. In newer versions of Citect that doesn't hurt anything, but in v5 it can be a problem.

Children