WebDAQ 504
The WebDAQ 504 is a stand-alone, vibration and acoustic data logger designed for remote monitoring, analysis, 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 504 provides four simultaneous IEPE inputs for measuring sensors like accelerometers and microphones plus four isolated digital bits that can be used as trigger inputs or alarm outputs. Housed in a heavy-duty chassis, the WebDAQ 504 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
- How can I send data files to a network folder in parallel to saving to the internal memory?
-
I have mapped a network folder to a FTP server and I need to send the job data file to that folder at the end of every job (not live). How can I do that? I'm using the WebDAQ 504When editing that job, use the right-most tab to add an Event of type “Job Stopped”. Afterward, for that event, turn on “Transfer Data File” and specify the destination for the file to be transferred.
- Can the data (FFT, alarms, other) be accessed via HTTP requests?
-
I would like to know if I can access the data with a REST API so another application can request the data for some purpose. This is useful for continuous monitoring in a fleet acquisition scenario.Yes, real-time data and alarm status can be accessed using the REST API. The FFT, however, is performed in real time and cannot be transferred using the REST API. FFTs would need to be performed dynamically using the real-time data collected from your WebDAQ 504.
- RPM measurement
-
Will the WebDAQ 504 record also TTL or similar pulse information from tachometer? Recording phase and accurate RPM from rotating machinery is critical information for vibration measurement and troubleshooting in general.The digital I/O on the WebDAQ 504 is not setup for use with a Tachometer signal. The isolated digital I/O lines can be used as triggers to start or stop the acquisition or as alarm outputs. However, we do have other vibration DAQ devices that support a tach input. Please take a minute to review our DT9837 series or our DT9857E series DAQ devices for details.
- What is the exact value of Digital Trigger delay?
-
What is the difference between following two events in digitally triggered acquisition? 1. Digital Trigger 2. First AI SampleThe digital trigger input is sampled by software running on the logger, and therefore it can have a variable delay. I am seeing a delay of around 30 mS. If you have a spare AI channel on the WebDAQ 504, you could bring your trigger signal in on an AI channel. Triggering off of an AI input channel (rising slope) will have a faster response. I am seeing a delay of just one A/D sample.
- How to acquire data periodically?
-
I want to create a schedule that generates data files after a fixed duration like 1 min data file after every 10 minutes. How is it possible?Start by creating a job. In the Acquisition tab of the Job Editor dialog, select “Duration” from the Stop Settings drop down and set the samples per channel to collect data for the desired duration. Once the remaining job setting are configured, click Finish. Next, click the gear icon next to “Schedule” to open the Schedule Settings dialog. In the Schedule Settings dialog, set the schedule repeat settings to the desired interval and click OK.
- Is it possible to conect a measurement microphone to acquire noise data?
-
We are looking for a data logger to acquire noise data signals. I think the sampling frequency is adequate, but can I download the data in dB? Is it possible with the WebDAQ 504?Yes, the WebDAQ 504 is compatible with most IEPE transducers which include microphones. The data can be displayed in dBs but is not saved to file using the dB format, it's saved in its raw state. The WebDAQ 504 was designed with the intent that our customers would analyze the data using use a different software package for data analysis.
- 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 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 analog input data?
-
Can the state of the digital I/O port be recorded along with the analog input data? 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 504 operates asynchronously to the analog input channels. Therefore, because of the difference in their clock signals, concurrent data logging of both the analog 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).
- Can the number of channels be increased?
-
Is there an expansion unit available?The WebDAQ 504 logger is self-contained, with no expansion option. Multiple WebDAQ 504 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.