FAQ(s)

⌘K
  1. Home
  2. FAQ(s)
  3. Application
  4. Symptoms pointing to a corrupted configuration

Symptoms pointing to a corrupted configuration

Q: What are the symptoms that point to a corrupted configuration?

A: On a ML-x17, check the parameter, output or measurement list for “strange” values.

  • Invalid or exceptional time frames. (Sample, alarm and data log intervals)
  • Impossible number of parameters. (ML-x17 >64 and ML-525 > 100)
  • Idiotic high or negative parameter values (factor, offset or number of decimals)

T: Check the (ML-x17) examples below.

T: Read this FAQ to restore or rebuild a corrupted ML-x17 configuration.

A: On a ML-525 series data logger, configuration corruption is blocking the device to run or start properly.

T: Check the ML-525xE examples below:

At this point, data logger activity has stopped, although “Running” is shown.

At this point, the data logger keeps looping during the initializing process.

T: Read the “Expert procedure” in this FAQ to restore or rebuild a corrupted ML-525xE configuration.

How can we help?