|
| Re: New composite type [message #1724592 is a reply to message #1724539] |
Wed, 24 February 2016 20:33   |
|
Unfortunately currently for both 4DIAC FORTE and FBRT you need to compile all types. The only option you could go is with subapps. I don't regard subapps as dirty option. There are certain use-cases where even composite FBs can not be used or are not appropriate (e.g, you need to distribute parts to different devices, you need to perform instance specific internal parameters).
The only drawback of this solution is that currently no tool really supports sub-applications as they should be supported. Any help on this topic is greatly appreciated.
|
|
|
| Re: New composite type [message #1755595 is a reply to message #1724592] |
Mon, 06 March 2017 09:00 |
|
|
What is the basic difference between Composite FB type and SubAppType? I think they are very similar to each other. It may be better to use the model SubApp for Composite FB and generate internal FBs in 4DIAC instead in FORTE.
|
|
|
| Re: New composite type [message #1755657 is a reply to message #1755595] |
Mon, 06 March 2017 15:49 |
|
Hi,
The main difference is that the content off subapplications can be distributed to different devices. This allows to do different things then CFBs. CFBs are atomic and for a user not destinquischable from Basic or SIFBs. SubApps are transperent and you can look in side. Especiaylly with the untyped subapps this get very interesting for structuring applications.
Alois
|
|
|
Powered by
FUDForum. Page generated in 0.04104 seconds
] 
Search
Help
Register
Login
Home
