Date: Fri, 29 Mar 2024 06:01:29 +0000 (UTC)
Message-ID: <109172489.129.1711692089236@6bf000190eb4>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_128_1102437763.1711692089236"
------=_Part_128_1102437763.1711692089236
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Online or Offline created 'boot application' have differ=
ent sizes
Online or Offline created 'boot application' have different=
sizes
The size of the boot application is different depending on the c=
reation method whether done 'Online' or 'Offline'.
The difference in boot application size results from the following assumpt=
ions:
When created offline, a default value for the communication's buffer is =
applied which may make the boot app larger than one created online.
Explanation
Offline generation:
- When a boot application is created offline, a default value for the com=
munication's buffer is applied.
- Since a determination with the PLC does not take place, a size is selec=
ted, which permits it in 99,9% of all cases these then with the Downloaden =
without problems to transfer to be able.
- This takes into account that there are also controllers which are equip=
ped accordingly "small".
Online generation:
- Depending on the hardware/PLC is determined/negotiated how large the bu=
ffer for downloading is, and the boot project is divided into corresponding=
ly large/fewer parts.
- This also requires less communication's headers and fewer splits in the=
code.
- This can be noticeable with significantly less code in the boot applica=
tion and therefore accordingly be smaller in size.
See also....
------=_Part_128_1102437763.1711692089236--