Heliotropic 3k

Abstract

Heliotropic 3K and the H3K Apparatus provide a constant, all day long real time method of leading the Tracker - Solar Panel system to constantly face perpendicularly against the sun. The Solar Power Industry is presented with an opportunity to increase significantly its solar power production, bypassing pre-existing difficulties and focusing on the desideratum. With an optimized and adaptable self-calibrating manner, through a novel method of exploiting a simple, yet, unexploited at its full potential geometrical phenomenon, Heliotropic 3K transforms a solar panel's surface into the core of an artificially intelligent 360° sun tracing robot, which respects all the aspects of the human evolution and operates to this evolution's benefits.

Description

[0001] Heliotropic 3K

[0002] Description

[0003] Technical Field

[0004] Heliotropic 3K is a novel process accompanied by its apparatus. It seeks its way into the Power Industry and in the field of Solar Energy. It offers a technical solution to the existing problem of “How” a solar panel can be consistently facing perpendicularly against the sun for as long as possible during the day, as to maximize its solar power production.

[0005] Background Art

[0006] So far the Solar Energy field has evolved in several directions. The improvement of the solar panels’ material quality, the transition from stable solar panels to rotating ones which use single-axis and dual-axis trackers, to then the “smart tracking”, tracing the sun and turning the tracker towards it. These tracers use astronomy algorithms regarding time, date and geographical location data, sensors that use chemistry, temperature, pressure or even photocells that work like “eyes”, locating the sun’s position with tremendous precision, again accompanied by the algorithm of how to translate this sun’s position to tracker commands as to turn the solar panel’s surface towards that position, how to translate solar tracing to solar tracking. Most usually, even with perfect tracing, there is still a small amount of degree declination which, however, significantly prevents the solar panel from producing at its full capability, so the pursuit persists. Other methods that exist include bifacial solar panels that collect sun from both front and back sides, as well as special glasses for the panels which aim to verticalize the sunlight. Certainly there are even more known and unknown inventions and methods, developed even at this very moment.

[0007] Disclosure of invention

[0008] Heliotropic 3K is a process that presents a new technical solution to the pursuit of centering the solar panel perpendicularly against the sun. It is the process of adapting four small solar panels on the circumference of a main solar panel, on the top, right, bottom and left side to act as its ‘organic parts’ and the process of controlling directly the dual-axis tracker through these panels’ power production measurements. This process leads to the invention of the necessary apparatus, the “H3K Apparatus”. The H3K Apparatus is adaptable and it can come by itself and get adapted on a solar panel that is mounted on a tracker or even come from the factory together with the solar panel. This apparatus is robotic, and it calibrates itself according to the circumstances of the day, as will appear in the process’s description. Description

[0009] The H3K Apparatus consists of the following five parts: i) The “H3KPanels” (Fig.1 ), four identical small solar panels equipped with a high-precision mechanism of angle adjustment from 0° to 180°. ii) The “H3KBrain”. An electronic / digital device with a chip, a computer, which takes input from the H3KPanels and outputs to the potential tracker’s operating mechanism (Fig 2) (Fig 3)

[0010] Heliotropic 3K and the H3K Apparatus transform a solar panel and its rotating mechanism into an autonomous robotic heliotropic unit (heliotropism is the behavior of some plants, like the sunflower, to turn towards the sun). This unit works with the sun in real time creating something like a tick-tock clock mechanism or a left foot - right foot walk. It works at any given moment of the day and at any prior position it may find itself related to the sun’s position. For the purposes of this description each individual completed “autonomous robotic heliotropic unit’’ that carries the H3K Apparatus and applies the Heliotropic 3K process will be called an “H3KUnit”

[0011] An H3KUnit consists of the following parts: i) The H3K Apparatus (Fig.3). ii) The main solar panel (Fig.4) of which we aim to increase its solar power production to the maximum. The main solar panel can also be a pack of panels that are placed around each other, creating a massive solar panel surface, something that happens often. For the purposes of this description I will describe the Heliotropic 3K system applied on only one solar panel, which I will often call in short with the abbreviation “MSP”, instead of “Main Solar Panel”. iii) The dual-axis tracker or any dual-axis horizontal and vertical rotating mechanism (Fig.5).

[0012] The H3KBrain

[0013] - H3KBrain’s core data values are the solar power production measurements of the four H3KPanels, which are constantly measured into the TPP, RPP, BPP and LPP variables accorded to the top, right, bottom and left H3KPanels and the available tracker axes’ arcs of rotation measured in degrees, each axis’ angle of one rotation’s instance.

[0014] - The H3KBrain requests from the user to insert these two angle measurements manually, the measurements that regard to the angle the axes rotate in one rotation’s instance. Then the H3KBrain saves these two values in the HorTrackerAngle and the VerTrackerAngle variables and it creates two constants, the HQAngle and the VQAngle. Their values equal to the ! (one fourth) of the according axes’ TrackerAngle values. For example if the horizontal axis turns 1 ° at Description a rotation’s instance the HorTrackerAngle value that is inserted is “1” and the HQAngle constant that is created is “0.25”.

[0015] - The H3K Brain controls the H3KPanels’ angle adjustment mechanisms. It can set their angle on a certain degree, such as 0°, 30°, (45°-5QAngle), 90°, (90°+3QAngle) etc and it can also rotate the H3KPanels by micro moves in QAngle steps, increasing or decreasing the angle of the Horizontal or the Vertical H3KPanels according to the HQAngle constant or the VQAngle constant respectively.

[0016] - Whenever the H3KBrain increases or decreases an H3KPanel’s angle, it also increases or decreases the angle of the opposite H3KPanel equally, thus each two opposite H3KPanels are always in the same angle. The Left and the Right H3KPanels form the Horizontal Pair of opposite H3KPanels while the Top and the Bottom H3KPanels form the Vertical Pair of opposite H3KPanels.

[0017] - The H3KBrain contains the procedures which are run during the day. These procedures store and recall values to and from the program’s arrays and variables or read and process the power production measurements of the four H3KPanels. They are grouped in three stages. These stages are named Olympus, Diana and Chronos. The full program of a day’s procedures and these procedures’ algorithms are presented further below, before the conclusions.

[0018] - The H3KBrain constantly measures the power production of each individual H3KPanel and computes the H3KPanels in a looping and serial order, right, bottom, left, top, right, bottom, left, top, right etc. It compares the power production of the given H3KPanel to its according MaxPP and MinPP variables and then performs accordingly. In other procedures the H3KBrain compares the power production of the processed H3KPanel with its own power production before or after a QAngle adjustment, comparisons that determine which actions are to be taken. These procedures are equally essential and important, as according to their measurements and the computing of these procedures the H3K Brain eventually sends operating commands to the dual-axis tracker, related to the H3KPanel that is being processed.

[0019] - The H3kBrain reads the H3KPanels and the axes in numbers, “1”, “2”, “3” and “4” for the top, right, bottom and left H3KPanel accordingly and “1” and “2” for the horizontal and vertical axis accordingly.

[0020] - The H3KBrain stores the last four moves of each axis in an LFM array, for example, “LFM.1.4 = 2” means the last move of the horizontal axis was towards its right side.

[0021] - Between two consecutive rotations the H3KBrain also compares the given H3KPanel’s power production to its previous power production measurement updating indicators for each Description

[0022] H3KPanel indicating if its power production has decreased or increased. This process has an allowed percentage deviation, such as 2%-3%, a percentage that can be adjusted to the area and region of the H3KUnit. It is used only after the fourth move of the stage 3, Chronos, and is operated only on the H3KPanel that has shown to be on the front side of each axis’ rotations. It is used in order to proceed in “Evening Stance”, to determine when the sun’s intensity starts decreasing later in the day, and it resets itself if there are interruptions from clouds.

[0023] - The H3KBrain contains two indicators for each axis; these are the TrackerError.Axis indicator and the BMP. Axis indicator, BMF standing for “Backwards Move Forbidden”. They are activated circumstantially, when the tracker does not perform a rotation tick equal to its normal rotation angle. This problem is rectified algorithmically, as will be analyzed in the process’s description, through the H3KBrain’s programming. A maintenance log can also be added here so, when a problematic coordination is processed it can also be reported in there.

[0024] - Unrelated to the sun-tracking operations, the H3KBrain has the ability to connect to Wi-Fi and to provide an environmental interface. It monitors in real time the H3KUnit’s power production or monitors several H3KUnits together and provides a high-end program, product and result. In this interface, the owner / user has the ability to remotely move the angle and the direction of the H3KUnit, allowing the Heliotropic 3K process to restart and turn the main solar panel back towards the sun.

[0025] - Finally, in respect to the above, always after checks and priorities, nonessential procedures can be added as well which are nonessential for the positioning of the main solar panel perpendicularly against the sun yet are useful. For example “wind protection” or “snow protection” procedures that position the main solar panel in a horizontal or vertical position, respectively. However, the environmental interface and the non-essential procedures are not included in the programming presentation further below in the description.

[0026] The H3K Apparatus Setup

[0027] In order to setup the H3K Apparatus we place the four H3K Panels on the four sides of the main solar panel at a 0° arrangement. The 0° arrangement is the flat position on the sides of the main solar panel, facing left, right, up and down, making the H3K Panels and the MSP’s surface form a 90° corner (Fig.6) (Fig.7). The 90° arrangement is when the H3KPanels are in parallel with the MSP, creating an expansion of its surface (Fig.8). This 90° arrangement must be so precise that each pair of opposite H3KPanels should have laser pointers and receivers which would confirm the 90° formation and create a cross in front of the MSP. Description

[0028] After adapting the H3KPanels on the four sides of the MSP we connect them to the H3KBrain we insert the axes’ rotation angles and we connect the H3KBrain to the dual-axis tracker’s rotating mechanism.

[0029] The “Cube Effect”

[0030] The Cube Effect is the simple geometrical phenomenon that the H3K Apparatus exploits.

[0031] The H3KPanels are put in a 0° formation, flat on the sides of the MSP, creating a 90° corner with the MSP’s surface, so when a main solar panel’s side gets hit by the sun then the according H3KPanel gets hit by the sun, increases power production and signals the H3KBrain.

[0032] Due to laws of physics and geometry only a maximum of two MSP sides with mounted H3KPanels are able to get hit directly by the sun at any given moment, one vertical and one horizontal (Fig.6) (Fig.7).

[0033] The H3KBrain calculates that an H3KPanel has increased its power production and proceeds to command the rotating mechanism to rotate by one TrackerAngle towards the side of this H3KPanel that gets hit by the sun. This procedure repeats itself until the H3KPanel ceases getting hit by the sun.

