NEMO GATEWAY Time and Date Stamp incorrect

editwiz · August 29, 2022, 6:21pm

NEMO GATEWAY GPS Time and Date are incorrect. It’s challenging the Predict Wind Hub that is installed on our Trawler Yacht. I’m working with Predict Wind Hub developer. Can the Rose Point Team remote in and correct this please? All other NEMA 2000 devices have corrected time and date stamp. I titled each device logged time with either GARMIN or NEMO GATEWAY N2K =0

Here are the other GPS times on your network…� everyone else is reporting the correct number of days since 1-1-1970
NEMO GATEWAY Ser# NG!-324025
NEMO GATEWAY IP Address 10.224.1.105
NEMO GATEWAY Firmware Version 1.13.5
Hardware Version 1.4.1
NEMO GATEWAY N2K = 0
N2kGNSS(0): Time=00:45:59, Date=30/08/2022
N2kGNSS(0): SID=17, Time=2759, Date=19234, Lat=41.3297, Lon=-71.9168, Alt=-25.2791
NEMO GATEWAY N2K = 0
N2kGNSS(0): SID=232, Time=2326, Date=19234, Lat=41.3296, Lon=-71.9168, Alt=-23.9387
GARMIN
N2kGNSS(22): Time=00:39:02, Date=29/08/2022
GARMIN
N2kGNSS(22): SID=48, Time=2342, Date=19233, Lat=41.3296, Lon=-71.9168, Alt=7.1
N2kGNSS(22): Time=00:39:15, Date=29/08/2022
GARMIN
N2kGNSS(22): SID=56, Time=2355, Date=19233, Lat=41.3296, Lon=-71.9168, Alt=7.5
N2kGNSS(22): Time=00:39:16, Date=29/08/2022
GARMIN
N2kGNSS(22): SID=76, Time=2356, Date=19233, Lat=41.3296, Lon=-71.9168, Alt=7.5
NEMO GATEWAY N2K = 0
N2kGNSS(0): Time=00:39:22, Date=30/08/2022
N2kGNSS(0): SID=10, Time=2362, Date=19234, Lat=41.3296, Lon=-71.9168, Alt=-24.1297
NEMO GATEWAY N2K = 0
N2kGNSS(0): Time=00:39:23, Date=30/08/2022
N2kGNSS(0): SID=11, Time=2363, Date=19234, Lat=41.3296, Lon=-71.9168, Alt=-24.1473
GARMIN
N2kGNSS(22): Time=00:39:25, Date=29/08/2022
N2kGNSS(22): SID=4, Time=2365, Date=19233, Lat=41.3296, Lon=-71.9167, Alt=7.6
NEMO GATEWAY N2K = 0
N2kGNSS(0): Time=00:39:25, Date=30/08/2022
N2kGNSS(0): SID=13, Time=2365, Date=19234, Lat=41.3296, Lon=-71.9168, Alt=-24.1425
GARMIN
N2kGNSS(25): Time=00:39:40, Date=29/08/2022
N2kGNSS(25): SID=16, Time=2380, Date=19233, Lat=41.3296, Lon=-71.9167, Alt=13.3
GARMIN
N2kGNSS(3): Time=00:39:42, Date=29/08/2022
N2kGNSS(3): SID=183, Time=2382, Date=19233, Lat=41.3296, Lon=-71.9168, Alt=-24.0063
NEMO GATEWAY N2K = 0
N2kGNSS(0): Time=00:39:55, Date=30/08/2022
N2kGNSS(0): SID=39, Time=2395, Date=19234, Lat=41.3296, Lon=-71.9168, Alt=-23.8215
GARMIN
N2kGNSS(22): Time=00:39:59, Date=29/08/2022
N2kGNSS(22): SID=180, Time=2399, Date=19233, Lat=41.3296, Lon=-71.9167, Alt=8.9
GARMIN
N2kGNSS(25): Time=00:39:59, Date=29/08/2022
N2kGNSS(25): SID=144, Time=2399, Date=19233, Lat=41.3297, Lon=-71.9167, Alt=13.3
NEMO GATEWAY N2K = 0
N2kGNSS(0): Time=00:39:59, Date=30/08/2022
N2kGNSS(0): SID=43, Time=2399, Date=19234, Lat=41.3296, Lon=-71.9167, Alt=-23.725
GARMIN
N2kGNSS(2): Time=00:40:02, Date=29/08/2022
N2kGNSS(2): SID=22, Time=2402, Date=19233, Lat=41.3297, Lon=-71.9167, Alt=-25.8487
GARMIN
N2kGNSS(25): Time=00:40:03, Date=29/08/2022
N2kGNSS(25): SID=224, Time=2403, Date=19233, Lat=41.3297, Lon=-71.9167, Alt=12.7
GARMIN
N2kGNSS(3): Time=00:40:05, Date=29/08/2022
N2kGNSS(3): SID=186, Time=2405, Date=19233, Lat=41.3297, Lon=-71.9167, Alt=-23.5928
NEMO GATEWAY N2K = 0
N2kGNSS(0): Time=00:40:05, Date=30/08/2022
N2kGNSS(0): SID=48, Time=2405, Date=19234, Lat=41.3297, Lon=-71.9167, Alt=-23.5928
GARMIN
N2kGNSS(2): Time=00:40:14, Date=29/08/2022
N2kGNSS(2): SID=154, Time=2414, Date=19233, Lat=41.3297, Lon=-71.9167, Alt=-26.1026
NEMO GATEWAY N2K = 0
N2kGNSS(0): Time=00:40:21, Date=30/08/2022
N2kGNSS(0): SID=62, Time=2421, Date=19234, Lat=41.3297, Lon=-71.9167, Alt=-23.918
NEMO GATEWAY N2K = 0
N2kGNSS(0): Time=00:40:22, Date=30/08/2022
N2kGNSS(0): SID=63, Time=2422, Date=19234, Lat=41.3297, Lon=-71.9167, Alt=-23.9687
NEMO GATEWAY N2K = 0
N2kGNSS(0): Time=00:40:27, Date=30/08/2022
N2kGNSS(0): SID=67, Time=2427, Date=19234, Lat=41.3297, Lon=-71.9167, Alt=-24.0908
GARMIN
N2kGNSS(2): Time=00:40:31, Date=29/08/2022
N2kGNSS(2): SID=91, Time=2431, Date=19233, Lat=41.3297, Lon=-71.9167, Alt=-26.064
NEMO GATEWAY N2K = 0
N2kGNSS(0): Time=00:40:31, Date=30/08/2022
N2kGNSS(0): SID=71, Time=2431, Date=19234, Lat=41.3297, Lon=-71.9167, Alt=-24.1967
NEMO GATEWAY N2K = 0
N2kGNSS(0): Time=00:41:05, Date=30/08/2022
N2kGNSS(0): SID=100, Time=2465, Date=19234, Lat=41.3297, Lon=-71.9167, Alt=-24.3872
NEMO GATEWAY N2K = 0
N2kGNSS(0): Time=00:41:12, Date=30/08/2022
N2kGNSS(0): SID=106, Time=2472, Date=19234, Lat=41.3297, Lon=-71.9167, Alt=-24.2867
GARMIN
N2kGNSS(25): Time=00:41:34, Date=29/08/2022
N2kGNSS(25): SID=28, Time=2494, Date=19233, Lat=41.3297, Lon=-71.9167, Alt=9
NEMO GATEWAY N2K = 0
N2kGNSS(0): Time=00:41:45, Date=30/08/2022
N2kGNSS(0): SID=135, Time=2505, Date=19234, Lat=41.3297, Lon=-71.9167, Alt=-23.8132
GARMIN
N2kGNSS(25): Time=00:41:58, Date=29/08/2022
N2kGNSS(25): SID=4, Time=2518, Date=19233, Lat=41.3296, Lon=-71.9167, Alt=9.6
NEMO GATEWAY N2K = 0
N2kGNSS(0): Time=00:42:28, Date=30/08/2022
N2kGNSS(0): SID=172, Time=2548, Date=19234, Lat=41.3297, Lon=-71.9167, Alt=-23.9389
GARMIN
N2kGNSS(25): Time=00:42:33, Date=29/08/2022
N2kGNSS(25): SID=200, Time=2553, Date=19233, Lat=41.3296, Lon=-71.9168, Alt=8.8
NEMO GATEWAY N2K = 0
N2kGNSS(0): Time=00:42:39, Date=30/08/2022
N2kGNSS(0): SID=182, Time=2559, Date=19234, Lat=41.3297, Lon=-71.9168, Alt=-23.8941
GARMIN
N2kGNSS(2): Time=00:42:45, Date=29/08/2022
N2kGNSS(2): SID=65, Time=2565, Date=19233, Lat=41.3297, Lon=-71.9168, Alt=-26.583
GARMIN
N2kGNSS(25): Time=00:42:56, Date=29/08/2022
N2kGNSS(25): SID=156, Time=2576, Date=19233, Lat=41.3296, Lon=-71.9168, Alt=7.7
GARMIN
N2kGNSS(2): Time=00:43:08, Date=29/08/2022
N2kGNSS(2): SID=68, Time=2588, Date=19233, Lat=41.3297, Lon=-71.9168, Alt=-26.1335
NEMO GATEWAY N2K = 0
N2kGNSS(0): Time=00:43:10, Date=30/08/2022
N2kGNSS(0): SID=209, Time=2590, Date=19234, Lat=41.3296, Lon=-71.9168, Alt=-23.5837
NEMO GATEWAY N2K = 0
N2kGNSS(0): Time=00:43:13, Date=30/08/2022
N2kGNSS(0): SID=212, Time=2593, Date=19234, Lat=41.3296, Lon=-71.9168, Alt=-23.5378
GARMIN
N2kGNSS(25): Time=00:43:28, Date=29/08/2022
N2kGNSS(25): SID=40, Time=2608, Date=19233, Lat=41.3296, Lon=-71.9168, Alt=7.3
GARMIN
N2kGNSS(3): Time=00:43:29, Date=29/08/2022
N2kGNSS(3): SID=179, Time=2609, Date=19233, Lat=41.3296, Lon=-71.9168, Alt=-23.603
NEMO GATEWAY N2K = 0
N2kGNSS(0): Time=00:43:30, Date=30/08/2022
N2kGNSS(0): SID=227, Time=2610, Date=19234, Lat=41.3296, Lon=-71.9168, Alt=-23.6429[date=2022-08-29 timezone=“America/New_York”]

