3 Views
top of page
Uncategorised/Other
Public·5 members
Advantage of Deckman
Hello,
from time to time I see raceing yachts using Deckman as navigation software.
Is ther anything Deckman can do what Expedition or Adrena can't do? (Or at least Deckman is way better in?)
Since Deckman never get's any updates und the user intreface is kind of cumbersome, im curious.
Thanks!
47 Views
New to expedition-software update
Hi - I need to update my expedition software will I loose all the settings and boat data? Thanks
48 Views
How to filter unwanted data from an H5000cpu?
Hello, for a long time now I am struggling to filter out data coming out of the cpu from a device that does not exist on my boat, yet it corrupts my logs. I have contacted Navico about it thru different channels, but it is low on the list, or not interresting enough. I don't know. The situation is as follows: I have a WS310 windsensor, wired directly into a nmea0183 socket on the cpu. (The MHU socket is nót in use). The ws310 is selected as 'measured source' and works fine otherwise. This does not keep the cpu from sending out standard values . (Normaly this is awa 180degr, aws 0.4kn. I gave the awa an offset of 180, so it reads 0.0 now.) Expedition is connected to the cpu thru the lan network.
The AIS comes in from the ZEUS3 which is set as a wificlient in same…
98 Views
Campbell Field
Apr 24
Expedition will display any valid data it receives. So, in the case of having two connections, one websocket to H5000 and one via Nmea2000 or 0183 for AIS, if wind data is streaming in from more than one source then Expedition will display the most recent data from all sources.
The fix is to deselect all unwanted sentences from the respective instrument connection input (eg the MWA for 0183 or the wind PGN in n2k). Also a good idea to deselect all sentences except VDM etc. Expedition will then ignore this data.
This wind situation is not unique, having seen it on a number boats with the ws310 wind sensor. Since the standard MHU device is still on the network and sending a PGN with null data (usually 180deg and 0.4kt) it is being picked up by other devices.
This behaviour is only recently being noticed as previously the MHU device was in use and the user would hardly notice that there were two wind inputs to Expedition unless there was for example a very different damping value on the variables or some device latency.
It is also common to see GPS data being input from two sources (instruments and AIS) resulting in a 'noisy' position with the boat jumping around on the chart, the further away the two antenna, the more noticeable. Hence the check box 'use GPS' on each port interface.
It is also important to remember that this situation does not affect the instruments or pilot behaviour in any way, as your H5000 system will always use the source selected within the system, otherwise you would also see the AWA/AWS on a display jumping in the same manner.
About
Welcome to the group! Connect with other members, get updates and share media.
bottom of page
A short answer to "Is there anything Deckman can do what Expedition or Adrena can't do? (Or at least Deckman is way better in?)":
No. Except control a WTP. Even then, most will use Exp for navigation and use the Exp2Dwf app to transfer data between Exp and Dfw.
Apart from this, there is a very long list of features that Dfw cannot do.