SPX-17236 ARGOS Satellite Transceiver Shield

Hi,

I have the ARGOS Satellite Transceiver Shield and ARGOS Omnidirectional Antenna with Artemis Thing Plus.

I’m testing using Example11_TransmitARGOS3WithPrediction from the Arduino 1.0.9 library. As a result of checking the data received from CLS’ ARGOS web, 3 bytes from SENSOR24 to SENSOR26 are always corrupted.

The data sent from SENSOR23 to SENSOR29 is as follows.

Original data: 1C 2D 3E 4F 5A 6B 7C

Received data: 1C 02 D3 E4 5A 6B 7C

I tried changing the TCXO voltage to 3.3V or 2.0V etc, but got the same result.

Is there anything worth checking out, such as a circuit, device, or source code?

Hi @shinjun,

Please do not change the TCXO voltage. The oscillator we use requires 1.8V for correct operation.

Have you modified Example11? Example11 uses setPayloadARGOS3LatLon which encodes the latitude and longitude into a 15 byte message. Yet you seem to be sending at least 29 bytes? I’m guessing you have modified the example to use setPayloadARGOS3? If so, how many bits or 32-bit words are you sending?

It looks like four extra zero bits are being added to the data stream at the start of SENSOR24… Very mysterious!

Best wishes,

Paul

I used setPayloadARGOS3 instead of setPayloadARGOS3LatLon to create and send new data.

I have now resolved this issue. This was my mistake.

Also I am trying Example7_ContinuousReceiveWithAOPParsing right now.

However, I haven’t received AOP yet.

How many times can I receive AOP in a day?

I wonder if I can always receive when the satellite passes.

Thanks in advance for the reply.

Hi @shinjun,

I am glad setPayloadARGOS3 is working for you. Thank you for letting me know.

Only some of the satellites have the “downlink” function. You can see which in the Satellite Allcast Info via the ARGOS website (see below). Please check you are using ARGOS3. You should see data when MA, MC or SR is overhead.

Best wishes,

Paul

“satellite” : “A1”,

“downlinkStatus” : “Downlink transmitter OFF”

“satellite” : “MA”,

“downlinkStatus” : “ARGOS-3 TX ON”

“satellite” : “MB”,

“downlinkStatus” : “Downlink transmitter OFF”

“satellite” : “MC”,

“downlinkStatus” : “ARGOS-3 TX ON”

“satellite” : “NK”,

“downlinkStatus” : “Downlink transmitter OFF”

“satellite” : “NN”,

“downlinkStatus” : “Downlink transmitter OFF”

“satellite” : “NP”,

“downlinkStatus” : “Downlink transmitter OFF”

“satellite” : “SR”,

“downlinkStatus” : “ARGOS-3 TX ON”

Hi PaulZC,

Thank you for your reply.

When the MC satellite passed, I did a reception test with the ARGOS shield and a spectrum analyzer, but no data was received yet.

However I will continue the AOP reception test through MA, MC, SR.

Thank you.

Hi @shinjun,

We learned recently that some ARTIC R2 boards had been incorrectly programmed with the wrong Platform ID. Each board has two IDs: a decimal one which you use to access your data on ArgosWeb; and a hexadecimal one which is embedded in each satellite uplink message. These boards had been incorrectly programmed with the decimal ID instead of the hexadecimal one. You can tell if your board is affected by calling readPlatformID(). If the true hexadecimal ID is returned, all is well. If the value is the decimal ID - expressed in hexadecimal - then your board requires reprogramming as your messages will not be delivered. Please return your board ( https://www.sparkfun.com/returns ). We will reprogram it and return it to you quickly. If your project is time-critical, please contact us again here and we will provide a software work-around. We apologise for the error and the inconvenience.

Best wishes,

Paul