Jump to content

Single Axis Tracker Mechanical Limits Graphical Entry


Recommended Posts

Posted

When simulating single-axis-trackers, limits affect the magnitude of deviation from a horizontal orientation:

file.php?mode=view&id=1490&sid=f92a7edafb14d52e222d214c7c6a3c3a

but when entering the corresponding limits in the Orientation dialog, the graphical “interpretation” assigns these angles to the post-to-limit angle, rather than the horizontal-to-limit.

file.php?mode=view&id=1491&sid=f92a7edafb14d52e222d214c7c6a3c3a

It is reasonable to indicate that some range of angles is not reachable (I would not have selected “green” as the color to reflect this restriction, but that is not material), but it is not reasonable to map the numbers in the numeric entries to that “green” region… they should be mapped to the complement (90-value) of that restricted region.

The “workaround” is to ignore the graphical assistance and simply enter the correct numbers, but the graphical assistance is highly misleading to inexperienced engineers.

60deg_limits.jpg.ef05d1187da8f4e52f5513d3b6afa153.jpg

Example of as-computed interpretation of tracker position angles

orientation_screen.thumb.png.bf649b1df09b0cc33ba020d7e8efb2d8.png

Example of incorrect graphical representation of this limit, with added (black) correct representation

Posted

Thank you for the feedback on this tool. We will take this kind of comments into account for a future overhaul.

The reason for this graphical representation is that the "handle" on the rotation angle is the "lever" with the red point, below the tracker table. If you move the lever around the limits should become quite intuitive.

Posted

I don't fault you for making the graphical input. If the 90-red_dot_angle fix is implemented then the corresponding graphical intuition should be very helpful. Thank you for adding this item to your backlog.

However, I strongly dispute your assertion that the current implementation is "improving" anyone's understanding of what is actually happening in the calculations. If it is used "intuitively" then wrong values will be entered into the text entries and the simulation results will not reflect the actual hardware design.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...