AIS targets all have

[KvotheBloodless]

Confirmed this is not an AIS or SignalK issue, the heading of other vessels is correct on NMEA2k equipment feeding directly from the AIS and also another UI feeding from the SignalK data.

[panaaj]

Can you please confirm the "Preferred Paths" values in Settings and confirm that the selected path for Heading/COG appears in the Signal K data stream. The path set here is what is used to orient the AIS targets on the map.

It would also be helpful if you could provide a screenshot of the data in the browser for one of the AIS targets or the data returned from http://host/signalk/v1/api/vessels/<vesselId>.

[KvotheBloodless]

@panaaj Confirmed that navigation.courseOverGroundTrue and navigation.headingTrue both appear in the data stream for other vessels. I have also tested all 4 options for Heading / COG in the preferred paths settings and none of these make any difference. All AIS targets just point north.

/signalk/v1/api/vessels/urn:mrn:imo:mmsi:503101970

{
    "mmsi":"503101970",
    "navigation":{
        "speedOverGround":{
            "meta":{
                "units":"m/s",
                "description":"Vessel speed over ground. If converting from AIS 'HIGH' value, set to 102.2 (Ais max value) and add warning in notifications"
            },
            "value":0.41,
            "$source":"Actisense.1",
            "timestamp":"2022-04-25T01:32:25.203Z",
            "pgn":129039
        },
        "courseOverGroundTrue":{
            "meta":{
                "units":"rad",
                "description":"Course over ground (true)"
            },
            "value":4.6923,
            "$source":"Actisense.1",
            "timestamp":"2022-04-25T01:32:25.203Z",
            "pgn":129039
        },
        "position":{
            "meta":{
                "description":"The position of the vessel in 2 or 3 dimensions (WGS84 datum)",
                "properties":{
                    "longitude":{
                        "type":"number",
                        "description":"Longitude",
                        "units":"deg",
                        "example":4.98765245
                    },
                    "latitude":{
                        "type":"number",
                        "description":"Latitude",
                        "units":"deg",
                        "example":52.0987654
                    },
                    "altitude":{
                        "type":"number",
                        "description":"Altitude",
                        "units":"m"
                    }
                }
            },
            "value":{
                "longitude":114.6122533,
                "latitude":-28.7662016
            },
            "$source":"Actisense.1",
            "timestamp":"2022-04-25T01:32:25.203Z",
            "pgn":129039
        },
        "headingTrue":{
            "meta":{
                "units":"rad",
                "description":"The current true north heading of the vessel, equals 'headingMagnetic adjusted for magneticVariation'"
            },
            "value":5.0256,
            "$source":"Actisense.1",
            "timestamp":"2022-04-25T01:32:25.203Z",
            "pgn":129039
        },
        "closestApproach":{
            "meta":{
                "description":"Calculated values for other vessels, e.g. from AIS",
                "properties":{
                    "distance":{
                        "description":"Closest Point of Approach (CPA), distance between own vessel and other vessel, based on current speeds, headings and positions",
                        "type":"number",
                        "units":"m",
                        "example":31.2
                    },
                    "timeTo":{
                        "description":"Time to Closest Point of Approach (TCPA), between own vessel and other vessel, based on current speeds, headings and positions",
                        "type":"number",
                        "units":"s",
                        "example":312
                    }
                }
            },
            "value":{
                "distance":544.6521663137146,
                "timeTo":1950.4753807513669
            },
            "$source":"derived-data",
            "timestamp":"2022-04-25T01:32:54.170Z"
        }
    },
    "sensors":{
        "ais":{
            "class":{
                "meta":{
                    "description":"AIS transponder class in sensors.ais.class, A or B"
                },
                "value":"B",
                "$source":"Actisense.1",
                "timestamp":"2022-04-25T01:32:25.203Z",
                "pgn":129039
            }
        }
    },
    "name":"SOUTHERN CROSS 3",
    "design":{
        "aisShipType":{
            "meta":{
                "description":"The ais ship type see http://www.bosunsmate.org/ais/message5.php",
                "properties":{
                    "id":{
                        "type":"number",
                        "description":"The ship type number"
                    },
                    "name":{
                        "type":"string",
                        "description":"The ship type name"
                    }
                }
            },
            "value":{
                "id":37,
                "name":"Pleasure"
            },
            "$source":"Actisense.1",
            "timestamp":"2022-04-25T01:27:54.516Z",
            "pgn":129810
        }
    }
}

[panaaj]

The data set is similar to what I see on my installation where the targets are oriented correctly. So there seems to a be a condition occuring which is causing the orientation to be left at the default of 0.

At this time you are the only one reporting this issue and I can't reproduce it with the data stream I have access to so debugging is going to require your assistance.

Are you comfortable using your browser's devtools to help find the issue?

[KvotheBloodless]

@panaaj definitely able to help. Just tell me what you need me to look at.

JS console shows nothing that seems related to this.

[panaaj]

You'll need to use the source and set a breakpoint so we can inspect some values. I will send some instructions through.

[panaaj]

closed due to inactivity