| Timer not started in the context. [message #1795908] |
Tue, 02 October 2018 08:33  |
 Julien Deltour
Messages: 6
Registered: September 2018 |
Junior Member |
|
|
Hello,
Still working on the ITS testsuites.
In the test TC_CAM_MSD_GFQ_TI_01, the function f_CAM_MSD_GFQ_TI_01 is called:
In this function, a timer is declared :
timer t_minTransInterval := PICS_T_GENCAMMIN * 0.90;
Then this timer is started in a branch of an alt :
alt {
[] camPort.receive(mw_camInd ( mw_camMsg_any )){
tc_ac.stop;
t_minTransInterval.start;
log("*** " & testcasename() & ": INFO: Initial conditions: First CAM message received ***");
I'm sure I go in this branch, I have got the log.
Then a function is called with this timer as parameter, and this is in this new function than the timeout is checked.
But when I run my test, I have an error message telling :
Timeout operation on timer t_minTransInterval failed: The timer is not started.
It looks lire there is a scope error, but is it the testsuite ou Titan ? In the standard, I see than "Timer references have meaning only within the test component instances where the timer is defined" and in my case, I am still in the same component.
Julien
|
|
|
|
| Re: Timer not started in the context. [message #1795917 is a reply to message #1795908] |
Tue, 02 October 2018 10:57  |
|
Hello Julien,
The scope of your timer "t_minTransInterval " is the body of function "f_CAM_MSD_GFQ_TI_01()".
If you want to see your timer within the whole component, move its definition into the definition of your component type, this way ( On module level):
type component CT{
timer t_minTransInterval := PICS_T_GENCAMMIN * 0.90;
port PCOType camPort;
}
BR Jeno Balasko
|
|
|
Powered by
FUDForum. Page generated in 0.02061 seconds
] 
Search
Help
Register
Login
Home
