Blinker with Flip-flop logic in a composite FB type in group util and named flipflop.
Tricks needed:
In 4DIAC
1. create the composite FB as desired
2. use the composite FB from the palette in an application
3. map application to FBDK device via System
3. map application to FBDK device via System
Before testing:
In 4DIAC preferences for FBDK
- add the group util to the list of packages
- open the xml for the composite function block
- Fix what ever it complains about. In this case:
- removed standard in
- removed xml statement
with no explicit beginning xml statement add imports needed (import fb.rt.hmi.*;) to Compiler Info / Header press Enter (lose what typed if forget) press OK button
- then save as and check XML and Java then the press the OK button
Ready to test in 4DIAC deployment using launch FBDK / (check appl) download.
Note: Received updated 4DIAC from Monika, because can't delete FB in composite FBs in last pre-edition.
Failed attempt: Composite blocks had a problem with spliting and merging events using connectors so tried with E_SPLITs and E_MERGEs. The updated 4DIAC from Monika fixed this problem, too.
Hi,
ReplyDeletecan you give me mor edatails on the spliting and merging problem. Thanks,
Alois
The updated 4DIAC from Monika fixed this problem, too.
ReplyDelete