[0034] This actually means that the tracker is commanded to rotate until the first rotation degree in which the given H3KPanel has come in parallel with the direction of the sunrays. Geometrically, this means that its opposite H3KPanel is also at the same in parallel direction and that the main solar panel surface’s axis which is between these two H3K Panels has been aligned vertically against the direction of the sunrays (Fig.9). Since it is the same procedure for all four H3KPanels, if there were a second MSP’s side and a second H3KPanel getting hit by the sun, what follows is the alignment of the second MSP surface’s axis, which geometrically means that the MSP’s surface has come in a cross-centered position that faces perpendicularly against the sun (Fig.10).

[0035] This is the “Cube Effect”, straight lines and parallel sides. All four H3KPanels are in parallel to the direction of the sunrays forbidding the MSP from moving away by being at the limit of being hit by the sunrays and increasing their power production again. When the sun moves, again a maximum of two MSP sides with H3KPanels, the ones on the sun’s movement direction, will increase their power production, activating the H3KBrain’s functions again, forcing the MSP’s surface again to cross-center perpendicularly against the sun’s new position.

[0036] Today’s solar panels however do not have a 180° reception angle in order to produce solar power, so a set of procedures and automations had to be inserted. Description

[0037] In a few words, two opposite H3KPanels are commanded to increase their angle in QAngles and when the first one starts increasing or reducing power production the H3KBrain commands the tracker to move towards the side of the H3KPanel that is affected by the sun, then resets the H3KPanels’ angle and repeats the process. If both opposite H3KPanels get hit by the sun simultaneously then the H3KBrain saves their power production measurement in an “UnaffectedBySun” constant and decreases the H3KPanels’ angle by 2QAngles, which is the half of a tracker’s rotation instance. It waits for the sun to move (relatively, the sun doesn’t move, the earth rotates around itself and around the sun) and force one of the two opposite H3KPanels to produce power equal to its according “UnaffectedBySun” constant, as to compute this, give the according move command to the tracker and restart the process. It always aims to the same, to find the first QAngle that both opposite H3KPanels get hit simultaneously, save their power production measurement, decrease the angle of these opposite H3KPanels by 2QAngles, which is half a tracker’s rotation instance, and wait for the sun to move.

[0038] This is in short the Heliotropic 3K Cube Mode and although it could theoritically create the desired tick-tock clock or left foot-right foot walking procedure, it would be a subject to the H3KPanels’ angle of receptiveness. The two opposite H3KPanels should have the exact same ability to produce minimum power when the sunlight hits them from different angles, so, even if this could be arranged in the H3KPanels’ factory, the exploitation of the “Cube Effect” had to be evolved even further than the Cube Mode.

[0039] The evolution of the Heliotropic 3K Cube Mode is processed by the same apparatus, the H3K Apparatus and is the Heliotropic 3K Cross Mode. An optimal mode which uses the arrays and the variables mentioned in the H3KBrain’s analysis and is described analytically below.

[0040] Heliotropic 3K Cross Mode

[0041] Stage One: Olympus

[0042] - The H3KBrain loads the Right H3KPanel, sets the Horizontal H3KPanels at a 0° position and commands them to rotate 4 moves forward in HQAngle micro moves. If one of the H3KPanels shows a decrease in its power production compared to its previous power production measurement this means that the sun is 90° to 179° towards the side of this H3KPanel, so the H3KBrain rotates the tracker’s horizontal axis by 90° towards this H3KPanel and restarts the Olympus. Now this H3KPanel will show an increase in its power production if its HQAngle is increased. If none of the H3KPanels showed a decrease in their power production after the 4 forward QAngles then the H3KBrain puts the H3KPanels back to 0° and proceeds. Description

[0043] - A counting variable “D”, for “Distance”, is set to 0 and the H3KBrain increases the horizontal pair’s H3KPanels’ angle in HQAngle steps counting how many steps have been taken. It compares the power production of both H3KPanels with their power production at their previous QAngle position until an H3KPanel starts decreasing power production or until a 180° rotation has been completed. This is “Until (D > 720 Div HorTrackerAngle)” QAngles, but this type of details appears better in the algorithm so I will remain in the essence of the procedures.

[0044] - If none of the H3KPanels gets affected by the sun then the sun is exactly behind the main solar panel, so the H3KBrain rotates the horizontal tracker axis by 180° and sets the horizontal H3KPanels’ angle at the 90° position, ready for Diana.

[0045] - Alternatively, if the sun’s angle is at one side from 0° to 89°, the power production of a single first H3KPanel will start increasing, until a certain point after which this power production will peak and start decreasing. When the first H3KPanel’s power production starts decreasing the H3KBrain stops the process and rotates the tracker for the relative distance as calculated by the computational mathematic ((90 Div HorTrackerAngle) - (D Div 4)). This computational mathematic means the H3KBrain divides the 90° in tracker rotation instances, subtracts the D number of HQAngles that the H3KPanel needed to peak its power production, and rotates the tracker for so many tracker rotation instances as much as the result of the subtraction. “Div” is a computing command that only gives the integer part of the division. Then it sets the horizontal H3KPanels at 90° to be ready for Diana and proceeds to the vertical pair.

[0046] - The H3KBrain loads the Top H3KPanel. Since the ground does not need to be measured and the horizontal axis has already turned towards a side this is a matter of 0 to 90 vertical degrees, which means that definitely one of the two H3KPanels will first increase and decrease its power production, compared to its own power production measurement at its previous VQAngle. The vertical H3KPanels are set to 0°, a counting variable “D” is set to 0 and the H3KBrain increases the vertical pair’s H3KPanels’ angle, in VQAngle steps this time, counting how many steps have been taken, comparing the power production of each H3KPanel with its own power production at its previous position until an H3KPanel starts showing a decrease.

[0047] - When the first H3KPanel’s power production starts decreasing the H3KBrain stops the process, rotates the tracker for the relative distance as calculated by the computational mathematic ((90 Div VerTrackerAngle) - (D Div 4)) towards this H3KPanel, sets both vertical H3KPanels at 90° to be ready for Diana, loads the Right H3KPanel, sets the value of the “DianaCounter” variable to 0 and proceeds to stage 2, Diana. Description

[0048] The Olympus stage of procedures directs the MSP to an only relative position, to face adequately towards the sun, so Diana can easier direct it to an accurate sun related position through one by one rotates and then pass the process to Chronos, for Chronos to carry the process through the day.

[0049] Stage Two: Diana

[0050] - The H3KPanels start getting processed in a serial looping order, T, R, B, L, T, R, B, L, etc.

[0051] - In every H3KPanel’s process the H3KBrain rotates the processed H3KPanel in single QAngle steps, always together with its opposite, comparing the H3KPanel’s power production to its power production before its new QAngle position. These rotations precisely are 90° to (90°-2QAngle), (90°-2QAngle) to (90°-3QAngle), (90°-3QAngle) to (90°+2QAngle), (90°+2QAngle) to (90°+3QAngle) and then back to 90° again.

[0052] - If the solar power production of the H3KPanel increases between (90°-2QAngle) to (90°-3QAngle) or between (90°+2QAngle) to (90°+3QAngle), the H3KBrain commands the tracker to move one TrackerAngle accordingly. This is, if the power production of the H3KPanel increases from the (90°-2QAngle) to the (90°-3QAngle) the H3KBrain commands the tracker to rotate one TrackerAngle towards the H3KPanel that is being processed and resets the “DianaCounter” back to 0, sets the H3KPanels back to 90° and repeats the step by step QAngle rotation procedure for the same H3KPanel. Similarly, if the power production of the H3KPanel increases from the (90°+2QAngle) to the (90°+3QAngle) the H3KBrain commands the tracker to rotate by one TrackerAngle towards the side of the Opposite H3KPanel, then resets the “DianaCounter” back to 0, the H3KPanels to back to 90° and repeats the step by step QAngle rotation procedure for the same H3KPanel that is being processed all this time.

[0053] - When the Tracker-MSP system reaches to an angle where this H3KPanel’s power production peaks between the (90°-2QAngle) and the (90°+2 QAngle) the H3KBrain moves on to measure and process the next H3KPanel.

[0054] - This process repeats itself in a serial order amongst the four H3KPanels until the H3KBrain does not command a TrackerAngle rotation for two circles of processing, for 8 consecutive H3KPanels’ processes, when the DianaCounter has reached to “8”.

[0055] - When this occurs, it means that the MSP has come to an angle perpendicularly placed against the sun or in a relative angle perpendicularly against the sun, a relative angle which mathematically equals to (+ / - ^ TrackerAngle) including the limits, and the H3KPanels find their maximum power production values between their (90°-2QAngle) and (90°+2 QAngle) positions. Description

[0056] - Diana now starts the preparation procedures for the Chronos stage. Loads the Right H3KPanel and stores its current power production, CPP, value in its MaxPP and MinPP variables, while it also saves the Left H3KPanel’s current power production value, OpCPP, in the OpMaxPP and OpMinPP variables. It sets the “D” counter to 6, sets the two horizontal H3KPanels at (90°+3QAngle) and starts decreasing the H3KPanels’ angle by one QAngle per instance and the counter by one, comparing the MaxPP, OpMaxPP, MinPP and OpMinPP variables’ values with the values of the CPP and OpCPP variables, storing accordingly the minimum and maximum power production measurements of each H3KPanel between these 6QAngles. It saves these values in the according RMaxPP, LMaxPP, RMinPP and LMinPP variables and sets the two horizontal H3KPanels at (90°-2QAngle) as ready for Chronos.

[0057] - The H3KBrain then loads the Top H3KPanel and performs the same procedure for the vertical pair of H3KPanels, in VQAngles micro moves this time, saving the MaxPP, OpMaxPP, MinPP and OpMinPP in the TMaxPP, BMaxPP, TMinPP and BMinPP variables respectively and sets the two vertical H3KPanels to (90°-2QAngle) as ready for Chronos.

[0058] - Finally it resets a number of variables and arrays as appropriately needed, and sends the process H3KPanel to Chronos.

[0059] This is the end of the Diana stage of procedures and it means that the main solar panel is perpendicularly positioned against the sun or at relative angle of + / -1 / 2 a tracker’s rotation instance towards each axis’ directions respectively. It means that the H3KBrain has a MaxPP and a MinPP value for each H3KPanel between these angles, including the limits, and that the H3KPanels are set to the (90°-2QAngle) position, again respectively to the axis they regard to.

[0060] With the data produced from Diana, the current positions of the sun and the MSP and the (90°-2QAngle) position of the H3KPanels, if we set the tracker to wait until an H3KPanel starts producing power equal to or above its MaxPP variable we cause the maximum solar power production that the MSP can afford to produce during the two consecutive tracker’s positions.

[0061] An extremely simplifying, yet very clarifying, example is shown in Figure 11, where the tracker is supposed to have a 90° rotation instance, a QAngle thus is 22.5°, the (90°-2QAngle) position equals to 45°, the tracker will rotate when the sun reaches at sun position 2, and will wait for the sun to reach at sun position 4 in order to rotate again (Fig. 11). This figure gives a bold understanding to all these procedures and all these QAngle micro moves that take place.

