Dear Colleagues,
We have in use solar radiometric complex which consists of solar radiometric sensors(9 sensors),
automatic solar-tracking unit 2AP BD and electronic units such as CR10X 4M dtalogger (with 4M
External Flash Memory Module), AM25T Multiplexer and SC32B RS-232 Interface to PC.
When we start the program PC208W, as usually as we did over a period of 13 years, and right
away we are facing with the continuous series of telecommunication errors with the following
message on PC screen: "Telecommunication Command Failed! See SWL Log...".
Please find below SWF Log.
SWF Log:
... ... ... ... ... ... ... .... ....
"20.07.16 14:55:03", W CR10X1 failed to get attention.
"20.07.16 14:55:04", W CR10X1 no echo of End command.
"20.07.16 14:55:15", W CR10X1 forced off-line while trying to get attention.
"20.07.16 14:55:15", W CR10X1 failed to get attention.
"20.07.16 14:55:15", W CR10X1 no echo of End command.
... ... ... ... ... ... ... .... ....
and so on.
In this connection, it became unavailable downloading of the data from the external Flash Memory
Module (4M). Also, it became unavailable viewing of any graphic information concerning the
measured data in on-line regime on the screen of PC . CR10X datalogger became unaccessible.
Another device under suspicion of failure is the SC32B RS-232 Interface to PC.
Are there any initial checks and tests of the CR10X and SC32B RS-232 Interface on-site before
shipping them to repair?
Whether is possible to "revive" the CR10X data logger in this case?
Thanks.
Take a look at this article:
https://www.campbellsci.com/blog/determine-if-datalogger-needs-repairing
Another possibility is a comport issue.
https://www.campbellsci.com/blog/test-com-ports-short-haul-modems
https://www.campbellsci.com/blog/usb-rs-232-adapter-cable-issues
SC32B modules rarely fail. I more often see failed CR10X.
I suggest installing a recent version of Device Configuration Utility and using that for testing communication.
Hi Jannet,
Thank you very much for your quick and detailed response.
We have already fulfilled a lot of checks and test including those that you have suggested in your reply.
But according to "Note" in your reply- @Note: The tests discussed in this article’s steps assume that your system is not having communications issues and that you can communicate with your datalogger." these tests are not applicable to us because our CR10X datalogger is not accessible and we simply cannot communicate with him.
We assume that the SC32B RS-232 Interface may be faulty, but we cannot check him.
Another assume consists in that the Flash Memory(EEPROM) and/or SRAM memory(with user program in the Active Area) may be faulty(user program may be broken because of a internal system failure), but it is impossible to check them because of we cannot communicate with datalogger and we cannot upload user program into the SRAM and EEPROM in order to restart the user program.
In general, the circle has become closed.
Thank you.
Hi JDavis,
Thank you very much for your quick response.
To our regret our CR10X datalogger is not accessible now and we simply cannot communicate with him.
We assume that the SC32B RS-232 Interface may be faulty, but we cannot check him.
Another assume consists in that the Flash Memory(EEPROM) and/or SRAM memory(with user program in the Active Area) may be faulty(user program may be broken because of a internal system failure), but it is impossible to check them because of we cannot communicate with datalogger and we cannot upload user program into the SRAM and EEPROM in order to restart the user program.
Thanks.
a problem compounded by the fact that the CR10X data logger is out of production.
I'm awaitng for the response from the Repair Dept. concerning the ability to check and repair my CR10X at the Campbell's repair facilities.
In extreme case, with a negative answer from them, I'm looking for the "old" version of the CR10X datalogger: may be somebody anywhere wants to sell his CR10X, which is still in working state(with Firmware 1983, 1986, 1995).
We can still check, repair and calibrate the CR10X and even its predecessor the CR10. Only occasionally is it not economic to repair the logger, e.g. due to water or lightning damage.
Hi aps,
Thank you for your response.
".....We can still check, repair and calibrate the CR10X" ...it's a really good news!
In 2003 we bought in Kipp@zonen solar radiometric sensors(9 sensors), automatic solar-tracking unit 2AP BD and electronic units such as CR10X 4M datalogger (with 4M External Flash Memory Module), AM25T Multiplexer and SC32B RS-232 Interface to PC. CR10X datalogger has S/N XE4877 with Firmwares 1983, 1986, 1995.
The equipment has worked like a Swiss watch...over 13 years!
I'm a researcher from Moldova ( http://arg.phys.asm.md ). Are you serving customers from Moldova? Not long ago I tried to buy the SC32B RS-232 Interface in Campbell Scientific Ltd., but the robot automatically re-directed my inquiry to Campbell Scientific Inc.
What I need to do from my party for check and repair of the CR10X on your facilities?
I think that I have to send you CR10X, wiring panel and SC32B RS-232 Interface(it is also under suspicion).
Am I right?
We could discuss all items(cost of repair, payment, shipping, etc) in details by e-mailing.
e-mail: akulinin@phys.asm.md
aculinin@gmail.com
Thanks.