I suspect that is because time is calculated from horizontal solar angle. I think that is the one thats always zero on the moon map. So what you see is just the sunrise time setting since it comes down to time = 0+sunrisetime.

I will look into this when i have time, you could try changing line 54 ("div r4 r1 15") to "div r4 r2 15" to switch it to use the vertical angle instead. Would require other sunrise times ofc.

First off, great script! I have used it in a few different places and noticed a problem with the clock as well under specific conditions. I have it set on my base on Vulcan and it works great. On the moon, not so much. I duplicated the positions and settings I used on Vulcan but the most I can ever get the clock to read is a static number. One of: 0,6,18 are the only ones I have seen while fiddling with it to try and get it working. Any idea why it would not work on the Moon? I am using solar panels with a combined data/power port facing south and a daylight sensor data port facing north. Updating the rotation line in the script and testing with 0, 90, 180 and 270 all with varied results but never a working clock.

clock d3 is not working, it show 0 as output value always

Yes. Also there is nothing "special" about the end of the program. every yield instruction makes the IC "pause" its execution, meaning the code you see actually gets executed over multiple ticks.
Obviously you need to jump back to the top (or somewhere else) at some point, otherwise it would be sort of a one time program.

Thanks for responding. I'll take another look at my setup.

So, if I understand this correctly, when you hit the end of the program and jump back to the beginning the registers keep their values? I'm still learning.

Its been a while since i actually looked at the code.
ode1 is the shorthand i used to indicate im an euler method like algorithm to estimate the suns position. i do this because i only set the vertical and horizontal position every two ticks as i need to switch the sensors mode. r2 is indeed used, it is the old value being stored for the next cycle.

I dont see how the vertical tracking would be broken though. Make sure your memories and batch writers are set up properly.

I should say that I'm on the moded planet mercury where the sun's position is always very low to the horizon. Between 78 and 100 degrees (or lower when it sets). My horizontal is tracking properly, but the vertical is not working. Whatever vertical angle I manually set the panels at, it stays that way.

I'm trying to follow the code to see what's going on, but I've so far had no luck. What would be the purpose of setting R2 in the vertical section of the code, but never using that value as far as I can tell. Can someone help me out please?

There's something wrong with this script. The calculated vertical angle always ends up being higher than 100, so it's cap at 100 and never changes. What does #ode1 stand for?

Thanks for a really great script. ;-)
The sun comes up in East direction and travel West.

1). setup your solar panel so the network slot faces North, and power faces south.
2). install a solar sensor so the tail faces North, and the sensor look up into the sky Name the sensor " sensor " ( without "" signs )

Now build the computer and two batch writers and minimum 2 memory.

Your sensor need to be named sensor
memory 1 need to be named mem_horz
memory 2 need to be named mem_vert

To make things work.
look at the IC casing ( where you installed the little computer chip )
use your screwdriver and select d0 and turn it until it say "sensor"
Do the same for D1 and select "mem_horz"
do the same for D2 and select "mem_vert"

now look on the batch writers.
Configure one of them to read "mem_horz" and select Horisontal, and solar panel..
configure the other and read "mem_vert" and select vertical, and solar panel.

Here to report a strange anomaly while using the system on europa. In the early morning as the sun comes up the system spins the panels around a complete 360 once, then resumes tracking normaly. I'm not sure why but outside of that the system works perfectly.

also love the fact that i can use it as a clock and it sets my lights on automaticly

hmm well from a friend of mine's experience, hes has no clue as to coding he didn't realize you only needed one sensor or that it had to be faceing up and that you had to change the variable to tell the program witch direction the cable output was on... wasn't a problem for me and I showed him how to run it but figured you should know that the average gamer without any programming experience finds it confusing.

me however i love it 99% power almost all the time discounting sunset and sunrise is awesome also love that i don't have to care witch way i place the sensor as long as i tell the program its good.

Thanks!

Instruction wise, the screws do have labels and the variables for offsets do have comments. Maybe the "relative rotation setting" could be more clear, but i thought it somewhat obvious that it refered to the rotation of the solar sensor.

this has to be the best solar control I have found yet. Still would be nice if you had instructions so those who don't know coding can figure it out easier.