emonVs voltage(s)

Getting Started
21

Is that plus only the voltage not updating pointing to a damaged emonCMS?

22

Yes something is definitely amiss, might be worth writing the SD card image again if an update does not magically fix it…

23

My thinking is, how can it not update the voltage at the same time unless something has got knocked off the command or more likely corrupted part of the command so that the voltage is rejected?

24

Ah, THank You! Thats what I was hoping to try - yep, both of those work and have fixed the issue… Of course that means I cant reproduce what was previously going on to debug for you any further…

Oh… Having said that, I just clocked that in the inputs I had previously there was a “Vrms” value that was being updated - that’s now ceased to be sent now the V1-V3 values are coming. Is that indicative of an older / different firmware on the micro?

25

Yes that’s right it’s V1, (V2 & V3 if 3-phase) in the latest firmware version.

26

Ah cool, that makes sense - I guess must be a mismatch between what the programmed emonhub anticipated vs what the avr provided?

27

Hi Trystan,

I’m also getting that same error when trying to run the serial config. Digging into the code it’s a valid error Admin::runService() has been defined as a private function, but its called from functions in a global scope i.e. its a non public method trying to be used from public scope. Looking in github, it looks like this is a change you made a month ago :

If I back out this part of the change, it works OK i.e. in Modules/admin/admin_model.php define as :

    public function runService($script, $attributes) {

I was about to submit a PR for this fix but looks like someone created one yesterday :

28

Thanks @pev , merged