Cuza
Member
Hy all, i bought an Epirb GME MT403FF and i don't know how program it.
What software program i need? and programmer?
Kind regards!
What software program i need? and programmer?
Kind regards!
Hy all, i bought an Epirb GME MT403FF and i don't know how program it.
What software program i need? and programmer?
Kind regards!
Hy all, i bought an Epirb GME MT403FF and i don't know how program it.
What software program i need? and programmer?
Kind regards!
Your supplier should program it with your MMSI number. Epirb's are not user programmable.
In the UK at least, EPIRBs aren't programmed with any custom data. Each one has its own ID assigned by the manufacturer, and we register that with MRCC Falmouth so that they know whose beacon it is when they receive the signal. The information about the vessel, owner, etc then comes out of the MCA's own database on shore, not from the beacon message.
Registration form here: https://forms.dft.gov.uk/mca-sar-epirb/
Pete
When I purchased my GME epirb from a UK company it had to have the MMSI prefix programmed for South Africa as each country has a different MMSI prefix. If you are buying in the UK for use in the UK it may be pre-programmed with the UK MMSI prefix.
When I purchased my GME epirb from a UK company it had to have the MMSI prefix programmed for South Africa as each country has a different MMSI prefix. If you are buying in the UK for use in the UK it may be pre-programmed with the UK MMSI prefix.
I also had to have my old EPIRB programmed by ARTECH with the South African MMSI prefix during the battery change and testing last time I was in the UK.
So If there is no indication of where the EPIRB is registered how does the system know which MRCC to send the emergency signal to verify the details of the vessel and to check with next of kin if the vessel could be in a real emergency or just a false alarm.
I didn't realise that the COSPAS-SARSAT 406 messages had any programmable fields like that.
In the UK at least, EPIRBs aren't programmed with any custom data. Each one has its own ID assigned by the manufacturer, and we register that with MRCC Falmouth so that they know whose beacon it is when they receive the signal. The information about the vessel, owner, etc then comes out of the MCA's own database on shore, not from the beacon message.
Registration form here: https://forms.dft.gov.uk/mca-sar-epirb/
Pete

Not exactly so; the programmed 15Hex code "includes" the MMSI (but not the shore contact for the MCA, which is indicated by the user at the registration).
The cospas sarsat web site has a section allowing the user to "decode" any 15hex code.
For example, this is what I obtain when I decode my Epirb 15Hex, some fields are related to position (in this case with gps), one is the country code 227 for France and the MID is the rest of my MMSI number. All is registered inside the beacon by the manufacturer before any registration is made by the user with the national authority mca etc. That is why if one sells the epirb to another user with a different MMSI, the beacon has to be sent back to the manufacturer for re-programming, it is not enough to change the registration details at the MCA.
Actually, when one user has the option of registrering through the internet, at the first input of the 15hex all the beacon characteristics appear.
View attachment 48647
regards
Not so. The beacon is identified only by means of the 15 digit country specific code entered by the manufacturer, at least in so far as the US and UK are concerned. I have re-registered a second hand beacon with the US coastguard who were happy to accept the registration albeit with the warning that the contact details supplied were for an overseas address. In addition, now that you can use PLBs inland in both UK and US, there is no MMSI associated with them in any case. So, whilst France may be insisting on including the MMSI in the signal from the beacon, this is not the case for US and UK.
I have just to write the hex code to the epirb, but how i can do that for this epirb.
Best regards!