OpenSkipper Files

OpenSkipper 1.3 (2014.05.011)
Developed by Andrew Mason, a.mason@auckland.ac.nz, and Jason Drake
Modified 20140511 by Timo Lappalainen and Kave Oy
Version 1.3 provides the code changes developed by Timo Lappalainen and Kave Oy

Open Skipper (Open Source, GPL)
Open Skipper is Open Source code for integrating and displaying NMEA 0183, NMEA 2000 and AIS data from nautical instruments, GPS units and internet data sources. See project official page on http://openskipper.org/	
Executable & Sample Files: OpenSkipper-1.3.zip 
Source Code: OpenSkipper-1.3-src.zip

Note: This demo is pre-configured for our testing to connect to ports associated with com0com and an Actisense NGT-1 for NMEA 2000; error messages will be reported at startup if the ports required for these are not configured. We recommend that you test OpenSkipper by downloading the log files provided at http://sourceforge.net/projects/openskipper/files/Logfiles.zip/download and using File... Reply Logfiles... to replay a log file.

----------------------------

Open Skipper v1.3 Change Log

Here is list of changes to Open Skipper application made by Timo Lappalainen.

My goal is to make this real tool for showing navigation and other boat information. Since I already have WLAN on my yacht, with current version it is possible to use e.g. tablets for showing all the information.

Version 1.3.2014.0511

Changes:

    Changed default setting for "Hide Menus On Start" to false so it will not confuse old users.
    Added WWW port configuration so that OpenSkipper web server can be used in combination with other systems.

Version 1.3.2014.0501

Changes:

    New parameters TopMost, DefLocation and StartMinimized for display definitions. Now application also saves user defined form positions.
    Changed Tools-"Actisense NGT-1 USB Explorer ..." to more common Tools-"Serial port listener...". The modified listener has option to listen in NMEA2000, NMEA0183 (Ascii) or HEX mode. You can choose also desired baud rate. The listener form has changed modeless, so you can use it as separate form. With com0com and hub4com you can spy the traffic while data is shown on controls.
    Now display selection chort cut keys works also on all forms.

Version 1.3.2014.0427

Changes:

    Now also display type Form is supported. So you can have all displays in own forms instead of tab pages.
    Form can be moved by mouse down almost anywere withing form. This makes positioning much easier.
    Forms also have context menu (right click over form) for e.g. minimizing, choosing other views (tabpage or form) and some other tasks. It may grow in future.

Version 1.3.2014.0423

Changes:

    There is no more default dials page. All pages are loaded through definition .xml files. Displays.xml defines a list of displays (currently only TabPage type is supported.). In sample Displays.xml there are four tabpages, where the first is like original Dials, but it has been defined with Display_Dials.xml. So you do not need Visual Studio to define your own tab pages at all. Unfortunately you will need some knowledge of available components and how to use them. Hopefully four sample pages gives good start.
    You can also edit display definition files on the fly. After you have made your changes just press ctrl-shift-R to update changes.
    Now application opens as default to minimal view, which has fixed position. By pressing ctrl-M, you get menu view so that you can move window and also have all old menus back. Then switch back to minimal view with ctrl-M. You can set startup behaviour under File-Settings... I will implement in future also some way to move window in minimal state.
    If you have definition files under application path, application will use them as default.
    Better Web server. Now you can write your www code all by your self. There are sample files under www directory. As in sample, you can also use images and style files for your web pages as in normal web programming.

    Currently parameter delivery works as in old version with POST. There are few important things. Let's look e.g. Steer.html sample file:
        <script type="text/javascript" language="javascript">var ParamPageName="/Steer.html"</script>
        This definition tells that for this file we use parameters defined on page Steer.html. At beginning it is easiest to define parameters on same page as your display.
        <script src="OpenSkipper.js"></script>
        Include also default script file. OpenSkipper has special handling for requests to /ParamData/.... It then responces u(ParamID,Value); u(...)... with parameters defined for that page. In default OpenSkipper.js there is handler for that u(...) function. At beginning it is easiest to use that and after getting in to system you can make more pfroessional views. But just keep in mind special handling for requests to /ParamData/... and responce for that is format u(ParamID,Value);
        <td><span name="t1" id="{OpenSkipperParam:Heading}"></span></td>
        With this we define that at this position comes parameter "Heading". If you want to show same parameter several times on same page, you need to add parameter ID after definition like: {OpenSkipperParam:Heading:Heading_1}.
    You can also set web server to start automatically. If you go to the View-"Web Server..." and set "Enable Web server" and "Start Web server to last state" to checked, it will be automatically started when application starts.
    Web server also works now with normal user rights for all network. You need to once start web server as "Local host only" uncheked so that application will ask to give rights for normal user to listen all network. Appliction will give these rights, but for one time you need to use administrator rights.
    Multiplier for parameters. In Parameters.N2kParams.xml you can define multiplier, which multiplies parameter received from hook.
    Hook filtering. E.g. NMEA0183 message MWV can contain true or apparent wind speed depending field "Reference, R = Relative, T = True" value. So as definition Parameters.N2kParams.xml file you can add filter "R" relative wind speed parameter and filter "T" for true values.
    Message instance filtering for "Decoded messages..." view.

