von Jason Ritter | Aktualisiert: 11/24/2015 | Kommentare: 5

Are you having communication problems or seeing readings you don't trust? Is it possible your solar-charged power supply is the cause? How can you find out for sure?
As we mentioned in the “6 Steps to Determine if Your Data Logger Needs Repairing” blog article, many data acquisition system failures are caused by problems with the power supply. These may include issues with batteries, charge regulators, or charging sources. In this article, we’ll look at seven steps to help you find out if your solar-charged power supply has a problem.
Before we get started, you will need to have these tools handy:
Most of the steps outlined here involve direct current (dc) or voltage measurements on different parts of your power system. To measure the dc voltage, set your DMM to the 20 Vdc range with the red probe firmly in the mAVΩ socket and the black probe firmly in the COM socket. During testing, you will touch the red probe to one of the following: the terminal screw labeled 12V, +, or the bare end of a red wire. In contrast, you will touch the black probe to one of these: the terminal screw labeled G, -, or the bare end of a black wire.

You can check whether the data logger is getting power from the power supply by following these steps:

You might be surprised how common it is for someone to turn off the power to a data logger for some reason and then forget to turn it back on later. (For more information on this subject, read the “Troubleshooting Best Practices for Data Acquisition Systems” blog article.)
If you look at your power supply, do you see multiple terminals labeled 12V and G? Just pick one of each terminal type to use.
Measure the voltage between the 12 volt and ground terminals on your power supply. If you measure more than 11 V on the power regulator, but less than 11 V on the data logger, check the wires that connect them.
At this step in the process, your measurements have been less than 11 V for both the data logger and the power supply. The next step is to test the battery voltage with the black probe on the negative (-) terminal and the red probe on the positive (+) terminal.
With the battery disconnected, you can recheck the voltage on the power supply using step #3 as a guide.
Now check the voltage on the two charge terminals of the power supply. These are both labeled CHG, but it doesn't matter which color probe you put on which terminal.

Now it's time to disconnect the solar panel from the power supply. You can measure the panel’s voltage by touching the probes to the ends of the panel’s bare wires. Be sure to do this test during the day at a time when the solar panel is not covered or in the shade. With the red probe touching the red wire, and the black probe touching the black wire, measure the voltage.
For this last step, set your DMM to measure amps so that you can measure the current coming from the solar panel.
Tip: To avoid sparking, it's good practice to temporarily cover the solar panel with a cloth or something similar.
Measure the current by following these steps:
| Solar Panel Output | Maximum Output Current (shorted) |
|
10 W |
0.7 A |
|
20 W |
1.4 A |
|
50 W |
3.3 A |
|
90 W |
5.6 A |
Depending on the time of day and weather, your measurement will probably be lower than the maximum listed, but it should be close to the value that is appropriate for the size of your solar panel.
Some Campbell Scientific data loggers have their power supply built into a rechargeable battery base. For this type of data logger, before you can perform steps #5 and #6, you will need to disconnect the battery by separating the data logger module from the base. (For more details, see your data logger manual.)
To find a power supply problem, we start at the data logger and test each part of the system back to the charging source. After you perform these steps, contact Campbell Scientific if you find any of the conditions outlined below:
| Condition | Cause |
|
The voltage from the power supply is less than 11 V with the battery attached, but the voltage increases to 13 to 14 V when the battery is disconnected. |
The battery needs to be replaced. |
|
The battery voltage is more than 11 V, but the voltage from the power supply is less than 11 V. |
The power supply needs to be repaired. |
|
The voltage on the charge terminals is more than 17 V, but the voltage between 12V and G on the power supply is outside the range of 13 to 14 V. |
The power supply needs to be repaired. |
|
The current output from the solar panel is realistic, but the voltage between 12V and G on the power supply is outside the range of 13 to 14 V. |
The power supply needs to be repaired. |
|
When the solar panel is in the sun, the solar panel voltage is considerably less than 17 V. |
The solar panel is defective or damaged. |
|
When the solar panel is in the sun, the solar panel current is not close to its maximum output current. |
The solar panel is defective or damaged. |
If your solar-charged power supply has a condition that hasn’t been covered in this article, or if you have a question, post your comment below.
Kommentare
IslandMan | 12/15/2016 at 11:42 AM
Thanks Sam.
Link to my weather station.
https://www.wunderground.com/us/ny/kings-park/zmw:11754.1.99999?MR=1
gonzalig | 03/29/2017 at 10:53 AM
Sam
I thanks you for this post, Its really helpful. The sub was working great in my CR1000 Ver 30 until I upgrade OS to 32. Now the part for the UTC has commands that don’t compile under the new OS.
Can you help?
GaryTRoberts | 03/29/2017 at 01:00 PM
gonzalig,
Thank you for finding and reporting this bug. We have fixed it and it will be part of a bug fix release we are planning in the very near future. The fix will be included in CR6 OS 06.03 and CR1000/CR800/CR3000 OS 31.03.
gonzalig | 03/31/2017 at 10:41 AM
GaryTRoberts
Yes, I meant I upgraded to 31.02. I´ll look forward to get the new OS.
Perhaps it’s not as popular but is there a post like this to help us send data to CWOP / MADIS? Your colleagues from Au already help some, but not all the times my data gets received by MADIS.
cellectronic | 11/17/2017 at 11:49 AM
Hi Guys,
I am wondering if the bugs got sorted ? I have an error when trying to compile and the offending line is
Call wundergroundPWS(Result,"stationID","password",WxData,0)
with the error Undeclared variable Result,, Any ideas anyone ? Please.
uplander | 11/28/2017 at 11:42 AM
This sounds like your program needs to have the variable 'result' declared. Add the following line to the other Public declarations at the beginning of your program:
Public Result
José Miguel Campillo Anguita | 07/04/2018 at 09:16 AM
hola muy buenas tardes utedes podrian poner ejemplos de programas para wunderground de los siguientes variables promediadas
3 Wind Gust en millas por hora, calculado durante un período definido por el usuario
4 Dirección de la ráfaga de viento en grados, calculada durante un período definido por el usuario
5 2 minutos Velocidad del viento promedio en mph
6 Dirección del viento promedio de 2 minutos en grados
7 10 minutos de ráfaga de viento en mph
8 10 minutos de dirección de ráfaga de viento en grados
16 Precipitación por hora en pulgadas
17 Lluvia diaria en pulgadas
ksandilands | 11/29/2018 at 03:01 PM
Thanks for doing this blog post!
Do we need to change anthing in the dld file before we load it to the logger's CPU? I just copied the text from the link to a new text file and called it "wuderground.dld"
I am using a CR1000, and the value I get for result is: -2 which whe I look in the .dld file means connected but not successful, did not receive "200 OK" from server and no data appear on my PWS.
any suggestions?
Robin D | 11/30/2018 at 11:19 AM
Thanks for your question. Unfortunately, our experts on this topic are out of the office currently. As soon as we have the answer for you, we'll post it. Thanks for your patience.
GaryTRoberts | 12/10/2018 at 02:32 PM
Ksandilands,
You should not have to make any changes to the DLD file. Just place it on the CPU and make sure to reference it in your program using "Include". As for the -2 error, it something is amiss with the information being sent to the server. If you make this lines in the include file Public instead of Dims, they can help us get a clue as to what WeatherUndergrounds server isn't liking:
Dim http_get_head As String * 500
Dim http_get_resp As String * 50
Dim http_get_uri As String * 1100
It would be good to set what http_get_uri, http_get_head, and http_get_response say after the failer. We can then go from there.
Please log in or register to comment.