Slow screen switching

[Jerry B]

I'm using a DP200. It is taking around 10 seconds to switch between areas except for the back button which resets the latches.

Each of the Areas has a screen being brought up that has between 10 - 30 references to signals feeding data read from CAN messages. One of the pages has a page within a page. There is some number crunching and formatting going on for the data.

Is the Area switching waiting for all the data to be ready for the screens before switching, or is the logic for the Area control getting hung up somewhere to take that long?

Soft buttons 2-4 all bring you to a new page. Button 4 is used as a back button for each of the pages. SW_BATTSET is the trigger for the page within a page linked to soft button1. Any help with logic to have this run faster would be appreciated. The areas linked to Latch 2-4 are enabled on a true signal.

[FluidPowerTom]

Do you have any high quality images on the pages?  It could be taking a while to render those, so if that's the case then they could be reduced in pixel size.

[Jerry B]

No. The areas are white backgrounds, and the screens are just text, lines, and a bunch of CAN data that has been received and possibly modified.
The "back" button, soft button 4 (that resets all the latches), works within a couple seconds to get back to the main page.

[Neil]

Are you using an enabled signaled on the images found in the in the inspector tab in the screen page?
These call the image on screen selected.
Suggest also using check points and measure the delay within the P1P.

[niteRider]

What's your loop time?

[BRIan]

I have come across this before. Make sure you have the latest hwd file and set the OS.ExecTimeOut to 40ms (Ack to the HelpDesk on this one)

[Jerry B]

@BRIan, THANKS! I had the latest hwd file, but changing the OS.ExecTimeOut from 10 to 40ms did it. Really appreciate the help.