editwiz · August 31, 2022, 3:00pm

Here is a dump of the actisense log showing the issue. Source address is 0 for the nemo

root@PW-Hub:/mnt/tmp# (/usr/local/bin/actisense-serial -r nmea2000.log | /usr/local/bin/analyzer) 2> /dev/null | grep 129029
2022-08-31T13:02:15.248Z 3 2 255 129029 GNSS Position Data: SID = 52; Date = 2022.08.30; Time = 12:50:22; Latitude = 41.3751495; Longitude = -72.3623943; Altitude = -28907962 m; GNSS type = GPS; Method = GNSS fix; Integrity = No integrity checking; Number of SVs = 11; HDOP = 0.80; PDOP = 1.37; Geoidal Separation = -33.24 m; Reference Stations = 0; Reference Station Type 1 = Unknown; Reference Station ID 1 = Unknown; Age of DGNSS Corrections 1 = Unknown
2022-08-31T13:02:15.266Z 3 25 255 129029 GNSS Position Data: SID = 164; Date = 2022.08.30; Time = 12:50:22; Latitude = 41.3751369; Longitude = -72.3624380; Altitude = 7.600000 m; GNSS type = GPS+SBAS/WAAS+GLONASS; Method = GNSS fix; Integrity = No integrity checking; Number of SVs = 24; HDOP = 0.49; PDOP = 0.95; Geoidal Separation = -34.00 m; Reference Stations = 0; Reference Station Type 1 = Unknown; Reference Station ID 1 = Unknown; Age of DGNSS Corrections 1 = Unknown
2022-08-31T13:02:15.267Z 3 3 255 129029 GNSS Position Data: SID = 110; Date = 2022.08.30; Time = 12:50:22; Latitude = 41.3751396; Longitude = -72.3624016; Altitude = -23.550968 m; GNSS type = GPS+SBAS/WAAS; Method = DGNSS fix; Integrity = No integrity checking; Number of SVs = 10; HDOP = 0.80; PDOP = 1.37; Geoidal Separation = -33.24 m; Reference Stations = 0; Reference Station Type 1 = Unknown; Reference Station ID 1 = Unknown; Age of DGNSS Corrections 1 = Unknown
2022-08-31T13:02:15.366Z 3 22 255 129029 GNSS Position Data: SID = 48; Date = 2022.08.30; Time = 12:50:26; Latitude = 41.3751484; Longitude = -72.3624426; Altitude = 7.500000 m; GNSS type = GPS+SBAS/WAAS+GLONASS; Method = GNSS fix; Integrity = No integrity checking; Number of SVs = 24; HDOP = 0.50; PDOP = 1.00; Geoidal Separation = -34.00 m; Reference Stations = 0; Reference Station Type 1 = Unknown; Reference Station ID 1 = Unknown; Age of DGNSS Corrections 1 = Unknown
2022-08-31T13:02:15.387Z 3 22 255 129029 GNSS Position Data: SID = 68; Date = 2022.08.30; Time = 12:50:27; Latitude = 41.3751488; Longitude = -72.3624423; Altitude = 7.500000 m; GNSS type = GPS+SBAS/WAAS+GLONASS; Method = GNSS fix; Integrity = No integrity checking; Number of SVs = 24; HDOP = 0.50; PDOP = 1.00; Geoidal Separation = -34.00 m; Reference Stations = 0; Reference Station Type 1 = Unknown; Reference Station ID 1 = Unknown; Age of DGNSS Corrections 1 = Unknown

