FAQs

FAQ for MX100

MX100Data Logger

  • Unable to connect multiple MX100/DARWIN APIs and one MX100

    The MX100's communication port only supports 1 connection at a time. Thus, you can't access one MX100 from multiple applications at the same time. Also, commands are processed sequentially, therefore command interrupts are not allowed. However, you can access multiple MX100's from a single applica...

    Publishd:
    Jan, 2018
    ID:
    w0005015
    Category:
    Setting
  • The API for Model MX190 MX100/DARWIN is a 32 bit DLL, but how can I use it on a 64 bit OS?

    To run MX190 on a 64 bit OS, build the application with 32 bit mode.

    Publishd:
    Nov, 2017
    ID:
    w0005018
    Category:
    Software
  • The input resistance (impedance value) of the MX110-UNV-M1010 CH medium speed universal input module for the MX100.

    The input resistances are as follows. DC voltage 1 V range or lower, TC range: 10 MΩ or greater DC voltage 2 V range or greater: Approximately 1 MΩ.

    Publishd:
    Aug, 2017
    ID:
    w0005017
    Category:
    Specification
  • Specifying the M3 screw terminal type for the MX110-UNV-M10

    For the MX110-UNV-M10, please use the /NC "No plate with clamp terminals" suffix code. Then, purchase the 772080 M3 plate with screw terminals separately, and attach them to the MX110-UNV-M10/NC.

    Publishd:
    Apr, 2016
    ID:
    w0005016
    Category:
    Model selection
  • Communication cuts out with the MX100/DARWIN API

    The MX100 cuts communications if idle for 3 minutes. Either get a system status periodically, or turn OFF communication and restore when necessary. If the communication just cut out, FIFO is running continuously. You can use a communication function to set the timeout, but this is not recommended. ...

    Publishd:
    Jul, 2014
    ID:
    w0005005
    Category:
    Wiring/Connection/Communciation
  • Does not know what FIFO is with the MX100/DARWIN API

    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. See the following manual chapt...

    Publishd:
    Jul, 2014
    ID:
    w0005009
    Category:
    Other
  • Unable to perform digital output with the MX100/DARWIN API

    For user digital output on the MX100, set the DO module channel to command DO, and send the DO data. Set the channel to command DO See the setup change function (setDOTypeMX) of the setting function. For extended API, see channel settings (setChKindMX100) Preparing DO data See the setup change ...

    Publishd:
    Jul, 2014
    ID:
    w0005010
    Category:
    Specification
  • Unable to perform analog output with the MX100/DARWIN API

    For user analog output on the MX100, set the AO module channel to command AO, and send the AO data. Set the channel to command AO See the setup change function of the setting function (setAOTypeMX) For extended API, see channel settings (setChKindMX100) Preparing AO data See the setup change f...

    Publishd:
    Jul, 2014
    ID:
    w0005011
    Category:
    Specification
  • Error number 9 with the MX100/DARWIN API

    This occurs when an error is returned from the measuring instrument. With the MX100, you can get the MX100-specific error number. See the following manual chapters. Chapter, "MX100 Setting Item Numbers" in the model MX190 MX100/DARWIN API user's manual

    Publishd:
    Jul, 2014
    ID:
    w0005012
    Category:
    Other
  • Error number 12 with the MX100/DARWIN API

    With the MX100, this error occurs when settings that are sent are invalid. Get the setting item number for determining where the invalid setting is located. See the following manual chapters. Chapter, "MX100 Setting Item Numbers" in the model MX190 MX100/DARWIN API user's manual

    Publishd:
    Jul, 2014
    ID:
    w0005013
    Category:
    Other
  • Support for the RoHS directive

    Please see the document below. You can confirm the compliance status of recorders and controllers with the RoHS directive. RoHS directive compliance status

    Publishd:
    Jul, 2014
    ID:
    w0000046
    Category:
    Other
  • Network search error after initialization

    This is a known issue with MX100 firmware release R3.01 and earlier, in which initializing the IP address results in failure of communication with PCs running Windows Vista or later. You can either use a Windows XP PC and set the IP address, or upgrade to a later release of the MX100 firmware (R3.0...

    Publishd:
    Jul, 2014
    ID:
    w0005001
    Category:
    Setting
  • Operation on power OFF during recording and communication interruptions

    Recording continues, but only dates and times are entered into the data files. MX100 standard software attempts to reconnect, and when it does, data is entered in data files starting from that point.

    Publishd:
    Jul, 2014
    ID:
    w0005002
    Category:
    Wiring/Connection/Communciation
  • DLL not found with the MX100/DARWIN API

    The MXAPI DLL is not in the right place. Place it in a valid search path of the executable, such as the current directory, project folder, or system folder.

    Publishd:
    Jul, 2014
    ID:
    w0005003
    Category:
    Specification
  • File cannot be opened with the MX100/DARWIN API.

    Old MX APIs cannot connect to new MX100's. Update to the latest MX API. If the error number is a communication error, please check your network settings.

    Publishd:
    Jul, 2014
    ID:
    w0005004
    Category:
    Specification
  • Modules installed in the 30 ch model of the MX100 Quick Start Package

    Three of the 10-CH Medium Speed Universal Input Module (model MX110-UNV-M10) are installed.

    Publishd:
    Jul, 2014
    ID:
    w0005006
    Category:
    Model selection
  • MX100/DARWIN API settings not entered

    After entering the MX API settings, there are times when the settings differ when viewed in the MX100 Standard software. When you connect the MX100 standard software, the MX100 standard software settings are changed.

    Publishd:
    Jul, 2014
    ID:
    w0005007
    Category:
    Specification
  • Unable to connect the MX100/DARWIN API and MW100

    The MW100 does not support that API.

    Publishd:
    Jul, 2014
    ID:
    w0005014
    Category:
    Model selection
  • Displaying MX100 and DA100 data

    MX100 → GateMX/MW or MXLOGGER → DAQLOGGER DA100 → DAQLOGGER with the above you can load both data on DAQLOGGER, but it will take at least one second.

    Publishd:
    Jul, 2014
    ID:
    w0013011
    Category:
    Specification