[Josh Keets]

Hi Tom,

Unfortunately that blue screen you are seeing with the Keil Dev Tools indicates that the device has lost it’s web files.

Please raise a ticket through the link below and our Tech Support will talk you through the steps of getting the device sent back to us;

https://actisense.zohodesk.eu/portal/en/newticket

Sadly we do not have a fix for this that can be implemented in the field yet, it has to be done by us here at base.

Thank you in advance,

Josh

[Josh Keets]

Hi Jeremy,

Thank you for reaching out to us.

Could you please raise this as a ticket via the following link; https://actisense.zohodesk.eu/portal/en/newticket

We’d like to explore this further, and we will pass it onto our software team for investigation.

Thanks

Josh

[Josh Keets]

Hi there!

This is not an issue we have come across before, and we need to investigate it further.

Could you please raise a Support Ticket via this link;
https://actisense.zohodesk.eu/portal/en/newticket

This will then send an e-mail to one of our support team who will be happy to assist you further and help resolve this matter.

Thanks

Josh

[Josh Keets]

Hi there!

The implementation of Tilt/Trim is something that has been considered for the additional Auxiliary connections on the EMU-1. We plan to review the options for these 2 connections at the next product review point for the EMU-1. I can’t confirm when this will be, but I will add your request into the capture database so we can log the number of requests for a specific feature.

Thank you

Josh

[Josh Keets]

Hi there!

We would like to investigate this further. Could you kindly create a ticket so our Tech Support can take the necessary next steps in the process.

Ticket link: https://desk.zoho.eu/portal/actisense/en/newticket

Thank you in advance.

Josh

[Josh Keets]

Hi there!

As this will involve sensitive information such as IP address of the W2K-1 in relation to your client network connection, can I suggest that a ticket it raised on our support desk so it is managed 1-to-1 rather than on a public forum.

Thank you in advance,

Josh

[Josh Keets]

Hi Chris,

If both devices are NMEA 2000 and utilise the same connectors then it will be plug and play. The NMEA 2000 standard denotes that Device Net Standard M12 connectors are used, however some proprietary cable and connector methods do exist. If the SIMRAD NMEA 2000 backbone is SIMNET then you will most likely need adapter cables.

If you are looking to get any sort of NMEA 0183 data into your NMEA 2000 backbone, then you will need an NGW-1 to convert between 0183 and 2000. If you are solely using NMEA 2000 PGNs (data), then no converters are needed.

Thanks

Josh

[Josh Keets]

Hi Chris,

Currently, the gauge inputs on the EMU-1 config do not support Exhaust Gas Temp. This data is usually contained within PGN 130316 [Temperature, Extended Range], which is a PGN that the EMU-1 does not currently output.

I have seen various customers attempt this using the custom gauge tool and creating their own graphs using the voltage values against a temperature value, however nobody has ever confirmed success using this method.

Thanks!

Josh

[Josh Keets]

Hi Steve,

My apologies, looks like my reply never actually sent way back in November!

Possibly in the future this is something we might work on. It is on our ‚potential ideas‘ list, as a future improvement (or new product if we ever make a W2K-2). However at this moment in time, configuring the EMU-1 is only possible via the NGT-1.

The NGT-1 is a very useful tool to have on board anyway, as it isn’t just a configuration USB Device, it can also be used to monitor and diagnose issues on your network, and log all of your data when used in combination with NMEA Reader. The device is capable of transferring every single NMEA 2000 PGN from the network to the PC… ideal if you also want a chartplotter / nav program on an on-board computer or laptop.

Please let me know if there is anything else you would consider a potential improvement to the W2K-1 in future and I will get it logged.

P.S. I will log your interest in the wireless configuration ideas, to keep track of how many customers are requesting this feature.

Thanks,

Josh.

[Josh Keets]

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

[Josh Keets]

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

[Josh Keets]

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

[Josh Keets]

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

[Josh Keets]

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!

[Josh Keets]

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.

[Autor]

Beiträge