Cruisers Forum
 


Join CruisersForum Today

Reply
 
Thread Tools Rate Thread Display Modes
Old 24-04-2013, 06:49   #1
Marine Service Provider
 
LifePart2's Avatar

Join Date: Sep 2010
Location: ex Canada - now on the boat
Boat: Leopard 42 catamaran
Posts: 125
OpenCPN not recognising Virtual COM port

I have a shipmodul 2USB/BT multiplexer which outputs NMEA sentences onto both a USB cable (which enters my computer as COM3) and bluetooth (which is converted on my computer into a virtual COM5).

Both COM3 and COM5 work fine on my laptop (Windows 8) and can be read by various programs EXCEPT OpenCPN.

If I go to the connections tab in OpenCPN and add a new connection, I can add the COM3 with no problems, and it works fine. However, COM5 does not appear in the drop down list, and if I try to add it manually, it receives no NMEA data.

Ultimately, the only way I could get the data into OpenCPN was to download PolarCom and use this to forward COM5 to a TCP port, and then connect OpenCPN to that TCP port.

At least I can now use OpenCPN with the bluetooth connection, but it isn't ideal.

Is this a bug? Something related to Windows 8 64bit?

Both I and a very knowledgeable fried tried every which way we could to try to get COM5 recognised by OpenCPN but it didn't happen.

Suggestions? Ideas?

Thanks,

Noel
__________________

__________________
Noel Swanson

Life is too short to live in ugly places.
LifePart2 is offline   Reply With Quote
Old 24-04-2013, 07:48   #2
Registered User

Join Date: Jan 2007
Location: Minneapolis
Boat: Irwin 37 CC
Posts: 660
Re: OpenCPN not recognising Virtual COM port

"Both COM3 and COM5 work fine on my laptop (Windows 8) and can be read by various programs EXCEPT OpenCPN."

Did you close the other programs before starting OpenCPN?

With the real com port, I've noticed that the GPS must be running before starting OpenCPN, to be reliably seen. Also if the real com port GPS drops out and comes back Opencpn may not see it. I don't have any trouble with USB connected GPS or those that come thru Xport. My system is XP.
__________________

__________________
David Kester
Pegasus IV
wdkester is offline   Reply With Quote
Old 24-04-2013, 08:14   #3
Marine Service Provider
 
bdbcat's Avatar

Join Date: Mar 2008
Posts: 4,883
Re: OpenCPN not recognising Virtual COM port

LifePart2....

Does COM5 appear in the Windows DeviceManager list of ports?

Could we see the relevant part of your OpenCPN log file?

Thanks
Dave
__________________
bdbcat is offline   Reply With Quote
Old 24-04-2013, 11:51   #4
Marine Service Provider
 
LifePart2's Avatar

Join Date: Sep 2010
Location: ex Canada - now on the boat
Boat: Leopard 42 catamaran
Posts: 125
Re: OpenCPN not recognising Virtual COM port

Yes, the COM5 shows in the Device manager as working properly, and, as I said, is accessible to other programs such as Termite and PolarCom.

Don't really know what to show you from the log file. What I have pasted below is the log when I opened OpenCPN with COM5 active, but COM3 ( the usb cable) not plugged in, and PolarCom (and hence port forwarding to TCP) not running.

In the Connections tab, the only port that is listed in the drop down is Garmin-USB. So on this occassion no NMEA input was found.

I then manually typed in COM5, but it still did not find any NMEA stream.

I don't think the log file really says much.

-----------


