Support Forums
Command Window Doesn't enable

Hi

When trying to use the command window after clicking "Enable" I am unable to type anything in the "send" window. Does anyone know why this might be the case?

Regards
Andrew

Hi When trying to use the command window after clicking "Enable" I am unable to type anything in the "send" window. Does anyone know why this might be the case? Regards Andrew

Hi Andrew,

Please check whether you are using port 7700 or 7701 in the following:

  • the label next to enable button in dEX
  • DTUsb page
  • PROFILE setting (check this setting using DeTransfer).

Best regards,
Rudy Gunawan

Hi Andrew, Please check whether you are using port 7700 or 7701 in the following: - the label next to enable button in dEX - DTUsb page - PROFILE setting (check this setting using DeTransfer). Best regards, Rudy Gunawan

Hi Andrew,

If you see port 7701, then you have to change PROFILE setting (via dEX) to match it.
From dEX Home, please go to "Configure the Logger" page and click on dataTaker model at the left configuration tree.
You will access dataTaker profile setting, go to Security tab to change Command Server port number to 7701.
Send the program to the logger then you can access dEX command interface.

Other option is finding the background program that use port 80 and switch it off temporarily.
Restart DTUsb and it will pick up port 80 (including subsequent port 7700).
In doing that you do not need to alter DT profile setting, in case you forgot it in the future. :D

Best regards,
Rudy Gunawan

Hi Andrew, If you see port 7701, then you have to change PROFILE setting (via dEX) to match it. From dEX Home, please go to "Configure the Logger" page and click on dataTaker model at the left configuration tree. You will access dataTaker profile setting, go to Security tab to change Command Server port number to 7701. Send the program to the logger then you can access dEX command interface. Other option is finding the background program that use port 80 and switch it off temporarily. Restart DTUsb and it will pick up port 80 (including subsequent port 7700). In doing that you do not need to alter DT profile setting, in case you forgot it in the future. :D Best regards, Rudy Gunawan

Hi Rudy

The "Command server port" is already set at "7701".

Regards
Andrew

Hi Rudy The "Command server port" is already set at "7701". Regards Andrew

Hi Rudy

As the logger was already set at "7701" I tried the second method which worked okay for a while but now the port has reverted to "7701" and I cannot get it to switch to "7700". Have you any more ideas?

Regards
Andrew

Hi Rudy As the logger was already set at "7701" I tried the second method which worked okay for a while but now the port has reverted to "7701" and I cannot get it to switch to "7700". Have you any more ideas? Regards Andrew

Hi Andrew,

Please change the command port vnumber ia dEX.
From dEX Home go to Configure the Logger the click on logger model (left side the very top).
You will see logger internal setting, go to Security to access command port number.

Best regards,
Rudy Gunawan

Hi Andrew, Please change the command port vnumber ia dEX. From dEX Home go to Configure the Logger the click on logger model (left side the very top). You will see logger internal setting, go to Security to access command port number. Best regards, Rudy Gunawan

Hi Rudy

Thank you for your response. I think know what is happening, port is being blocked by a Windows service linked to http activity. So when the DTusb program tries to find the logger it has to use port 81 and also switches to port 7701 for the command function. So far I haven't been able to identify which service is doing the blocking as the netstat command cannot identify it. I need to do some further investigations.

Assuming I can keep port 7700 open is it possible to send commands to the logger using a bespoke program written in Python?

Regards
Andrew

Hi Rudy Thank you for your response. I think know what is happening, port is being blocked by a Windows service linked to http activity. So when the DTusb program tries to find the logger it has to use port 81 and also switches to port 7701 for the command function. So far I haven't been able to identify which service is doing the blocking as the netstat command cannot identify it. I need to do some further investigations. Assuming I can keep port 7700 open is it possible to send commands to the logger using a bespoke program written in Python? Regards Andrew

Good evening Andrew,

The dataTaker command window is simple a telnet session.
Sending plain text command is all the logger needs.

Cheers

Roger

Good evening Andrew, The dataTaker command window is simple a telnet session. Sending plain text command is all the logger needs. Cheers Roger

Hi Roger

Thank you for your reply.

So, if I want to stop the logger all I need to do is send "h" via the TC/IP connection?

Regards
Andrew

Hi Roger Thank you for your reply. So, if I want to stop the logger all I need to do is send "h" via the TC/IP connection? Regards Andrew

Hi Rudy

Thank you, unfortunately it doesn't work for me with a simple Python program. I can read the data stream from the DT80M but the command I sent is ignored.

Regards
Andrew

Hi Rudy Thank you, unfortunately it doesn't work for me with a simple Python program. I can read the data stream from the DT80M but the command I sent is ignored. Regards Andrew

Hi Andrew,

Check you are sending the commands to port 7700.
Also check if a password is set on the logger

Cheers

Roger

Hi Andrew, Check you are sending the commands to port 7700. Also check if a password is set on the logger Cheers Roger

Hi Roger

Thank you for your reply.

The port I am connecting to is 7700 and I can get data from the logger. I haven't set a password for the logger, is there a default that i would need to use?

Regards
Andrew

Hi Roger Thank you for your reply. The port I am connecting to is 7700 and I can get data from the logger. I haven't set a password for the logger, is there a default that i would need to use? Regards Andrew

Hi Andrew

The default is not to have a password set.

Get yourself a program called wireshark so you can diagnose the TCP/ip packets to see what is wrong

Cheers

Roger

Hi Andrew The default is not to have a password set. Get yourself a program called wireshark so you can diagnose the TCP/ip packets to see what is wrong Cheers Roger

Hi Andrew

Just had another thought, are you adding a carriage return / line feed to the command?
It's someting I do automatically so forget to tell people

Cheers

Roger

Hi Andrew Just had another thought, are you adding a carriage return / line feed to the command? It's someting I do automatically so forget to tell people Cheers Roger

Hi Roger

I'll try the wireshark program and see what I get, I'll also add a carriage return, that's not something I had included.

Regards
Andrew

Hi Roger I'll try the wireshark program and see what I get, I'll also add a carriage return, that's not something I had included. Regards Andrew

Hi Andrew

Yes you send hcrlf that is h carriage return line feed
Also the DT80's are not case sensitive

Cheers

Roger

Hi Andrew Yes you send hcrlf that is h carriage return line feed Also the DT80's are not case sensitive Cheers Roger

Hi Roger

Thank you for your reply

I used "g\r" in my program to start the logger and that appeared to work okay. Next problem is running the schedule using a string from my program. I set up a trigger to use "P141" as a string to send on the USB port but I get an error "E122 - Command incompatible with configured port function at line 27 col 56 [MB]SERIAL <err>'P141'. The attached jpg shows the settings I have used. If I select "Serial sensor port" the schedule saves okay but I get an error at the command window. I am using a TCP/IP socket in my Python program, however I get the same error in the deX command window.

5cb2bdcb64cf5

Regards
Andrew

Hi Roger Thank you for your reply I used &quot;g\r&quot; in my program to start the logger and that appeared to work okay. Next problem is running the schedule using a string from my program. I set up a trigger to use &quot;P141&quot; as a string to send on the USB port but I get an error &quot;E122 - Command incompatible with configured port function at line 27 col 56 [MB]SERIAL &lt;err&gt;&#039;P141&#039;. The attached jpg shows the settings I have used. If I select &quot;Serial sensor port&quot; the schedule saves okay but I get an error at the command window. I am using a TCP/IP socket in my Python program, however I get the same error in the deX command window. ![5cb2bdcb64cf5](serve/attachment&amp;path=5cb2bdcb64cf5) Regards Andrew

Hi Andrew

You have set the USB port to receive serial data
You must have it set to command mode for this to work.

Cheers

Roger

Hi Andrew You have set the USB port to receive serial data You must have it set to command mode for this to work. Cheers Roger
12
266
27
3
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