
5.8.2 How do application program run on each equipment
In this section, how each task of the application program runs is described.
(1) FS300i with PC
Status of CNC & PC Status of C-EXE application
-------------------- ------------------------------
PC starts
│
v
CNC starts -------> Auxiliary tasks start [1]
│ │
v │
"CNCscrnApp" starts ------------> Main task starts [2]
│ │ │
│ │ *---> Window task starts
│ │ │ [3] │
v │ │ │
"CNCscrnApp" ends ----------------------> x - - - - - > x
│ │ .[4] │[5]
│ │ . │
v │ . │
"CNCscrnApp" starts --------------------> x - - - - - > x
│ │ │[6] │[7]
│ │ │ │
v │ │ │
"CNCscrnApp" ends ----------------------> x - - - - - > x
│ │ .[4] │[5]
│ │ . │
v v v v
[1] Auxiliary tasks start at CNC system start-up time. After started,
they run as same as on the ordinary FS30i. Because the main task and
the window task don't run until "CNCscrnApp" starts for the first
time, auxiliary tasks can't communicate with the main task or the
window task. Except this, it is not necessary for auxiliary tasks to
take care of whether CNC screen is displayed on PC or not.
(Auxiliary tasks may not exist.)
[2] The main task starts at the first time "CNCscrnApp" started. After
this, it runs as same as on the ordinary FS30i until "CNCscrnApp"
closes. Until then, the main task runs during displaying C-EXE
screen and it sleeps during displaying CNC's screen.
[3] The window task starts when "os_strt_wtsk()" function is called in
the main task. After this, the window task goes on running whether
CNC's screen is displayed or not.
(The window task may not exist.)
[4] The main task goes sleeping when "CNCscrnApp" is closed. This status
is same as the screen is changed to CNC's screen. If C-EXE appli-
cation inhibits screen changing, "CNCscrnApp" can't close itself.
The application program should sometimes enable to change the screen.