I am wondering if anyone can help me out with programming a DTS-12 SDI Turbidity Sensor. I can program it with a generic SDI 12 sensor in Shortcut. However I need to figure out how to communicate with it through a Campbell logger (CR500, CR510 or CR10X). Could anyone give me the steps I need to send the SDI commands to the sensor?
Jennifer,
I just created this program using Shortcut as you described for a CR10X.
1: Batt Voltage (P10)
1: 1 Loc [ BattV ]
2: If time is (P92)
1: 0 Minutes (Seconds --) into a
2: 1440 Interval (same units as above)
3: 30 Then Do
3: Signature (P19)
1: 2 Loc [ ProgSig ]
4: End (P95)
5: SDI-12 Recorder (P105)
1: 0 SDI-12 Address @@1
2: 0 Start Measurement (aM!)
3: 8 Port
4: 3 Loc [ Result1 ]
5: 1 Multiplier
6: 0 Offset
6: If time is (P92)
1: 0 Minutes (Seconds --) into a
2: 60 Interval (same units as above)
3: 10 Set Output Flag High (Flag 0)
7: Set Active Storage Area (P80)
1: 1 Final Storage Area 1
2: 101 Array ID
8: Real Time (P77)
1: 1220 Year,Day,Hour/Minute (midnight = 2400)
9: Sample (P70)
1: 1 Reps
2: 3 Loc [ Result1 ]
10: If time is (P92)
1: 0 Minutes (Seconds --) into a
2: 1440 Interval (same units as above)
3: 10 Set Output Flag High (Flag 0)
11: Set Active Storage Area (P80)
1: 1 Final Storage Area 1
2: 102 Array ID
12: Real Time (P77)
1: 1220 Year,Day,Hour/Minute (midnight = 2400)
13: Minimum (P74)
1: 1 Reps
2: 0 Value Only
3: 1 Loc [ BattV ]
14: Sample (P70)
1: 1 Reps
2: 2 Loc [ ProgSig ]
Instruction 5, the P105 SDI-12 Recorder instruction will send the measurement command M to the SDI-12 sensor with address 0 connected to control port 8 and store the result in input location Result1. You may want to use the terminal emulation mode to talk through to the sensor directly and query it as to how many results you should expect. The Shortcut program I generated will accommodate up to 9 results. You may want to consult your sensor manual or look at the section that covers transparent mode communication with SDI-12 sensors in the CR10X manual.
Thanks, Jeff
Thanks Jeff!
I figured out that my wiring scheme was incorrect (should be C2/P3 data line instead of C1). The manual for this specific SDI sensor calls for an unlock command of aU OPEN!. Using this sensor with other logging equipment I have been able to send the sensor this command to activate it, as well as change the SDI address if needed. However now that the wiring is correct the sensor is working perfectly well with the CR500 and I never needed to send it the unlock command. Strange. The sensor itself needs an aM2! command to query 7 results, all which are currently showing reasonable values. Have you ever had experience sending the SDI sensor commands (besides the measurement command) using a Campbell logger? You mention using terminal emulation to do so. Do you mind giving me more explanation on how to do that?
Jennifer
Jennifer,
You can use different command codes in the p105 instruction. Also check out the p68 instruction for extended sdi12 commands. In order to trouble shoot or just talk directly through to the sensor, while connected to the logger from the connect screen in loggernet:
1. Under the datalogger heading choose terminal emulator
2. Click on the open terminal button
3. Hit the enter key a few times till you get the asterisk back
4. Enter the port number where the sdi12 sensor is connected followed by an X, ie 1X
5. The logger will respond with 'entering sdi-12'
6. Enter the sensor address, sdi12 command, followed by! ie '0I!'
Take a look at the cr1000 manual for a good overview and partial list of commands. http://www.sdi-12.org/ would give a more complete list of commands and protocals.
Thanks, Jeff
If I may !
Most sensors will respond to the "aI!", wheer a is the device address, it all dependes on how much information the manufacture wants to show. If you do get a response, then you can follow up with the M or C command to get the unit to sample and then an aD0!, aD1!.... to display the data.
When trouble shooting SDI-12 sensors its best to have an SDI-12 verifier monitoring the SDI-12 bus, its a very useful piece of test equipment to have, however, if one is not available the next best thing is a terminal emulator such as Hyper terminal or Putty. Set the PC port properties to 1200 baud, 7 bit, E parity, 1 stop, then take the PC port Rx line (pin 2 on a db9 connector) and connect it to the SDI-12 bus. You will see every command from the logger to the sensor and every sensor response.
hope this helps.
fb