WebDAQ 316

Under Construction!

Buy Reference Manual Technical Support
WebDAQ 316
Internet Enabled Thermocouple Data Logger
Analog Input
16 thermocouple
Max Sample Rate
75 S/s/ch
Digital I/O
Memory Options
Internal 3GB, optional SD card, and USB slots
External AC Adapter (Included)
Product Compliance

Digilent is now a proud distributor of Measurement Computing Corporation (MCC) DAQ and data logging products. MCC is a leading supplier of data acquisition solutions that are easy-to-use, easy-to-integrate, and easy-to-support.

The MCC WebDAQ 316 is a stand-alone, temperature 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 temperature 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 316 provides 16 isolated thermocouple inputs, and four isolated digital bits that can be used as trigger inputs or alarm outputs. Housed in a heavy-duty chassis, the WebDAQ 316 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.

MCC is a leading supplier of data acquisition solutions that are easy-to-use, easy-to-integrate and easy-to-support. Digilent has partnered with MCC and we now offer MCC DAQ and data logging devices on the Digilent website.


  • WebDAQ 316 Datasheet
  • WebDAQ 316 User Guide
  • WebDAQ Quick Reference
  • MCC DAQ Selection Guide


  • WebDAQ REST API Examples zip file
  • WebDAQ mounting installation
  • WebDAQ Web Interface Application
  • WebDAQ Web Application Help File

Additional Resources

  • WebDAQ Firmware Update
  • SERI 316
  • CE (EU Declaration of Conformity)


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 concurrent 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 316 operates asynchronous 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 O/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 316 logger is self-contained, with no expansion option. Multiple WebDAQ 316 loggers can be configured to start at the same time, with data from each displayed on a separate tab on 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.
ref: 75 S/s per second, is that simultaneous for all channels?
One correction: in the high-speed mode, the sample rate is 75 S/s per channel. Still, the sampling is not simultaneous (one A/D converter is shared).
The supported sample rate for the WebDAQ 316 is not simultaneous across all channels. It is an aggregate sample rate.