# Stuck in failure state: Offshore deployed buoys

**URL:** <https://discuss.blues.com/t/stuck-in-failure-state-offshore-deployed-buoys/2062>\
**Category:** Uncategorized\
**Created:** [April 11, 2024, 7:59am UTC](https://discuss.blues.com/t/stuck-in-failure-state-offshore-deployed-buoys/2062 "2024-04-11T07:59:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![gauteh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/gauteh/32/269_2.png) [@gauteh](https://discuss.blues.com/u/gauteh)\
**Post date:** [April 11, 2024, 7:59am UTC](https://discuss.blues.com/t/stuck-in-failure-state-offshore-deployed-buoys/2062/1 "2024-04-11T07:59:18Z")

</div>

Hi,

I have previously asked about a buoy where the GPS stopped working after several months. But which we do not yet have access to. Recently, we had another buoy stop working (transmitting), and I managed to get hold of it before it went into the water. Our MCU keeps restarting (indicating that it does not get contact with the notecard), I’ve checked that the voltage is good (output from the lithium-capacitor regulator you sell). There is a vague orange/red light constantly on on the notecard. It’s got an external SIM. The device has been without coverage for prolonged periods of time, so it has probably tried to connect a lot. It might also be full of log messages from the MCU which, but my understanding is that it will protect itself from getting to full.

It’s running the 6.1.1 firmware.

In these cases it would be very useful to send a command to the notecard to restart it. Though in the latter case it doesn’t even connect.

> [@GPS troubles: No GPS acquired, stopped working, or not detecting movement](https://discuss.blues.com/t/gps-troubles-no-gps-acquired-stopped-working-or-not-detecting-movement/1678):
>
> Hi, I have had a device being deployed for several months where the GPS has suddenly stopped working (heartbeat 1 hour). I don’t have access to the device since it is currently anchored in almost 4 meters waves offshore, but everything else appears to work as it should - transmitting data ferociously. I suspected a disconnected antenna, but that does not seem very plausible given that the modem is working. Recently, we tried to deploy a couple of buoys in South Africa and the GPS is struggling…

---

<div class="post-metadata">

**Author:** ![gauteh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/gauteh/32/269_2.png) [@gauteh](https://discuss.blues.com/u/gauteh)\
**Post date:** [April 11, 2024, 1:31pm UTC](https://discuss.blues.com/t/stuck-in-failure-state-offshore-deployed-buoys/2062/2 "2024-04-11T13:31:20Z")

</div>

There was no response when connecting through microUSB, the device did not show up. When pulling `EN` low the light just dimmed slightly, and went back up to its semi-dimmed state. I attached a debugger to the MCU and it gets no response over I2C. The power was fine, there was 3V3 on VIO, there was 3.8V on VIN. Swapped out the entire board (carrier, notecard, MCU), and connected to the same regulator and it works.

 ![20240411_094743](https://us1.discourse-cdn.com/flex020/uploads/blues/original/2X/9/9ee2eafdc5f1a9cc56e48229032346aea4d79361.jpeg)  
 ![Screenshot from 2024-04-11 10-00-55](https://us1.discourse-cdn.com/flex020/uploads/blues/original/2X/4/484dd3df21b415da7730a019e477210c30cf6eea.png)

---

<div class="post-metadata">

**Author:** ![gauteh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/gauteh/32/269_2.png) [@gauteh](https://discuss.blues.com/u/gauteh)\
**Post date:** [April 15, 2024, 7:45am UTC](https://discuss.blues.com/t/stuck-in-failure-state-offshore-deployed-buoys/2062/3 "2024-04-15T07:45:36Z")

</div>

I hooked the device up using microUSB back in the lab. I don’t get a ttyACM0 device, but the kernel log shows the device to be recognized as a `STM32 bootloader`:

```auto
$ journalctl -k -r
Apr 15 09:43:14 pc5857 kernel: usb 3-1.3: Manufacturer: STMicroelectronics
Apr 15 09:43:14 pc5857 kernel: usb 3-1.3: Product: STM32 BOOTLOADER
Apr 15 09:43:14 pc5857 kernel: usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 15 09:43:14 pc5857 kernel: usb 3-1.3: New USB device found, idVendor=0483, idProduct=df11, bcdDevice=22.00
Apr 15 09:43:14 pc5857 kernel: usb 3-1.3: new full-speed USB device number 26 using xhci_hcd
Apr 15 09:42:56 pc5857 kernel: usb 3-6.3: USB disconnect, device number 13
Apr 15 09:41:55 pc5857 kernel: usb 3-6.4.2.3.1: reset high-speed USB device number 20 using xhci_hcd
Apr 15 09:40:54 pc5857 kernel: usb 3-6.4.2.3.1: reset high-speed USB device number 20 using xhci_hcd

```