[0062] The core differences between Diana and Chronos are that Diana accepts the MaxPP of the H3KPanels to be at the + / - 2QAngle limits while Chronos does not. Diana is constantly adjusting the H3KPanels’ angle during its processes while Chronos is mainly a “waiting” procedure. Description

[0063] Procedures Next, Load [x] and SaveValues

[0064] Before I proceed to the description of Chronos I find it important to describe how the H3KPanels serially loop, what it means when an H3KPanel “gets loaded” and how the values of the operated variables eventually get saved in the according H3KBrain’s variables.

[0065] Procedure Next

[0066] The H3KBrain perceives the H3KPanels as numbers. The Top H3KPanel is “1”, the Right Is “2”, the Bottom is “3” and the Left is “4”. The relevant variables are the “H3KP” variable and the “OpH3KP” variable. When the “Next;” procedure is called it adds “+1” to these variables and then checks if the number created is “5” in which case it turns it to “1”.

[0067] Next

[0068] H3KP <= H3KP+1 ; OpH3KP <= OpH3KP+1 ;

[0069] If H3KP = 5 then H3KP <= 1 End If

[0070] If OpH3KP = 5 then OpH3KP <= 1; End If

[0071] Next

[0072] Procedure Load [x]

[0073] The command that calls the Load [x] procedure is “Load H3KP;”. Load [x] takes the H3KPanel as the number it is and proceeds to store the H3KPanel’s and the opposite H3KPanel’s stored values into the variables that are operated by the H3KBrain’s procedures. The power production variables (TPP, RPP, BPP and LPP) are also loaded appropriately. The stored values are TMaxPP, TMinPP, RMaxPP, RMinPP, BMaxPP, BMinPP, LMaxPP and LMinPP. The variables operated are MaxPP, MinPP, OpMaxPP, OpMinPP, Axis, QAngle, CPP and OpCPP. In this point I will give only one example instead of writing the whole Load [x] code.

[0074] Load [x]

[0075] If x = 1 then

[0076] MaxPP <= TMaxPP; MinPP<= TMinPP;

[0077] OpMaxPP <= BMaxPP; OpMinPP <= BMinPP;

[0078] Axis <= 2; QAngle <= VQAngle;

[0079] CPP => TPP; OpCPP => BPP; ( “=>” is an interconnection symbol )

[0080] End If

[0081] If x = 2 then (the same for R / L H3KPanels, Axis “1”, HQAngle) End If

[0082] If x = 3 then (the same for B / T H3KPanels, Axis “2”, VQAngle) End If

[0083] If x = 4 then (the same for L / R H3KPanels, Axis “1”, HQAngle) End If

[0084] Load Description

[0085] Procedure SaveValues

[0086] When “SaveValues;” is called the values of the variables that got operated get stored back into the loaded H3KPanels’ variables according to the process H3KPanel, hence there is no need for an [x] indicator. Only the MaxPP, MinPP, OpMaxPP and OpMinPP variables are saved from the operations, with their values getting saved into the TMaxPP, TMinPP, RMaxPP, RMinPP, BMaxPP, BMinPP, LMaxPP and LMinPP variables respectively. There is also a SaveValue procedure that only saves the MaxPP and the MinPP values of the loaded H3KPanel, used when the OpMaxPP and OpMinPP values are not needed in the operations. It functions similarly to the SaveValues procedure for which again, in this point I will give only one example instead of writing the whole SaveValues code.

[0087] SaveValues

[0088] If H3KP = 4 then

[0089] LMaxPP <= MaxPP; LMinPP <= MinPP;

[0090] RMaxPP <= OpMaxPP; RMinPP <= OpMinPP;

[0091] End If

[0092] If H3KP = 1 then (the same for T / B H3KPanels) End If

[0093] If H3KP = 2 then (the same for R / L H3KPanels) End If

[0094] If H3KP = 3 then (the same for B / T H3KPanels) End If

[0095] SaveValues

[0096] The reason I put this interfering description here was to explain the fact that when an H3KPanel is loaded it is not an abstract or fleeting imaginary process. A whole pack of relevant information is loaded together, including the opposite H3KPanel’s values into the corresponding opposite variables, the axis, the QAngle and the constantly varying power production of the two opposite H3KPanels into CPP and OpCPP. Similarly, when values are saved they are instantly stored in corresponding H3KPanels’ according variables and are ready to be recalled by the procedures and take part in their operations. These procedures and operations are the same for all H3KPanels, yet need the occasional correctly corresponding different values.

[0097] With these stated the description of Chronos, which is already a large and complex pack of procedures, can become easier and more understandable, without the need to explain every time how or why certain values exist and reach to the desired state.

[0098] As described, Chronos finds every H3KPanel at a (90°-2QAngle), all H3KPanels’ MaxPP and MinPP values, the sun’s position related the MSP surface’s angle at an angle of (+ / - Vz TrackerAngle rotation instances) and a number of appropriately reset arrays and variables. Description

[0099] Stage Three: Chronos

[0100] - This third part of the program has three main procedures. The first procedure is called “Chronos”. It is constantly processing the H3KPanels in a serial and looping order, computing if the given H3KPanel’s current power production, the CPP variable, is higher or lower than its MaxPP and MinPP variables respectively.

[0101] - If the CPP is higher than the MaxPP value Chronos sends the H3KPanel to a “PreMoveCheck” procedure, which tests if these conditions are enough to consider the momentum as the right moment to rotate the axis or if it is just a matter of an increase in the sun’s intensity. If the rotation is eventually computed as desirable, if the sun is truly between the tracker’s current position and the tracker’s position after a single rotation’s instance towards the process H3KPanel, PreMoveCheck executes the rotation and sends the H3KPanel to an “AfterMoveCheck” procedure. AfterMoveCheck and PreMoveCheck are going to insert the new MaxPP and MinPP values of the specific axis’ two H3KPanels into their respective variables and will then reset the process by sending the H3KPanel back to Chronos.

[0102] - If Chronos computes that the current power production of an H3KPanel abruptly decreased below its MinPP value, if the CPP is lower than the MinPP value, then this means that a cloud has interfered. It saves the current H3KPanel’s and the opposite H3KPanel’s power production measurements as their new MaxPP values respectively so when the sun comes out again the H3KPanels’ MaxPP values will be lower than the power production measurement of that moment. Chronos will compute this and it will send each one H3KPanel at its turn to the PreMoveCheck procedure to gain new MaxPP and MinPP values from it or from the AfterMoveCheck procedure if a rotation is approved.

[0103] Another action that is taken before the H3KPanel is sent to the PreMoveCheck procedure when an H3KPanel’s CPP drops below its MinPP is that an Interrupt. H3KP variable and an lnterrupt.OpH3KP variable are set to “1”. This is a signal to the “Curve” procedure, the fourth of the five procedures that exists into Chronos. Curve only operates on the forward H3KPanels by first checking the last four moves array of the axis. It determines if the power production of an H3KPanel has peaked before reaching its MaxPP and outputs an lnconsistentCurve.H3KP price when the case is such, used to eventually initiate one H3KPanel’s “evening stance”. This will be described more extensively deeper into Chronos’ description. Curve takes action before the H3KPanel’s CPP reduces to lower than the H3KPanel’s MinPP variable thus separates the occasions of a cloud’s interference and the reduction of the sun’s intensity. Description

[0104] - If Chronos computes that the current power production of an H3KPanel increases above its MaxPP value then it sends the H3KPanel directly to the PreMoveCheck procedure.

[0105] - The PreMoveCheck procedure initially stores the current power production value of the H3KPanel’s (90°-2QAngle) position in the variable PrPP, a variable and abbreviation that stands for Previous Power Production. Then PreMoveCheck decreases the angle of the H3KPanel by 2QAngles in two single QAngle steps, then increases the H3KPanel’s angle by 4QAngles, in a 3QAngle step and a single QAngle step, then returns it back to where it was initially found. Unless the process is in a tracker’s fault rectification, the above steps mean (90°-2QAngle) to (90°-3QAngle), (90°-3QAngle) to (90°-4QAngle), (90°-4QAngle) to (90°-QAngle), (90°-QAngle) to 90° and 90° to (90°-2QAngle).

[0106] - Regarding to the essence of the rotation, if the sun is exactly at the right angle between the two consecutive tracker’s positions, perpendicular against the process H3KPanel, then the given H3KPanel’s power production at all the above four QAngle positions, its CPP, will present a value lower than the one stored while at the (90°-2QAngle) position, its PrPP.

[0107] - After the first QAngle decrease PreMoveCheck saves the H3KPanel’s power production measurement as its new MinPP value in case the sun’s intensity has increased. During the two decreasing QAngle steps and with the values of the OpMinPP and OpCPP variables, PreMoveCheck also compares the opposite H3KPanel’s current power production measurement to its own MinPP, in case a rotation occurs later in the PreMoveCheck procedure. If during the two decreasing QAngle steps this comparison shows that the power production measurement of this opposite H3KPanel is lower than the OpMinPP value this power production measurement, the OpCPP, is saved into the OpMinPP variable to be later saved into the corresponding H3KPanel’s MinPP variable.

[0108] - If during the two decreasing QAngle steps, (90°-3QAngle) and (90°-4QAngle), the CPP shows a value higher than the PrPP variable stored in the (90°-2QAngle) position it means the sun has moved further than the middle angle between the current and the next axis’ rotations. The H3KBrain saves the OpCPP into the OpMinPP as precise in case only one rotation is needed, executes the rotation of the according axis towards the given H3KPanel and proceeds to the AfterMoveCheck procedure.

[0109] This scenario can only occur if a cloud interfered for a long time and the sun has appeared again. It is instantly calculated by Chronos, due to the procedures that took place when the power production of the H3KPanels first dropped below their MinPP, because PreMoveCheck stored the measurements as the new MaxPP values of the axis’ H3KPanels when the cloud first Description interfered. PreMoveCheck and AfterMoveCheck will rotate the tracker by rotation instances towards the process H3KPanel and recheck it until the H3KUnit regains a new correct position against the sun. At the last two tracker rotations they also find and store the new correct MaxPP, MinPP, OpMaxPP and OpMinPP values of the two axis’ H3KPanels as related to the new sun’s and tracker’s positions. They set the H3KPanels at the (90°-2QAngle) position and send it to Chronos for a final check, to get past it and move on to process the next H3KPanel.

[0110] - If during the increasing QAngle steps, (90°-QAngle) and 90°, the current power production measurement presents a higher value than the PrPP variable, then it just means the sun’s intensity has increased, so the H3KBrain, PreMoveCheck, saves the current power production measurement of the process H3KPanel as the new H3KPanel’s MaxPP and returns to Chronos.

