(* *)
(* *)
(* *)
(* *)
(* *)
(*--------------------------------------------------*)
(*##################################################*)
(*##################################################*)
8.5.6
History
The history documents changes in the code.
The completely filled history contains the following pieces of information:
●
Version
●
Name of the programmer
●
Date of change
●
Description of change
The header should be written in English.
Using the history is highly recommended.
The template below can be used to achieve a uniform history. To do this,
copy the text to the clipboard. Then paste the content of the clipboard into
IndraLogic at the end of the declaration.
If pasted at the end of the declaration, the history is no longer visi‐
ble when the user changes to the tabular view and subsequently
makes changes in the declaration.
If Declaration in table form has been selected in the IndraLogic
editor, you have to paste the content of the clipboard under the
"Info" tab page, directly after the header.
History template
Program:
(*##################################################*)
(*Modification - History*)
(*--------------------------------------------------*)
(* Version : *)
(* Name : *)
(* Date : *)
(* Comment : *)
(**)
(* Version : *)
(* Name : *)
(* Date : *)
(* Comment : *)
(**)
(* Version : *)
(* Name : *)
(* Date : *)
(* Comment : *)
(*--------------------------------------------------*)
(*##################################################*)
8.5.7
Type identifiers
General information
Standardized naming of types increases the legibility of the program code.
This makes it much easier for third persons to become acquainted with the
code and reduces the time required for troubleshooting.
In principle, we distinguish two types:
Bosch Rexroth AG
DOK-INDRV*-MLD3-**VRS*-AP02-EN-P
224/267
Rexroth IndraDrive Rexroth IndraMotion MLD (2G) as of MPx-18
Programming information
LSA Control S.L. www.lsa-control.com [email protected] (+34) 960 62 43 01