My Account  Cart Contents  Checkout  
  Top » Catalog » Yacht Electronics » My Account  |  Cart Contents  |  Checkout   

Yacht Electronics
Yacht Electronics->


spare parts
spare parts

Hobby Electronics and Controller
Hobby Electronics and Controller->

Cleaning and caring products
Cleaning and caring products->


What's New? more
empty housing for SeaTalk Bridge
empty housing for SeaTalk Bridge
Quick Find
Use keywords to find the product you are looking for.
Advanced Search
Shipping & Returns
Privacy Notice
Conditions of Use
Contact Us
Seatalk Alarm Device 149.00EUR

+ Shipping / Versandkosten

SeaNet Alarm is a small device that monitors a SeaTalk(R) network, different devices on a SeaTalk network , it monitors different alarm conditions and sets off an alarm when certain conditions appear.

The main functions are

  • Produce an unmistakable alarm when a SeaTalk instrument produces a warning or alarm.
  • Monitor the SeaTalk instruments and set off an alarm if an instrument - or the whole SeaTalk network - should stop working.

SeaNet Alarm provides

  • Remote alarm for ST40, ST50, ST60 depth & wind instruments
  • Remote alarm for autopilots
  • Remote alarm for SL,RL,C and E series radar
  • Built in alarm clock - wake up singelhanded sailor
  • Built in SeaTalk network surveillance and alarm if network stops sending data
  • SeaTalk instrument surveillance and alarm if instrument  stops sending data
  • Monitors up to 10 alarms simultaniously
  • Solid state switch with short-circuit and overload protection
  • Pushbutton for alarm acknowledge and special functions
  • LED's to visualize alarm source
  • Galvanic isolation between SeaTalk network and alarm voltage
  • Powers supply and alarm power independent from SeaTalk network
  • Configuration via USB connection to PC and configuration software.

SeaNet Alarm

 SeaTalk is Reg. Trademark of Raymarine Inc.

SeaTalk Instruments are normally installed in the cockpit of your vessel.

The built in alarms are not loud enough to be heard by the crew inside a vessel or to wake up sleeping crew members.

So even with anchor alarm activated, it is not sure that the crew will wake up if the anchor is dragging.

Single handed skippers often get too little sleep and need a loud warning if depth, windspeed or radar indicates a dangerous situation. They usually also want to be waked up every half hour or hour in order to check if everything is all right.

It's easy to miss an instrument beep while sitting on the chart table while the engine is running.

It's easy to miss a radar beep, when the radar is mounted at the chart table and you are at the helm.

If an instrument should break, without the SeaNet Alarm it might take a long time before the failure is noticed. Maybe the boat operator would rely on a device that that isn't functioning any more.

There is clearly a need for loud sound or an optical alarm, that makes you aware of possible dangers and instruments failure.

With the SeaNet Alarm this needs can be filled in an easy and economic way.

When an alarm condition is recogniced, SeaNet Alarm activates a switch that can activate a powerfull external alarm and/or switch an optical alarm.


Alarm sources

SeaNet Alarm his highly configurable. It listens to different instrument alarms and also has it's own built in alarm triggers.


Alarms can be triggered by :

  • Internal “wake-up” timer → internally generated
  • SeaTalk network failure → internally generated
  • Shallow water alarm → from depth instrument
  • Anchor alarm → from depth instrument
  • Transducer defective → from depth instrument
  • High & low windspeed alarm → from wind instrument
  • Wind angle high & low alarm → from wind instrument
  • Windshift → from autopilot
  • Off course & drive stopped & auto release alarm   → from autopilot
  • Object in guard band 1&2 → from radar
  • MOB Alarm → from instrument
  • Instrument failure → internally generated

Alarms can be switched on/off individually. A unique alarm sound pattern can be assigned to the different alarms – so that the user can “hear” what caused the alarm.

User Interface

SeaNet Alarm has

* 1 Pushbutton
* 3 LED's

With the pushbutton , an active alarm can be acknowleded to turn off the alarm manually.

