Cruisers Forum
 


Join CruisersForum Today

Reply
 
Thread Tools Rate Thread Display Modes
Old 26-06-2012, 11:43   #31
Registered User

Join Date: Aug 2010
Posts: 297
Re: Autopilot output device open failed

Downloaded Actisense NMEA reader. Thanks for the tip.

With VSPE I created a new virtual port (com 1) to monitor com 6 at the same time as Opencpn is using it for the AP function. Activated the route point, but no data on the virtual port in Actisense NMEA Reader. Error: Time Out.

Was the approach correct?

George
__________________

__________________
George64 is offline   Reply With Quote
Old 26-06-2012, 11:56   #32
Registered User

Join Date: Aug 2010
Posts: 297
Re: Autopilot output device open failed

I tried the same approach with com 9, which is the data from the shipmodul, and there I see nmea data in Actisense reader.

George
__________________

__________________
George64 is offline   Reply With Quote
Old 26-06-2012, 12:09   #33
Registered User

Join Date: Jun 2007
Location: SW Florida
Boat: FP Belize, 43' - Dot Dun
Posts: 3,424
Re: Autopilot output device open failed

You apparently have (2) USB-serial devices, correct?

If com9 is from the multiplexer, then OPCN gps port is set to com9, correct?

Set the AP port of OCPN to com9 and jumper it's transmit to the receive of the other USB-serial. Monitor com6 with NMEA Reader.

Set a goto in OCPN.
__________________
DotDun is offline   Reply With Quote
Old 26-06-2012, 12:31   #34
Registered User

Join Date: Aug 2010
Posts: 297
Re: Autopilot output device open failed

@DotDun, done and got output on COM 6 Here is the output:
Quote:
$IIMWV,27.1,T,1.5,N,A*0B
$GPVTG,,T,64,M,0.0,N,0.0,K*4C
$IIMWV,27.1,R,1.4,N,A*0C
$GPZDA,182303,26,06,2012,-2,0*6F
$HCHDG,211.00,,,,*70
$IIRMB,A,,,,,,,,,,,,V,A*0B
$IIDBT,11.9,f,3.6,M,2.0,F*2F
$GPRMC,182303,A,5047.5088,N,00019.5442,E,0.0,62,26 0612,2,W*54
$HCHDG,211.00,,,,*70
$IIVLW,1786.518,N,534.531,N*7C
$IIVHW,210.0,T,212.0,M,0.0,N,0.0,K*57
$IIZTG,,,*65
$HCHDG,212.00,,,,*73
$IIHDG,211.0,0,E,2.0,W*45
$HCHDG,211.00,,,,*70
$IIAPB,A,A,,,N,,,,M,,,M,,,A*70
$GPGLL,5047.5088,N,00019.5442,E,182304,A*2A
$IIDPT,3.6,-1.4,100.0*6E
$HCHDG,210.00,,,,*71
$GPGGA,182304,5047.5088,N,00019.5442,E,1,8,0.9,2,M ,47,M,,*72
$IIRMC,182303,A,5047.509,N,00019.544,E,0.0,107.0,, 2.0,W,A*16
$GPVTG,,T,77,M,0.0,N,0.0,K*4E
$HCHDG,210.00,,,,*71
$GPZDA,182304,26,06,2012,-2,0*68
$IIMTW,18.6,C*1C
$IIMWV,27.1,T,1.5,N,A*0B
$HCHDG,212.00,,,,*73
$IIMWV,27.0,R,1.2,N,A*0B
$GPRMC,182304,A,5047.5088,N,00019.5442,E,0.0,75,26 0612,2,W*55
$IIRMB,A,,,,,,,,,,,,V,A*0B
$HCHDG,211.00,,,,*70
$IIDBT,11.9,f,3.6,M,2.0,F*2F
$GPGLL,5047.5088,N,00019.5443,E,182305,A*2A
$HCHDG,211.00,,,,*70
$GPGGA,182305,5047.5088,N,00019.5443,E,1,8,0.9,2,M ,47,M,,*72
$GPVTG,,T,119,M,0.0,N,0.1,K*76
$HCHDG,212.00,,,,*73
$GPZDA,182305,26,06,2012,-2,0*69
$HCHDG,211.00,,,,*70
$GPRMC,182305,A,5047.5088,N,00019.5443,E,0.0,117,2 60612,2,W*60
I don't see any data from the Goto...

