# Unreliable content with RFM69C and emonBase

**URL:** <https://community.openenergymonitor.org/t/unreliable-content-with-rfm69c-and-emonbase/9805>\
**Category:** Hardware\
**Tags:** rfm69pi\
**Created:** [19 January 2019 09:11 UTC](https://community.openenergymonitor.org/t/unreliable-content-with-rfm69c-and-emonbase/9805 "2019-01-19T09:11:30Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![franck102](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/f/35a633/32.png) [@franck102](https://community.openenergymonitor.org/u/franck102)\
**Post date:** [1 February 2019 16:29 UTC](https://community.openenergymonitor.org/t/unreliable-content-with-rfm69c-and-emonbase/9805/21 "2019-02-01T16:29:55Z")

</div>

More troubles today trying to get JeeLib to work with an ATMega 2560 (Robodyn mega mini).  
After lots of debugging this appears to be an issue with the SPI setup, this sequence makes it work for me:

```
SPI.begin();
delay(100);
rf12_initialize(nodeId, RF_freq, networkGroup);
delay(100);

```

I haven’t investigated further.

Franck

---

_[View the full topic](https://community.openenergymonitor.org/t/unreliable-content-with-rfm69c-and-emonbase/9805)._