Target List

[brijill]

Hello, new bod here.

I wonder if you can help with the following.. I am running OpenCPN at the moment, fed with data from AISMon, received via Funcube Pro+ dongle which is driven by SDR Sharp...

What I would like to do, as a hobby thing rather than a actual sailor, is to keep a log of targets received by my system. Is there any way of copying or saving in some way, the Target List. I can't see any option do this, so any help would be appreciated. Thanks!

If no option is presently available, I wonder if the Authors of OpenCPN would consider adding this facility?

[Hakan]

brijill..
There's no option for this in OCPN.
For such a special need I think you've to learn to code something yourself.
It wouldn't be so hard to code. In for example OCPN you can get AISdecoder.cpp to write to your own file when the AIS target name is printed to file MMSINAME.
How to set up a coding environment for OCPN is described here: https://opencpn.org/wiki/dokuwiki/do...eveloper_guide
This is a nice hobby, good luck
Håkan

[rgleason]

Originally Posted by brijill

Is there any way of copying or saving in some way, the Target List.

If this is land based, with internet, very near the sea, you could try to join MarineTraffic and provide your data, then you'd be able to see it on MarineTraffic.

[.Paul.]

brijill,

OpenCPN automatically records the MMSI number and vessel name for every AIS target that has been identified by name. Every AIS message contains the MMSI number, but the vessel name is sent less frequently. The file containing this is named MMSINAME.CSV, and it is saved in the same folder as the opencpn.log file.

Here is a part of the MMSINAME.CSV from my system.

338187545,TWOSCO

220597000,GUTHORM MAERSK

338193601,ELLA BEL

371290000,WEST TREASURE

367682340,AMISTAD

538004172,DUBAI ATTRACTION

373165000,BASIC OCEAN

636091196,LONDON STAR

366998510,AMNAV LIBERTY

367184720,EAGLET

338174439,ANN-ELYSE

366998830,ROYAL MELBOURNE

636092413,DS PROMOTER

367581220,AHBRA FRANCO

338207691,POST TIME

367396710,Z FOUR

367353110,PELICAN STATE

You can find more information on this in the manual that comes with OpenCPN.

The Voyage Data Recorder plugin can record all AIS messages and other NMEA0183 messages that are received by OpenCPN. You might find or write a program that would extract the information you want to log from the VDR recording.

You may add a Feature Request in the "Tracker" at official OpenCPN website:

https://opencpn.org/

If the suggested feature is wanted by many users (users vote for features they want added to OpenCPN) it might get added either in OpenCPN's code or as a plugin. There are many more feature requests than the OpenCPN developers can get to, so as Håkan suggested, you might need to code it yourself.

Paul

[brijill]

Thanks for that. Actually I already contribute to Marine Tracker, but my data s not distinguishable from everyone else's that I can see...

[brijill]

Thanks Paul. Actually that would do ie opencpn.log then MMSINAME.CSV Unfortunately after checking every file in OpenCPN in program files, I can't find either of them. Can you give a screenshot or describe how to get to it?. I've even used search OpenCPN and it comes up with no items match your search. Puzzled!. I'm using Version 4.8 by the way.

[brijill]

Ok Paul, I've found MMSINAME. I was looking in Program files/opencpn and it's actually in Program data/opencpn....Brilliant!. Now I can go to bed happy. Thanks guys for your help anyway.Cheers!

[rgleason]

I do not see that in my version. In AIStargetList.h I do see

ArrayOfMMSI *m_pMMSI_array;

and

void UpdateAISTargetList( ); // Rebuild AIS target list
void UpdateNVAISTargetList( );
void CopyMMSItoClipBoard(int);

Then in AIStargetList.cpp it all seems to be working out of that array.

The MMSI Properties TAB under Ship has a list. I have not found where that is stored, or if it is stored as an outside file.
Hakan worked with it to Make a "Buddy Category" that does not alert.

