Lesson 10 – L: Launch Your Learning: How Can We Troubleshoot a Solar Energy System?
L: Launch Your Learning
From Symptom to Safe Next Action
Engineers use a repeatable process to investigate unexpected results.
- Define the symptom. State what is different from what was expected.
- Pause for safety. Decide what can be observed safely and what requires authorized support.
- Compare to the baseline. Identify what normal operation looked like and what may have changed.
- Trace the energy pathway. Identify where there is evidence of expected behavior and where evidence is missing.
- Collect evidence before changing anything. Use observations, records, indicators, and only authorized measurements.
- Test one hypothesis at a time. Avoid changing several conditions at once.
- Classify the probable issue. Use the available evidence to make the most responsible conclusion.
- Recommend the next safe action. Identify what should happen next and who is authorized to do it.
- Document the reasoning. Record the claim, evidence, uncertainty, and recommendation.
This process helps teams avoid a common error: changing something before they understand the problem. If a team changes several switches, reconnects a device, and moves the panel all at once, it becomes difficult to know which change affected the result.
Worked Example: A Phone Will Not Charge
A solar charging cart was documented as working normally when it charged one approved phone. Later, the phone does not show its charging symbol.
|
Baseline Record |
Current Evidence |
|---|---|
|
The panel was in direct light. |
The panel is in direct light. |
|
The battery status showed normal charge. |
The battery status shows normal charge. |
|
The inverter switch was ON. |
The inverter switch is OFF. |
|
The approved charger and cable were connected. |
The approved charger and cable appear connected. |
Step 1: State the symptom
The approved phone does not show a charging symbol.
Step 2: Compare evidence with the baseline
The inverter switch is OFF now, but it was ON in the documented normal condition.
Step 3: Make a cautious classification
The most probable classification is an operating/setup issue because a documented operating condition differs from the baseline.
Step 4: Recommend a safe next action
An authorized person should verify the switch position and return the system to the approved operating condition if appropriate.
This is not the same as saying that the inverter is broken. The evidence points first to a changed operating condition.
Pause and Think
Suppose the inverter switch is ON, but the phone still does not charge. What additional evidence would you want before deciding that the inverter is faulty?
Four Responsible Classifications
|
Classification |
What It Means |
Evidence Pattern |
Responsible Next Action |
|---|---|---|---|
|
Component fault |
A component may not be functioning as intended. |
Setup and normal conditions match the baseline, but evidence suggests that one component may not be producing or passing the expected response. |
Document the evidence and recommend instructor or qualified-technician review. |
|
Operating/setup issue |
A condition differs from the approved baseline. |
A switch, setting, position, connection, selected load, or other operating condition differs. |
Identify the mismatch and recommend return to the approved condition under authorized direction. |
|
System-design limitation |
The system may be functioning as intended but cannot meet the current demand or condition. |
Some evidence shows normal operation, but the demand, load, or environmental condition exceeds the documented system capability. |
Recommend load management, design review, scheduling, or additional testing. |
|
Insufficient evidence |
The available information is not enough for a responsible conclusion. |
Important observations, conditions, records, or approved readings are missing or conflicting. |
Identify the missing evidence and who is authorized to gather it. |
Key Idea
A responsible diagnosis is not the fastest guess. It is the conclusion best supported by the available evidence, including a clear statement of what is still unknown.
Real-Life Grid Scenario: A Solar Mini-Grid During a Heat Wave
A solar mini-grid supplies electricity to a community center, several small businesses, and a water pump. On a very hot afternoon, more people use fans and device chargers than usual. The water pump still operates, but the community center’s lights dim and some device chargers stop working.
A team must investigate without assuming that the panels, battery, or inverter have failed.
|
Evidence |
What It Might Suggest |
|---|---|
|
The water pump is still operating. |
At least some energy is reaching an important load. |
|
More fans and chargers are being used than usual. |
Demand may be greater than the usual operating condition. |
|
The system was designed around a lower typical load. |
The current demand may exceed a documented design limit. |
|
The lights dim only when several devices are added. |
The symptom may be related to the amount of demand, not necessarily a failed component. |
A responsible team would ask what the baseline record says about normal load use, which loads are essential, and what performance data are needed before it recommends a change.
Pause and Think
Suppose the inverter switch is ON, but the phone still does not charge. What additional evidence would you want before deciding that the inverter is faulty?
Scenario Comparison: Fault or Limitation?
Scenario A: A Possible Component Problem
A system’s configuration, light condition, switch positions, and approved load all match the baseline. The controller and battery indicators match the baseline. The inverter is switched on, but its normal output indicator is not visible. An authorized person records an output value that differs from the baseline.
What can be concluded?
- The system has evidence of an unexpected difference at or near the inverter stage.
- The evidence does not prove the exact cause.
- A responsible conclusion is that there may be a component-related issue requiring additional authorized investigation.
Scenario B: A Possible Design Limitation
A system was documented as charging one approved phone. During an emergency drill, one phone, two additional phones, and a tablet are connected at the same time. The original phone charges, but the tablet does not.
What can be concluded?
- At least part of the system appears to be operating.
- The demand has changed from the documented baseline.
- The system may not have been designed or approved to charge all four devices simultaneously.
- Additional performance information is needed before claiming a component fault.
Pause and Think
How could Scenario B lead to a design improvement rather than a repair? Consider options such as charging fewer devices at one time, scheduling device charging, using more efficient devices, gathering data on power demand, or redesigning the system to meet a larger load requirement.
