There was some discussion recently on using the AIM* OPC servers. How do you all recommend or actually implement your architecture to get around the timezone problem in IA? Let's pretend we have and AW70 w/ AIM* OPC server and a standard OPC Client on a different (windows) machine: [AW70 w/ AIM*OPC server w/ GMT timezone] <----> [windows box w/ OPC Client w/ EST timezone] A standard OPC Client will not display the values with the correct timestamp as the OPC server will present the data with a timestamp of GMT. The simplest solution is to change the timezone on the AW70 to what your actual timezone. However, to my knowledge this is NOT a supported configuration as explicitly stated in the IA Documentation. You could change all your clients to GMT, but who wants to do that? You could keep your IA system in GMT w/ clients in EST, but then you'd have to change your IA system to the time it really is in GMT. And who wants to do that? You could cludge an OPC client to ignore timezone, but then you won't be able to use standard vendor stuff and basically defeats the purpose of OPC. And who wants to do that? just wonderin' chris. chris browder __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave