Hello,
I need to know the SDI12 address of a sensor which have been plugged on the CR1000 on the C5 port.
I know the command to send ("?!"), I think I have to use the terminal emulator via PC400, but how to say to the CR1000 that it has to be sent on the C5 port specificly ?
And, more difficult : remotely ... (IP connexion on a NL120)? I can reach easily the CR1000 but terminal emulator seem to be unclear, it seem it just can receive the "enter" command.
So, any idea ?
Thanks, bye.
Well, I have answered myself on one point, here what I did :
First, to know what command you can use with the terminal emulator, use de "H" command after press several time "enter" button until the prompt "CR1000>" appear.
In the terminal emulator on PC400, use a connexion that you setting before (the profil to connect a datalogger remotely and just use the commands :
SDI12
And choose whitch port to use (C1, 3, 5 or 7).
Then, you can send directly a specific command, like "?!" to know the SDI-12 address of a sensor.
But, in my case, the only response I have is "SDI12 Failed". So I'm still stuck. It is possible that the sensor is not parametred well (I broke a wire and not be able to communicate with it since a long ...)
SDI12 Failed means no response from the sensor.
SDI12 Busy means the datalogger program was busy trying to talk to the sensor.
You need to stop the program that is currently running on the CR1000, before using the terminal emulator.
Watch this tutorial for detailed walkthrough:
https://www.campbellsci.com/videos/sdi12-sensors-transparent-mode
Hello,
thanks for your help.
I tried to stop the program, and didn't change the answer of terminal emulator : SDI12 Failed.
Another SDI-12 sensor on the same CR1000 works fine with the terminal emulator, I tip "?!" and it say "0", so I think that is my sensor that is not correctly set...
Last question : If my sensor (the one that not respond to my SDI12 request) is on the same address that the other sensor that works fine, it can block it answer ?
Bye
If you have two sensors with the same address connected to the same port, you will have problems.
Actually they are not on the same port, only the same datalogger, I thought that could be a problem too.