Hello,
During a maintenance operation, our DT80 series 4 did not respond to commands sent through dEx2, even though the commands server was activated in the configuration (port = 7700, 600s timeout).

As you can see in the attached picture below, server commands connection is successful, but an error window appears when trying to send any command or random characters.

On DeTransfer, the connexion was succesful at first but immediately lost afterward.

Turning on and off the DT80 did not resolve the issue, only reinstalling the firmeware after a deleteall resolved the problem. However, it impose to remove the DT80 from our system, and it is not acceptable as standart maintenance procedure.

When installing the DT80 in our sytem, this issue was absent, it seems to appear after a certain operation time.

What could be the cause of this problem? And how can we prevent it or correct it without having to physically access the datataker?

Thank you for your help,

Theo

Hi Theo,

This issue happens when you connect the logger with a USB cable and DTUsb. The DTUsb uses ports 80, 7700, 21, and 502, but under special conditions, when port 80 is used by other software, DTUsb will shift the number to 81, 7701,22, and 503. Since the dEX command interface is hardcoded with port 7700, it cannot talk to port 7701, which DTUSb prepared.

We are currently working to resolve this issue and we'll release a new dEX soon.

Best regards,
dataTaker Expert

Hi,
During this operation, the DT80 was connected with an ethernet cable only.
The issue you describe can be triggered if the DT80 has been previously connected via USB, even with a restart in-between?
Or does the problem have another origin?

Thanks,

Theo