Here is the NEMO

2022-08-31T13:02:15.595Z 3 0 255 129029 GNSS Position Data: SID = 109; Date = 2022.0831; Time = 12:50:37; Latitude = 41.3751412; Longitude = -72.3624045; Altitude = -22.931873 m; GNSS type = Unknown; Method = Unknown; Integrity = No integrity checking; Number of SVs = Unknown; HDOP = 0.80; PDOP = 1.37; Geoidal Separation = -33.24 m; Reference Stations = 0

here is a capture of the RAM N2K data

6039739 : Pri:3 PGN:129029 Source:0 Dest:255 Len:43 Data:67,23,4b,d0,c3,8c,1b,0,e8,e6,d7,b3,f0,bd,5,0,e0,60,97,ca,2b,f5,f5,52,2a,98,fe,ff,ff,ff,ff,ff,fc,ff,50,0,89,0,4,f3,ff,ff,0
SetSystemTime: Updating system from time(1661863823) = 12:50:23 30/08/2022 to time(1661950221) = 12:50:21 31/08/2022
N2kGNSS(0): Time=12:50:21, Date=31/08/2022
N2kGNSS(0): SID=103, Time=46221, Date=19235, Lat=41.3751, Lon=-72.3624, Alt=-23.5821

I have highlighted the two bytes which indicate the date since 1-1-1970 Preformatted textconverting that from hex to dec we get 19235 which is off by one day.

ModeID: Nemo Gateway
Source: 0
Manufacturer code: 384
Product code: 18714
Unique number: 1196069
Software version: 1.0.0
Model version: Nemo Gateway
Manufacturer Information:

I have attached log files for you in my email response.

–luis

stevenh · August 31, 2022, 5:19pm

Louis,

Check with Jeff. That PGN should no longer be on the network. We still have a few things to look at to determine if the date discrepancy is an error in the Nemo or GIGO, but that PGN, and others, should no longer be sourced from the Nemo. Please confirm and get back to me via our email channel. Thanks!