Real Time Clock

B

ben&bobbi

Supporting Member
I did a little searching, and checked the wiki pages (http://www.falconchristmas.com/wiki/FPP:FAQ). Searches said if it is connected to the network on reboot, it will update time. That didn't seem to work for me. I did not find anything that shouted look here idiot on the wiki either.

Do i need to make any changes to the clock settings to get it to stay on time? It shifts more than i think is correct. I think it was almost 30 minutes off. It is connected to my home network and i believe it works right.

setting clock.JPG
 
One of the FPP config pages enables NTP (Network Time Protocol). If NTP is enabled and there is a connection to a network that has access to the internet then the time will be set automatically.
 
If you find that doesn't work, or you can't seem to keep a network connected (even wirelessly), you can buy an RTC module that works on the RPi. You insert a small coin battery, plug it in to the RPi headers, go to the same page you showed in your post, and update. The module is around $6, comes fully assembled, and the battery will last 2-3 years, according to what I've read from people here. Here's a link: https://www.adafruit.com/product/33..._dvnmFm67BzBPQsUo5c3aX7BGVea17JEaAu3REALw_wcB
 
MartinMueller2003 said:
One of the FPP config pages enables NTP (Network Time Protocol). If NTP is enabled and there is a connection to a network that has access to the internet then the time will be set automatically.
Click to expand...

I have that box checked. Right under Real Time Clock, the drop down is set to none, is that correct?
 
Stormyblade said:
If you find that doesn't work, or you can't seem to keep a network connected (even wirelessly), you can buy an RTC module that works on the RPi. You insert a small coin battery, plug it in to the RPi headers, go to the same page you showed in your post, and update. The module is around $6, comes fully assembled, and the battery will last 2-3 years, according to what I've read from people here. Here's a link: https://www.adafruit.com/product/33..._dvnmFm67BzBPQsUo5c3aX7BGVea17JEaAu3REALw_wcB
Click to expand...


Is that what the drop down is for under Real Time Clock in the setup page?
 
ben&bobbi said:
Is that what the drop down is for under Real Time Clock in the setup page?
Click to expand...

Yes, the drop down is for the seperate RTC circuit board you could purchase. I have used both the board and the built in RTC. Both work equally well. Always within 1 second of the national time clock. Your first screenshot looks fine for NTP. A reboot is required when enabling the RTC. Then I usually set the time, date, time zone. Then it just works.
 
I never did the research to see which servers are NTP, or how to enter their names, so I can only speak to the RTC module. That little module performed superbly for me -- I checked the time numerous times this season and it was always holding correctly.

Remember that you don't have to do the RTC module - it's just an option.
 
aknflyer said:
Yes, the drop down is for the seperate RTC circuit board you could purchase. I have used both the board and the built in RTC. Both work equally well. Always within 1 second of the national time clock. Your first screenshot looks fine for NTP. A reboot is required when enabling the RTC. Then I usually set the time, date, time zone. Then it just works.
Click to expand...

I use the RTC on the FPP to get my show to start at a specific time.
RTC circuit board is for a real time clock (RTC is a small daughter board that plugs into the 40 pin header [i2C] on your Pi) that can be purchased for about 10.00. It has a battery to keep it running and once set, should keep time for a couple of years. If you want, you can click on the RTC pull down menu and see which types of RTC's are supported. I use both the Rasclock and the Adafruit RTC's and have no issues.
As stated above, when using a RTC, you must select the time and day, choose the correct RTC, and select your time zone. After clicking submit, you must reboot for the RTC to take effect.
 
thanks for the information. I thought i read somewhere that i had to enter a web address for it to look for time. I will leave it run for now and see what happens.
 
ben&bobbi said:
thanks for the information. I thought i read somewhere that i had to enter a web address for it to look for time. I will leave it run for now and see what happens.
Click to expand...

It already has the info embeded in the firmware for the ntp servers. No need to enter one unless you wish a different one.
 
Don’t put a NTP server at all unless you know what you are doing and need to. This setting is there for people that have systems that can’t get out to the internet and have to specify a local NTP server. By default, when you enable NTP, FPP will use random servers from a pool of NTP servers on the internet.
 
CaptainMurdoch said:
Don’t put a NTP server at all unless you know what you are doing and need to. This setting is there for people that have systems that can’t get out to the internet and have to specify a local NTP server. By default, when you enable NTP, FPP will use random servers from a pool of NTP servers on the internet.
Click to expand...

Not sure how to interpret that statement. I assume you mean: Do not manually enter an NTP server. Please allow the PI to use the built in list. (with this I fully agree)

The alternative interpretation is: Dont use NTP unless you know what you are doing. With this I would have to say, NTP is probably the simplest way for your PI to stay in sync and should be the preferred way (as opposed to adding an RTC).
 
MartinMueller2003 said:
Not sure how to interpret that statement. I assume you mean: Do not manually enter an NTP server. Please allow the PI to use the built in list. (with this I fully agree)
Click to expand...

Yeah , maybe I could have been a little clearer. The point is to let let the OS (DNS really) choose which NTP server to use unless you know you need to override the default. We have some people running FPP where the Pi/BBB can’t get to a NTP server on the internet due to firewall restrictions so they needed to specify an internal NTP server IP.
 
i am not sure why i don't have much luck with this stuff that seems simple. I set the clock to 4:24pm (16:24) it is 7:55pm (19:55) now (as i typed that). I restarted FPP, time did not update, i rebooted FPP, time did not update. I shutdown FPP and restarted the pi. Time did not change. So i will either buy the clock thing or just keep an eye on it.

I appreciate the help
 
ben&bobbi said:
i am not sure why i don't have much luck with this stuff that seems simple. I set the clock to 4:24pm (16:24) it is 7:55pm (19:55) now (as i typed that). I restarted FPP, time did not update, i rebooted FPP, time did not update. I shutdown FPP and restarted the pi. Time did not change. So i will either buy the clock thing or just keep an eye on it.

I appreciate the help
Click to expand...

My controllers didn't either, which is why I bought the RTC module. $10 shipped = peace of mind...can't beat that.
 
ben&bobbi said:
i am not sure why i don't have much luck with this stuff that seems simple. I set the clock to 4:24pm (16:24) it is 7:55pm (19:55) now (as i typed that). I restarted FPP, time did not update, i rebooted FPP, time did not update. I shutdown FPP and restarted the pi. Time did not change. So i will either buy the clock thing or just keep an eye on it.

I appreciate the help
Click to expand...

does the fpp have a path to the internet?
do you have ntp turned on?
 
You must log in or register to reply here.
Back
Top