My SM clock is stuck in Jan 2000. I've tried using the time window in the upper right hand corner, and a linux command, e.g.,

date --date "2022-10-10" which is correctly echoed back to me. But, when I type 'date' again I'm back in 2000.

Anyone had a similar experience? Is there a solution?

I did the normal reboot, complete power shut-down, etc.

One easy solution is to connect SM App to StellarMate, this would sync time + location. You don't need to use StellarMate App afterwards, but it syncs both time and location upon connecting to the unit automatically. Other options include RTC clock or better GPS dongle. The App seems the easiest route.

You used wrong option.
You should use -s option and launch date command with sudo.

Please see “man date”.

Thanks. That did it. I actually read the man pages last night and still got it wrong!

CS,
Bob

Jasem,

Thanks. It never occurred to me that StellarMate was writing the FITS file until I saw the screwy time in the header. When doing Variable Star work, the people who receive the reports like to have the time expressed in terms of solar system barycentric time for stars with really short periods, cataclysmic, etc. My control room clock is usually accurate to 60 ms according to a link to the NIST web site.

I'll give the SM App a go and see what happens.

CS,
Bob

That is strange.
Can't the raspberry pi set the time with a command like the following?
sudo date -s '2021-01-04 13:04:00'
You might want to stop ntp once beforehand.

The following site may be helpful
raspberrytips.com/set-date-time-raspberry-pi/

Yes, that's what I did following your suggestion via a VNC connection and the SM terminal window. Time and date are now set.

The rasberry-pi link will be useful. Already did a quick scan.

One thing we don't have here is internet except via the hot spot on my cell phone. Always makes things interesting.