Hobby Electronics and Controller->
Cleaning and caring products->
Use keywords to find the product you are looking for.
Shipping & Returns
Conditions of Use
Welcome, Please Sign In
I am a new customer.
By creating an account at gadgetPool.de you will be able to shop faster, be up to date on an orders status, and keep track of the orders you have previously made.
I am a returning customer.
Password forgotten? Click here.
SeaTalk NMEA Bridge 32 (Basic Line) without Display
SeaTalk NMEA Bridge32 (basic line) with repeater display
SeaTalk NMEA Link (USB) with galvanic isolation
5V Switching Power Supply
SeaTalk NMEA Link (RS232) with galvanic isolation
JTAG-ICE for AVR controllers (USB Interface 3,3..5 V )
NMEA Multiplexer with bidirectional SeaTalk port and USB
Plug for SeaTalk Connection
SeaTalk NMEA Bridge128SD w. repeater display, Keyboard and USB
Reflow Kit (Big)
There are currently no product reviews
Is seatalk from st30 supported?
Hello I am trying to connect st30 speed to st60 multi repeater and st60 wind. When connecting the three "normally" via seatalk, the st30 does not pass speed through water to st60 multi. I found some information that this could be due to st30 using an older version of seatalk1 than that used by St60, see [url] http://raymarine.ning.com/m/discussion?id=6492755%3ATopic%3A110542 [/url] for a discussion of a similar issue. My questions are: 1. I need speed though water as nmea (to show in garmin gps). Can the multiplexer convert speed through water data from st30 to nmea? I just wanted to ensure that st30 version of seatalk1 is supported by the multiplexer - because the st60 multi does not repeat the data from the seatalk network. 2. Can the multiplexer help feed speed though water from st30 to st60 wind? How would that be achieved? Seatalk->nmea->seatalk - with the "overwrite" option as explained on p. 18 in the manual? Many thanks for your inputs on this issue. Marcin [/code]
Hello Frank, I just purchased a new VHF DSC which accepts only RMC and not GLL to display the position, but my GPS sends only GLL. Is there a way to do the conversion with the bridge to convert the GLL in RMC? Thanks for your feedback, Best regards
I didn't read this section as I thought it was only applicable to Seatalk messages. But this is exactly what I'm looking for. I use a triducer Airmar DST800 (speed - depth - temperature) and I need to calibrate speed and depth in nmea, not in seatalk My previous nmea multiplexer had such option (in % for speed and value for depth), but it was always overflowing and configuration tool wasn't userfriendly.
Thanks for clarifying. Btw, apart from the photos, you also missed the "2 NMEA 0183 outputs" text [url=http://www.gadgetpool.de/bestellen/catalog/product_info.php/products_id/93] on this page (below the first two photos).
I actually think that even if the laptop is powered from the boat supply, there might be ground differences (my DC/DC converter that powers my laptop probably isn't really clean on its ground). At the very least you'd get a ground loop that could cause problems? Adding it for a next version seems like a good plan, especially since it seems rather easy - just power the FT232 from USB and keep its ground separate, then add two high-speed optos on the RX and TX lines? Now I'm doubting wether to get this multiplexer, or perhaps go for the miniplex after all. It's a lot of money to spend to run into problems later...
Thanks for clarifying. I'm not sure if I actually need to filter/route seatalk data like that, but I didn't want to be stuck when it turns out I do. Having the sourcecode makes me not worry about this, if I really need it I could even hardcode it to get started :-)
As with most NMEA devices, we have galvanic isolation on the NMEA
Ports. We also have a galvanic isolated SeaTalk Port. NMEA-OUT Ports and USB are not isolated. I guess it might be good idea to implement this in the future. If the computer is powered from a different power source ( Shore power ) , it might indeed result in ground loops between multiplexer and computer.
There are 4 NMEA inputs and 4 NMEA outputs. In our first firmware releases, we only had 2 out ports. Meanwhile all 4 out ports are available. I have updated the manual, but not the photos. Sorry about that - I'll have to fix that ... :-(
Well - i just have not made a filter for different seatalk sentences. Sure - could be done. I just didn't have the time and - up to now - nobody asked for it. What we have it a few diffentent configuration options. [img:9dbb911acb]http://www.gadgetpool.de/nuke/images/articles/multiplexer/SeaTalkOptions.png[/img:9dbb911acb] So you can switch on/off things like Seatalk -> NMEA - create and send a HDM sentence, when appropriate data is received from SeaTalk - create and send a RMC sentence, when appropriate data is received from SeaTalk - create and send a VLW sentence, when appropriate data is received from SeaTalk etc. NMEA -> Seatalk - create a SOG SeaTalk datagram, when appropriate data is available from NMEA. Since SeaTalk and NMEA data not allways come in the same structure, it would be a bit more difficult. We would have to think about how to set up a filter for this. Example : NMEA RMC sentence contains speed, position, heading, time, date - all in one sentence. In SeaTalk this information will be in different datagrams. You see. You can, to some degree, switch on/off creation of NMEA or SeaTalk sentences, but you can not filter to which port this newly created NMEA sentence should be sent to. It will be sent to all.
... I just sent the sources and schematics :-)
Saturday 05 September, 2015
1886339 requests since Tuesday 04 April, 2006
Copyright © 2015