Vesper Marine Configuration and Status (vmAIS)

What works

 As for WINE 1.6

Connecting with the AIS Transponder via WiFi, most software functions work, including configuring Vessel details, viewing WiFi router details, viewing Satellite numbers and signal strength, viewing NMEA message stream, viewing Serial data stream.

Update 29 March 2014: Using the workaround suggested in Bug 34497, I can now connect with the Transponder via the Serial-USB cable as well.

What does not

Initially, connecting with the AIS Transponder via the COM port (using a supplied USB cable that emulates a Serial port) would not work as the software would not find any COM ports. However, after adding an explicit link to the COM port:

ln -s /dev/ttyUSB0 ~/.wine/dosdevices/com1

and then adding the following registry entries:

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\SERIAL\COM1\COM1]
"ClassGUID"="{4D36E978-E325-11CE-BFC1-08002BE10318}"
"FriendlyName"="Serial Port (COM1)"
"PortName"="COM1"

as detailed in  Bug 34497, the software utility finds the COM port and uses it to communicate properly with the AIS Transponder.

Workarounds

What was not tested

As for WINE 1.6

Firmware update.

Hardware tested

Graphics:

• GPU:
• Driver:

Additional Comments

Installed OK under Wine 1.6. For this test, I upgraded to Wine 1.7 so installation specifically not tested.

Bug 34497 looks suspiciously like it might be the cause of my problem however I can't test this until I am next at my boat (where the AIS unit is installed). I hope to do this on the coming weekend (in 48 hours or so).

Update 29 March 2014.  I can confirm that the workaround suggested in Bug 34497 fixes my problem - after updating the Windows Registry, the Vesper SW finds the com port and communicates via it with the AIS Transponder.

When I plug in the USB cable from the Vesper AIS unit, it is recognised by my computer (from Syslog):

and later allocated to device ttyUSB0:

I subsequently made this accessible to WINE via a symlink: