Timer application

[kumuch]

Hi,

I am preparing for CLD. I developed code for CLD 14 timer application as per the attached document(Timer with pause functions using state machine) in CLD success package. During the execution, time consume more in one of the states so it wont switch into next state in given interval. so kindly find the attachment and give me the solution where problem occurs and how to resolve it.

Cheers,

kumuch

[natasftw]

It sounds like you've already isolated where the problem occurs.  You need to reduce the time taken in that state.

The packet includes a solution.  Take a look at what it does and try to understand what is different with your code and the working code.

Also, try to get away from llb.  Use projects instead.

You might find better advice using the Certifications forum.  People browsing those threads tend to be more focused on the kinds of questions you're going to ask leading up to your exam.

[kumuch]

Thanks for reply...

I know where the problem occurs but i dont know how to resolve it. can you help me? 

[billko]

---

@kumuch wrote:

Thanks for reply...

I know where the problem occurs but i dont know how to resolve it. can you help me? 

---

Did you try the suggestion about looking at the solution included with the sample?

[kumuch]

Yes, They give a solution using queued Message handler architecture. I tried to get a solution using user interface event handler with queue (pass the states). my doubt is to time delayed due to queue function or not ?.

[Hooovahh]

You may want to checkout the Certification board.  People there are quite familiar with the CLD and can probably help.  I'd also recommend staying away from LLBs.  For uploading just zip all of your files.

[BowenM]

Out of curiosity, why would you use message queue for a single one loop state machine? It seems like that would add needless extra complexity.

And for that reason, why do you have your 100ms delay set for every loop iteration instead of attaching it to your event structure. There are (usually) no problems with a loop spinning quickly as long as it is doing the processing needed. You just don't want it to spin out of control and hog up the CPU when it is doing nothing.

Edit: Oh, and your FGV also seems needlessly complex. I attached one I used awhile ago to do a very similar thing if you want to look at it.