Forum Replies Created
-
Posts
-
Hi there!
I see this has also been raised as a ticket on our support system. I will leave it from here and we can continue to assist you via the Zoho ticket instead. You have had contact with our Technical Support Engineer, however I have had some input and gives some tips on this ticket already.
In short, it is possible for us to integrate most, if not all of this together, with NMEA 0183 and NMEA 2000. SeaTalk1 (ST1) is a proprietary messaging format, which sadly we do not work with directly or convert. To get this data, you will either need ST1 to STNG, or ST1 to NMEA 0183 first.
Please feel free to ask us any questions on there, and I’ll be happy to give my input where necessary 🙂
Thank you
Josh
Commercial Engineer
Hi There!
The data available via the W2K-1 is dependent on the format of the data server, which must match that of the application / receival device that it is connected to. If the W2K-1 is being used in NMEA 0183 format, it has the same output as the NGW-1 in terms of conversion capability.
Other formats that are NMEA 2000 will potentially have ‘more’ data available, depending on what you are trying to send. For example, Engine Data would be available via Wi-Fi if using an NMEA 2000 format, but is not if using NMEA 0183 as there is no supported conversion from the NMEA as of yet for Engine Data in 2000 –> 0183 conversions.
Thanks
Josh
Hi there!
Happy to hear that you have the set-up working with HWVSP.
In regards to the data format and configuration, NMEA 0183 will give you the most data at the moment, as some of the formats are not designed to be supported and decoded by NMEA Reader, rather they are designed with applications developed for these formats in mind.
Thank you.
Josh
Hi There!
The W2K-1 will take the lowest source address (highest priority device) at the moment. In future, we may add definable sources for messaging, so a lower priority device can be selected as primary.
Thanks
Josh
Hi there,
Currently NMEA Reader and Toolkit are not configured to receive data via TCP/IP/UDP Comms, however it is on the to do list. Unfortunately integrating IP Comms into the applications is a reasonably complex process requiring a large amount of work.
Whilst it is not directly possible at the moment, there is a way to get your Wireless 0183 data into NMEA Reader via the W2K-1 using a third party application. Using HWVSP3, you can create a VCP on the program which is fed from an IP Address.
Essentially, you set the COM Port number (ensure this does not collide with one that is already existing on the PC from a physical device), set the IP addr it is from (192.168.4.1 for W2K-1 AP), and set the Port number as that of the Port Number for the data server you are trying to receive from.
If you would like instructions on configuring this program to work with the W2K-1 and NMEA Reader, or need any support, please create a ticket on our help desk.
Thanks
Josh!
Please contact Actisense Tech Support for access to the SDK. When contacting us, please provide as much detail about your project as possible, so we understand the use case and purpose, and also which programming languages you are using.
Should you be developing on a different platform to Windows, we can also provide access to our ACCompLib, but this does require an NDA due to it containing some source code. Actisense recommends that you use our demo project and Windows SDK as a first point so you are familiar with how it works, before moving onto the CompLib, however this isn’t a mandatory requirement.
The most important point to remember about the EMU-1 is that it is the senders and gauges that are important when trying to understand compatibility and not the engine model / manufacturer. This is a helpful article that describes this in more detail:
https://test.actisense.com/knowledge-base/nmea-2000/emu-1-nmea-2000-engine-monitoring-unit/emu-1-engine-compatibility-and-setup/The EMU-1 will output standard NMEA 2000 engine, transmission and fluid level PGNs that will be understood by any NMEA 2000 MFD.
Points to check are that both engines share a common ground and that each engine doesn’t require more than 3 gauges and 2 alarms to be monitored. One of the other benefits of using one EMU-1 per engine is that the battery voltage of each engine can be transmitted on the NMEA 2000 network.
Please note that an NGT-1-USB will be required to configure an EMU-1. For many customers, leaving that NGT-1-USB on the NMEA 2000 network after EMU-1 installation is beneficial as it can be very useful for diagnosing NMEA 2000 data issues (when used with our NMEA Reader software application) and it can be used to update the EMU-1 firmware and tweak the configuration if required.
The Actisense NGW-1 is sold pre-configured, either with ‘standard’ or ‘AIS’ firmware depending on which model you purchase. Should you wish to reconfigure your NGW-1, this is done via our free to download Actisense Toolkit program.
There are 2 ways of configuring your NGW-1, remotely using an NGT-1, or directly using a physical connection between the NGW-1 and the PC.
If you own an NGW-1-ISO, we recommend connecting it to your PC via an Actisense USG-2, so you have full isolation and protection of both the PC and the NGW-1. If you wish to use an RS-232, or serial to USB adapter, details of connecting your NGW-1 to a PC via an RS-232 cable, or RS232 to USB Adapter are in the manual.
If you own an NGW-1-USB, then simply plug your USB into the PC. If this is the first time, please ensure that the PC is online, as Windows will automatically find and install the required drivers.
Please note, configuring your NGW-1 via Actisense Toolkit only works with the latest 2.660 firmware. If your device is on an older version such as 2.420, upgrade it first using the NGW-1 2.660 Actipatch relevant to your device variant.
Integrating STNG cables and devices with NMEA 2000 DeviceNet is a straight forward process thanks to the adapter cables. STNG and NMEA 2000 are identical on a data and protocol front, the only difference is the physical layer.
The STNG to NMEA 2000 adapter cable (A06045) can be purchased with our NMEA 2000 products as part of a bundle (not sold separately), and can also be purchased from Raymarine.
The use of certified manufacturer adapter cables is always recommended.
