I am using LoggerNet 3.4.1 with a CR3000 whose time is kept accurate with a Garmin GPS16X-HVS. The LoggerNet server to which this station is attached does not have access to an accurate time server. Is there any way to keep the LoggerNet server clock set accurately (whether automatic or manual) using the time from the CR3000 station? From what I can find in LoggerNet, you can set the station from the server (in Connect mode) but not vice versa.
A very long time ago in our old DOS software we did support such a feature. However, as far as I can see that function disappeared some time ago and they are no standard or back door ways for doing this now other than writing your own code.
Thanks Andrew for your reply. Any chance this functionality could be implemented (restored!) in a future release of LoggerNet? This seems like a no-brainer. My LoggerNet server is out in the field with no way of connecting to a time server. It seems silly to have to set the LoggerNet server's clock manually when we already have a GPS working to keep the CR3000 clock set accurately.
Hello David,
I have added this to our database as an enhancement request, but keep in mind that it might be a lot more involved to set a Windows system value than it was to set the clock in DOS :)
Thanks for the input; we'll see what we can do.
Dana W.
Folks-
The CR3000 can act as an NTP time server. See help on NetworkTimeProtocol. This requires that the logger be connected to a Network Link Interface (e.g., NL115). You can direct your Loggernet machine's (running Windows?) clock update setting to the IP address of the NL115. (I just tried this and it works.) This requires that you establish a network connection between the Loggernet machine and the CR3000 which may or may not require a router or switch to be in between the two. I'm sure Campbell tech support could set this up to see what the minimum network configuration is for this to work. BTW, you need to set the NTPOffset using the NetworkTimeProtocol command (NetworkTimeProtocol("",LOCAL_TIME_OFFSET*3600,0)) where LOCAL_TIME_OFFSET*3600 is the same parameter used by the GPS command.
Chris E.
We investigated this further; I have the following comment from our LoggerNet engineer:
The capability to set the computer clock was available in PC208W because DOS (and, by extension, Windows 3.1) did not have any real security. That is not the case for more recent versions of Windows. Any application that is going to set the PC clock must have special privileges granted to the application and to the user account under which that application runs.
This is more restrictive than we would like to impose, so for now, it won't be something that we pursue.
Dana W.
I have a device (StarDot Netcam, runs uClinux) connected to a CR1000 logger (OS v24) using the NL115 interface, and would like to set the clock on the device using NTP. The logger does function as an NTP server, but it appears to ignore the UTC Offset setting in the logger. I can make things work if that's the case, but want to confirm this.
I tried to use the LoggerNet (v4.0 on a Windows laptop) terminal mode 'W' command, but it offers watching/snooping on TCP/IP, while NTP uses UDP. I see no NTP packets in the terminal display.
I tried telnetting to the logger, then using '65535D' can see some network activity, but again no NTP packets. The Netcam is configured to request an NTP connection when it starts up, and I'm pretty sure this is happening, though not 100% certain of it.
Is there a way to troubleshoot or otherwise view NTP packets coming to and from the logger?
* Last updated by: kirving on 3/22/2013 @ 5:48 PM *
Hello, colleagues,
I am facing a clock sync issue on my CR1000X. It is set to sync via Garmin's GPS16-HVS, following the settings recommended by Campbell's setup module. My reference offset is −3, but it is syncing with an offset of +4. I am reviewing the settings, but have not been able to find a solution yet.
I would appreciate any guidance or suggestions you can offer to resolve this issue.
Thanks!
Const GPS_TimeOffset = -3 'The local time offset, in hours, from UTCConst GPS_MaxTimeDiff = 6000
#If Use_GPS16X_HVS = 1
Dim NMEASent(2) As String * 100 Public GPSData(15) Alias GPSData(1)=Latitude_A 'Degrees latitude (+ = North; - = South) Alias GPSData(2)=Latitude_B 'Minutes latitude Alias GPSData(3)=Longitude_A 'Degress longitude (+ = East; - = West) Alias GPSData(4)=Longitude_B 'Minutes longitude Alias GPSData(5)=Speed 'Speed Alias GPSData(6)=Course 'Course over ground Alias GPSData(7)=MagVar 'Magnetic variation from true north (+ ='East; - = West) Alias GPSData(8)=FixQual 'GPS fix quality: 0 = invalid, 1 = GPS, 2 ='differential GPS, 6 = estimated Alias GPSData(9)=NumSats 'Number of satellites used for fix Alias GPSData(10)=Altitude 'Antenna altitude Alias GPSData(11)=PPS 'usec into sec of system clock when PPS'rising edge occurs, typically 990,000 once'synced Alias GPSData(12)=SecSinceGPRMC 'Time since last GPRMC string, normally less'than 1 second Alias GPSData(13)=GPSReady 'Counts from 0 to 10, 10 = ready Alias GPSData(14)=MaxClockChange 'Maximum value the clock was changed in msec Alias GPSData(15)=NumClockChange 'Number of times the clock was changed
'Define Units to be used in data file header Units Latitude_A=degrees Units Latitude_B=minutes Units Longitude_A=degrees Units Longitude_B=minutes Units Speed=knots Units Course=degrees Units MagVar=degrees Units FixQual=code Units NumSats=count Units Altitude=meters Units PPS=microseconds Units SecSinceGPRMC=seconds Units GPSReady=count Units MaxClockChange=milliseconds Units NumClockChange=count'GPS16X-HVS GPS Receiver measurements 'Latitude_A', 'Latitude_B', 'Longitude_A', 'Longitude_B', 'Speed', 'Course', 'MagVar', 'FixQual', 'NumSats', 'Altitude', 'PPS', 'SecSinceGPRMC', 'GPSReady', 'MaxClockChange', and 'NumClockChange' 'The datalogger clock will be synchronized to GPS time. #If Use_GPS16X_HVS = 1 #If ((LoggerType = CR3000) OR (LoggerType = CR1000) OR (LoggerType = CR1000X)) GPS(GPSData(),GPSComPort,GPS_TimeOffset*3600,GPS_MaxTimeDiff,NMEASent()) #ElseIf LoggerType = CR300 GPS(GPSData(),GPSComPort,PPS_Port,GPS_TimeOffset*3600,GPS_MaxTimeDiff,NMEASent())
If the UTC Offset setting in the data logger is set, it will override the parameter in the GPS instruction. Check the data logger settings.