Simulator
Try the openDAQ SDK in your browser
Short programs run real openDAQ code against simulated devices with no hardware, account or installation needed. Use devices shows the application side in Python or C++. Build a device shows in C++ how a device module turns firmware data into openDAQ signals.
Step 1 of 7
Find what is on the network
$ waiting for the program…
The code is the real openDAQ API and the devices and their values are simulated. In Build a device the calls that start with fw:: stand in for your own firmware API. Run the Use devices programs against any compatible device on your network and you get the same shape of output with your own numbers in it.
What to try
What to look for
Analog, digital, counter and bus
Step 3 lists them side by side. They are all signals with a descriptor for sample type, unit, range and time base so software knows how to show each one without vendor-specific code.
Settings that describe themselves
Step 4 reads a property's unit and allowed values before changing it. That is how an application builds a settings dialog for a device it has never seen.
One time base
Step 5 draws a vibration channel, a door switch and a speed counter from one reader aligned on the device's clock. Step 7 then adds two more vendors to the same plot.
Both ends use the same SDK
The Build a device tab shows the other end of the cable. A device module reads the firmware, describes the signals and serves them so every program in the Use devices tab can find it.
Want to see this against your own hardware instead of a simulation? Book a free technical discovery call