Support Forums
No active configuration detected

Hi,

I've received this message when starting up my DT, which had already been running for some time. It states there's no active configuration. My DEX configuration was still stored, I just needed to restart the logger. I faced this issue another time when I reprogrammed a DT remotely, and noticed the next day, that the configuration wasn't active.

Anyone else faced this problem? Is there any possible way to avoid this from happening?

Thank you.

5c9622f5b152d

Hi, I've received this message when starting up my DT, which had already been running for some time. It states there's no active configuration. My DEX configuration was still stored, I just needed to restart the logger. I faced this issue another time when I reprogrammed a DT remotely, and noticed the next day, that the configuration wasn't active. Anyone else faced this problem? Is there any possible way to avoid this from happening? Thank you. ![5c9622f5b152d](serve/attachment&path=5c9622f5b152d)

Hi Arivan,

That might happen when the running job (configuration) is not CONFIG.
Standard dEX configuration has a single job name, so it is not possible to have two dEX configuration at the same time in the logger.

Through command interface, you may create another job (configuration) replacing (not deleting) dEX configuration, i.e.: TEST
CONFIG job is still reside in dataTaker but inactive.

When you check the list of jobs using DIRJOBS, you will find:
*TEST
CONFIG

-* in front of job name indicates the active job.

Best regards,
Rudy Gunawan

Hi Arivan, That might happen when the running job (configuration) is not CONFIG. Standard dEX configuration has a single job name, so it is not possible to have two dEX configuration at the same time in the logger. Through command interface, you may create another job (configuration) replacing (not deleting) dEX configuration, i.e.: TEST CONFIG job is still reside in dataTaker but inactive. When you check the list of jobs using DIRJOBS, you will find: *TEST CONFIG -* in front of job name indicates the active job. Best regards, Rudy Gunawan

Hi Rudy,

Thank you very much for the explanation.

But the thing is, I created the running job using dEX, and didn't alter the program. It was running normally for a few weeks, and suddenly this happened. Could there be any external factor which causes this to occur?

Thank you.

Regards,
Arivan G.

Hi Rudy, Thank you very much for the explanation. But the thing is, I created the running job using dEX, and didn't alter the program. It was running normally for a few weeks, and suddenly this happened. Could there be any external factor which causes this to occur? Thank you. Regards, Arivan G.

Hi Arivan,

Have you check the job list?
Adding an additional job through command interface is not altering your previous dEX job. It is replacing it to become the active job.
dEX job still reside in dataTaker memory.

There are several scenarios for this problem:

  1. Like my explanation earlier, you add another job using command interface
  2. You insert a USB stick contain another job. If the job is saved as ONINSERT.dxc, dataTaker will run it and will assume the new job as an active job.
  3. You have an existing job in the logger (i.e.: TEST) prior to creating a dEX job and you set PROFILE STARTUP RUN=TEST, even after you write a program in dEX whenever dataTaker recycle its power it will resume TEST job.

Best regards,
Rudy Gunawan

Hi Arivan, Have you check the job list? Adding an additional job through command interface is not altering your previous dEX job. It is replacing it to become the active job. dEX job still reside in dataTaker memory. There are several scenarios for this problem: 1. Like my explanation earlier, you add another job using command interface 2. You insert a USB stick contain another job. If the job is saved as ONINSERT.dxc, dataTaker will run it and will assume the new job as an active job. 3. You have an existing job in the logger (i.e.: TEST) prior to creating a dEX job and you set PROFILE STARTUP RUN=TEST, even after you write a program in dEX whenever dataTaker recycle its power it will resume TEST job. Best regards, Rudy Gunawan
23
3
2
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft