By:
On:

veKonvert connects to the SmartShunt via the veDirect interface.  All calibration of the boat’s battery capacity etc is done via the Bluetooth interface integrated into the SmartShunt.  Download the Victron app and follow the set up instructions included with the SmartShunt.  There’s no calibration required on the veKonvert interfaceRead More →

By:
On:

veKonvert is compatible with the following Victron products… BMV -700 BMV -702 BMV -700H BMV-712 Smart BMV-710H Smart BMV-712 Smart Rev2 SmartShunt 500A/50mV SmartShunt 1000A/50mV SmartShunt 2000A/50mV All MPPT Charge Controllers NOTE – veKonvert is not compatible with Victron Chargers and Inverters. It should also not be plugged in to the VE.Direct interfaces of any Victron “Consumers” such as Multiplus, Quattro, Cerbo, etc.Read More →

By:
On:

When you scan for wireless networks on whatever mobile device you are using, can you see the 4GXtream wireless network? If you can, please connect to it using the default wireless password = 4GXtream Once you are wirelessly connected to the 4GXtream, then please open your web browser in a Private/Incognito window (important so that it does a fresh load of the 4GXtream web interface) and then try to go to http://192.168.1.1 or http://4gxtream Whichever, address you use, it is very important that you include the http:// as this tells your browser that you want to go to a specific address and not do aRead More →

By:
On:

In the fast moving world of wireless technology, our WL510 is quite old now and you might get the message: “err_ssl_version_or_cipher_mismatch” when trying to upload the configuration file. This is due to the age of the firmware as V5.5.8 used TLS V1.0 which is no longer supported in most modern browsers. The way to get round this, is to use an older computer with an older browser on it. Once you have an older computer connected and can bring up the WL510 web interface, update the firmware to the latest version and the “err_ssl_version_or_cipher_mismatch” issue will be gone. The latest version of the WL510 firmwareRead More →

By:
On:

You need to setup a data link between the two LANLinks, as this will not happen automatically. We recommend using a TCP connection between the LANLinks, this is much more reliable and a proper socket connection is created that you can see in the LANLink Status page, where as UDP is just a broadcast with no status or packet checking. Setup the LANLink, connected to whichever device is outputting NMEA 0183, as a TCP server with a unique fixed IP address outside of the router’s DHCP range. Then set the other LANLink to be a TCP Client also with a unique fixed IP address outsideRead More →

By:
On:

Things have moved on in the iPhone world since 2012 and a number of security updates and changes in the way this wireless data is handled have made some of our older wireless products incompatible without getting an update. You can either send your WLN10HS back to us for an update which is 1hr labour £45 + VAT plus postage or we can offer you a special 30% discount price on our latest WLN10SM – https://digitalyacht.co.uk/product/wln10sm/ Contact us at sales@digitalyacht.co.uk for a 30% discount code, including your proof of purchase and return the WLN10HS to us by following this FAQ: https://support.digitalyacht.co.uk/question/returning-a-product-to-our-uk-office-for-service/Read More →

By:
On:

Hi Sergio, Although the approach you are taking with DDNS and Port Forwarding would work well on a conventional land based network, that is connected to the internet via a Cable/ADSL router, there are several reasons why they may not work on a mobile network: NAT (Network Address Translation): Mobile networks, especially those using IPv4, typically employ NAT to conserve IP addresses. NAT allows multiple devices to share a single public IP address. When you connect a device to a mobile network, it is assigned a private IP address that is not directly accessible from the internet. This makes it challenging for DDNS and portRead More →

By:
On:

All Class B and Class B+ AIS transponders can transmit the True Heading of the vessel as part of the dynamic data they transmit to other vessels; MMSI Number, Position, COG, SOG, etc. If received most charting systems will plot the AIS target with both the COG and True Heading vector displayed, useful when the vessel is stationary and COG becomes unstable/inaccurate. Our AIT2500 and AIT5000 units can receive the True Heading (HDT or THS sentences) data via their Low Speed NMEA 0183 Input (Yellow+ and Green- wires) or via PGN#127250 Vessel Heading on NMEA 2000. However, not all NMEA 2000 systems will transmit TrueRead More →

By:
On:

Hi Kasper, If I understand correctly, you have 21 devices on the network and when you go to the Device List page of NAVDoctor they are all shown but when you go to the Test Report page, only a limited number are shown – is this correct? The device list in both pages should be the same, assuming all of the devices are still present on the network. Please confirm if I have understood the problem correctly, as I may have to involve one of our development engineers to investigate deeper. Best regards DY Support TeamRead More →