Question details

The problems are fixed in the FCB revision: 4.3/1 Additional information: The 31.12.2027 is the highest date in a time stamp that is supported by FCB.

POSSIBILITY TO CIRCUMVENT THE PROBLEM It has to be avoided that a time stamp in the ODB or target gets a date > 2000”. For this purpose you can modify the time on the computer running the FCB to a year <2000 for doing “Generate target Code” (off-line) or “Save and Load” (on-line)

Handling: • Modify time on the computer to year <2000 • Start FCB and do your work with the “critical” operations “Generate target Code” or “Save and Load” • Exit FCB • Change time and date back to correct value

Please note that you should always set a time later than the newest timestamp (i.e. don’t go back in time) and don’t modify the time during an FCB session. If you reduce the time by 1 day or more, while the FCB is running, the function “Dynamic display” will not work until FCB is restarted!

AdvaBuild for Windows, Function Chart Builder - Year 2000 problems in on-line mode The here mentioned problems are limited to the time stamps in the ODB and on the target and on the display of the target time in FCB, i.e. the internal clock of the target works correct. A timestamp is a data field that contains the date and time of target code generation or on-line change. This timestamp is kept locally in the internal database of FCB (ODB) and then also transferred to the target RAM and PROM of the controller in order to check, if on-line mode is allowed.

Detailed explanation Year = 2000 If the target time (internal clock in the controller) has year 2000,

• it is displayed as 1.1.78 0:00:00 in the “Set Date and Time” message box.

If a timestamp has year 2000, • it is displayed as “-” in the status report window.

Year >= 2001 After successful connection of FCB to an AC 100 series target, a Status Report is automatically displayed in FCB.

If the target returns a time stamp containing a year > 2000, all FCBs with version <= 4.3/0 cause a general protection fault.

That means, with FCB versions <= 4.3/0 you can never reach a target system with an application date > year 2000, even if the application is stored in FPROM. Reason: The Status Report shows the application date of the application in RAM as well as of the application in FPROM.

The application in RAM can be deleted by a cold start of the target system, the application in FPROM can only be deleted by FCBs target control function “Clear FPROM”.

As target control functions are possible only after connection and connection is not possible, there is no chance to access that target with an FCB version <= 4.3/0.