Our full technical support staff does not monitor this forum. If you need assistance from a member of our staff, please submit your question from the Ask a Question page.


Log in or register to post/reply in the forum.

SDI12 Mode CR510 Datalogger


jcurran Mar 27, 2023 06:13 PM

We have a CR510 datalogger that we use to communicate with SDI12 sensors.  We had to return our working device to its owner, so we purchased one second-hand .  I can connect to the CR510 and communicate with it, using Loggernet SW, it seems fine there.  When I enter Terminal Emulator Mode, and give the "1X" command to enter SDI-12 Mode, it just returns an Asterick (*) and nothing else happens.  On the device that did work, "1X" would trigger the response like "Entering SDI-12 Mode".  Ive seen else where that in Terminal Emulator, hitting enter several times give you a prompt ">" which I have not seen.  Hitting enter just returns an Asterick (*) no matter how many times its pressed.  The "1X" Command was always the command to enter SDI-12 communications mode.  I have tried reinstalling Standard OS and also resetting to factory through the Loggernet software.  From the moment we got it, it has not been able to enter SDI-12 Mode.  I've also tried leaving the 3v board battery out overnight before replacing it with a fresh one, since it was close to dead when we purchased it.

Does anyone have any advice, something I am missing, something I need to activate to be able to enter SDI-12 mode.  Without it, our CR510 is a pricey paperweight.

Thanks in Advance!


pokeeffe Mar 28, 2023 06:03 PM

I've never worked with CR510 but assuming you've got the same program loaded, using the same SDI-12 sensors, with the same wiring connections, and using the standard OS, it sounds like logger security is somehow enabled and you're locked out generally.

I also would have started by reflashing the OS and factory resetting. Could it be the choice of OS - standard vs. table based?


jcurran Apr 6, 2023 02:01 PM

I would assume resending the OS and/or resetting the datalogger would reset security?  I have standard OS installed, when I tried to install table based it gives me an error.  I was doing a lot of tinkering and was able to get into SDI-12 mode, but now cannot remember exactly what I did, nor can I currently duplicate it.  I do think you are right, there may be something in the security settings possibly?


smile Apr 18, 2023 01:13 PM

From CR10X manual:

TRANSPARENT MODE (SDI-12)

The SDI-12 transparent mode is used tocommunicate directly with an SDI-12 sensor. Acommon application of the transparent mode isto verify proper operation of the SDI-12 sensor. A computer or terminal is required to use thetransparent mode; the CR10KD (keyboarddisplay) cannot be used. Transparent mode is entered while the computer is in telecommunications with the SDI-12 recorder CR10X (at the asterisk '∗' prompt). Enter 'pX' at the asterisk prompt, where 'p' is the Control Portnumber (1-8) attached to the SDI-12 data line.The CR10X responds with ‘entering SDI-12.’Any SDI-12 command preceded with the sensoraddress and followed with an exclamation point'!' may then be entered. For example, entering'0I!' would request identification from an SDI-12sensor addressed at 0. The SDI-12 prompt will not appear until theCR10X finishes executing all program tables.While in transparent mode, scheduled tables inthe CR10X will not execute. Transparent modeends and the ‘*’ prompt is returned when aninvalid SDI-12 command (e.g., a blank line) isentered, if the SDI-12 sensor doesn’t respondwithin the time-out period following a validcommand (approximately 1/3 second), or if theuser does not enter a command before themode times out (approximately 35 seconds).Security must be unlocked to level 2 before theTransparent mode is enabled.







smile Apr 18, 2023 01:23 PM

What OS version are you using?

If you receive the ">" character you are not in terminal mode but in keypad mode.

Try again with last OS 1.15

https://www.campbellsci.co.uk/downloads/cr510-os


pokeeffe Apr 18, 2023 04:29 PM

I think smile's posts contain the answer. It doesn't sound security code related if you've already reloaded the o/s and still have issues.

Log in or register to post/reply in the forum.