George
__________________
George64 is offline   Reply With Quote
Old 26-06-2012, 12:33   #35
Registered User

Join Date: Jun 2007
Location: SW Florida
Boat: FP Belize, 43' - Dot Dun
Posts: 3,424
Re: Autopilot output device open failed

Quote:
Originally Posted by George64 View Post
@DotDun, done and got output on COM 6 Here is the output:


I don't see any data from the Goto...

George
That's not from OCPN. Set the AP port in OCPN to com9. Physically connect the transmit of com9 to the receive of com6. Monitor com6 with NMEA Reader.
__________________
DotDun is offline   Reply With Quote
Old 26-06-2012, 13:04   #36
Registered User

Join Date: Aug 2010
Posts: 297
Re: Autopilot output device open failed

Quote:
Originally Posted by DotDun View Post
That's not from OCPN. Set the AP port in OCPN to com9. Physically connect the transmit of com9 to the receive of com6. Monitor com6 with NMEA Reader.
I set COM 9 to GPS and the AP. Between the laptop and the Shipmodul mux is a USB cable (no usb to serial), so the only thing I can do as far as I can see, is monitor the output from the mux, the one connected to the AP. That's the out put you saw. In the shipmodul there are no rules set to block data going to the output.

George
__________________
George64 is offline   Reply With Quote
Old 26-06-2012, 13:08   #37
Registered User

Join Date: Aug 2010
Posts: 297
Re: Autopilot output device open failed

In addition, I checked the log file:
Quote:
21:02:34: NMEA Data Source is....Serial:COM9
21:02:34: NMEA AutoPilot Port is....Serial:COM9
21:02:34: OpenPD: 592, new_count = 1 for COM9
21:02:34: NMEA input device open failed: COM9...GetLastError(): 5
Seen this before, and that is quit un-understandable, to me at least. I whish I had a laptop with only serial ports instead of usb....

George
__________________
George64 is offline   Reply With Quote
Old 26-06-2012, 13:27   #38
Registered User

Join Date: Jun 2007
Location: SW Florida
Boat: FP Belize, 43' - Dot Dun
Posts: 3,424
Re: Autopilot output device open failed

I'm simply trying to eliminate potential problems. Get OCPN talking to a 'normal' usb-serial device and monitor it with another 'normal' usb-serial device. Only then can you be sure that OCPN is doing what it is suppose to do, or not.
__________________
DotDun is offline   Reply With Quote
Old 26-06-2012, 15:05   #39
Registered User

Join Date: Aug 2010
Posts: 297
Re: Autopilot output device open failed

I really do appreciate your patience and help DotDun.

Luckily I have aboard an extrap pair of usb2serial and serial connecters. Connected it all together and used port com 10 from my laptop as AP port and port com 6 as input for port 10.... Ran Actisense and saw an ECRMB and a ECRMB To say the least, I'm confused.

At least we know that Opencpn sends out the two sentences.

George
__________________
George64 is offline   Reply With Quote
Old 26-06-2012, 15:25   #40
Registered User

Join Date: Aug 2010
Posts: 297
Re: Autopilot output device open failed

Hmmm, it seemed a one off Retried it with a new route, and no ECRMB or ECRMC.

George
__________________
George64 is offline   Reply With Quote
Old 26-06-2012, 20:25   #41
Registered User

Join Date: Jun 2007
Location: SW Florida
Boat: FP Belize, 43' - Dot Dun
Posts: 3,424
Re: Autopilot output device open failed

This type of behavior might happen if you unplug/plug a usb-serial device while OCPN is using it.

If not, I would begin to question the Windose drivers for your usb-serial devices.
__________________
DotDun is offline   Reply With Quote
Old 27-06-2012, 03:53   #42
Registered User

Join Date: Aug 2010
Posts: 297
Re: Autopilot output device open failed

Thanks DotDun. I will make the setup with usb2serial connections and see how it goes the coming days.

The fact that opening the same com port, when connected with an usb cable, leads to an error as shown in the logfile, is that something to raise as a 'bug'?

George
__________________
George64 is offline   Reply With Quote
Old 27-06-2012, 05:48   #43
Registered User

Join Date: Jun 2007
Location: SW Florida
Boat: FP Belize, 43' - Dot Dun
Posts: 3,424
Re: Autopilot output device open failed

Quote:
Originally Posted by George64 View Post
The fact that opening the same com port, when connected with an usb cable, leads to an error as shown in the logfile, is that something to raise as a 'bug'?

George
Is it a bug with OCPN or the driver for the multiplexer?

It would be interesting to try with an older version of OCPN.
__________________
DotDun is offline   Reply With Quote
Old 27-06-2012, 06:17   #44
Registered User

Join Date: Aug 2010
Posts: 297
Re: Autopilot output device open failed

Quote:
Originally Posted by DotDun View Post
Is it a bug with OCPN or the driver for the multiplexer?

It would be interesting to try with an older version of OCPN.
I do have version 2.5.0 on the same laptop. Here is the output of the log file:
Quote:
14:12:43: 2012-06-27
14:12:43: -------Starting opencpn-------
14:12:43: Version 2.5.0 Build 2011-07-26
14:12:43: MemoryStatus: mem_total: 8139 mb, mem_initial: 10 mb
14:12:43: SData_Locn is C:\Program Files (x86)\OpenCPN\
14:12:43: Using existing Config_File: C:\ProgramData\opencpn\opencpn.ini
14:12:43: Setting Viewpoint Lat/Lon 50.7705, 0.3258
14:12:43: Setting Ownship Lat/Lon 50.7918, 0.3258
14:12:49: System default Language: nl_NL
14:12:49: Opencpn language set to: nl_NL
14:12:50: Using s57data in C:\Program Files (x86)\OpenCPN\s57data
14:12:50: Using Tide/Current data from: C:\Program Files (x86)\OpenCPN\tcdata\
14:12:50: Setting Viewpoint Lat/Lon 50.7705, 0.3258
14:12:50: Setting Ownship Lat/Lon 50.7918, 0.3258
14:12:50: NMEA Data Source is....Serial:COM9
14:12:50: AIS Data Source is....None
14:12:50: Using WVSChart datafile: C:\Program Files (x86)\OpenCPN\wvsdata\wvs43.dat
14:12:50: OpenPD: 356, new_count = 1 for COM9
14:12:50: NMEA AutoPilot Port is....Serial:COM9
14:12:50: Re-OpenPD: 356, new_count = 2 for COM9
14:12:50: PlugInManager searching for PlugIns in location C:\Program Files (x86)\OpenCPN\plugins
14:12:50: PlugInManager: Loading PlugIn: C:\Program Files (x86)\OpenCPN\plugins/dashboard_pi.dll
14:12:50: PlugInManager: Loading PlugIn: C:\Program Files (x86)\OpenCPN\plugins/findit_pi.dll
14:12:50: Error: Failed to load shared library 'C:\Program Files (x86)\OpenCPN\plugins/findit_pi.dll' (error 127: kan opgegeven procedure niet vinden.)
14:12:50: PlugInManager: Cannot load library: C:\Program Files (x86)\OpenCPN\plugins/findit_pi.dll
14:12:50: PlugInManager: Loading PlugIn: C:\Program Files (x86)\OpenCPN\plugins/gecomapi_win32_pi15_v08_pi.dll
14:12:50: PlugInManager: Loading PlugIn: C:\Program Files (x86)\OpenCPN\plugins/grib_pi.dll
14:12:50: PlugInManager: Loading PlugIn: C:\Program Files (x86)\OpenCPN\plugins/logbookkonni_pi.dll
14:12:50: PlugInManager: Loading PlugIn: C:\Program Files (x86)\OpenCPN\plugins/vdr_pi.dll
14:12:50: PlugInManager: Loading PlugIn: C:\Program Files (x86)\OpenCPN\plugins/wmm_win32_pi15_v03_pi.dll
14:12:50: Warning: WMM model data file C:\Program Files (x86)\OpenCPN/plugins/WMM.COF can't be loaded, using the bundled data.
14:12:51: ChartDB Cache policy: Application target is 4069 MBytes
14:12:51: Loading chart db version: V016
14:12:51: Chartdb: Chart directory list follows
14:12:51: Chart directory #0: C:\Users\Gregor\Documents\CM93
14:12:51: GPS Watchdog Timeout is: 6 sec.
14:12:51: Initializing Chart C:\Users\Gregor\Documents\CM93\00300000\A\00300000 .A
14:12:51: CM93Composite Chart Root is C:\Users\Gregor\Documents\CM93\
14:12:51: Loaded CM93 Dictionary from C:\Users\Gregor\Documents\CM93\
14:12:51: Loading CM93 cell C:\Users\Gregor\Documents\CM93\03900000/E/04210000.E
14:12:51: Loading CM93 cell C:\Users\Gregor\Documents\CM93\03900000/E/04210001.E
14:12:51: Loading CM93 cell C:\Users\Gregor\Documents\CM93\03900000/E/04220000.E
14:12:51: Loading CM93 cell C:\Users\Gregor\Documents\CM93\03900000/E/04220001.E
14:12:51: Loading CM93 cell C:\Users\Gregor\Documents\CM93\03900000/D/04200000.D
14:13:44: LOGBOOK: 2012-06-27 12:13:44 UTC GPS Lat 50.79182 Lon 0.32582 COG 101.00000 SOG 0.00
14:14:13: PlugInManager: Deactivating PlugIn: C:\Program Files (x86)\OpenCPN\plugins/dashboard_pi.dll
14:14:13: PlugInManager: Deactivating PlugIn: C:\Program Files (x86)\OpenCPN\plugins/gecomapi_win32_pi15_v08_pi.dll
14:14:13: PlugInManager: Deactivating PlugIn: C:\Program Files (x86)\OpenCPN\plugins/grib_pi.dll
14:14:13: PlugInManager: Deactivating PlugIn: C:\Program Files (x86)\OpenCPN\plugins/logbookkonni_pi.dll
14:14:13: PlugInManager: Deactivating PlugIn: C:\Program Files (x86)\OpenCPN\plugins/vdr_pi.dll
14:14:13: PlugInManager: Deactivating PlugIn: C:\Program Files (x86)\OpenCPN\plugins/wmm_win32_pi15_v03_pi.dll
14:14:13: opencpn::MyFrame exiting cleanly.
14:14:16: PlugInManager: UnLoading PlugIn: C:\Program Files (x86)\OpenCPN\plugins/dashboard_pi.dll
14:14:16: PlugInManager: UnLoading PlugIn: C:\Program Files (x86)\OpenCPN\plugins/gecomapi_win32_pi15_v08_pi.dll
14:14:16: PlugInManager: UnLoading PlugIn: C:\Program Files (x86)\OpenCPN\plugins/grib_pi.dll
14:14:16: PlugInManager: UnLoading PlugIn: C:\Program Files (x86)\OpenCPN\plugins/logbookkonni_pi.dll
14:14:16: PlugInManager: UnLoading PlugIn: C:\Program Files (x86)\OpenCPN\plugins/vdr_pi.dll
14:14:16: PlugInManager: UnLoading PlugIn: C:\Program Files (x86)\OpenCPN\plugins/wmm_win32_pi15_v03_pi.dll
14:14:16: Stopping Secondary Thread
14:14:16: ClosePD: 356, count_after_close = 1 for COM9
14:14:17: Stopped in 1 sec.
14:14:17: ClosePD: 356, count_after_close = 0 for COM9
14:14:17: and so CloseComPortPhysical
14:14:17: LOGBOOK: 2012-06-27 12:14:17 UTC OFF: Lat 50.79182 Lon 0.32582 COG 101.00000 SOG 0.00
14:14:17: opencpn::MyApp exiting cleanly...
No error as you can when opening the same port. Does this help? If you want me to run another test, please let me know.

George
__________________
George64 is offline   Reply With Quote
Old 27-06-2012, 06:25   #45
Registered User

Join Date: Jun 2007
Location: SW Florida
Boat: FP Belize, 43' - Dot Dun
Posts: 3,424
Re: Autopilot output device open failed

Quote:
Originally Posted by George64 View Post
I do have version 2.5.0 on the same laptop. Here is the output of the log file:


No error as you can when opening the same port. Does this help? If you want me to run another test, please let me know.

George
Any OCPN developers care to comment?
__________________

__________________
DotDun is offline   Reply With Quote
Reply

Tags
autopilot

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off




Copyright 2002- Social Knowledge, LLC All Rights Reserved.

All times are GMT -7. The time now is 03:57.


Google+
Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.
Social Knowledge Networks
Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.

ShowCase vBulletin Plugins by Drive Thru Online, Inc.