Problems with Date SystemIO

I would be grateful for any suggestions on what the problem is with the way I am using a date-type user system IO. It all works fine on my laptop in simulation mode but once downloaded to the touchscreen, it fails to function. The original intention was to create a "return from holiday" date which would re-awaken the heating schedules.

To aid diagnosis I created a blank test page with one test component.

On the test page I placed a clock component whose properties are set to display a system IO time (system IO date is not presented as an option). The system IO properties tab is set to display the status of the user-defined date-type system IO variable called "test"). I note from the the help file that the B&W touchscreen can't cope with dates before 1/1/2000. Screenshots attached below.

In simulation mode on the laptop all is good. Transferred to the screen the component just displays 1/1/2000. In the original "Holiday Return Date" page, I was using the day/month/year increment/decrement button functions to change the system IO value. These buttons usually failed to change the date on the touchscreen though sometimes the date would jump to something in 2069. All worked flawlessly on the laptop.

In case it's relevant I have attached the Windows XP regional date/time option dialog.

Touchscreen is SC5000CTL2,WE
Hardware version 1.0, Cbus firmware ver 5.1.00 Ctouch firmware ver 3.43.0 PICED 4.7.0.0

Any ideas?

Phil

 

What's 100 years amongst friends

Hi,

What's happening here is some confusion between PICED and B&W C-Touch with the base date. PICED uses days from 1/1/1900 and C-Touch uses days since 1/1/2000.

For now, you can work around this by setting the date of the User SysIO back 100 years in PICED. You'll need to set:
- Min Date = 1/1/1900
- Max Date = 21/12/1999
- Value = Today's date - 100 years (14/12/1909 today)

We will get it tidied up so it all hangs together properly. Sorry for the hassle...
Mark.

 

I always knew I was 100 years ahead of my time....

Thanks for the speedy reply, I'll try the work-around.

Phil

 

Did this ever get fixed?

Hi

Did this ever get fixed?- I can't find a reference to #18324 in the PICED revision history.

The reason I ask is that I'm currently using the workaround you suggested (which does the trick). I may need to upgrade my Toolkit/PICED/CIRCA version. It would be useful to know if I will need to undo the workaround after the upgrade.

Cheers

Phil

 

This was fixed in firmware V3.50 (shipped with PICED V4.8).

For some reason it was not listed in the firmware version history.