# Starting out - Raspberry PI3b / Arduino Uno R3 =\> local Emoncms

**URL:** <https://community.openenergymonitor.org/t/starting-out-raspberry-pi3b-arduino-uno-r3-local-emoncms/16730>\
**Category:** Getting Started\
**Created:** [1 February 2021 13:20 UTC](https://community.openenergymonitor.org/t/starting-out-raspberry-pi3b-arduino-uno-r3-local-emoncms/16730 "2021-02-01T13:20:39Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![pb66](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/pb66/32/27_2.png) [@pb66](https://community.openenergymonitor.org/u/pb66)\
**Post date:** [3 February 2021 08:57 UTC](https://community.openenergymonitor.org/t/starting-out-raspberry-pi3b-arduino-uno-r3-local-emoncms/16730/20 "2021-02-03T08:57:47Z")

</div>

> [@borpin](#):
>
> and the feed is set to 10s, you will get the last value of the input in that 10s window.

In the context of what you are explaining, yes you do ++get every 10th value++ but in actual fact, when running low-write emoncms ie feedwriter, you would in fact **get the first value in any 10s window.**

Feedwriter will **only** update the feed once and then **not** update further, ie not over write existing values. Whilst standard emoncms would in fact write the given feed value window 10x, once each time the 1s input is updated so it is only then that you end up with the **last** value jn eazh 10s window.

But yes overall that sounds pretty much it for **fixed** timeseries feed data.

---

_[View the full topic](https://community.openenergymonitor.org/t/starting-out-raspberry-pi3b-arduino-uno-r3-local-emoncms/16730)._