[0111] - If during the increasing QAngle steps, (90°-QAngle) and 90°, the CPP of the H3KPanel appears decreased compared to the PrPP variable it means that the sun was vertical against the H3KPanel at the (90°-2QAngle) position, that the sun has come to the correct angle for the rotation to occur, so the H3KPanels of the axis return to the (90°-2QAngle) position, the opposite current power production gets saved in the OpMinPP value, the rotation gets executed and the under-process H3KPanel gets sent to the AfterMoveCheck.

[0112] - The AfterMoveCheck procedure receives the H3KPanel after a potential casual rotation instance. This means the H3KBrain has commanded the tracker to rotate towards an H3KPanel, the rotation has been executed and the sun is expected to travel 4QAngles above the main solar panel from the (-%TrackerAngle) position to the perpendicular position against the main solar panel’s surface and to the (+1 / TrackerAngle) position, where and when Chronos is going to calculate it and command a next axis’ rotation for this to happen again, and all of this is expected to be happening for the whole day. A potential normal rotation instance also means that the opposite H3KPanel instantly comes to a perpendicular position against the sun and for the moment produces power that equals to its maximum power production.

[0113] - AfterMoveCheck saves this OpCPP value into the OpMaxPP variable it resets the QAngle at (90°-2QAngle) in case the rotation is coming from a tracker’s fault (abnormally long rotation) rectification procedure, stores the power production of the currently processed H3KPanel into the PrPP variable, and initially commands the H3KPanel to first rotate 2 QAngle micro moves backwards. After the first backward QAngle micro move the CPP value of the currently processed H3KPanel is again saved into its MinPP since it is at a +5QAngle related to the sun and its power production is going to start increasing as the sun continues its course. Before it finishes its full process and save this OpMaxPP in the according H3KPanel’s MaxPP, Description

[0114] AfterMoveCheck increases this OpMaxPP value by an additional (OpMaxPP - OpMinPP) small amount to avoid an instant backwards rotation in case there is also an immediate increase in the sun’s intensity, as this backwards rotation would have no meaning. If this intensity decrease occurs later then the PreMoveCheck will normally compute it without a rotating command.

[0115] - If during these two backward QAngle micro moves, (90°-3QAngle) and (90°-4QAngle), the CPP measurement rises above the PrPP value it means the sun is still ahead. AfterMoveCheck saves again the OpCPP into the OpMinPP, sets the H3KPanel back to (90°-2QAngle), executes a rotation towards the currently computed H3KPanel and resends the H3KPanel to itself, to the AfterMoveCheck procedure.

[0116] - If the above does not happen AfterMoveCheck proceeds to return the H3KPanel at the (90°-2QAngle) position setting the value of a counting variable “D” to “0”. It starts increasing the H3KPanel’s angle in single QAngle steps, essentially representing the expected forward 4QAngle movement of the sun. The process H3KPanel will start increasing its power production, will peak at +4QAngles and will start decreasing its power production from the fifth QAngle and further. Before each +QAngle step the H3KBrain saves the CPP into the PrPP variable, adds +1 to the D counting variable, performs the H3KPanel’s +1QAngle rotation and compares the CPP value to the PrPP value until the CPP value becomes lower than the PrPP value. When this happens the H3KBrain saves the PrPP value into the MaxPP variable, which will now contain the new peak H3KPanel’s power production of the present momentum and the present tracker’s position. The H3KPanel is ready to be set at the (90°-2QAngle) position, to get sent to Chronos and stay still waiting.

[0117] - What interferes, however, is the “CheckTrackerError” procedure, the fifth procedure of Chronos.

[0118] - If this D counter variable is “5” or lower then CheckTrackerError does nothing and the process H3KPanel returns in the AfterMoveCheck procedure at the line where it left from. AfterMoveCheck reduces the H3KPanel’s QAngle back by the D QAngles it took it to find its MaxPP and at the same D QAngle reduction process it searches and stores possible improved OpMaxPP and OpMinPP values. It adds to the OpMaxPP the (OpMaxPP - OpMinPP) difference, it saves all the MaxPP, MinPP, OpMaxPP and OpMinPP values in the according TMaxPP, TMinPP, RMaxPP, RMinPP, BMaxPP, BMinPP, LMaxPP and LMinPP variables and returns the H3KPanel to Chronos.

[0119] - If the D counter variable’s value is bigger than “5” this means that the sun is further than one axis TrackerAngle behind, that the tracker in the specific rotation instance rotated for more Description than one axis TrackerAngle and that the opposite H3KPanel and the main solar panel are accordingly way ahead. The process H3KPanel is facing towards the sun plus one QAngle.

[0120] - This is the only time that a backwards rotation has a meaning in order to maximize the MSP’s solar power production. The axis has to rotate to the previous instance and the process H3KPanel has to be set in a QAngle position that is reduced further than the (90°-2QAngle) by the half of this false tracker rotation. The half of this false tracker rotation is calculated by the mathematical operation (D-5) / 2 which is the half of the QAngles that took place by the process H3KPanel to find its MaxPP after the subtraction of the 4QAngles that equal to the axis’ TrackerAngle and should have been the only ones used by the H3KPanel and the subtraction of the +1QAngle, the decreasing QAngle of the MaxPP computing.

[0121] Thus, what is needed is the axis to rotate once backwards, the process H3KPanel to decrease by D QAngles to return to the (90°-2QAngle) position and to decrease even further by (D-5) / 2 QAngles in order to wait for its MaxPP at the half of the distance of this specific axis’ foul rotation instance. Before the tracker’s backward rotation gets executed by the H3KBrain, the QAngle reduction is performed step by step in order to find the opposite MaxPP as well. The counter D is set to (D-5) / 2 +D, followed by a “D <= D Div 1” command in case the operation’s result is not an integer and the step by step QAngle decrease begins until D reaches to “0”. In every step the D variable decreases by 1 and the OpCPP is compared to the OpMaxPP, storing OpCPP into OpMaxPP every time the comparison shows that its value is bigger. The H3KPanels reach at the final reduced QAngle, the forward H3KPanel will be facing vertically towards the middle angle of the tracker’s full false rotation instance, Curve gets reset and the OpMinPP is set to “0” as the QAngle is going to be reduced to an unknown degree and the OpMinPP is going to present a reduction that does not need to affect the system for any reason. The stored values get saved and a “TrackerError. Axis” indicator is set to “1”. The H3KPanel then gets sent directly to Chronos to wait for the sun to reach to this scheduled angle.

[0122] - Now there is an indication for the problematic axis and its upcoming rotation while the tracker will make this particular rotation when the sun is found, once again, in the middle position between these two problematic tracker angles. In expansion to this problematic situation one more adaptation is mandated.

[0123] - When this particular rotation finally takes place with the TrackerError. Axis indication on, the H3KBrain will have to look for the peak power production of the process H3KPanel again in a longer QAngle arc than the usual (-4QAngle) to (+3QAngle) arc which is normally used, and it will do, so by increasing the QAngle of the H3KPanel for as long as its power production Description increases, until it peaks and starts decreasing. This time, after saving this peak power production value as the MaxPP value of the processed H3KPanel, the H3KBrain will have to set the H3KPanel at the normal (90°-2QAngle) position waiting for the sun to travel above the MSP, come vertical against the process H3KPanel at the (90°-2QAngle) and give the command for the next move forward. When this problematic rotation we are occupied with finally occurs, the opposite H3KPanel will again find itself perpendicularly placed against the sun and at a power production equal to its MaxPP. But it was in a (90°-2QAngle-% extra QAngle) position and it will be now set to its normal (90°-2QAngle) position so the sun is bound to travel from behind to above and beyond the rear H3KPanel, making the values highly complex and unpredictable, especially if clouds interfere or there is an increase in the sun’s intensity.

[0124] For this reason when this particular rotation finally takes place, when the AfterMoveCheck has found the new MaxPP through the “D” counter process and enters the CheckTrackerError procedure, CheckTrackerError picks up the TrackerError. Axis indicator, sets it back to “0”, again sets the OpMinPP to “0” and sets up a BMF.Axis indication to “1”, BMF standing for Backwards Move Forbidden. This BMF.Axis value is checked by the “R1” procedure, the procedure that sends the rotating command to the tracker towards the H3KPanel that is being processed. R2 is the procedure that rotates the axis towards the opposite H3KPanel but does not have these checks as it is used only in occasions where the backwards rotation is preapproved.

[0125] - If R1 finds the BMF.Axis value at “1” it checks if the LFM.Axis.H3KP value indicates that the last rotation of the axis was towards the side of the process H3KPanel, which is the same as the side towards which the axis is allowed to rotate next. - If it was, it executes the rotation, updates the last four moves array and sets the BMF.Axis back to “0”.

[0126] - If it was not, it is a peculiar case which is highly unexpected but not impossible. It is the case that a cloud has interfered during this rectification process and the forward H3KPanel dropped below its MinPP, Chronos saved new MaxPP values for both opposite H3KPanels, the sun came back out and the rear H3KPanel happened to be first processed by Chronos. The sun was still behind the vertical position against the back H3KPanel, PreMoveCheck found the CPP value higher than the PrPP value during the QAngle decrease checking and commanded a rotate towards this fake “forward” H3KPanel. Well in this case R1 picks it up and because the BMF.Axis indicator is set to “1”, it does not give a rotation command, instead it sets the H3KPanel’s MinPP value back to “0” and multiplies its MaxPP value by 100, so this situation can occur again only through the same way, it saves these values of this single H3KPanel to its according MaxPP and MinPP variables and returns the H3KPanel back to Chronos. These Description values will put the H3KPanel in a state that can be considered as a completely numb state, but will be renewed appropriately after the immediate next correct axis rotation.

[0127] - Fortunately, if the tracker rotates for a smaller angle than it should then there is no problem. AfterMoveCheck which will run after the rotation will find the MaxPP and MinPP values in the acceptable and desirable limits and QAngles and will prepare the unit for rotation when the sun is where it is normally expected to be by the Heliotropic 3K process, perpendicular against the process H3KPanel’s (90°-2QAngle) position.

[0128] - Finally, there is the fourth procedure of Chronos, the procedure Curve. It is used to determine if the power production of an H3KPanel peaked before reaching its MaxPP.

[0129] This procedure only processes the forward H3KPanel of each axis by first checking in the LFM array if at least three of the last four axis rotations are towards the given H3KPanel’s side. This array is reset during Diana’s preparation procedures for Chronos and Chronos receives it with four “0” values for each axis, so Curve does not process further in itself until each axis has been rotated by Chronos four times.

[0130] - Curve’s function is to compare the power production of the H3KPanel to its own power production between two rotation instances, after one axis rotation and before the next, operated solely on the (90°-2QAngle) position and gets reset by the AfterMoveCheck after every rotation instance or it resets its own values by itself if it finds the H3KPanel’s Interrupt. H3KP value at “1”.

[0131] - Curve checks if the H3KPanel’s power production has increased or decreased since the last measurement in the same position for more than a 3% percentage. This percentage can be adjusted or multiple checks can be integrated in Curve for different percentages. Curve counts the number of times it found an increase and if there is a following decrease without a drop below the MinPP value then Curve sends to Chronos the lnconsistentCurve.H3KP indication.