The Led's show system status and active alarms.
An alarm type - like depth, windspeed,autopilot etc. -  can be assigned to a LED, so that you can "see" what triggered the alarm.

Alarm Output

SeaNet Alarm has a detachable 2 pin screw terminal to connect one or more alarms, sirens or lights.

This output is protected against short circuits, has a thermal protection an overvoltage and overload protection and current limitation.

Nominal alarm current - up to 3.5 A

   Connection Overview 

When will alarms be set / reset

SeaNet Alarm listens to the SeaTalk Bus for coming or going alarm conditions.
Instrument alarms – like shallow water, high wind speed etc. - have to be set and enabled in the SeaTalk instrument.

The Alarm output is activated when :

  • An instrument newly sets the appropriate alarm on the SeaTalk Bus
  • AND this alarm type is enabled in SeaNet Alarm.
  • AND the Alarm is active longer than delay time set in SeaNet Alarm ( If delay time is set )

The Alarm output is reset when :

  • An Instrument clears the appropriate alarm on the SeaTalk Bus
  • OR the acknowledge button on SeaNet Alarm is pressed
  • OR alarm duration time, set in SeaNet Alarm, is expired

An alarm will be retriggered if the appropriate alarm is reset on the SeaTalk Bus and later set again.

If an alarm stays active on the seatalk bus and the alarm output is switched off by the acknowledge button or timeout, this alarm will only be retriggered after it has disapperared on SeaTalk and reappeared later.

A „SeaTalk instrument failure“ alarm is triggered, when an instrument ( like depth, windspeed etc.) has sent data to the Seatalk network, and than suddenly stops sending data.

It is not possible to announce two or more alarms at the same time. If two or more alarms are active at the same time, the first one will be announced.

When the currently announced alarm is acknowledged – by pressing the pushbutton or because it's alarm time has exired – the next alarm be announced.

If a second alarm comes and goes while the first alarm is still active, this second alarm will never sound.

Power supply

SeaNet Alarm requires a 12 Volt power supply. This power supply is isolated from the SeaTalk network. This galvanic isolation protects the SeaTalk network and enables the SeaNet Alarm to react to possible failures of the SeaTalk network – even if SeaTalk power should be disrupted.

SeaTalk connection

SeaNet Alarm has a detatchable 3 pin screw terminal for connection to the SeaTalk network.

SeaTalk connection


SeaNet Alarm comes with a USB cable and a configuration software for a standard PC.
The configuration software is available for Microsoft Windows and for Linux.

Currently the MS-Windows Version comes as executable and Source.
Linux Version comes as source and executable for Ubuntu, Fedora 5, Suse etc..
For other Linux systems it might be necessary to compile it on your machine.
No Problem - all sources are included.

Main Configuration screen

Configuration screen

Alarm status and logging window

Technical Data

Power input 9-15 Volt DC
Current draw LED off 16,8 mA
Current draw LED on 1,8 mA per LED
Max. switched current     
3.5 A, 11-15 Volt DC. Low Side switch.
 Dimensions    8 cm x 5,5 cm ( without Plugs )
 Dimensions  11 cm x 5,5 cm ( with Plugs )

SeaNet Alarm Software

The heart of SeaNet Alarm is a standard AT-Mega microcontroller made by ATMEL.
SeaNet Alarm comes with a CD with all source codes of the board software. 
No licence fees, no hidden functions. The software of SeaTalk alarm can be adapted, improoved, extended or changed in any way you like. The necessary compilers are available freely in the internet. SeaNet Alarm comes with a built in boot loader software and a programmer software for the PC. You don't need any special hardware programmer to bring a new software onto SeaNet Alarm. Just a normal RS232 cable.

For further information aboutr SeaNet Alarm - please read the manual.

CLICK to load Manual

Items in stock : 9
This product was added to our catalog on Saturday 13 October, 2018.
Shopping Cart more
0 items
Notifications more
NotificationsNotify me of updates to Seatalk Alarm Device
Tell A Friend
Tell someone you know about this product.
Reviews more
Write ReviewWrite a review on this product!
English Deutsch

