OpenCPN not recognising Virtual COM port

[dansken]

Dave,
I am sorry I can not be of much help there. The previous version I used was the 3.2.2 - My boat (including the Shipmodul) is sitting on the hard 2500 km from where I currently work, and I haven't had the option of trying out the intermediate Beta versions.

One observation: The Electronics (GPS, shipmodul etc) needed to be on before opening OpenCpn - if it was done the other way araound OCPN wouldn't pick up the signal (it is not a problem - but maybe it might help you in understanding "how it works"). Once OCPN has the signal, the PC can go in and out of hibernation and still hold the signal.

Thanks again

[rgleason]

Perhaps the issue has to do with Bluetooth Handshaking which goes something like this?

Note: This procedure will not work if the AIRcable devices have been configured before using one of the automatic connection mode "Service-Slave" or "Service-Master". Please refer to the Command Line Interface to reset the AIRcable modules (^A Z).
See section on "Hardware Handshake" below.

See the discussion under "Hardware Handshake" on this page:
https://www.aircable.net/support/art...ng-process.php

Also Stackflow "Bluetooth pairing without user confirmation"
android - Bluetooth pairing without user confirmation - Stack Overflow
which might help.

Something creative from Apple?
http://www.macrumors.com/2013/11/07/...h-speculation/

[CarCode]

You do not need a long way round and establish first a virtual com port for Bluetooth as it works now in OpenCPN. You can use directly a Bluetooth stack by its driver classes in Linux, Android or Apple. For Windows however you will need a library like Wireless Communication Library - Bluetooth, WiFi, IrDA support for your applications to do this.

Gerhard