[0132] - When the evening comes the intensity of the sun will start decreasing in an increasing rate and this is the only condition the H3KBrain can securely take advantage of in order to adapt the Heliotropic 3K process to the phenomenon. Otherwise the sun will start moving ahead and the H3KUnit will be left behind and chasing, working with the MinPP variables, finding the correct (+ / - % TrackerAngle) position each time the current power production measurement of the forward H3KPanel falls below its MinPP, but then waiting for the sun to move again far ahead.

[0133] - In order to avoid such an occasion a certain timer is being set. This timer gets activated by Chronos after it receives the lnconsistent.Curve.H3KP indication twice and it is activated only for the H3KPanels that appeared to be the forward ones during the day. It is a 1 minute timer that when it reaches to 0 and the Chronos processes the specific H3KPanel, Chronos restarts Description the timer and sends the H3KPanel to the PreMoveCheck procedure, to determine through its procedures, which do not include comparisons with the MaxPP and MinPP values, if the sun has reached to the correct position for the TrackerAngle rotation to be executed. This way Heliotropic 3K balances the sun’s intensity reduction rate with the position of the sun related to the main solar panel’s angle and position, updates the MinPP and MaxPP values and remains relevant to the natural phenomenon and its own programming.

[0134] - This countdown procedure could be arranged for a longer than a 1 minute period or for a shorter one, even performing PreMoveChecks consecutively and endlessly until the night falls, but it is a choice given to the owner of the H3KUnit as it regards to the durability of the H3K Apparatus in time.

[0135] - There is also a possibility that this whole issue of interruptions, inconsistent curves and timers is completely not needed. When the sun reaches closer to the front H3KPanel and farther from the back H3KPanel with a decreasing intensity, the opposite H3KPanel is found with power production lower than its MinPP value. Chronos saves the current power production value of both H3KPanel as their new MaxPP, the rear H3KPanel that is under process gets sent to the PreMoveCheck, which without a rotation command stores again a new MaxPP value at the +2QAngle position similar to the procedure that occurs in the front H3KPanel when the sun’s intensity increases during the day. The rear H3KPanel will still decrease its power production while the front H3KPanel will still increase its own due to the sun’s course. Chronos is going to compute this when the time comes to operate on it and send it to PreMoveCheck for a rotation or an update of its MaxPP values. On the one hand, it feels better to be certain and covered; removing these procedures and their potential results can be tested in the fields.

[0136] - On the other hand, in the evening stance the H3KPanel is processed every minute by the PreMoveCheck procedure not to update its MaxPP and MinPP variables, but to check if the sun is in a position that a rotation instance has to be executed. If the front H3KPanel’s QAngle increases but its power production decreases, the sun, as related to the MSP’s surface, is at the +' / z TrackerAngle position, which is as much productive as the axis’ next rotation instance at the

[0137] TrackerAngle position. So the rotation gets executed, maximizing the MSP’s solar power production for the two consecutive TrackerAngle rotations through repeated 1 minute checks.

[0138] - Depending on the tracker, further checks can be circumstantially integrated In H3KBrain’s processes. One is that if the tracker’s vertical axis only rotates for 90° then when the H3KBrain through the R1 is about to send to the tracker a rotation command towards the Top H3KPanel and the tracker is at 90° the H3KBrain instead commands the horizontal axis to rotate by 180°. Description

[0139] - Also a tremble check, where for every axis if the last three moves are forth-back-forth, the tracker can be forbidden to make a fourth move backwards and be forced to wait for the time that the sun will come in a position suitable for a forward move, saving some tracker durability in the depth of time.

[0140] - The days that the sun does not appear at all because of clouds, days that the MSP is bound to produce solar power equal to a 10% to 25% compared to that of a sunny day, setting a reoccurring countdown for an Olympus stage at the end of every hour can still turn the MSP towards the direction that the light source is stronger, increasing this way adequately the committed to be reduced solar power production.

[0141] - An H3KUnit Sleep Timer can be implemented which zeroes every 24 hours, sometime during the night, zeroes the MaxPP and MinPP values and turns the H3KUnit horizontal, in parallel to the ground with the H3KPanels at 45° or turns the H3KUnit at the position that the previous day’s Diana procedure positioned the main solar panel before it passes it to Chronos.

[0142] - And to close with it, the power production of the H3KPanels can be also stored after the H3KBrain’s measurements.

[0143] - With all the above stages and procedures the H3KUnit has transformed into a 360° solar clock robot with only one unit of measurement, the arc of the available tracker’s axes’ rotation. With only one source of energy which is the sun. It places the main solar panel’s surface at the maximum productive position it can find itself at any given moment of the day in real time, bypassing every obstacle. Without problems from interfering clouds or problems from unpredictable inadequacies of the tracker, as these are all algorithmically rectified and the H3KUnit remains loyal to the execution of its purpose, which is that every time the sun’s position, related directly to the main solar panel surface’s angle, reaches to the middle of a tracker’s rotation instance and a tracker’s next rotation instance, the tracker makes the according move and waits for the sun to travel across, above the main solar panel, until the middle of the now current and the tracker’s next rotation instances. It then rotates again the same way, maximizing the main solar panel’s power production during the whole day, while adjusted to the capabilities that the available dual-axis rotation mechanism has to offer.

[0144] All of the above description’s wording syntax was written down as simply as I could afford to explain the Heliotropic 3K Cross Mode. Presented below is the Heliotropic 3K Cross Mode in computer language, in case the Search Authority has to program the invention and test it. Description

[0145] Program: Heliotropic 3K Cross Mode

[0146] Symbols:

[0147] “ <= “ - The value of the variable on the right is inserted into the variable on the left.

[0148] - End of command.

[0149] “ => “ - The value of the variable on the left becomes interconnected with the value of the variable on the right. Whenever the variable on the right gets operated it first picks up a value from the variable on the left in order to present it in the operation.

[0150] “ . “ - Separates for the program language the according arrays’ dimensions.

[0151] “ Set ” - Black box procedure of the H3KBrain which sets the H3KPanel’s position to the position commanded.

[0152] “ Rotate [H3KP] “ - Black box procedure of the H3KBrain, sends a rotating command to the tracker to rotate towards the number of the given H3KPanel. It is the final connection between the H3KBrain’s programming and the dual-axis rotation mechanism.

[0153] Next

[0154] H3KP <= H3KP + 1 ; OpH3KP <= OpH3KP + 1 ;

[0155] If H3KP = 5 Then H3KP <= 1; End If

[0156] If OpH3KP = 5 Then OpH3KP <= 1 ; End If

[0157] Next

[0158] Load [x]

[0159] If x = 1 Then

[0160] MaxPP <= TMaxPP; MinPP<= TMinPP;

[0161] OpMaxPP <= BMaxPP; OpMinPP <= BMinPP;

[0162] Axis <= 2; QAngle <= VQAngle;

[0163] CPP => TPP; OpCPP => BPP;

[0164] End If

[0165] If x = 2 Then

[0166] MaxPP <- RMaxPP; MinPP<= RMinPP;

[0167] OpMaxPP <- LMaxPP; OpMinPP <- LMinPP;

[0168] Axis <= 1; QAngle <- HQAngle;

[0169] CPP => RPP; OpCPP => LPP;

[0170] End If Description

[0171] If x = 3 Then

[0172] MaxPP <= BMaxPP; MinPP<= BMinPP;

[0173] OpMaxPP <- TMaxPP; OpMinPP <= TMinPP

[0174] Axis <= 2; QAngle <- VQAngle;

[0175] CPP => BPP; OpCPP => TPP;

[0176] End If

[0177] If x = 4 Then

[0178] MaxPP <= LMaxPP; MinPP<= LMinPP;

[0179] OpMaxPP <= RMaxPP; OpMinPP <= RMinPP;

[0180] Axis <= 1 ; QAngle <= HQAngle;

[0181] CPP => LPP; OpCPP => RPP;

[0182] End If

[0183] Load [x]

[0184] SaveValues

[0185] If H3KP = 1 Then

[0186] TMaxPP <= MaxPP; TMinPP <= MinPP;

[0187] BMaxPP <= OpMaxPP; BMinPP <= OpMinPP;

[0188] End If

[0189] If H3KP = 2 Then

[0190] RMaxPP <- MaxPP; RMinPP <- MinPP;

[0191] LMaxPP <= OpMaxPP; LMinPP <= OpMinPP;

[0192] End If

[0193] If H3KP = 3 Then

[0194] BMaxPP <= MaxPP; BMinPP <= MinPP;

[0195] TMaxPP <= OpMaxPP; TMinPP <= OpMinPP;

[0196] End If

[0197] If H3KP = 4 Then

[0198] LMaxPP <= MaxPP; LMinPP <= MinPP;

[0199] RMaxPP <= OpMaxPP; RMinPP <= OpMinPP;

[0200] End If

[0201] SaveValues Description

[0202] SaveValue

[0203] If H3KP = 1 Then

[0204] TMaxPP <= MaxPP; TMinPP <- MinPP;

[0205] End If

[0206] If H3KP = 2 Then

[0207] RMaxPP <- MaxPP; RMinPP <- MinPP;

[0208] End If

[0209] If H3KP = 3 Then

[0210] BMaxPP <= MaxPP; BMinPP <= MinPP;

[0211] End If

[0212] If H3KP = 4 Then

[0213] LMaxPP <= MaxPP; LMinPP <= MinPP;

[0214] End If

[0215] SaveValue

[0216] H3KPQA [Degree]

[0217] Set H3KP at Degree;

[0218] Set OpH3KP at Degree;

[0219] H3KPQA [Degree]

[0220] IQA [DD]

[0221] Repeat

[0222] DD <= DD - 1 ;

[0223] H3KPQA <= H3KPQA + QAngle;

[0224] OpH3KPQA <= OpH3KPQA + QAngle;

[0225] Until DD = 0

[0226] IQA [DD]

[0227] DQA [DD]

[0228] Repeat

[0229] DD <= DD - 1 ;

[0230] H3KPQA <= H3KPQA - QAngle;

[0231] OpH3KPQA <= OpH3KPQA - QAngle;

[0232] Until DD = 0

[0233] DQA [DD] Description

[0234] If BMF.Axis = 0 Then

[0235] LFM.Axis.1 <= LFM.Axis.2

[0236] LFM.Axis.2 <- LFM.Axis.3

[0237] LFM.Axis.3 <- LFM.Axis.4

[0238] LFM.Axis.4 <= H3KP;

[0239] Rotate [H3KP];

[0240] End If

[0241] If BMF.Axis = 1 Then

[0242] If LFM.Axis.4 = H3KP Then

[0243] LFM.Axis.1 <= LFM.Axis.2

[0244] LFM.Axis.2 <= LFM.Axis.3

[0245] LFM.Axis.3 <= LFM.Axis.4

