[pandaro] Re: Clock
- From: "Chris Evans (CJE/4D)" <chris@xxxxxxxxxxxxxxx>
- To: pandaro@xxxxxxxxxxxxx
- Date: Mon, 2 Jun 2014 16:36:40 +0100 (BST)
On Mon 02 Jun, Chris Bell (Lists) wrote:
>
> cj <chris@xxxxxxxxxxxxxxxxxxxx> wrote:
> > Chris Bell (Lists) <chris.lists@xxxxxxxxxxxx> wrote:
> > > It's either a PandaRO problem or something wrong here - does it
> > > work for other PanaRO users or not?
>
> > Seems to work here fine.
>
> > *nettime_status
> > Current time: Monday, 2 June 2014 12:36:01.13
> > Status: Sleeping
> > Last adjustment: 12 minutes 55 seconds ago
> > Last delta: 0.053125 seconds slow
> > Last server: ntp.oceanmediagroup.eu
> > Last protocol: SNTP
> > Poll interval: 30 minutes
>
> Not here...
>
> Configuration
> => Time and Date
> => Set from network, Pick a server automatically
> => Try...
> Says 'Not connected', counts to 100, then says 'Busy'
Works here.
> Then...
>
> *NetTime_Status
> Current time: Monday, 2 June 2014 15:06:37.51
> Status: Expecting
> Last server: lyla.preshweb.co.uk
> Last protocol: SNTP
> Poll interval: 30 minutes
> *
> *show *time*
> NetTime$Loaded(Number) : 1
> Sys$Time : 15:19:25
> TimeSetup$Dir : SDFS::Panda.$.!Boot.RO500Hook.Res.Configure.!TimeSetup
>
> I'm using the following. Are you using the same...?
>
> RISC OS 5.21 (21-Apr-14)
> NetTime 0.43 (28 Nov 2013)
> !Boot - current, updated from ROOL website a few days ago
*nettime_status
Current time: Monday, 2 June 2014 15:47:49.52
Status: Sleeping
Last adjustment: 14 minutes 39 seconds ago
Last delta: 0.046952 seconds fast
Last server: time.videxio.net
Last protocol: SNTP
Poll interval: 30 minutes
Timer latch: 384007 (-18ppm)
NetTime 0.40 10.4.2012
RISC OS 5.21 21-Apr-2014
> > Why not use the Battery Backed RTC? (Tick 'Manual') If it tries and
> > fails to reach a timeserver it should use the BatteryBacked RTC.
AIUI If time server is ticked on booting it gets the time from a timeserver, if
that fails it uses the BB RTC.
If manual is ticked then it uses the BB RTC
> My PandaRO must use the battery-backed clock, since it keeps time
> between sessions. I assumed that 'Set manually' and 'Set from the
> network' are merely there to correct any drift - am I wrong?
>
> > I'm pretty certain the problem is not PandaRO specific and appears to
> > be a RISC OS 5 - NetTime/FreeTime problem.
>
> > Other options are: contact the authors of NetTime and/or FreeTime. or
> > ROOL via their forums.
>
> NetTime works for ARMiniX users,
and most PandaRO users! Not a lot of comfort when you are the one person
with a problem.
AIUI the ARMiniX has an BB RTC which is functionaly the same as ours
(Probably also a DS1338)
> so I see no point in pursuing other
> avenues. It's either a PandaRO problem or something wrong here - does
> it work for other PanaRO users or not?
I'm 99% sure it is something in your boot or to do with with your satelitte
connection.
> > You did mention you have carried some things over from your Iyonix and
> > PandaLand.
>
> Everything now Pandaboard-specific as far as I'm aware.
Tracking down problems within $.!Boot can take forever.
Why not set the clock to manual?
Chris Evans
--
*** PandaRO: The most advanced ARM RISC OS computer so far! ***
------------------ http://www.pandaro.co.uk/ ------------------
CJE Micro's / 4D 'RISC OS Specialists'
Telephone: 01903 523222 Fax: 01903 523679
chris@xxxxxxxxxxxxxxx http://www.cjemicros.co.uk/
78 Brighton Road, Worthing, West Sussex, BN11 2EN
Don't let the urgent things in life, crowd out the important things!
Other related posts:
