1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97

/*
	Data Smoothies – an example on how to take incoming data values for a variable but smoothly transition to the new value
	(instead of having the old value 'snap' to the new one)

	This is a simple, linear way to smooth data points coming in from an external source, for example from your data flows
	in IoTa.

	The MIT License (MIT)
	Copyright © 2018 Chuan Khoo

	Permission is hereby granted, free of charge, to any person obtaining
	a copy of this software and associated documentation files (the
	"Software"), to deal in the Software without restriction, including
	without limitation the rights to use, copy, modify, merge, publish,
	distribute, sublicense, and/or sell copies of the Software, and to
	permit persons to whom the Software is furnished to do so, subject to
	the following conditions:

	The above copyright notice and this permission notice shall be included
	in all copies or substantial portions of the Software.

	THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
	OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
	FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
	THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR
	OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
	ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
	OTHER DEALINGS IN THE SOFTWARE.
*/

// set up a timer that can 'manage' the updating of our variable that we wish to 'smooth'
// check out the updateDataVar function - because this is where all of the data smoothing action happens
// the smaller the interval is (50), the smoother + faster the transition will be
Timer updateDataTimer(50, updateDataVar);

// we declare newVar as 'volatile' because it is a variable that is actively being changed from the Particle cloud (via our ParticleFunc node)
volatile int newVar = 0;
int myVar = 0;

// set a value to increment the variable by.
// in this case, we are using integers (whole numbers), so the minimum increment will be 1.
// the larger this is, the faster the transition too
int incre = 1;


void setup() {
    Serial.begin(9600);

    // register a function with the Particle cloud, so you can call this function using the ParticleFunc node in your flows
    Particle.function("newData", newData);
    delay(2000);

    // start the timer to keep updating the data smoothing!
    updateDataTimer.start();
}


void loop() {
    // nothing to do here (except add your other code to read sensor readings, for example)
}


////////////

int newData(String command) {
    // assume for this example that we have a Particle flow setup to send a string containing just a single value ("91")

    // ready to transition to this new value
    newVar = atoi(command);

    // return a 1 back to ParticleFunc, to say we are 'good'
    return 1;
}


void updateDataVar() {
    // here is the very simple algorithm used for linear traversal

    // find how how far we are away form target value
    int delta = myVar - newVar;

    // check if absolute (positive) value of delta is larger than incre
    if(abs(delta) >= incre) {
        if(newVar < myVar) {
            myVar -= incre;
        } else if(newVar > myVar) {
            myVar += incre;
        }
    } else {
        // we are too 'near' the target value but the size of incre means we will oscillate just above/under the target value!
        // we don't want that, so this else condition catches that (delta < incre) and sets the final value immediately
        // this is a lot more noticeable if you use a very large value for incre
        myVar = newVar;
    }

    Serial.println(myVar);
}