I don't see the MMSINAME.CSV .Paul wrote about....
and have done several searches on it in github/OpenCPN
nor have I found it in my Ov4.8.0 program file (x86) directory..

[.Paul.]

Originally Posted by rgleason

.
.
.
I don't see the MMSINAME.CSV .Paul wrote about....
and have done several searches on it in github/OpenCPN
nor have I found it in my Ov4.8.0 program file (x86) directory..

I wrote about the MMSINAME.CSV that OpenCPN saves in the same folder that contains the opencpn.log--on a Windows PC:

C:\ProgramData\opencpn

Here is a screenshot from Windows:


MMSINAME.CSV won't be there if your OpenCPN installation has not received any vessel names from AIS.

Paul

[rgleason]

Paul, I am still learning.. which is good. -- found it with 3200 lines filled. Thanks.

I think the MMSINAME.CSV file & path should be noted in the manual.

Is this the correct area to make a note about this file?

https://opencpn.org/wiki/dokuwiki/do...is_target_list

[.Paul.]

Originally Posted by rgleason

Paul, I am still learning.. which is good. -- found it with 3200 lines filled. Thanks.

I think the MMSINAME.CSV file & path should be noted in the manual.

Is this the correct area to make a note about this file?

https://opencpn.org/wiki/dokuwiki/do...is_target_list

You put the note about the MMSINAME.CSV file in a good place. I have noted some edits (Windows uses the back slash "\" Linux and most other systems use the forward slash "/"):

MMSINAME.CSV File

This file is a simple list with two columns, MMSI Number and Vessel Name. It is saved in your User file the /ProgramData/opencpn/ folder (Windows: C:\ProgramData\Opencpn\ ) near the opencpn.ini file. It is used to provide Vessel names that frequent your area because the vessel name is not sent or available all the time.

You might add:

Static data including vessel name, call sign, dimensions, etc., are sent once every six minutes. The MMSINAME.CSV exists to provide names for vessels sending AIS messages while your system has yet to receive the static data.

Paul

[skipperearly]

While we are discussing on this MMSI log may I raise some questions:

1. I noticed that in my file many entries are doubble, yes 2 lines with the same mmsi,name pair. - What could be the reason for this?

2. I am usine OCPN on several systems and think about merging the mmsitoname.csv files to hold a personal history log. Will a ever growing mmsitoname file start slowing down my system?

3. Some entries a obviously garbled, which I assume comes from jammed messages but what will happen when the next ais message provides the full name ? Nothing - a new entry - or a correction?

I attach my file in case someone wishes to investigate.

[bcn]

Originally Posted by skipperearly

3. Some entries a obviously garbled, which I assume comes from jammed messages but what will happen when the next ais message provides the full name ? Nothing - a new entry - or a correction?

If the MMSI/Name pair is not matching with the entry in the file the latest MMSI/name pair will be added to the file.

Had the case where a semi broken AIS transmitter on a merchand vessel would send garbled names quite often. And its MMSI piled up for every alternating occurrence.

[cagney]

mmsitoname.csv was discussed earlier this year in relation to a bug. Start reading with this post -> http://www.cruisersforum.com/forums/...ml#post2344842

Thomas

[rgleason]

Cagney,
As I understand it, the mmsiname.csv gets updated to the bottom (and is read from the bottom) and bdbcat made some changes at the last minute which you and Hakan tested which were to refresh the mmsiname.csv with the most recent MMSI Ship Name pairs on the AIS screen, which will be used to when restarting OpenCPN.

Upon restarting O, the AIS system continues updating to update and then updates mmsi and names at the bottom when it closes....

There is an issue with regard to duplicate entries, misformed or mangled data and GPS that are renamed frequently, which tends to fill the MMSIname.CSV file. That has not been addressed yet.

Is this about right? What of if would you put in the manual? Is there any need for a tracker on this?

Paul, I added your line and fixed \ (Ever since I used Linux, I've had backslash screwed up.)
Thanks.