Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Knowledge Base Home
  • Contact Us
  • Home
  • Moku:Lab
  • Software integrations

What is causing the latency in my Moku:Lab measurement when using APIs?

Written by Paul Cracknell

Updated at December 22nd, 2020

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Moku:Go
    Moku:Go Arbitrary Waveform Generator Moku:Go Data Logger Moku:Go Frequency Response Analyzer Moku:Go Logic Analyzer & Pattern Generator Moku:Go Oscilloscope & Voltmeter Moku:Go PID Controller Moku:Go Spectrum Analyzer Moku:Go Waveform Generator Moku:Go Power Supplies Moku:Go Digital Filter Box Moku:Go FIR Filter Builder Moku:Go Lock-in Amplifier
  • Moku:Lab
    Windows Moku:Lab general Moku:Lab Instruments iPad app Software integrations
  • Moku:Pro
    Moku:Pro Instruments
+ More

Discussion of latency due to network connections : Python, MATLAB and LabVIEW

When using the various APIs, there are various sources that can contribute to latency collection from a Moku:Lab, such as network condition, data packet size, and local host computer processing environment.

As Moku:Labs are network connected, data collection is strongly dependent on the network condition. The same data package will take longer to be sent from the Moku:Lab to the computer in slow network speed environment. For applications that require high speed data transmission, we recommend using wired connection methods over wireless connection. The data transfer latency is dependent on the connection method. Based on our test, Wi-Fi connection generates a data transfer latency of ~100 ms. Wired ethernet connection generates a latency of ~6 ms. USB connection generates a latency of ~1 ms. Check out our articles on how to connect your Moku:Lab via Ethernet cable to an existing network or directly to the computer. 

The size of the data packet can also effect the collection latency. The "get_data" command will download the full resolution data from the device, whereas the "get_realtime_data" command will get downsampled data from the device with a lower latency.

The computer system condition can also cause latency, even after the data package has already reached the computer. Once the data package is downloaded, it will still need to be interpreted by the Moku APIs and the speed of this process is dependent on the computer, e.g. what processes are running and how powerful the CPU is. In a heavily loaded computer, the latency will therefore also increase.

api latency delay

Was this article helpful?

Yes
No

Related Articles

  • How do I convert Ki, Kp, Kd to crossover frequencies or vice versa?
  • WiFi is not permitted in our lab. How can I use Moku:Lab and iPad
  • How much current can Moku:Lab source and sink?
  • How to install the Moku:Lab iPad App
  • How to fix missing instruments on Moku

Sitemap

  • Moku:Lab
  • Instruments
  • Software
  • Company
  • Support
  • Store
  • Terms & Conditions
  • Privacy Policy

Offices

United States
+1 (619) 332-6230
740 Lomas Santa Fe Dr
Suite 102
Solana Beach, CA 92075

Australia
+61 2 6171 9730
243 Northbourne Avenue
Suite 2
Lyneham, ACT 2602

Follow us

Youtube LinkedIn

官方微信

Contact us
© 2021 Liquid Instruments. All rights reserved.

Definition by Author

0
0
Expand