Looking for SyncServer S350 SAASM cf card image

[drdmr]

Interesting, I can ping both eth0 and eth1. What do you see from ifconfig? Mine shows the following:

root@SyncServer:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:A0:69:0B:61:BC
          inet addr:192.168.1.13  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::2a0:69ff:fe0b:61bc/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4649013 errors:0 dropped:0 overruns:0 frame:0
          TX packets:485193 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:324196798 (309.1 MiB)  TX bytes:100734424 (96.0 MiB)
          Interrupt:9 Base address:0x4000

eth1      Link encap:Ethernet  HWaddr 00:A0:69:0B:61:BD
          inet addr:192.168.1.27  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::2a0:69ff:fe0b:61bd/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6155997 errors:0 dropped:2 overruns:1 frame:0
          TX packets:44956 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:580598598 (553.7 MiB)  TX bytes:2149734 (2.0 MiB)
          Interrupt:9 Base address:0x4000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:12220135 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12220135 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:901790250 (860.0 MiB)  TX bytes:901790250 (860.0 MiB)

root@SyncServer:~#

[smgvbest]

OMG,   this may fall under a stupid user trick

i went to my S350 and was checking things and i saw the LAN2 connection (ETH1) was not showing activity.   I checked the connection and it was fine.  I went to the switch and the bloody network cable had a broken tab and the cable pulled loose 

now I am seeing it syncing again

Code: [Select]

Tue Jun 02 2020 21:41:37 Info:    Wait expired after 5 minutes
Tue Jun 02 2020 21:41:38 Info:    Summary: 1 sample (aggregate); delta is +0.0000001 seconds, latency +0.0002309
Tue Jun 02 2020 21:41:38 Info:    Local clock and 192.168.1.148 match to within local timer resolution; delta +0.0000001 seconds, protocol PTP, latency 0.0002309 seconds; time not changed (slewing min not met)
Tue Jun 02 2020 21:41:38 Info:    Next time check due in 5 minutes (sliding window)

I'm sure it was one of the cats that did it.   they're always causing trouble 

[texaspyro]

I'm sure it was one of the cats that did it.   they're always causing trouble 

I have some tasty cat recipes...   

[drdmr]

Sandra,

Cool -- glad it's working again!  If it's okay with you, I'll take a bit of credit for leading you to check the obvious. And I've spent hours tracking down simple problems like this, so I can relate.

I recognize the output from Domain Time II, which I use to keep my laptop sync'ed to NTP. It's a nice program, though I don't use PTP on the laptop because it doesn't work well over WiFi. My PTP slaves use hardware time-stamping, which typically keeps them sync'ed to within tens of nanoseconds or better. It's all used equipment, but still an expensive hobby!

I'm impressed that you're getting PTP synchronization "to within local timer resolution" (100 ns?). That happened occasionally on my laptop when I used DT II with PTP and a hardwire connection. Is that a typical result for you, and if so, how do you maintain that level of synchronization accuracy?

-- Dean

[smgvbest]

Yep,  that got me thinking and after finding all i could think was check your power supply voltage.   for network , check your cabling
and yeh, that is Domain Time II.  I tend to hardwire all my computers and use WiFI for phones, tablets and printers

I am typically pretty close to the 100ns most the time but I'm not doing anything special.  gigibit network in the home which is where this pc is
my goal here is for my observatory to use the S350.   I'll move it out there when things are back up.   I would like as accurate timestamps as I can get on my images when I do astroroid hunting

[smgvbest]

I'm sure it was one of the cats that did it.   they're always causing trouble 

I have some tasty cat recipes...   

 

[drdmr]

I am typically pretty close to the 100ns most the time but I'm not doing anything special.  gigibit network in the home which is where this pc is
my goal here is for my observatory to use the S350.   I'll move it out there when things are back up.   I would like as accurate timestamps as I can get on my images when I do astroroid hunting

Nice! Please ignore the attached screenshot showing a PTP slave sync'ed to 1 nanosecond. You really don't need that level of accuracy. Seriously, you probably don't. As I said, it's an expensive hobby, and I'm guessing an observatory is even more expensive.

Full disclosure: sometimes my PTP slaves are off by tens or occasionally (horrors!) almost 100 nanoseconds. But they're often much better, as in this screenshot.

[smgvbest]

show off 

yes, the observatory is more than all the test equipment I have combined both newly purchased and repaired.   Now new cost on a few pieces would be more than the observatory but I only count what I actually paid.

For me once this is in the observatory I could loose my main network and maintain accuracy to more than I need.   but Nasa does like accurately time stamped images I just dont think they specify what accurately means

does this qualify us as time nuts??

[drdmr]

show off 

Guilty as charged.

For me once this is in the observatory I could loose my main network and maintain accuracy to more than I need.   but Nasa does like accurately time stamped images I just dont think they specify what accurately means

So, to get the kind of accuracy I "showed-off", you need hardware time-stamping in the PTP slave and any ethernet switches between it and the master. I added those components piecemeal over time, and then didn't know when to quit -- meaning I have more time synchronization servers, masters, slaves, and hardware time-stamping switches than I really need. It's sometimes hard not to buy when I recognize an eBay item is both an upgrade to my current equipment and a "bargain".

For the observatory, do you need a switch and PTP slave, or can you somehow time-stamp directly from the S350? If you could benefit from having a switch and slave with hardware time-stamping, maybe I could sell some to you -- used, of course -- at a bargain price.

does this qualify us as time nuts??

That's an interesting question. Compared to most people, I'd say you are a time nut, and I am beyond one. But since I'm on their mailing list, I know how truly nutty some of them are, with their hydrogen masers and so on. That makes me reluctant to call myself a time nut before one of them -- i.e., a certified (or certifiable?) time nut -- calls me one.