[0246] LFM.Axis.4 <= H3KP;

[0247] BMF.Axis <= 0;

[0248] Rotate [H3KP];

[0249] End If

[0250] If LFM.Axis.4 = OpH3KP Then

[0251] MaxPP <= 100 * MaxPP;

[0252] MinPP <= 0;

[0253] SaveValue;

[0254] Chronos;

[0255] End If

[0256] End If

[0257] R1

[0258] R2

[0259] LFM.Axis.1 <= LFM.Axis.2

[0260] LFM.Axis.2 <= LFM.Axis.3

[0261] LFM.Axis.3 <= LFM.Axis.4

[0262] LFM.Axis.4 <= OpH3KP;

[0263] Rotate [OpH3KP];

[0264] R2 Description

[0265] Olympus

[0266] Load 2; BMF.Axis <= 0; H3KPQA <= 0; D <= 4;

[0267] PrPP <= CPP; OpPrPP <- OpCPP;

[0268] IQA 4;

[0269] If CPP < PrPP Then

[0270] D <- 90 Div HorTrackerAngle;

[0271] Repeat

[0272] R1; D<=D-1;

[0273] Until D = 0

[0274] Olympus;

[0275] End If

[0276] If OpCPP < OpPrPP Then

[0277] D <= 90 Div HorTrackerAngle;

[0278] Repeat

[0279] R2; D<=D-1;

[0280] Until D = 0

[0281] Olympus;

[0282] End If

[0283] H3KPQA <= 0; D <= 1;

[0284] Repeat

[0285] PrPP <= CPP; OpPrPP <= OpCPP; IQA 1 ; D <= D + 1 ;

[0286] Until CPP < PrPP or OpPrPP < OpPrPP or D > 720 Div HorTrackerAngle

[0287] If D > 720 Div HorTrackerAngle Then

[0288] D <= 180 Div HorTrackerAngle;

[0289] Repeat

[0290] R2; D<=D-1;

[0291] Until D = 0

[0292] H3KPQA 90;

[0293] End If

[0294] If CPP < PrPP Then

[0295] D <= (90 Div HorTrackerAngle) - (D Div 4);

[0296] Repeat

[0297] R1; D <= D — 1 ; Description

[0298] Until D = 0

[0299] H3KPQA 90;

[0300] End If

[0301] If OpCPP < OpPrPP Then

[0302] D <- (90 Div HorTrackerAngle) - (D Div 4);

[0303] Repeat

[0304] R2; D<=D-1;

[0305] Until D = 0

[0306] H3KPQA 90;

[0307] End If

[0308] Load 1; BMF.Axis <= 0;

[0309] H3KPQA <= 0;

[0310] Repeat

[0311] PrPP <= CPP; OpPrPP <= OpCPP; IQA 1; D <= D + 1 ;

[0312] Until CPP < PrPP or OpPrPP < OpPrPP

[0313] If CPP < PrPP Then

[0314] D <= (90 Div VerTrackerAngle) - (D Div 4);

[0315] Repeat

[0316] R1; D<=D-1;

[0317] Until D = 0

[0318] H3KPQA 90;

[0319] End If

[0320] If OpCPP < OpPrPP Then

[0321] D <= (90 Div VerTrackerAngle) - (D Div 4);

[0322] Repeat

[0323] R2; D<=D-1;

[0324] Until D = 0

[0325] H3KPQA 90;

[0326] End If

[0327] DianaCounter <= 0; H3KP <= 2;

[0328] Diana;

[0329] Olympus Description

[0330] Diana

[0331] Load H3KP;

[0332] DQA 2; PrPP <= CPP;

[0333] DQA 1;

[0334] If CPP > PrPP Then

[0335] H3KPQA 90; DianaCounter <- 0; R1;

[0336] Diana;

[0337] End If

[0338] IQA 5; PrPP <= CPP;

[0339] IQA 1;

[0340] If CPP > PrPP Then

[0341] H3KPQA 90; DianaCounter <= 0; R2;

[0342] Diana;

[0343] End If

[0344] DianaCounter <= DianaCounter + 1;

[0345] If DianaCounter = 8 Then

[0346] Load 1 ;

[0347] MaxPP <= CPP; MinPP <= CPP;

[0348] Repeat

[0349] DQA 1 ; D <= D - 1 ;

[0350] If CPP > MaxPP Then MaxPP <= CPP; End If

[0351] If CPP > MinPP Then MinPP <= CPP; End If

[0352] If OpCPP > OpMaxPP Then OpMaxPP <= OpCPP; End If

[0353] If OpCPP > OpMinPP Then OpMinPP <= OpCPP; End If

[0354] Until D = 0

[0355] SaveValues;

[0356] H3KPQA 90 - 2QAngle;

[0357] Load 2;

[0358] MaxPP <= CPP; MinPP <= CPP;

[0359] OpMaxPP <- OpCPP; OpMinPP <= OpCPP;

[0360] H3KPQA 90 + 3QAngle; D <= 6; Description

[0361] Repeat

[0362] DQA 1 ; D <= D - 1 ;

[0363] If CPP > MaxPP Then MaxPP <= CPP; End If

[0364] If CPP > MinPP Then MinPP <= CPP; End If

[0365] If OpCPP > OpMaxPP Then OpMaxPP <- OpCPP; End If

[0366] If OpCPP > OpMinPP Then OpMinPP <- OpCPP; End If

[0367] Until D = 0

[0368] SaveValues;

[0369] H3KPQA 90 - 2QAngle;

[0370] DxC <= 0;

[0371] Repeat

[0372] DxC <= DxC + 1 ;

[0373] PrepareTimer.DxC <= 0;

[0374] EveningTimer.DxC <= 0;

[0375] Interrupt. DxC <= 0;

[0376] InconsistentCurve. DxC <= 0;

[0377] PrCurveValue.DxC <= 0;

[0378] Curveincrease. DxC <= 0;

[0379] LFM.I .DxC <= 0;

[0380] LFM.2.DcC <= 0;

[0381] Until D = 4

[0382] DxC <= 0;

[0383] Repeat

[0384] DxC <= DxC + 1 ;

[0385] Forward. DxC <= 0;

[0386] TrackerError.DxC <= 0;

[0387] BMF.DxC <= 0;

[0388] Until DxC = 2

[0389] Chronos;

[0390] End If

[0391] H3KPQA 90; Next; Diana;

[0392] Diana

[0393] PreMoveCheck Description

[0394] PrPP <= CPP;

[0395] DQA1; MinPP <= CPP;

[0396] If OpCPP < OpMinPP Then OpMinPP <= OpCPP; End If

[0397] If CPP > PrPP Then

[0398] OpMinPP <= OpCPP; IQA1; R1; AfterMoveCheck;

[0399] End If

[0400] DQA1; MinPP <= CPP;

[0401] If OpCPP < OpMinPP Then OpMinPP <= OpCPP; End If

[0402] If CPP > PrPP Then

[0403] OpMinPP <= OpCPP; IQA2; R1; AfterMoveCheck;

[0404] End If

[0405] IQA 3;

[0406] If CPP > MaxPP Then MaxPP <= CPP; End If

[0407] If CPP < PrPP Then

[0408] DQA1; OpMinPP <= OpCPP; R1; AfterMoveCheck;

[0409] End If

[0410] IQA 1;

[0411] If CPP > MaxPP Then MaxPP <= CPP; End If

[0412] If CPP < PrPP Then

[0413] DQA2; OpMinPP <= OpCPP; R1; AfterMoveCheck;

[0414] End If

[0415] SaveValues;

[0416] DQA2;

[0417] Chronos;

[0418] PreMoveCheck

[0419] AfterMoveCheck

[0420] OpMaxPP <= OpCPP;

[0421] H3KPQA 90 - 2QAngle; ResetCurve; PrPP <= CPP;

[0422] DQA1; MinPP <= CPP;

[0423] If CPP > PrPP Then

[0424] OpMinPP <= OpCPP; IQA1; R1; AfterMoveCheck;

[0425] End If

[0426] DQA 1; Description

[0427] If CPP > PrPP Then

[0428] OpMinPP <= OpCPP; IQA 2; R1; AfterMoveCheck;

[0429] End If

[0430] IQA 2; D <= 0;

[0431] Repeat

[0432] PrPP <= CPP; IQA 1; D <= D + 1 ;

[0433] If CPP < PrPP Then MaxPP <= PrPP End If

[0434] Until CPP < PrPP

[0435] CheckT rackerError;

[0436] If OpCPP < OpMinPP Then OpMinPP <= OpCPP; End If

[0437] Repeat

[0438] DQA1; D<=D-1;

[0439] If OpCPP > OpMaxPP Then OpMaxPP <= OpCPP; End If

[0440] If OpCPP < OpMinPP Then OpMinPP <= OpCPP; End If

[0441] Until D = -2

[0442] IQA 2;

[0443] OpMaxPP <= 2 * OpMaxPP - OpMinPP;

[0444] SaveValues;

[0445] Chronos;

[0446] AfterMoveCheck

[0447] CheckT rackerError

[0448] If T rackerError. Axis = 0 and D>5 Then

[0449] D <= (D- 5) / 2 + D; D<=DDiv1;

[0450] Repeat

[0451] DQA1; D<=D-1;

[0452] If OpCPP > OpMaxPP Then OpMaxPP <= OpCPP;

[0453] End If

[0454] Until D = 0

[0455] R2; ResetCurve;

[0456] OpMaxPP <= 2 * OpMaxPP - OpMinPP; OpMinPP <= 0;

[0457] SaveValues;

[0458] TrackerError.Axis <= 1; BMF>Axis <= 0; Description

[0459] Chronos

[0460] End If

[0461] If TrackerError.Axis <= 1; Then TrackerError.Axis <= 0; BMF>Axis <- 1 ;

[0462] 975 OpMinPP <- 0;

[0463] End If

[0464] CheckT rackerError

[0465] ResetCurve

[0466] RCx <= 0;

[0467] 980 Repeat

[0468] RCx <= RCx + 1 ;

[0469] PrCurveValue.RCx <= 0;

[0470] Curveincrease. RCx <= 0;

[0471] Until D= 4

[0472] 985 ResetCurve

[0473] Curve

[0474] Cx <= 0; Cy <= 0;

[0475] Repeat

[0476] Cx <= Cx + 1 ;

[0477] 990 If LFM.Axis.Cx = H3KP Then Cy <= Cy + 1 ; End If

[0478] Until Cx = 4

[0479] If Cy > 2 Then

[0480] Forward. Axis <= H3KP;

[0481] If lnterrupt.H3KP = 1 Then

[0482] 995 ResetCurve;

[0483] Interrupt. H 3 KP <= 0;

[0484] End If

[0485] If CPP > 1.03 * PrCurveValue.H3KP Then

[0486] PrCurveValue.H3KP <= CPP;