19:43:26: 2013-04-24
19:43:26: ------- Starting OpenCPN -------
19:43:26: Version 3.2.0 Build 2013-02-26
19:43:26: wxWidgets version: wxWidgets 2.8.12
19:43:26: MemoryStatus: mem_total: 8079 mb, mem_initial: 8 mb
19:43:26: SData_Locn is C:\Program Files (x86)\OpenCPN\
19:43:26: Using existing Config_File: C:\ProgramData\opencpn\opencpn.ini
19:43:26: Styles loading from C:\Program Files (x86)\OpenCPN\uidata\styles.xml
19:43:26: No styles found at: C:\ProgramData\opencpn\
19:43:26: No styles found at: C:\ProgramData\opencpn\.opencpn\
19:43:26: Setting Viewpoint Lat/Lon 36.7715, 14.6604
19:43:26: Setting Ownship Lat/Lon 36.7812, 14.5463
19:43:26: System default Language: en_CA
7:43:26 PM: Opencpn language set to: en_US
7:43:26 PM: ChartSymbols loaded from C:\Program Files (x86)\OpenCPN\s57data\chartsymbols.xml
7:43:27 PM: Using s57data in C:\Program Files (x86)\OpenCPN\s57data
7:43:27 PM: Setting Viewpoint Lat/Lon 36.7715, 14.6604
7:43:27 PM: Setting Ownship Lat/Lon 36.7812, 14.5463
7:43:27 PM: Opening NMEA Datastream Serial:COM3
7:43:27 PM: Opening NMEA Datastream TCP:127.0.0.1:11083
7:43:27 PM: PlugInManager searching for PlugIns in location C:\Program Files (x86)\OpenCPN\plugins
7:43:27 PM: PlugInManager: Loading PlugIn: C:\Program Files (x86)\OpenCPN\plugins/dashboard_pi.dll
7:43:27 PM: C:\Program Files (x86)\OpenCPN\plugins/dashboard_pi.dll Version detected: 106
7:43:28 PM: PlugInManager: Loading PlugIn: C:\Program Files (x86)\OpenCPN\plugins/grib_pi.dll
7:43:28 PM: C:\Program Files (x86)\OpenCPN\plugins/grib_pi.dll Version detected: 107
7:43:28 PM: PlugInManager: Loading PlugIn: C:\Program Files (x86)\OpenCPN\plugins/libaisradar_win32_pi17_v096_pi.dll
7:43:28 PM: C:\Program Files (x86)\OpenCPN\plugins/libaisradar_win32_pi17_v096_pi.dll Version detected: 107
7:43:28 PM: PlugInManager: Loading PlugIn: C:\Program Files (x86)\OpenCPN\plugins/vdr_win32_pi16_v03_pi.dll
7:43:28 PM: C:\Program Files (x86)\OpenCPN\plugins/vdr_win32_pi16_v03_pi.dll Version detected: 106
7:43:28 PM: PlugInManager: Loading PlugIn: C:\Program Files (x86)\OpenCPN\plugins/weatherfax_pi18_v06_win32_pi.dll
7:43:28 PM: C:\Program Files (x86)\OpenCPN\plugins/weatherfax_pi18_v06_win32_pi.dll Version detected: 108
7:43:28 PM: OpenGL-> Renderer String: GeForce GT 630M/PCIe/SSE2
7:43:28 PM: OpenGL-> Framebuffer Objects unavailable
7:43:28 PM: OpenGL-> Using Stencil buffer clipping
7:43:28 PM: OpenGL-> Estimated Max Resident Textures: 98
7:43:28 PM: ChartDB Cache policy: Application target is 1024 MBytes
7:43:28 PM: Loading chart db version: V017
7:43:28 PM: Chartdb: Chart directory list follows
7:43:28 PM: Chart directory #0: C:\Users\Public\Documents\Charts\CM93_Jan_2011
7:43:28 PM: Chart directory #1: C:\Users\Public\Documents\Charts\CM93_May_2010
7:43:28 PM: Chart directory #2: C:\Users\Public\Documents\Charts\CM93ed2_2009
7:43:28 PM: Chart directory #3: C:\Users\Public\Documents\Charts\ENC_ROOT
7:43:28 PM: Chart directory #4: C:\Users\Public\Documents\Charts\Italy.ENC
7:43:28 PM: Chart directory #5: C:\Users\Public\Documents\Charts\Spain.ENC
7:43:28 PM: Chart directory #6: C:\Users\Public\Documents\Charts\Charts.CLB
7:43:28 PM: GPS Watchdog Timeout is: 6 sec.
7:43:28 PM: Initializing Chart C:\Users\Public\Documents\Charts\CM93_Jan_2011\
7:43:28 PM: CM93Composite Chart Root is C:\Users\Public\Documents\Charts\CM93_Jan_2011\\
7:43:28 PM: Loaded CM93 Dictionary from C:\Users\Public\Documents\Charts\CM93_Jan_2011\\
7:43:28 PM: Loading CM93 cell C:\Users\Public\Documents\Charts\CM93_Jan_2011\\03 300000/D/03780042.D
7:43:28 PM: Initializing Chart C:\Users\Public\Documents\Charts\CM93_May_2010\
7:43:28 PM: CM93Composite Chart Root is C:\Users\Public\Documents\Charts\CM93_May_2010\\
7:43:28 PM: Loaded CM93 Dictionary from C:\Users\Public\Documents\Charts\CM93_May_2010\\
7:43:28 PM: Initializing Chart C:\Users\Public\Documents\Charts\CM93ed2_2009\
7:43:28 PM: CM93Composite Chart Root is C:\Users\Public\Documents\Charts\CM93ed2_2009\\
7:43:28 PM: Loaded CM93 Dictionary from C:\Users\Public\Documents\Charts\CM93ed2_2009\\
7:43:33 PM: EnumerateSerialPorts() Found Garmin USB Driver.
7:43:55 PM: Closing NMEA Datastream Serial:COM3
7:43:55 PM: Closing NMEA Datastream TCP:127.0.0.1:11083
7:43:55 PM: Opening NMEA Datastream Serial:COM3
7:43:55 PM: Opening NMEA Datastream TCP:127.0.0.1:11083
7:44:27 PM: LOGBOOK: 2013-04-24 17:44:27 UTC DR Lat 36.78120 Lon 14.54630
7:46:19 PM: EnumerateSerialPorts() Found Garmin USB Driver.
7:47:52 PM: EnumerateSerialPorts() Found Garmin USB Driver.
7:48:15 PM: Closing NMEA Datastream Serial:COM3
7:48:15 PM: Closing NMEA Datastream TCP:127.0.0.1:11083
7:48:15 PM: Opening NMEA Datastream Serial:COM3
7:48:16 PM: Opening NMEA Datastream TCP:127.0.0.1:11083
7:48:16 PM: Opening NMEA Datastream Serial:COM5
7:48:29 PM: Closing NMEA Datastream Serial:COM3
7:48:29 PM: Closing NMEA Datastream TCP:127.0.0.1:11083
7:48:29 PM: Closing NMEA Datastream Serial:COM5
7:48:29 PM: Opening NMEA Datastream Serial:COM3
7:48:29 PM: Opening NMEA Datastream TCP:127.0.0.1:11083
7:48:29 PM: Opening NMEA Datastream Serial:COM5
__________________
Noel Swanson

