gassy wrote:Make sure you have DNS server settings on the network page setup. I believe that two most common ones used are 8.8.8.8 and 8.8.4.4
Attached is my network configuration tab, I went in and changed the DNS Server mode to manual put and assigned 8.8.8.8 then pinged it successfully. However when I navigated back to the main status page and then back to network configuration it was gone? Maybe it's because I put the name of my FPP in the Hostname field?
Either way, yesterday I manually entered the date & time then shutdown the controller. Just booted it back up about 24 hours later and it still kept the time. Not sure how long the board keeps that data internally or if it's now working? Guess I'll try shutting it down for a longer period of time and seeing what happens. However I plan to run a script at the end of my shows to shut down the board, then less than 24 hours later boot it back up so if it worked last night I'm thinking it'll work come show time. Might need me to manually enter the date & time on the first night but should keep the time after that?
-Russ
Not sure if it is relevant, but...
We have multiple RPi with FPP on them. Each has a RasClock attached. This is the third year in a row that my "helpers" put the units back in their storage boxes and did NOT remove the button batteries. I'm doing checks right now for updates to the FPP software, and have found that ALL OF THEM have the correct date and time. None of them have been connected to the Internet (there isn't any out at the show site).
Just an observation.
The PI does not keep any time info beyond server and timezone. When you reboot the PI gets its time from an attached RTC or / and from NTP. Take the daughter board off and see it the time is correct. If it is then NTP is working. If not then NTP is having a network issue.
Sorry. Didn't make it clear that there is NO NTP out here (no wifi, no internet, no - anything.)
The onboard time (either through a RASClock or a built in time clock as in several of the Kulp Boards) is a necessity.
Then again, with them working this well, who needs the internet. :blink:
Yes Al. I understood that. The OP however IS trying to use NTP so I am trying to work out getting him set up. I also have an RTC on some of my PIs and it works very well in stand alone configurations.
Just an FYI for those that might not know...
A good way to tell if you're connecting to the internet or not is to go to About and see what shows next to Remote Git Version. If it says "unknown" then you're not connected to the internet.
At least in my case I'm unable to use DHCP under host & dns settings and connect to the internet.
Instead, I have to select manual and put the Google IP 8.8.8.8 in for both dns 1 and dns 2.
sfraise wrote:Just an FYI for those that might not know...A good way to tell if you're connecting to the internet or not is to go to About and see what shows next to Remote Git Version. If it says "unknown" then you're not connected to the internet.
At least in my case I'm unable to use DHCP under host & dns settings and connect to the internet.
Instead, I have to select manual and put the Google IP 8.8.8.8 in for both dns 1 and dns 2.
Wow! I have been unable to get the NTP to sync for 2 years now, never being able to figure out why. You solved it for me. It said "unknown" in the Remote Git Version, so I set the DNS to 8.8.8.8, restarted, and BAM, time synced and Remote Git Version actually shows now. Can't thank you enough!!