[0487] 1000 Curveincrease. H3KP <= Curveincrease. H3KP + 1 ;

[0488] End If

[0489] If CPP < 0.97 * PrCurveValue.H3KP Then Description

[0490] PrCurveValue.H3KP <= CPP;

[0491] If Curveincrease. H3KP > 0 Then

[0492] 1005 lnconsistentCurve.H3KP <= 1;

[0493] End If

[0494] End If

[0495] End If

[0496] Curve

[0497] 1010 Chronos

[0498] Load H3KP;

[0499] If PrepareTimer.H3KP > 1 and Forward.Axis = H3KP and EveningTimer.H3KP = 0 Then

[0500] Restart EveningTimer.H3KP;

[0501] 1015 PreMoveCheck;

[0502] End If

[0503] If CPP < MinPP Then lnterrupt.H3KP <= 1 ; lnterrupt.OpH3KP <= 1; MaxPP <= CPP; OpMaxPP <- OpCPP;

[0504] 1020 PreMoveCheck;

[0505] End If

[0506] If CPP > MaxPP Then PreMoveCheck;

[0507] End if

[0508] 1025 Curve;

[0509] If lnconsistentCurve.H3KP = 1 Then lnconsistentCurve.H3KP <= 0;

[0510] Curveincrease. H3KP <= 0;

[0511] PrepareTimer.H3KP <= PrepareTimer.H3KP + 1 ;

[0512] 1030 PreMoveCheck;

[0513] End If

[0514] Next;

[0515] Chronos;

[0516] Chronos Description

[0517] 1035 Heliotropic 3K Conclusions

[0518] The conclusion is that by adapting four angled solar panels on the four sides of a main solar panel we are enabled to make this main solar panel the heart of a robot that seeks the sun constantly, the core of a sun tracer, an H3K Unit. The “Cube Effect” that presents itself in the Heliotropic 3K arrangement of 0°, the Heliotropic 3K Cube Mode where the H3KPanels are

[0519] 1040 placed forming a 90° corner with the main solar panel, is a special and novel way of leading the surface of a solar panel to a position that is cross-centered perpendicularly against the sun.

[0520] Exploiting the “Cube Effect” through the 90° arrangement, the Heliotropic 3K Cross Mode as the optimal mode of the process, Heliotropic 3K mechanically avoids a large number of measurements and algorithms as known so far, focusing straight on the desideratum. Added to

[0521] 1045 the above are an Artificial Intelligent and robotic operation and apparatus, with a self-calibrating manner, which optimally respects the capabilities of the H3KUnit, the laws of physics and the laws of nature. It regards to computing, measurements and trigonometry applied straight on the surface of the main solar panel having nothing to do with the way the main solar panel is placed on the tracker neither with any other tracker calculations further than its axes’ rotation arcs.

[0522] 1050

[0523] Brief Description of Drawings

[0524] Figure 1 : Four H3K Panels.

[0525] Figure 2: The H3K Brain disconnected.

[0526] Figure 3: The H3K Brain fully connected with the rest of the H3K Apparatus and a tracker.

[0527] 1055 Figure 4: The MSP (main solar panel).

[0528] Figure 5: The tracker, or any type of horizontal and vertical rotating mechanism.

[0529] Figure 6: H3K Panels mounted and a max number of possible available light angles.

[0530] Figure 7: H3K Panels mounted and another max number of possible available light angles.

[0531] Figure 8: The 90° arrangement, the H3KPanels parallel to the main solar panel’s surface as

[0532] 1060 its expansions, the basic formation and arrangement of the Heliotropic 3K Cross Mode.

[0533] Figure 9: The main solar panel aligned after the 0° arrangement Heliotropic 3K process operated the Cube Effect’s exploit on only one axis.

[0534] Figure 10: The MSP after a 0° Heliotropic 3K process has completed all of its procedures.

[0535] Figure 11 : An extremely simplified, yet very clarifying 2D example image which helps to the

[0536] 1065 understanding of the Heliotropic 3K Cross Mode’s main function, the set of an H3KPanel with its momentum’s maximum power production value stored, waiting at the (90-2QAngle) degrees. Description

[0537] When the sun reaches at position 2 the H3KUnit rotates facing at sun’s position 3, when the sun reaches at position 4, the H3KUnit rotates facing at sun’s position 6.

Claims