Life is too short to live in ugly places.
LifePart2 is offline   Reply With Quote
Old 24-04-2013, 11:56   #5
Marine Service Provider
 
LifePart2's Avatar

Join Date: Sep 2010
Location: ex Canada - now on the boat
Boat: Leopard 42 catamaran
Posts: 125
Re: OpenCPN not recognising Virtual COM port

Yes, we closed everything before trying to open in OpenCPN. And rebooted. And tried every other configuration we could think of.

Couldn't run Xport as that is 32 bit only. Which is why we then went to PolarCom.
__________________
Noel Swanson

Life is too short to live in ugly places.
LifePart2 is offline   Reply With Quote
Old 24-04-2013, 12:46   #6
Marine Service Provider
 
bdbcat's Avatar

Join Date: Mar 2008
Posts: 4,883
Re: OpenCPN not recognising Virtual COM port

LifePart2

I see OCPN opening COM5, I suppose in response to your manually entering the field in Connections. It opens without error.

But it receives no data. Hmmm...
I have no BlueTooth hardware here, so I will need to do some research on this. It seems that the paired BT connection does not exactly emulate a standard serial connection, in some subtle way.

I'll see what I can find.

Any other users have this setup?
Thanks
Dave
__________________
bdbcat is offline   Reply With Quote
Old 24-04-2013, 12:56   #7
Marine Service Provider
 
LifePart2's Avatar

Join Date: Sep 2010
Location: ex Canada - now on the boat
Boat: Leopard 42 catamaran
Posts: 125
Re: OpenCPN not recognising Virtual COM port

Correct, it receives no data, but gives no error message. Just the same, in fact, as the opening of COM3 and TCP which genuinely had no data running through them.
__________________
Noel Swanson

Life is too short to live in ugly places.
LifePart2 is offline   Reply With Quote
Old 25-04-2013, 01:44   #8
Marine Service Provider
 
LifePart2's Avatar

Join Date: Sep 2010
Location: ex Canada - now on the boat
Boat: Leopard 42 catamaran
Posts: 125
Re: OpenCPN not recognising Virtual COM port

It seems that Windows 8 labels Bluetooth devices as 'Offline' if they are not currently passing data. Not passing data seems to mean not actually interacting with a program on the computer.

