Application Testing
HW mapping determines what applications will be run during deployment.
Usually just 1 application, so can unmap all but 1 application to test.
OR connect the INIT of next application to be tested to output event of previous application.
Then they run at same time.
4DIAC-IDE preferences FORTE location:
default with no additions: C:\...\4DIAC-IDE_0.3\runtime\FORTE\FORTE_0.3.6.exe
with applications compiled into:
C:\...\FORTE-0.3.6\FORTE_0.3.6\bin\pc\src\forte.exe
HW mapping
STD mapped to: FBDK.VIS_IN
BFB mapped to: FBDK.VIS_IN; FORTE.EMB_RES; FBDK.VIS_OUT
CFB mapped to: FBDK.VIS_IN; FORTE.EMB_RES; FBDK.VIS_OUT
SFB mapped to: FBDK.VIS_IN; FORTE.EMB_RES; (out via fprintf on bash console)
4DIAC Export:
Only Function Block types are exported.
When Export there is an option to merge old and new source.
Testing via Deployment:
STD: Launch FBDK (FORTE not used)
BFB: Have input but not used for output
CFB: (will be similar to BFB)
SFB: not sure how / where C++ code gets/ has values of x and y variables
What is OUT.operator ? Why not just OUT like in the calculation.
Given a 4DIAC-IDE 3.7 bug fix pre-release
Common Error: Event not connected to variable so don't see input.
Etc.
cygwin bash had problems finding the dll?? Thought might be from install of the RCX simulator, but restart of windows seems to have fixed the problem.
No comments:
Post a Comment