The Software Toolbox Data Logger uses an object oriented architecture to provide you with flexibility. Because of the way the product is structured you can start out with simple text file logging and if your needs grow, you can move up to database logging without starting over in your project configuration
Strong OPC Support
• Collect data from any OPC Data Access 2.0 to 3.0 compliant server
• Collect data from any OPC UA Server that implements the OPC DA Profile
• Connect to 1 to N OPC servers
• Automatically re-connects to OPC Server.
• Works with local or remote OPC Servers - powerful DCOM timeout feature helps with remote connections
• OPC Interoperability tested
• Flexible formatting of data storage tables/records
• Flexible Logging & Rollover Options
• Trigger logging start/stop based of system event
• Import Tags from popular OPC servers for fast configuration - saves engineering time
• 32-bit multi-threaded architecture
• Diagnostic log for start/stop and errors
• Simultaneous logging to multiple output types
• Runs as a Windows Service to auto-start on reboots
• No tag count limits
• Licenses start at $595 - Click for Pricing
• Special bundles available that include one of our OPC Servers that can connect to over 70 different device types
• Multi-machine volume licensing available
The OPC Data Logger is packed full of Wizards that make configuration extremely easy. Its ability to browse and choose multiple OPC items makes configuration fast. Its use of standard text and database files along with a proven OPC Client makes it open to use in almost any situation or location. Upon first opening the OPC Data Logger Configuration, the user is prompted to begin a Project Wizard, which houses inside of it 4 other Wizards for ease of set up throughout the entire configuration process. These wizards help with the setup of:
Configuring a Collector (OPC Server) that will tell the OPC Data Logger where to retrieve data from
Configuring a Storage medium
Determining how the data will be presented when it is logged, including direct mapping to database tables
Setting up logging triggers
The OPC Data Logger must run as a service to log data beyond simple testing. There is no option to run in an application mode. The data-logger has been designed this way to allow for automatic restarts on failure or shutdowns. It also allows the administrator to secure the service from being tampered with or shut down by users.
You can setup the service run options during the installation. This gives you the option to run the service automatically at startup or allows you to manually run at startup.
If you have selected to auto start the service selection during installation, then in the service menu it will be set to Automatic. If the auto start is enabled and the service has not been manually stopped you will see the status as started and the startup type as automatic.
If manual startup has been selected, the service does not automatically start during startup. In the service manager you will see the startup type as Manual and the status will be stopped, unless it has previously been started. You can right click the service and click start. Or you can start the service using start menu – launch Data Logger service.
The OPC Data Logger has the ability to interface with multiple OPC Servers simultaneously. Any OPC Server that has been certified by the OPC Foundation can be used as a Collector for Data Logger. The current version of the Data Logger supports OPC DA 2.x or 3.x, as well as OPC UA that also supports the OPC DA profile. The architecture of the Data Logger gives it room for future expansion of data sources.
Data Logger has the ability to simultaneously output information to multiple destinations seamlessly. With a single license comes unlimited potential for organizing and storing your data. Groups of items can be configured to log to one or multiple destinations, different tables in a database, or completely separate text files.
With our modular licensing model, you have the ability to log to text files, SQL databases, Access & Oracle all side by side in one standalone application.
In the Data Logger, there are two formats for which data can be organized prior to being logged.
Table mode organizes data by timestamp; all data points that were read at a certain time stamp will be logged in columns. No quality information will be logged, only the timestamp and value of each data point.
Detail mode organizes data by tag. Each tag will have its own row with the value, quality, and timestamp of each item that is being logged.
Both of these styles of presenting data can be mapped to database tables. Data Logger has a verification step when creating your tables that will test the data types configured with those that can be accepted in each cell of the database table. This provides a good check step prior to logging.
Data Logger allows you to specify an item from your collector to monitor, and will trigger any number of configurable events. It can be used to begin logging, end logging, enable or disable groups of items, or even launch file spanning based on an item’s condition. Some example use cases would be:
A scheduled trigger leverages the power of the Windows Scheduler service, and allows you to specify a date and time to start or stop logging, enable or disable groups of items or to launch a file spanning event.
•Log end of shift of end of day report data
•Start a new log file at the end of a shift or day
•Log weekly data
•Log monthly data
•Schedule different groups of data to be logged at different time.
Overview: See Example Configurations in the on-line help
A trigger is a mechanism that allows you to configure when the OPC Data Logger should begin or end logging or start a file span event. Triggers can be used together to create multiple logging behaviors in one process.
The Data Logger contains several types of triggers. Each trigger is an identifier that signals when or under what condition events occur:
•End logging, or
•Launch file spanning event.
Every trigger type is capable of signaling each event type.
The trigger types are Scheduled (at a given time), Recurring (repeating at a given interval), and Monitored Item (based on a value of a monitored tag). You can define one or multiple of any or all types of these in your project. Any or all types of triggers can be enabled for use simultaneously.
Exception based logging is the most reliable form of logging data. It allows the OPC Data Logger to read by using a subscription. This means that the data source will continuously poll the target device/PLC and will notify the application when values change. Because the target device/PLC is always being polled, the data will always be fresh. Also, because the application is receiving the value change event notifications only, it will help with resources and bandwidth between the two systems. Subscription based reads can be selected in the group properties and the polling interval is customizable by milliseconds, seconds, and minutes.
The OPC Data Logger has the capability of using stored procedures as a means to log data to a database. A Stored Procedure is a group of Transact-SQL statements compiled into a single execution plan. Stored Procedures offer the highest performance due to their nature of being pre-compiled. To use a stored procedure in OPC Data Logger the corresponding tables and procedure must already exist within your database.
Stored Procedures can be selected in the database configuration window from the dropdown under the storage tab.
If Data Logger loses connection to a database during the logging process, there is a configurable size buffer that will hold all information until the connection is re-established. A standard “store and forward” method is employed for this buffer in the application space of Data Logger.
A Writeback is a mechanism that allows you to assign a value to an OPC Item when a condition is met or a certain event is fired.
Configuring a Writeback is done by:
• Adding a Writeback
• Adding OPC Items
• Removing a Writeback
Writebacks uses are with:
• Database Logging
• Text File Logging
• Writeback: The read-only name of the writeback.
• Enabled: Enables and Disables the effect associated with the writeback.
• Cause: Three choices for when the writeback will be sent.
• Description: An optional entry to describe the action of the writeback.
• Add: Lists: all configured writebacks and allows them to be added.
• Remove: Remove Selected or Remove All writebacks.
• Properties: Opens the properties pages for the highlighted writeback.
The OPC Data Logger tool can be used with Dream Report to generate reports. This reporting tool can extract the data from any ODBC database and create data statistics, as well as display analytical data in multiple views like tables, bars graphs, pie charts and more. Dream Reports interactive studio allows you to interface with the data collected by Data Logger into an intuitive graphical editor allowing the user to create custom templates. Dream Report also allows you to generate reports automatically, this allows you to schedule or create an event based report.