Hi Steve,
Thanks for the suggestion given. really appreciate it... is there a simpler way to it other than using the hardware in the loop as you suggested? Hardware in the loop is quite advanced at this stage...
For the timeout wise if I adjust the timing by lengthening it to 10 seconds in the AE itself configuring the Modbus Initialisation Part API. do you think it might help solve it or I have a wait in the action cases itself to give it sufficient time instead?
To answer your questions on the free-running loops, the program does not read the enable VSD command when I place the AE alone in the Action Cases, hence I have to poll it and have a timeout for 5 seconds after the program read it and it moves on to the next action case after that ... true enough the program might be hard to follow as it took me quite a while to get the hang of it, the action queue is needed to define the queue in the QMH Loop, where the state logic enqueues the action and dequeues the various action in the action cases, hence is quite important in this template itself...