# Base64 format details in note.add

**URL:** <https://discuss.blues.com/t/base64-format-details-in-note-add/708>\
**Category:** Notecard API\
**Created:** [February 23, 2022, 1:46pm UTC](https://discuss.blues.com/t/base64-format-details-in-note-add/708 "2022-02-23T13:46:09Z")\
**Posts on this page:** 8\
**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:** [February 23, 2022, 1:46pm UTC](https://discuss.blues.com/t/base64-format-details-in-note-add/708/1 "2022-02-23T13:46:10Z")

</div>

Hi,

what is the exact details of the base64-encoded payload in `note.add`? I am sometimes getting errors like: `'cannot interpret JSON: unrecognized base64 at offset 5972 {io}'`. I am currently using the configuration `Standard char set, unpadded` ([base64 - Rust](https://docs.rs/base64/0.13.0/base64/)). If you could point me in the direction of the library or implementation you are using that would probably help.

It happens fairly seldom, so it might just be some random I2C error and nothing to worry about.

Regards, Gaute

---

<div class="post-metadata">

**Author:** ![RobLauer](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/roblauer/32/1567_2.png) [@RobLauer](https://discuss.blues.com/u/RobLauer)\
**Post date:** [February 23, 2022, 2:17pm UTC](https://discuss.blues.com/t/base64-format-details-in-note-add/708/2 "2022-02-23T14:17:13Z")

</div>

Hi @gauteh,

It sounds like you’re getting some data corruption over I2C or Serial. Can you try adding 10K pull-up resistors on both sides of your header wires that connect the boards to see if that helps?

Rob

---

<div class="post-metadata">

**Author:** ![RobLauer](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/roblauer/32/1567_2.png) [@RobLauer](https://discuss.blues.com/u/RobLauer)\
**Post date:** [February 23, 2022, 2:51pm UTC](https://discuss.blues.com/t/base64-format-details-in-note-add/708/3 "2022-02-23T14:51:58Z")

</div>

I forgot to mention ☝ this is especially important for boards like the nRF52840 that fail to put pull-ups on the board. We’ve seen problems like this when the nRF52840 (and others like it lacking pull-ups) are placed on a breadboard with header wires attached to the Notecarrier.

---

<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:** [February 23, 2022, 6:58pm UTC](https://discuss.blues.com/t/base64-format-details-in-note-add/708/4 "2022-02-23T18:58:11Z")

</div>

Good catch. Maybe that’s the cause of my other troubles as well. I’ll check.

---

<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:** [February 23, 2022, 7:05pm UTC](https://discuss.blues.com/t/base64-format-details-in-note-add/708/5 "2022-02-23T19:05:25Z")

</div>

Although the board I am using is missing the pull-ups, and they are required by the datasheet of the MCU, the notecarrier by Sparkfun do have them. The boards are connected over Qwiic, only a couple of centimeters.

 ![2022-02-23-200324_1716x1336_scrot](https://us1.discourse-cdn.com/flex020/uploads/blues/original/1X/caac246353f388c9e144b667dd57fc70ae933430.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:** [February 25, 2022, 9:16am UTC](https://discuss.blues.com/t/base64-format-details-in-note-add/708/6 "2022-02-25T09:16:40Z")

</div>

I finally managed to get back to the office (damn pandemic) and monitor voltage. The base64 error happens when input voltage drops to 3.2V (and might be lower without my multimeter noticing), so I think it is pretty likely that is the issue. For whatever reason this probably triggers my other I2C error as well.

---

<div class="post-metadata">

**Author:** ![RobLauer](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/roblauer/32/1567_2.png) [@RobLauer](https://discuss.blues.com/u/RobLauer)\
**Post date:** [February 25, 2022, 2:52pm UTC](https://discuss.blues.com/t/base64-format-details-in-note-add/708/7 "2022-02-25T14:52:40Z")

</div>

Are you seeing any dips below 3.2V (for instance when the modem powers on)? For reference, the Notecard + Notecarrier work down to 2.5V, however it must be a _sustained_ 2.5V, so it can’t dip below that level.

---

<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:** [February 25, 2022, 3:06pm UTC](https://discuss.blues.com/t/base64-format-details-in-note-add/708/8 "2022-02-25T15:06:28Z")

</div>

No not on my meter. But it could be too short for it to pick it up. There’s a voltage regulator for the host MCU as well that can do down to 2.8, but I don’t see the MCU brown-out (usually the LEDs fade well before the MCU stops), but it might be low enough to make the logic levels too low.