Hello Frank, the latest firmware link in the downloads section - firmware V2.8, config tool V1.14 is still broken. Can you please take a look? Cheers Ian
Thank you for telling me. Has been fixed now. The download is available again. Cheers Frank


Hello Frank, the latest firmware link in the downloads section - firmware V2.8, config tool V1.14 is still broken. Can you please take a look? Cheers Ian


Hello Ian,
I would like to re-visit this feature. Is this something you would have time to add
I hope I can do it in the not too far future. Currently I'm still busy transfering or website from the unreliable provider to the new provider. And I have to address a few issues with the SeaTalkNnmeBridge128SD. After that is done, I'll gladly look at the Alarm. But - I can't really say when that will be.
or should I look at modifying the firmware source myself?
I'll gladly send you the source codes - for the Alarm and for the SeaTalkNmeaBridge. The Sources for Bridge include NMEA handling and might be useful.
Also the link to the firmware download for this device doesn't seem to work.
Well - another issue caused by the transfer of to Sorry about that. I'll fix it. Kind Regards Frank


Hi Frank, I would like to re-visit this feature. Is this something you would have time to add or should I look at modifying the firmware source myself? Also the link to the firmware download for this device doesn't seem to work. Kind Regards Ian


New Firmware V1.73 with bugfixes released for testing

Today I released a new firmware version for the tiny SeaTalk NMEA Link. New firmware for the BridgeSD128, mentioned in this thread, will be available shortly. I had a longer exchange with codger at the [url=] Cruisers and Sailing Forum[/url], and his explanations and logfiles helped a lot to solve the problems the old firmware had. My problem is - I currently don't have access to to a boat with seatalk instruments. So this firmware changes are tested on the workbench only. I would need someone with a tiny seatalk-nmea link and a boat and the instruments that showed the problems. We certainly need some real word testing to verify this changes really solved to problems. If someone out there is willing to test the new firmware, please let me know ! Again - it's not for the 128SD bridge, but for the smaller USB SeaTalk to NMEA0183 link. Firmware can be downloaded from Firmware : [url][/url] Firmware update tool for Windows : [url][/url] The files are also available in the download section of [url][/url] Changes are :
    Fixed calculation of COG for RMC, GLL sentence. Before : magnetic variation was ignored in calculation. New : reading Compass variation from Seatalk datagram #99 and from NMEA RMC sentence and included into calculations.
    Fixed VHW sentence. Before : VHW sentence was directly created from seatalk datagram 53. New : VHW data come from compass heading datagrams. Variation also included in calculation.
    Position in 1000th of a minute. Before it was 100th of a minute RMC/ GLL sends ddmm.fff before ddmm.ff When more precise data are available, don't send unprecise data (i.e. When receiving SeaTalk position with 1000th minute, don't use 100th datagram) Same with STW and Water temperature.


Hello Frank Works as advertised. Thank you very much !!! One note: When you compile the source code on one machine and want to copy it to another you still need to install qt5 and the libraries but do not need to compile it again. I needed to change the file permission on the new device to allow execution: pi@raspberry:~ $ sudo chmod 0755 stConfig Obviously it needs to be executed in a graphical environment. Since I use my raspberry headless i was able to run it in a x11vnc session perfectly. Thank you again so much !!! Ralf


Multiplexer Config tool running on Raspbeerypi 3 [img:2d0cf14502][/img:2d0cf14502] Install QT5 development files : [code:1:2d0cf14502] sudo apt-get install qt5-default libqt5serialport5-dev libqt5websockets5-dev [/code:1:2d0cf14502] How I compiled it : Click [url=]---HERE--- to get the sources [/url] [code:1:2d0cf14502] unzip cd stConfig qmake make ./stConfig [/code:1:2d0cf14502] please let me know it it works on your RasPi Frank


