Ernie

Thanks for noticing! 5 years of great information, great questions and great support from Nick.

I set this up on a whim after chatting with Nick and noting his reluctance to deal with spammers, hackers and trolls, but acknowledging the need for a source of wisdom on the tool. 
Expedition is a complex piece of software and expertise in it is widely distributed around the globe.  By setting up the forum we created an opportunity to ask questions, suggest solutions and help each other. 
Nick's continuing presence and daily responses means that we get great support without deluging him with email.  

While I often wish the forum had more features, better search and admin controls, I'm limited by the boardhost platform.  But I think it fulfills its purpose well.  

I get multiple attempted registrations by trolls and spammers daily but the email verification mechanism keeps them at bay for the most part. 

Thanks to Ernie, Nick, Campbell, unplugged, sheldon.haynie, us7070, DuncanR, ZeeZee and others for your regular posts.  I note that Nick alone has posted 1656 times!

Fergal (Admin)

Not a question, but just wanted to share some information in case it was of interest to anyone.
I use a Shipmodul Miniplex (3wiN2K) to bridge between NMEA 0183 devices and NMEA 2000. I also use its Wifi capability to connect to Expedition (running on a Toughened IP67 tablet)

I have a B&G GPS Antenna and Compass which can also send Heel and Pitch info over NMEA 2000.  But the heel info wasn't showing up in my Expedition screens.  It should be mapped from an NMEA 2000 PGN (Attitude) to an NMEA 0183 XDR message, but that just was not happening.

I dropped the company an email and they kindly provided me with new beta software version (v2.7.0)  This provides the correct mapping to the XDR statement.  I haven't tried it out yet, hoping to get to it tomorrow.  But great service from a great company with a really powerful and configurable product.
 

Olli

I've played around with this issue in the past and it seems to be an ongoing challenge.  Each successive version of Windows locks the system down further and further and in general an application under Windows 10 is not expected to change the systemTime.  The application would need Administrator rights.

More specifically it needs SE_SYSTEMTIME_NAME privilege.  You can read more about it here.  
https://docs.microsoft.com/en-us/windows/desktop/api/sysinfoapi/nf-sysinfoapi-setsystemtime

The calling process must have the SE_SYSTEMTIME_NAME privilege. This privilege is disabled by default. TheSetSystemTime function enables the SE_SYSTEMTIME_NAME privilege before changing the system time and disables the privilege before returning. For more information, see Running with Special Privileges=16px.

I'd love if Nick could find a way to implement it reliably but I think it is simply too dependent on the Windows configuration.  If anyone has had any success with this on a recent version of Windows then maybe they could share with the group.
 

Schumaam

Yes, you can use a demo version of Expedition to try out much of the functionality without connecting it to your boat system.  Many of us do 'offline' navigation activities in the comfort of our own homes.  Expedition has a simulation mode where you can set location, wind speed and direction as well as marks and courses.  This is a good way to get to know the product and to understand much of the functionality.  You can set start lines and practice start sequences also.  As Nick mentioned above you cannot connect to a data source and cannot run optimizations, but most of the rest of the  functionality is there.  

10.7.25
Update for Diverse HLA,
Update for B&G H2000 configuration,
Various performance, interface and reliability updates.

10.7.24
Fix for editing basic sail chart.

10.7.23
Yacht Devices NMEA 2000 USB Gateway

10.7.22
NOC Proudman 1.8km UK tidal model,
Updated Actisense for faster NMEA 2000,
Fix for saving tests,
Fix for damping some channels.