|
The MXAPI DLLs are not in the correct location.
Place them in a searchable path such as the current directory during execution, project folder, or system folder.
|
The old MXAPI cannot connect with new MX100s.
Upgrade to the latest MXAPI. If the error number was a communication error, check the network settings.
Reference
- MXAPI updater
- MW100 not connected
|
| If no communications occur on the MX100 within 3 minutes, communications are dropped.
Regularly obtain system status data, or, allow the communications to be dropped and reconnect when necessary. If it is just that communication is dropped, FIFO will continue to function. Functions can be used to set a communication time out, but this is not recommended.
|
| When checking settings on the MX100 Standard Software After entering settings with the MXAPI, the settings are different.
This is because when you connect the MX100 Standard Software, its settings are applied.
|
| The decimal place is the value that shows the exponent of the measured value. It is fixed for each range type. If the span value is specified with an integer, 1 mV would be "1000" in the 20 mV range (-20.000 to 20.000 mV). See the corresponding manual chapter below.
Reference
- The chapter, "MX100 Constants" in the user's manual.
|
| It is a process in which measured data is written to a buffer. On the MX100, measured data cannot be acquired unless FIFO is started. On the MX100 you can use different FIFO buffers for each measurement interval (up to 3). See the corresponding manual chapter below.
Reference
- The chapter, "MX100 Terminology" in the user's manual.
|
| To output user-defined digital output on the MX100, set the DO module channels to command DO, and send DO data.
Setting channels to command DO
See the setting change function (setDOTypeMX) of the setting function
For the extended API, see channel settings (setChKindMX100)
Preparing DO data
See the setting change function (changeDODataMX) of the setting function.
For the extended API, see the data manipulation functions (createDOMX100 and change DOMX100)
Sending DO data
See the collective setting function (setDODataMX) of the setting function
For the extended API, see the data manipulation function (commandDOMX100)
Reference
- The chapter, "Correspondence between Functions and Functions" in the user's manual.
|
| To output user-defined analog output on the MX100, set the AO module channels to command AO, and send AO data.
Setting channels to command AO
See the setting change function (setAOTypeMX) of the setting function
For the extended API, see channel settings (setChKindMX100)
Preparing AO data
See the setting change function (changeAOPWMDataMX) of the setting function
For the extended API, see the data manipulation functions (createAOPWMMX100 and changeAOPWMMX100)
Sending AO data
See the collective setting function (setAOPWMDataMX) of the setting function
For the extended API, see the data manipulation function (commandAOPWMMX100)
This is the same for PWM as well. See the function for entering settings (setPWMTypeMX).
If a value is specified on the instrument (output data value), it differs from the value that is actually output. See the change utility functions.
Reference
- The chapter, "Correspondence between Functions and Functions" in the user's manual.
|
|
|
|
|
| If you can not find your answers here, please feel free to contact us. |
|
|
|
|
|
