WebDAQ 904
The MCC WebDAQ 904 is a stand-alone, universal input data logger designed for remote monitoring and control. All the intelligence is built into the WebDAQ, eliminating the need for a PC or additional software. By using the embedded WebDAQ web server, users can easily configure simple or sophisticated applications, log data, update digital outputs and/or send notifications based on alarm conditions, and view real-time data from any location and any device with a web browser. The WebDAQ 904 performs high-accuracy measurements from up to four analog inputs. Users can measure several signals from sensors such as strain gauges, RTDs, thermocouples, and load cells. Four isolated digital bits can be used as trigger inputs or alarm outputs. Housed in a heavy-duty chassis, the WebDAQ 904 is rugged enough for industrial applications.
There are three devices in the WebDAQ Series. Devices are available to log multiple signal types including voltage (up to +/-60 V), thermocouples, IEPE-based sensors like accelerometers, current, RTDs, resistance, and bridge-based sensors.
The WebDAQ Series embedded OS and web server provides an all-in-one package for stand-alone data logging and alarming. Users can monitor and control their applications from anywhere with a web browser. The WebDAQ web server is optimized for both desktop and mobile use. Users can perform data acquisition tasks from phones, tablets and laptops with a single, intuitive user interface.
For users requiring more custom functionality than is provided by the web browser interface, a RESTful API is provided to start and stop an acquisition, retrieve data in real-time, access information about the system, schedules, and jobs, and to get the status of an acquisition and alarm(s). With the RESTful API, data from WebDAQ devices can be displayed on any popular data dashboard, cloud application, or custom program.
Getting Started
Documentation
Additional Resources
Q&A
- Is it possible to connect a 2-wire RTD to this device?
-
The manual for the WebDAQ 904 only specifies the correct wire configuration for 3 and 4-wire RTD's, so I'm wondering what the required channel inputs are for a 2-wire RTD on this device.To use a 2-wire RTD, you can select the 3-wire RTD mode, but you also must add your own shorting wire between pin 5 (EX-) pin 6 (CH-).
- When will the REST API be documented so data can be accessed directly with third party applications
-
I would like to be able to access the measurement data using a web application, and being able to request data from the device would be ideal. Such as: receiving a string or JavaScript object in return. The REST API was mentioned in another post 24 months ago. The WebDAQ series are primarily stand-alone loggers, with data collected to its local non-volatile memory storage. To receive relatively-live data from the currently running job over the network, the REST API can be used by a programmer. We provide REST API examples in LabVIEW, C#, VB, and Python. The REST API is considered fully documented now, but note that the logger must still be configured manually. So while a 3rd party application (such as a LabVIEW app) cannot configure the logger, it can start, receive data from, and stop the logger.
- Can digital I/O be recorded concurrently with thermocouple data?
-
Can the state of the digital I/O port be recorded along with the temperature data from the thermocouples? For instance, if one of the digital I/O were configured as an input to track an external event, would that information show up in the plotted data through the Web UI and in the recorded data file?Thank you for your question. The digital I/O on the WebDAQ 904 operates asynchronously to the thermocouple input channels. Therefore, because of the difference in their clock signals, concurrent data logging of both the thermocouple inputs and digital inputs cannot be supported. At present, the digital I/O is supported in the form of a trigger event or alarm condition (input) or an alarm action (output).
- Real-time temperature measurement through Ethernet interface
-
Is it possible to perform a real-time temperature measurement using a Windows-based program? I am trying to consolidate temperature measurements from different resources and would like to create a library allowing me to perform temperature measurements “on demand” via a Windows-based application. I would like information on available libraries and APIs… Thanks!Thanks for the question. The easiest way to bring WebDAQ data into a 3rd party application today is to use the Server Message Block (SMB) Protocol to read the data file on the WebDAQ as it is being updated. SMB access is a Beta feature right now, so please let us know if you would like to try this and we will send you a firmware image to install on your device. In the future, MCC will document the subsection of the WebDAQ REST API that will allow applications to access data directly from the DAQ service running on the WebDAQ CPU. After releasing this API, MCC will provide examples with source code for accessing WebDAQ data from various programming languages and applications. Please let us know what 3rd party application or programming language you would like to support and we will evaluate the effort needed to support this through the REST API.
- Can the number of channels be increased?
-
Is there an expansion unit available?The WebDAQ 904 logger is self-contained, with no expansion option. Multiple WebDAQ 904 loggers can be configured to start at the same time, with data from each displayed on a separate tab in the same web browser.
- Access from the web
-
How do I access the WebDAQ from outside the LAN over the Web?One way to access a WebDAQ remotely is via VPN. Alternatively, you could assign it an IP address that is on the internet. Such an IP address can be obtained through router configuration (port forwarding of HTTP port 80) or by plugging in the WebDAQ directly into a cable modem.
- Power on support for WebDAQ?
-
Is there a way to restart the WebDAQ in case I lose power and it is in a remote location?Yes; remove the onboard jumper W1 to start the WebDAQ whenever the power adapter is plugged in and receiving power. If a power loss occurs, the device will restart automatically when power is restored. You may also want to configure the Schedule to start on power up so it runs when power is restored.