App

Deploy Error 2

The Moku stopped responding during the deploy. This sometimes seems to happen intermittently, we don't really know why. This is also often the error if you try and deploy an MCC bitstream with a mismatched firmware version. Retry and/or reboot your Moku, depending how hung up it is.

API

404 Not Found

The API function that you tried to call doesn't exist on the device. If you're using a library then the most common cause is a version mismatch between the firmware and the library, try updating both. The firmware should be backwards compatible in most cases.

Invalid Key/Value

An argument to the function you're trying to call is invalid. This might be type (e.g. trying to send a number rather than a string) or value (e.g. trying to ask for channel 3 on a 2-channel device). We're working on a change to tell you which value is wrong but for now you need to check your values against the documentation.

LabVIEW

Error 56

Timeout on connection. Usually happens when the IP address is wrong (or not set before the VI is run). There's weak evidence that having a Moku connected by both WiFi and Ethernet at the same time exacerbates this.