Expedition Navigation Software 
1 of 1- JLmarine100
- Member
Offline - Registered: 12/16/2019
- Posts: 1
H5000 Ethernet connection to Expedition, setting?
Hi all,
I can connect expedition to the H5000 using a NGT-1 USB to NMEA2000 adapter with no problem. I'd like to eliminate the adapter and connect via Ethernet. When I try this, expedition does not receive any data from the H5000.
I assume the the IP field in the Expedition setup should be set to the IP of the 5000, correct? What should the Port be set to?
Should I select H5000 or Hlink?
Any settings need to be changed in the 5000?
TIA,
John
- Nick
- Moderator
Offline
- Registered: 9/16/2015
- Posts: 2,964
Re: H5000 Ethernet connection to Expedition, setting?
The default connection settings for the H5000 Websocket are 192.168.0.2:2053The H5 will assume 192.168.0.2 if no other DHCP server present after power up. If there is DHCP on network then it will acquire address from that. The IP address of the H5 CPU is available from a GFD If it is a fixed installation, it is worth thinking about retaining the Actisense NGT-1. You will then also get AIS data if you have it and it is better for GPS data. Obviously you need to tell Exp not to use wind data from the NGT-1 and not to use GPS data from the H5000 websocket.
- pivata
- Expert
Offline
- From: Sydney Australia
- Registered: 3/18/2016
- Posts: 10
Re: H5000 Ethernet connection to Expedition, setting?
Nick
What's the advantage of using the NGT-1 for gps data instead of the websocket? And what's the disadavantage of using the NGT-1 for wind data, especially if Expedition is used to calculate TWD, TWS etc instead of repeating the H5000 values?
If you rest you rust
- Nick
- Moderator
Offline
- Registered: 9/16/2015
- Posts: 2,964
Re: H5000 Ethernet connection to Expedition, setting?
The main advantage of the NGT-1 for GPS data is that you remove latency associated with the GPS data being forwarded by the H5000. You also get more data, especially if the H5000 fails for some reason.
If you have an AIS in the system, you also get that data.
I can't imagine a reasonable scenario where you would get Exp to do the calibration rather than the H5000 though.
- us7070
- Expert
Offline
- Registered: 12/06/2017
- Posts: 260
Re: H5000 Ethernet connection to Expedition, setting?
are there any disadvantages associated with changing from getting all the H5000 data from a websocket connection to getting all the H5000 data from an NGT-1?
- Nick
- Moderator
Offline
- Registered: 9/16/2015
- Posts: 2,964
Re: H5000 Ethernet connection to Expedition, setting?
You won't be able to get any B&G specific data, eg load cells.
You also won't be able to send custom data back.
- us7070
- Expert
Offline
- Registered: 12/06/2017
- Posts: 260
Re: H5000 Ethernet connection to Expedition, setting?
Nick wrote:
You won't be able to get any B&G specific data, eg load cells.
You also won't be able to send custom data back.
so, it would be better to get AIS and GPS over the NGT-1, and the H5000 over the websocket - right?
what about the 9 axis compass?
Last edited by us7070 (1/24/2020 12:09 pm)
- Nick
- Moderator
Offline
- Registered: 9/16/2015
- Posts: 2,964
Re: H5000 Ethernet connection to Expedition, setting?
Yes, I normally recommend GPS over NMEA 2000 for latency and redundancy reasons.
The H5 doesn't send AIS data, so AIS over NMEA 2000 too.
I hadn't thought about the compass. Although, there isn't a way to not get it from H5000 at present.