PGN127250 / Raymarine EV-1 / Vesper XB-8000 AIS

[SVJOCO]

Hi guys,

I have a problem where I know the EV-1 is outputting PGN 127250 on the network, but the Vesper AIS “WatchMate” will not show the heading info in “My Instruments” view. Ideas?

Thanks,

Jeff

[AllenRbrts]

Have you tried looking at the raw stream in the watchmate app? You can also upload the stream as well to look at it with a text editor.

[SVJOCO]

The raw stream feed appears to be only 0183 data, so doesn’t show PGN.

[AllenRbrts]

I have the same setup as you do but with the Cortex rather than the 8000. I can monitor the nema output with either OpenCPN or with the terminal emulator putty. In both cases, I see heading messages with 183 format $AIHDG,82.4,,,9.1,W*0E

One suggestion is to connect to your 8000 with the vmAIS tool (download from Vesper) and click on the NEMA2000 tab. That tab allows you select which NEMA 2000 PGNs you want the Vesper to receive. Perhaps 12720 sentence is not enabled.

[moseriw]

Originally Posted by SVJOCO

The raw stream feed appears to be only 0183 data, so doesn’t show PGN.

Vesper XB-8000 is on NMEA 2000 so you should upgrade your EV-1 with a converter from NMEA 0183 to NMEA 2000. Usually it is easy with an Raymarine "multiple socket" but it is best to upgrade the whole bus to NMEA 2000.

[AllenRbrts]

Originally Posted by moseriw

Vesper XB-8000 is on NMEA 2000 so you should upgrade your EV-1 with a converter from NMEA 0183 to NMEA 2000. Usually it is easy with an Raymarine "multiple socket" but it is best to upgrade the whole bus to NMEA 2000.

I’m not a NMEA expert but the EV1 manual says it puts out NMEA 2000 PGNs and the Vesper 8000 manual says it receives them and translates them to 0183 when it broadcast last them on WIFi. So if the OP is looking for NMEA 2000 PGNs they will not be seen coming from the vesper, only translated to 0183 heading sentences.

[wholybee]

The vesper 8000 has a very limited set of PGNs that it can translate to 0183(wifi is 0183). There is a list on vespers support page(sorry i don't have a link) but you might need a 3rd party converter that works with a more complete set of PGNs/0183 sentences.

I have used both actisense and yacht devices converters to wifi. Both work with EV1 heading information. Currently using yacht devices, which also calculates true wind is not present, and translates some proprietary Raymarine autopilot pgns.

I do this with vesper AIS, do to limitations i ran into with the vesper conversation.

[smac999]

'im pretty sure he is looking at the vesper app.. he is not converting anything. I'd be surprised if the vesper app could not show nmea 2000 heading data.

[stevead]

This should not be rocket surgery. There are only three elements.

1. Raymarine EV1

a. Does the EV1 support PGN 127250 (Heading) ? Well duh, it's a compass so obviously it does.

b. Is it connected ? I presume you have connected it to your Seatalkng network correctly.

c. Is it working and transmitting heading data ? I presume you have a Raymarine Autopilot and Multifunction display and they are receiving heading data.

2. Vesper XB8000 transponder.

a. Does the XB8000 convert NMEA 2000 PGN 127250 message to NMEA 0183 $--HDG sentence. According to their specs, yes it does.

b. Is the XB8000 correctly connected to the Seatalkng network ? I presume you have a Seatlkng to NMEA 2000 Device Net adapter cable for connecting to the XB8000. Once connected, I guess it should show up on the list of devices on the Raymarine MFD, and presumably if you are seeing AIS targets on your Raymarine MFD, then it most certainly is connected.

c. Have you enabled the PGN 127250 conversion. (I don't own a Vesper device, but I presume there may be some configuration required)

d. Is its Wifi connection configured correctly ? (Again, I presume there is some configuration required, or the default settings are sufficient) One way to test this, independent of the WatchMate app is to try connecting to the XB8000 with another app. If you have a PC, try OpenCPN, instructions are available here

3. Vesper Watchmate App
a. Is it configured correctly ? I presume you can connect to the XB8000 and can get/set the XB8000 configuration information, observe AIS targets and receive position, cog, sog, depth, wind data.

If none of the above steps are working, then they need to be rectified.

There is also the obvious answer which is to contact Vesper for advice, from all accounts they are very responsive.

Just for the hell of it, I installed the WatchMate App on my phone, connected it to the hotel Wifi network and to my laptop's IP address and "fed" it some simulated data from a script running on my laptop which it displayed correctly. So in that regard, the WatchMate App could be used as a generic instrument display over Wifi using TCP port 39150. (Why they didn't use the standard port 10110 beats me, they're a funny lot those New Zealanders.)

PS D:\code\powershell> ./send-stuff.ps1
$IIMWV,130.0,R,11.4,N,A*0B
$SDDPT,3.0,-0.3,100.0*79
$SDVHW,,T,,M,5.7,N,10.4,K*75
$HCHDG,60.0,10.0,E,0.0,E*45
$GPGGA,223015.00,3811.00,S,14430.00,E,1,10,0.98,1113.0,M,-21.3,M,,*50
$GPGLL,3811.00,S,14430.00,E,223015.00,A,A*7A
$GPRMC,223015,A,3811.00,S,14430.00,E,5.5,70.0,171221,10.0,E,A*08
!AIVDM,1,1,,B,H7Ohlw0mJ0@Di0PTqE>22222220,2*12
!AIVDM,1,1,,B,H7Ohlw4pPPPPPPPF;Fmlip0p:228,0*13
!AIVDM,1,1,,B,C7Ohlw00F2U=jBrRmrln?we4Je08:HP@BLbW11111110L0L5110`,0*57

AIS wasn't displayed, as I guess it is transmitted separately over a different port, and that the bearing, CPA, TCPA calculations are performed in the XB8000 and not in the app. FYI, it uses HTTP over TCP port 39151, and in addition to AIS I presume this is how the XB8000 configuration information is retrieved. For fun, point your browser to https://192.168.15.1:39151 (assuming you are using the default IP address for the XB8000) This is what the Watchmate App sends

Port 39151
Connected
GET /v3/openChannel HTTP/1.1
Connection: Close
User-Agent: Dalvik/2.1.0 (Linux; U; Android 5.0.1; GT-I9507 Build/LRX22C)
Host: 192.168.43.84:39151
Accept-Encoding: gzip