What I am guessing is happening is that OpenCPN looks for online COM ports. Since COM5 is labeled as offline, even though it is presenting data, OpenCPN does not find it. This would be consistent with the fact that COM3 does not show up in the drop down list when the cable is not attached (because, presumably, it is Offline at that time). Once the cable is plugged in, then OpenCPN can find it.

Clearly OpenCPN is checking for available COM ports in a different manner than is PolarCom which does find it, even when it is 'offline' according to Windows 8.

Does that help you developers in any way?
__________________
Noel Swanson

Life is too short to live in ugly places.
LifePart2 is offline   Reply With Quote
Old 01-05-2013, 13:28   #9
Registered User

Join Date: Jun 2009
Posts: 1
Quote:
Originally Posted by LifePart2 View Post
It seems that Windows 8 labels Bluetooth devices as 'Offline' if they are not currently passing data. Not passing data seems to mean not actually interacting with a program on the computer.

What I am guessing is happening is that OpenCPN looks for online COM ports. Since COM5 is labeled as offline, even though it is presenting data, OpenCPN does not find it. This would be consistent with the fact that COM3 does not show up in the drop down list when the cable is not attached (because, presumably, it is Offline at that time). Once the cable is plugged in, then OpenCPN can find it.

Clearly OpenCPN is checking for available COM ports in a different manner than is PolarCom which does find it, even when it is 'offline' according to Windows 8.

Does that help you developers in any way?
same problem using last version (3. 2. 1) and windows 7 sp1. Com 5 is in use, transfer data from my BT using hyperterminal but it is not seen in opencpn.
Best regards
Fernando
__________________
Save Our Souls is offline   Reply With Quote
Old 21-05-2013, 06:13   #10
Registered User

Join Date: Nov 2010
Posts: 62
Images: 2
Re: OpenCPN not recognising Virtual COM port

Similar situation here. Also using Shipmodul bluetooth. Work fine on Polar Navy/Com. Also works fine on other GPS monitoring software. OpenCPN just won't recognise the stream. Win7 32bit.
__________________
ktcanuck is offline   Reply With Quote
Old 24-05-2013, 05:38   #11
Registered User

Join Date: Nov 2010
Posts: 62
Images: 2
Re: OpenCPN not recognising Virtual COM port

Could someone assist me to obtain data that will help resolve this issue?
__________________
ktcanuck is offline   Reply With Quote
Old 24-05-2013, 07:02   #12
Marine Service Provider
 
LifePart2's Avatar

Join Date: Sep 2010
Location: ex Canada - now on the boat
Boat: Leopard 42 catamaran
Posts: 125
Re: OpenCPN not recognising Virtual COM port

Ktcanuck, what data do you need? Not that I know any more than you do, but maybe the programmers can help.
__________________
Noel Swanson

Life is too short to live in ugly places.
LifePart2 is offline   Reply With Quote
Old 24-05-2013, 07:25   #13
Registered User

Join Date: Nov 2010
Posts: 62
Images: 2
Re: OpenCPN not recognising Virtual COM port

Actually I am hoping those that will know how to fault find this issue will tell me what they need so I can go get it.

My chartplotter PC is 32 bit Win7 so I guess for now I will try using Xport.
__________________
ktcanuck is offline   Reply With Quote
Old 24-05-2013, 09:58   #14
Marine Service Provider
 
bdbcat's Avatar

Join Date: Mar 2008
Posts: 4,883
Re: OpenCPN not recognising Virtual COM port

ktcanuck....

OK, I just received in the mail today a BlueTooth GPS receiver, so this bug has popped onto my todo list.

I would appreciate it if you could enter this bug, with supporting detail, on the Flyspray bug tracker. It will get addressed if it is on that list, and might get lost otherwise.

Thanks
Dave
__________________
bdbcat is offline   Reply With Quote
Old 24-05-2013, 14:23   #15
Senior Cruiser

Cruisers Forum Supporter

Join Date: Aug 2009
Location: between the devil and the deep blue sea
Boat: a sailing boat
Posts: 17,314
Re: OpenCPN not recognising Virtual COM port

@bdbcat:

If I forward some NMEA data to a COM that has BT module on it, will this module transmit (as a rule) the data to my other BT capable devices?

I have sent NMEA over TCP / wifi but I would possibly use BT now because of wifi energy consumption issues.

Thank you.

b.
__________________

__________________
barnakiel is offline   Reply With Quote
Reply

Tags
opencpn, paracelle

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 07:39.


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.