Display given sensor data at a particular time

I’m using various sensors like temperature, humidity,etc with arduino nano and display data on phone using blynk(bluetooth).
The problem is all sensor data display at the same time. Can there be an option to display data on phone only from a particular sensor at a time?

What’s the difference between wrapping many sensors under one timer object Vs. having one timer object for each sensor?

The structure of my code is like :

//variable declarations
void setup()
{

SerialBLE.begin(9600);
Blynk.begin(SerialBLE, auth);

Serial.println(“Waiting for connections…”);

timer1.setinterval(1000L,sensor1);
timer2.setinterval(1000L,sensor2);
timer3.setinterval(1000L,sensor3);
}

void loop()
{
Blynk.run();
timer1.run();
timer2.run();
timer3.run();
}

void firstsensor()
{
int data1=analogRead(A0);
Blynk.virtualWrite(V7,data1);
}

void secondsesnor()
{
//similarly
}

void thordsensor()
{
//similarly
}
Before creating the topic

  1. Search forum for similar topics
  2. Check http://docs.blynk.cc and http://help.blynk.cc/
  3. Add details :
    • Hardware model + communication type. For example: Arduino UNO with Ethernet Shield
    • Smartphone OS (iOS or Android) + version
    • Blynk server or local server
    • Blynk Library version
    • Add your sketch code. :point_up:Code should be formatted as example below.

Simply paste your code between ``` If you don’t format your code, your topic can be deleted by moderators.


void loop()

Seems like you missed reading the instructions (still showing in your post) when creating your post… you code is not formatted properly :stuck_out_tongue_winking_eye:

Blynk%20-%20FTFC

You must be showing a form of pseudo code as your timer functions are not named the same as the actual functions

All your timers are trying to run at the exact same time every second… better to stagger them for non-simultaneous and non-converging times. eg. 1000… 1025… 1063… and so on, assuming 25ms between 1st and 2nd is enough time to complete the 1st before starting the 2nd and so on…

And as for the method of running a multi-instance timer vs multiple single instance timers… not sure, but i think the former is smaller memory footprint and more processor efficient?