39707 How To Configure An RSView Data Log Model To Log To A Microsoft Acce...

Page 1 of 1

Rockwell Automation Support Center 39707 - How To Configure An RSView Data Log Model To Log To A Microsoft Access Database Using ODBC
Access Level: TechConnect Date Created: 05/04/2007 04:40 PM Last Updated: 04/21/2010 05:55 PM

This document provides step by step instructions on how to configure an RSView Data Log Model to log to a Microsoft Access database using ODBC. This example was done using Windows Server 2003 with Microsoft Office XP. Regardless which ODBC database you are using, for example, SQL Server 2000, steps 12 thru 23 (below) will be the same. 1. Go to Control Panel and double click on Administrative Tools 2. Double click on Data Source (ODBC) to launch the ODBC Data Source Administrator 3. Select the System DSNtab 4. Click on Add on the right 5. Under "Select a driver for which you want to set up a data source" select the "Microsoft Access Driver (*.mdb)" 6. Click Finish 7. The ODBC Microsoft Access Setup window will come up 8. Type in a desired Data Source Name. For example, Sample_ODBC (It is important to remember the Data Source Name since you will have to enter that name in the RSView Data Log Model configuration under ODBC Data Source in step 15 below) 9. Under Database, either click on Select to select an existing mdb file or click on Create to create a new mdb file in a location of your choice. When done hit OK 10. Hit OK to save and exist out of the ODBC Microsoft Access Setupwindow 11. Hit OK to save and exist out of the ODBC Data Source Administrator window 12. Open your application in RSView Studio 13. Using the Explorer tree on the left, under the desired HMI server, expand Data Log, right click on Data Log Models and select New 14. Under the Setup tab, highlight ODBC Database instead of File Set 15. Type in the ODBC Data Source name from step 8. The example used is Sample_ODBC. 16. Type in a name for each of the three tables that will need to be created. You will need a name for the Tag Table, a name for the Float Table and a name for the String Table. The three fields are usually pre-populated with the default names, TagTable, FloatTable and StringTable. 17. Whether you keep the default names or create new names for the three tables, go ahead and click on Create Tables and hit OK to the RSView Datalog Editor window that pops up stating that the ODBC tables were successfully created. 18. The Paths tab is to configure an ODBC Backup Path if desired 19. The File Management tab is used to Purge Oldest Records in the ODBC Database if desired to do so. 20. The Log Triggers tab is used to set this Data Log Model to either Periodic, On Change or On Demand. By default it is set to Periodic with an Interval of 10 Seconds 21. Finally, under the Tags in Model tab, add the tags to be logged 22. Hit OK on the right to exit, give this Data Log Model a name under Component name, for example, NewODBCModel, and hit OKagain. 23. To start logging, simply issue the following command: DataLogOn NewODBCModel

DISCLAIMER This knowledge base web site is intended to provide general technical information on a particular subject or subjects and is not an exhaustive treatment of such subjects. Accordingly, the information in this web site is not intended to constitute application, design, software or other professional engineering advice or services. Before making any decision or taking any action, which might affect your equipment, you should consult a qualified professional advisor. ROCKWELL AUTOMATION DOES NOT WARRANT THE COMPLETENESS, TIMELINESS OR ACCURACY OF ANY OF THE DATA CONTAINED IN THIS WEB SITE AND MAY MAKE CHANGES THERETO AT ANY TIME IN ITS SOLE DISCRETION WITHOUT NOTICE. FURTHER, ALL INFORMATION CONVEYED HEREBY IS PROVIDED TO USERS "AS IS." IN NO EVENT SHALL ROCKWELL BE LIABLE FOR ANY DAMAGES OF ANY KIND INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS PROFIT OR DAMAGE, EVEN IF ROCKWELL AUTOMATION HAVE BEEN ADVISED ON THE POSSIBILITY OF SUCH DAMAGES. ROCKWELL AUTOMATION DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED IN RESPECT OF THE INFORMATION (INCLUDING SOFTWARE) PROVIDED HEREBY, INCLUDING THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, AND NON-INFRINGEMENT. Note that certain jurisdictions do not countenance the exclusion of implied warranties; thus, this disclaimer may not apply to you.

This page is best viewed in Internet Explorer 7, Firefox 3.5, Chrome 4, Safari 4 or newer.

http://rockwellautomation.custhelp.com/app/answers/detail/a_id/39707

1/20/2012