Undeclared meaasage

[PeteKnight]

You’re declaring Irms1 and Irms2 as Double precision integers inside your void loop.
This makes these variables LOCAL to your void loop and therefore invisible within the rest of your code.
Hence the message that these variables were undeclared within the scope of the myTimerEvent function.

The solution is to declare these variables near the top of your code (not within a function) then assign the readings to these variables without re-declaring them. This means dropping the Double from the start of these lines of code…

@ocsum

 double Irms1 = emon1.calcIrms(2280);  // Calculate Irms only
  double Irms2 = emon2.calcIrms(2280);  // Calculate Irms only

However, your sketch has other issues…

You have a timer set-up to cal the sendSensor function once per second…

@ocsum

timer.setInterval(1000L, sendSensor);

But you don’t have a function called sendSensor so you’ll get a compilation error.

You do have a function called myTimerEvent, but there is no timer set-up to call this function, so it will never execute.

Also, the code that takes these readings and assigns the results to the Irms1 and Irms2 variables is in your void loop. This isn’t good practice as far as Blynk is concerned, and it should really be in a function that is called with a timer (myTimerEvent once it’s actually being called, or renamed as sendSensor).

It’s not clear what your virtual pin question is, but maybe reading this would help…

Using Virtual Pins to control physical devices

I thought I’d write a guide about how to use virtual pins with app widgets such as buttons, to control physical devices such as relays, LEDs etc… Why use virtual pins anyway? I’d always recommend using virtual pins over physical pins when developing your code. There are a number of reasons, but here are what I consider to be the main ones: Virtual pins are hardware independent. This means that it’s far easier to port your code from one hardware platform to another in future (when you realise…

Pete.