Some fixes too.

----------------------

Overview of Operation (based on v1.2)

NMEA Messages
Many nautical instruments generate messages in an NMEA 0183 or NMEA 2000 (N2k) format. These messages might give the boat speed or water depth. Open Skipper is designed to process and display the data contained in these messages. Open Skipper can also process AIS messages which give information about other vessels; these messages might be received by your VHF radio or AIS receiver, and then transmitted via an NMEA 0183 or NMEA 2000 connection to a PC. 

Incoming Streams
Open Skipper can receive NMEA 0183, NMEA 2000 (N2k) and AIS messages and decode (some of) them to extract the data in the messages. NMEA 0183 and AIS messages can be received via a COM port or the internet (via UDB or TCP/IP). NMEA 2000 messages can be received using the Actisense NGT1-USB NMEA-to-USB converter or over the internet. We describe each of the message sources as a stream. Open Skipper can also process log files (in various formats) that have been recorded from NMEA instruments. 

Out-going Streams
As well as processing incoming streams, Open Skipper can forward messages (or generate new messages) into outgoing streams. For example, N2k messages might be forwarded to another computer using a TCP/IP connection, or broadcast over a network using UDP. Streams can also be recorded to (and replayed) from log files. 

Decoding Message
Open Skipper provides editors (called ‘explorers’) for displaying and editting the XML definition files used to describe how an N2k, AIS or 0183 message should be decoded. These XML files will, we hope, be used by other developers as a single up-to-date definition of the NMEA messages. The definition files are not yet complete; we welcome more definition details and corrections. 
OpenSkipper has default definition files built in to the executable. You can edit and save these to disk, and then use them as your default definitions. 

Parameters
The user can define ‘Parameters’ such as speed that automatically update their values when the appropriate N2k or 0183 message arrives. A parameter such as 'speed' can be updated by either N2k or 0183 messages. The parameter definitions define the named fields given in the N2k, AIS and 0183 definitions that should be used to update the value for each parameter. 

Data Display
The user can design their own screen displays that are used to graphically display values of parameters. These are built using Visual Studio at ‘design time’ by opening ‘MainForm.cs’. Any standard C# control can be added, with an ‘extender’ being provided to add NMEA properties specifying which Open Skipper parameter should be displayed, and the name of the control’s property that should be used to do this. More sophisticated custom controls can also be built that directly interpret the messages. (Note that work is progressing on allowing screens to be designed and saved for file without requiring Visual Studio.) 

Web Server
Open Skipper has a simple built in Web server. (You may need admin privileges to run this.) This lets you serve up a selection of parameters which get updated in real time. Using an ad-hoc wireless network, you can now view your boat instruments on your WiFi cell phone or tablet. 

More Information
There is more technical information on Open Skipper at www.openskipper.com. 


All copyrighted terms, including NMEA, NMEA 018, NMEA 2000, Actisense, and NGT1, are the property of their respective owners. Everything provided in Open Skipper is available in the public domain, and has not been obtained as the result of signing any non-disclosure agreements with Actisense or NMEA.