Feb.8 Gleaning 61499 details from X2Y2 Tutorial

Started a clean 4DIAC system to help my understanding of what is exactly happening: 
(which it has) 

IEC6144 devices can execute 1499 so FBDK and FORTE are virtual devices.
On a pc they simulate the behavior of a control device.

On a real control device like lego they are performing the task of a device.

IEC61499 resources  are created in a device
Service Interfaces to "devices" that can't run 61499 use Service Interface blocks to send/receive messages. SIFBs are also used for accessing stuff outside of a 61499 device like sensors, motors, and even things like databases.


The 4DIAC-IDE FORTE preference should point to where the forte application is that is updated by Eclipse. That could be some bin\pc\src\FORTE_ver#.exe

• in 4DIAC directories:  (ex:...runtime\bin\pc\src\FORTE_0.3.6.exe)    
• default currently C:\Training\forte_mc\bin\pc\src\forte.exe -  (doesn't exist by default)
• location of FORTE version used: (ex: .....\FORTE_0.3.7\bin\pc\src\forte.exe)
• If Project copied into Eclipse workspace, then its of course the Eclipse workspace:            (ex: .....\workspaceX2Y2\FORTE_0.3.7\bin\pc\src\forte.exe)

4DIAC-IDE workspace contains the XML files for each project and its applications, the system configuration, and the device mappings.


4DIAC User Interface annoyances / funnies :

• When add a fb type doesn't show up right away in list, but its there. 
• Drag/ Drop for Composite Function Blocks: 
• didn't allow dropping except on left bottom 
• plus connectors didn't connect if instances moved before connecting
• after connecting drag/drop was allowed anywhere

Standard connections: Connect all:

• INITOs to next logical INIT and first INIT connected to cold START (in System Config)
• QOs to the next logical QI and first QI initialized to 1
• for X2Y2 tutorial: associated CNFs or INDs to next logical REQ

Standard Pallet events: Usually REQ goes with CNF in the same device and IND if REQ is from another device.