Category Sitemap
Home / Our Businesses / Controllers & Data Acquisition / Products / Software /
Data Acquisition Software Suite

DAQWORX
MXLOGGER
  1 2  
Test conditions: Measurement channels only, excluding alarm and computation channels
Measurement Interva Number of Channels Number of Units
10 ms 24 channels 1
100 ms 600 channels 10
200 ms 1200 channels 20
The performance data shown above varies depending on the measurement conditions, the number of channels, and the PC’s environment settings. For high-speed systems covering 500 or more channels, refer to the following PC system requirements as a guideline:

-Pentium 4 (3 GHz)
-2 GB internal memory
-360 GB hard disk space (7200 rpm)
  • Advanced recording (multiple logging)
    • The multi-logging of 32 channels x 50 groups by groups is avaialble in combination with Addmulti.
  • Advanced recording (triggered logging)
    • The event logging with advanced trigger conditions is available in combination with AddTrigger.
  • Advanced monitoring (user-created screens)
    • User-created screens offer convenient monitoring in real time in combination with AddObserver and AddObserver Runtime.
Note: Direct connection to MXLOGGER for acquisition by AddMulti or AddTrigger can occur on only one system (one measurement interval of one of the MX100 units connected to MXLOGGER). Any system can be connected, enabling data acquisition at speeds of 100 ms, or up to 10 ms.
  • The maximum number of measurement channels on which acquisition can be performed is 24 at 10 ms, or 60 at 100 ms.
  • Measurement channels can be loaded into MXLOGGER's MATH channels, and acquisition can be achieved on up to 240 channels at 100 ms by specifying MATH channels as the system to connect to from AddMulti or AddTrigger.
To maximize the number of available channels, you can connect MXLOGGER to DAQLOGGER and acquire data via DAQLOGGER. In this case, the shortest measurement interval of AddMulti or AddTrigger becomes that of DAQLOGGER (one second).
Example of Building a System Comprising MX100 and DARWIN Units
Example of Building a System Comprising MX100 and DARWIN Units
DAQLOGGER acts as a client of MXLOGGER and simultaneously makes acquisitions from both MXLOGGER and DARWIN units.
Notes) The data acquisition interval of DAQLOGGER is 1 s at the shortest. If data acquired at intervals shorter than 1 s needs to be saved, let the data be saved on the MXLOGGER side.
GLOBAL  
YOKOGAWA

Powered by Ultraseek
·  DAQWORX
Demo Movies
Flash
DAQOPC Server
DAQOPC/DAQOPC for Darwin are communication interface packages that comply with the OPC standard.
more
Top of this page
  1 2