Hallo Auch wenn ich noch keine Erfahrungen mit QT5 gemacht habe kann ich gerne versuchen es mit den Sourcen zu compilieren. Gruss Ralf


Hallo, ich bin gerade dabei zu versuchen eine neue Version fuer den PI zu compilieren. Ist etwas aufwaendiger. Ich habe hier mittlerweile QT5 installiert und nun muss ich schauen wie ich das zu einer lauffaehigen Version mit allen benoetigten Libraries packen kann. Alternativ - wenn die QT Entwicklungsumgebung installiert ist, sende ich gerne sie Sourcen. Gruss Frank


Hallo auch von mir ein riesiges Dankeschoen fuer den gelungenen Muxxer. Ich betreibe ebenfalls den RPi 3 als Nav-Computer an Bord meines Segelbootes und wuerde diesen gerne zum Konfigurieren des Muxxers nutzen. Bei mir startet stConfigPi ebenfalls nicht. Im Desktop Mode tut sich gar nichts und im Terminal mode gibt es den folgenden Fehler: pi@raspberrypi:~ $ ./stConfigPi Segmentation fault Ich habe qt4 wie folgt installiert: pi@raspberrypi:~ $ sudo apt-get -y update pi@raspberrypi:~ $ sudo apt-get -y install qt4-default qt4-dev-tools qtcreator Da ich nicht weis welche libraries benoetigt werden habe ich gesucht und die Folgenden installiert: libqt4-dbg libqt4-dbus libqt4-declarative libqt4-declarative-folderlistmodel libqt4-declarative-gestures libqt4-declarative-particles libqt4-declarative-shaders libqt4-designer libqt4-designer-dbg libqt4-dev libqt4-dev-bin libqt4-help libqt4-network libqt4-opengl libqt4-opengl-dev libqt4-phonon libqt4-ruby libqt4-script libqt4-script-dbg libqt4-scripttools libqt4-sql libqt4-sql-mysql libqt4-sql-odbc libqt4-sql-psql libqt4-sql-sqlite libqt4-sql-sqlite2 libqt4-sql-tds libqt4-svg libqt4-test libqt4-xml libqt4-xmlpatterns libqt4-xmlpatterns-dbg libqtassistantclient-dev libqtassistantclient4 libqtconnectivity1 libqtcontacts1 libqtcore4 libqtcore4-perl libqtcurve-utils2 libqtdbus4 libqtexengine-dev libqtexengine1 libqtfeedback1 libqtgallery1 libqtglib-2.0-0 libqtgstreamer-1.0-0 libqtgstreamer-dev libqtgstreamerui-1.0-0 libqtgstreamerutils-1.0-0 libqtgui4 libqtgui4-perl libqtkeychain1 libqtlocation1 libqtmessaging1 libqtmultimediakit1 libqtnetwork4-perl libqtorganizer1 libqtpublishsubscribe1 libqtruby4shared-dev libqtruby4shared2 libqtscript4-core libqtscript4-doc libqtscript4-gui libqtscript4-network libqtscript4-opengl libqtscript4-phonon libqtscript4-qtbindings libqtscript4-sql libqtscript4-svg libqtscript4-uitools libqtscript4-webkit libqtscript4-xml libqtscript4-xmlpatterns libqtsensors1 libqtserviceframework1 libqtsolutions-soap-2.7-1 libqtsysteminfo1 libqttest4-perl libqtversit1 libqtversitorganizer1 libqtwebkit-dev libqtwebkit-qmlwebkitplugin libqtwebkit4 libqtwebkit4-dbg libqtxdg0 libqtxdg0-dev libqtxml4-perl Ich habe auch versucht QT Creator nach folgender Anleitung abzusetzen: Aber stConfigPi ist ja schon compiliert und sollte im Desktop Modus nativ laufen, korrekt? Ich waere Ihnen dankbar, wenn sie die Benutzung des Raspberry Pi Config Tools noch kurz erklaeren koennten. Vielen Dank fuer Ihre Unterstuetzung Ralf


Copyright © 2020
Powered by osCommerce