AMENDED CLAIMS received by the International Bureau on 30 March 2025 (30.03.2025)ClaimsBy the present claim, I disclose a novel process and its corresponding apparatus for commanding a solar panel’s tracker to consistently orient the solar panel toward the sun, thereby maximizing its energy production.The apparatus necessary for this process consists of a specialized computing device, hereinafter referred to as the “H3KBrain”, and two small solar panels for each tracker's axis, hereinafter referred to as “H3KPanels”. Each H3KPanel has its own high precision one-axis rotation mechanism. The H3KBrain controls the rotation of the H3KPanels, measures their individual power output, and, based on these measurements, either proceeds to measure the next H3KPanel’s power output or sends rotation commands to the tracker, enabling the tracker to adjust the orientation of the main solar panel.To install the apparatus, each pair of H3KPanels corresponding to a tracker's axis is mounted on the main solar panel as flat extensions of its surface. The rotation axis of each H3KPanel is parallel to the respective side of the main solar panel on which it is mounted, enabling it to scan angles along the corresponding tracker axis. For the horizontal axis of the tracker, the H3KPanels are positioned as left and right flat extensions of the main solar panel’s surface. For the vertical axis, they are positioned as top and bottom flat extensions. This position of the H3KPanels will hereinafter be referred to as “Position 0”.The H3KPanels are then connected to the H3KBrain, which is in turn connected to the tracker's rotation mechanism. The only input required from the user occurs exclusively at this stage, and it is the angle by which each tracker axis rotates in response to a single-rotation- instance command. This single-rotation-instance angle of a tracker’s axis will hereinafter be referred to as “S.R.I.A”.The single-rotation-instance angle of the H3KPanels is then calculated automatically by the H3KBrain. This single-rotation-instance angle of the H3KPanels is equal to one-quarter of the S.R.I.A of the corresponding tracker axis and will hereinafter be referred to as “QAngle”.The above five terms, H3KBrain, H3KPanels, Position 0, S.R.I.A, and QAngle, as well as the terms “Waiting Position” and “Expected Value,” which will be defined later in this document, are established to enhance clarity and readability and to avoid the repetition of lengthy and complex expressions, since this document refers to both a process and an apparatus, making such definitions necessary for precision and consistency.Whenever the H3KBrain rotates an H3KPanel forward or backward by any number of QAngles, it simultaneously rotates its paired H3KPanel forward or backward by the same number of QAngles.The first stage of the Heliotropic 3K process aims to orient the main solar panel toward the sun. The H3KBrain first rotates a pair of H3KPanels 90 degrees backward from Position 0, then gradually rotates them forward by one QAngle at a time. At each position, the H3KBrain measures the power output of each H3KPanel individually and compares its power output at the given position to the power output at the previous position. If either of the two H3KPanels registers a lower power output than at its previous position after a sequence of increasing power outputs, this indicates that its previous position corresponded to its peak power production and was the closest to being perpendicular to the sun. The H3KBrain determines this optimal position by calculating the number of QAngle rotations performed and then rotates the tracker by the required number of S.R.I.A.s to align the corresponding axis with thisoptimal position. The same process is repeated alternately for the horizontal and vertical axes until the H3KBrain no longer needs to adjust the tracker's position.This first stage of the Heliotropic 3K process positions the main solar panel optimally toward the sun, based on the best position the tracker can achieve depending on its axes’ S.R.I.A. The H3KPanels are arranged in opposite pairs, even though they are not used to measure illumination imbalances between them, because in this point the direction at which the sun will move is unknown.The second stage of the Heliotropic 3K process, which also forms the core of the Heliotropic 3K process, ensures that the tracker rotates again at the most suitable moment and maintains an optimal position throughout the day.The H3KBrain returns the H3KPanels to Position 0 and then rotates them backward by two QAngles. As a result, each H3KPanel is positioned to face parallel to the sagitta of the arc that would be created by the main solar panel's center if it were rotated by a single-rotation- instance toward the respective H3KPanel's side. To clarify further, whenever the tracker rotates the main solar panel, the panel follows a curved path; therefore, during a single- rotation-instance, the main solar panel’s center traces an arc between its starting position and its ending position, and this arc’s angle is one S.R.I.A. Each H3KPanel, when rotated from its Position 0 backward by two QAngles, is positioned to face parallel to the sagitta of this potential arc that would be formed if the main solar panel were rotated by a single-rotation- instance toward the side of this H3KPanel. This means that each side’s H3KPanel is positioned to face perpendicular to the potential position of the sun when the sun reaches the angular midpoint between the two consecutive positions of the main solar panel on its side. This position of the H3KPanels will hereinafter be referred to as “Waiting Position”.From the Waiting Position, the H3KPanels are rotated forward four times by one QAngle at a time. This equals their corresponding axis’ S.R.I.A., so essentially the H3KPanels scan the area above the main solar panel across an S.R.I.A., from the half of an S.R.I.A. in the front of the direction at which the main solar panel is facing, to the half of an S.R.I.A. in the back. During these four rotations of the H3KPanels, the H3KBrain measures their individual power output at each of their four QAngles and records the minimum and maximum power output values found for each H3KPanel in a temporary database. This temporary maximum power output value of an H3KPanel will hereinafter be referred to as “Expected Value”.The H3KBrain returns the H3KPanels to their Waiting Position and begins processing them individually and repeatedly in a cyclical order, comparing each H3KPanel’s current power output to the Expected Value saved for that H3KPanel. If an H3KPanel is found to produce power equal to or greater than its Expected Value, this indicates that the sun is perpendicular to that H3KPanel. In response, the corresponding axis is rotated by a single-rotation-instance toward this H3KPanel and then reinitiates the actions of the second stage.This means that the main solar panel’s surface, in respect to the rotated axis, was facing half an S.R.I.A. behind the sun but is now facing half an S.R.I.A. ahead of the sun, while the H3KPanels have updated Expected Values and are in their Waiting Positions. As the sun continues its course, it will pass above the main solar panel, again reaching a position half an S.R.I.A. ahead of it. The respective H3KPanel will again reach its Expected Value, prompting the H3KBrain to command the tracker to rotate again by an S.R.I.A. toward that H3KPanel, once again bringing the main solar panel from half an S.R.I.A. behind the sun to half anS.R.I.A. ahead of the sun. This process will repeat continuously throughout the day, maximizing the main solar panel’s power production output according to the rotation capabilities of the available tracker.The H3KBrain maintains a record of the last four rotations of each axis to identify which H3KPanel is at the forefront of the axis’ movements throughout the day.Before the H3KBrain generates a command to rotate the tracker when an H3KPanel has reached a power output equal to or greater than its Expected Value while in its Waiting Position, it first performs a “PreMoveCheck” procedure to validate the sun's position. During this procedure, the H3KPanel under process is rotated backward by two QAngles, one step at a time, then returned to its Waiting Position, and subsequently rotated forward by two QAngles, one step at a time. Its power output at these positions is compared against its power output at the Waiting Position.If the power output increases during the H3KPanel’s backward rotations, this indicates that the sun has already passed the perpendicular to the H3KPanel position. This can occur if a cloud has temporarily obstructed sunlight. In this case, the H3KPanel returns to its Waiting Position, and a command is generated to rotate the tracker for an S.R.I.A. toward this H3KPanel.If the power output increases during the two forward QAngle rotations, this indicates that the sun’s intensity has increased. As a result, the highest power production output found at these two forward QAngles is saved as the new Expected Value, and the H3KPanel is returned to its Waiting Position without a command to rotate the tracker being generated.If the power output decreases in all four forward and backward QAngles of the PreMoveCheck procedure, the sun’s position is confirmed as perpendicular to the H3KPanel being processed. The H3KPanels then return to their Waiting Position, and a command is generated to rotate the tracker for an S.R.I.A. toward the H3KPanel under process.After the H3KBrain generates a command to rotate the tracker, an “AfterMoveCheck” procedure is performed to validate the correctness of the new position. The H3KPanel under process is rotated backward by two QAngles, one step at a time, and its power output at these two QAngles is compared against its power output at the Waiting Position.If the power output increases, this indicates that the sun is even further ahead in relation to the H3KPanel’s side on the specific axis. In this case, the H3KPanel returns to its Waiting Position, and a command is generated to rotate the tracker for an S.R.I.A. toward this H3KPanel. This can occur if a cloud has obstructed sunlight for a significant amount of time.If the power output decreases, the H3KPanels return to their Waiting Positions, and the second stage of the Heliotropic 3K process is reinitiated for the H3KPanels to acquire new potential minimum and maximum output values and wait for the next correct moment to rotate.The potential minimum power output values of the H3KPanels are saved to distinguish an occasion of cloud interference from the natural decrease in the sun's intensity during evening hours. When a cloud interferes, the H3KPanel’s power output drops significantly lower than when the sun shifts by an S.R.I.A. along with a natural decrease in intensity, in which case the front H3KPanel of each axis records an escalating decline of power output. When a cloud interferes, the H3KBrain saves the abruptly decreased power output value of the H3KPanel as both its new potential minimum power output and Expected Value.As a result, when the sun reappears, the increase of the H3KPanel’s power output will trigger the H3KBrain to perform a PreMoveCheck on the H3KPanel to determine whether the side and timing are optimal for rotation or whether to assign a new potential minimum power output and Expected Value to the H3KPanel.When the sun’s intensity initially begins to decrease during the first evening hours, the sun moves across the main solar panel and causes the power output of each front H3KPanel to gradually increase, peak before reaching its Expected Value, and then decline. The H3KBrain recognizes this power output pattern and enters “Evening Mode”, where it starts operating on a time-based operational logic, periodically performing PreMoveCheck procedures on the front H3KPanels, assessing whether the sun has travelled beyond the angular midpoint between the main solar panel’s current and next position toward one of these H3KPanels’ sides. Based on this assessment, the H3KBrain either generates a command for the tracker to rotate by one S.R.I.A. toward the operated H3KPanel or proceeds to assess the next front H3KPanel.The Evening Mode is an integral technical feature. It constitutes a fundamental part of the Heliotropic 3K process’s inventive steps. It can be used throughout the entire day as a backup procedure, to periodically validate the current position of the main solar panel or rotate it as necessary, since the PreMoveCheck procedure does not rely on comparing the H3KPanel’s current power output with its Expected Value, but instead it compares the H3KPanel’s power output at its Waiting Position against the power outputs at its immediate two forward and two backward QAngles, effectively aligning it with the main solar panel’s two consecutive positions. This backup usage is optional for the user, as it can wear down the mechanism unnecessarily.The Heliotropic 3K process is characterized by the three distinct ways of utilizing the rotation of the H3KPanels. Each way serves a specific operational purpose:First, the rotation of the H3KPanels is utilized to detect the position of the sun in relation to the respective side of their corresponding axis, achieved by comparing each H3KPanel’s power output exclusively to its own power outputs at its different angular positions across its entire range of angles. When the angle where its power output peaks is identified, and the number of rotations used until that angle is calculated, the corresponding axis is rotated accordingly, for the main solar panel to face the optimal position relative to the axis.Second, the core inspirational idea that led to the development of the Heliotropic 3K process, the rotation of the H3KPanels is utilized to identify the optimal moment and side for the next rotation of the main solar panel. This is achieved by rotating each side’s H3KPanel to determine its individual potential maximum power production at the given moment, based on the current intensity of sunlight. Each H3KPanel, according to the side of the main solar panel on which it is mounted, is then positioned to face perpendicular to the potential position of the sun if the sun reaches the angular midpoint between the main solar panel’s current angle and a potential next angle, one S.R.I.A. toward the respective H3KPanel’s side. After the H3KPanels assume these positions, the H3KBrain continuously measures their power output individually and sequentially. If any H3KPanel produces power equal to or greater than its identified potential maximum power production, this indicates that the sun is perpendicular to the angular midpoint between the main solar panel’s current position and its next position in the direction of that H3KPanel, marking the optimal moment to rotate the corresponding axis of the tracker for a single-rotation-instance toward that H3KPanel’s side. Before executing the tracker’s rotation, that specific H3KPanel performs backward and forward rotations, having its power outputs at its current, previous, and next rotational angles compared against each other in order to confirm that this potential maximum power output did not occur due to an increase in the sun's intensity. Once confirmed, the main solar panel’s rotation is executed, and the entire procedure for identifying the optimal side and moment for the next rotation of the main solar panel restarts. This procedure ensures that the main solar panel maintains the maximum possible power production between these two consecutive positions and that it maintains the maximum possible power production consistently throughout the day.Third, the rotation of the H3KPanels is utilized on a time-based operational logic, to periodically assess whether the sun has traveled beyond the angular midpoint between the main solar panel's current position and its next position, one S.R.I.A. toward an axis’ side. Each H3KPanel, while facing perpendicular to the potential position of the sun if the sun reaches the angular midpoint between the main solar panel’s current angle and its next angle, one S.R.I.A. toward the respective H3KPanel’s side, is periodically rotated backward, comparing the power output at its starting position to the power output at its backward rotational position. If the power output increases at the backward position, this confirms that the sun has traveled beyond the angular midpoint between the main solar panel’s current position and its next position, one S.R.I.A. toward the respective H3KPanel’s side, and a command is generated to rotate the corresponding axis toward the H3KPanel under process.The H3KPanels together with the H3KBrain form the “H3KApparatus”. The H3KApparatus includes solar panels and rotation mechanisms, elements that are already known in the prior art. The H3KPanels are small solar panels equipped with high precision single-axis rotation mechanisms, arranged in pairs corresponding to each tracker axis.The uniqueness of the H3KApparatus lies in the H3KBrain, a specialized computing device that rotates the H3KPanels at angles proportional to the S.R.I.A. of their corresponding axis, thereby enabling the processing of the angle equal to half the corresponding axis’ S.R.I.A., processes the real-time power output data of the H3KPanels, compares each individual H3KPanel’s power output exclusively to its own power outputs across its different angular positions, and generates movement commands for the tracker at the optimal time based on the outcomes of these comparisons.The innovative step that derives from the combination of the Heliotropic 3K process and the H3KApparatus is that every rotational command for the tracker is generated based solely on the power output values of a single H3KPanel, determined by rotating the H3KPanel and comparing its power output at a certain initial angle with its power outputs at its next and previous angles. It is particularly efficient when this initial angle corresponds to the midpoint between two consecutive rotational positions of the main solar panel-tracker system on the corresponding side. The rotational angle of an H3KPanel, being proportional to the S.R.I.A of the tracker’s corresponding axis, provides a unit of measurement which can be mathematically interpreted by the tracker. This enables the H3KPanel’s power outputs across its angular positions to be processed either as a scan of the horizon along the tracker’s corresponding axis, or as criteria about whether the sun’s position is at a specific point relative to that axis. There is no need to calculate an illumination imbalance between two panels. An H3KPanel’s rotational attribute is used to assess the effectiveness of the rotational angles of the main solar panel before and after it is rotated, while consuming minimal energy, preventing unnecessary mechanical wear, and eliminating tilting issues. This intelligent control approach enhances efficiency while preserving the long-term performance of the entire solar tracking system.Claims1. The combination of the Heliotropic 3K process and the H3KApparatus, as a system that utilizes the rotation and the power outputs of a small solar panel to assess the efficiency of a larger solar panel’s rotational positions, constitutes an innovative system that can significantly contribute to the solar power industry by enhancing solar energy production and with this claim, I, Anastasios Panopoulos, as the inventor and claimant, seek protection against any unauthorized commercial use, reproduction, distribution, or sale of the Heliotropic3K process, as well as against any unauthorized commercial manufacturing, use, reproduction, distribution, import, or sale of the H3KApparatus, as provided for by the Patent Cooperation Treaty and the Paris Convention.Dependent Claims2. With this claim, I, Anastasios Panopoulos, as the inventor and claimant of the Heliotropic 3K process and the H3KApparatus, seek protection against any unauthorized manufacturing, use, reproduction, distribution, import, or sale of any variation of the Heliotropic3K process and of any variation of the H3KApparatus, including but not limited to altering the rotation angle of the small solar panels to differ from one-quarter of the corresponding axis' single-rotation-instance angle while still preserving their function of rotating and having their power output processed across their rotational positions to detect whether the sun is at a midpoint angle between two consecutive main solar panel’s rotational positions; the modified H3KApparatus variation where all paired H3KPanels are replaced with a sole double-axis rotating external small solar panel, operating on a time-based operational logic along both of its axes and utilizing its rotations in accordance with the functional principles of the Heliotropic 3K process and the H3KApparatus, to trace the sun’s position by processing the angle at which its power output peaks, and to further determine whether this position of the sun corresponds to a position perpendicular to or beyond the angular midpoint between any two consecutive rotational positions of the main solar panel assuming its first rotational position is its current position; the implementation of multiple small solar panels on each side of the main solar panel, collectively corresponding to a tracker axis; the use of a sole rotating small solar panel applicable to both sides of a corresponding axis, operating on a time-based operational logic for each side of the axis, or with a predetermined forward direction derived from separate sun-tracing procedures; and the mounting of rotating small solar panels on an independent tracking structure or in locations other than the sides of the main solar panel, while preserving their aim to individually rotate, detect the angle at which their power output peaks, and further determine whether the angle at which their power output peaks corresponds to a sun’s position perpendicular to an angular midpoint between two consecutive rotational positions of a main solar panel, as provided for by the Patent Cooperation Treaty and the Paris Convention.Anastasios Panopoulos

Images