Kilowatt hours still not correct

[qrper]

Running newest firmware for both MNGP2 and Rosie

I saw 10.5 kWh and I think 11 kWh.

Next time I checked, the kWh meter reset back to zero.

So starting over a 0.00 kWh.

mike

[boB]

You sure that it didn't just reset because it was another day ?

Not sure myself if there is supposed to be another kW-Hour display for total energy.

[qrper]

You sure that it didn't just reset because it was another day ?

Not sure myself if there is supposed to be another kW-Hour display for total energy.

boB,
The re-set happened around 2pm...

I checked the clock and it was an hour out of whack... reset the MNGP2 and re-set the time.

Are you telling me that kWh meter is only daily with a re-set at midnight? I was hoping it would be like an odometer on the family buick—a lifetime running total of kWh produced.
Will let you know if a re-set happens in the middle of the day.

Mike

[boB]

There should be BOTH a trip meter and an odometer and they system should keep both of those values.

But resetting in the afternoon should not be happening.

First though you have to set the time in the MNGP2 and that might help the resetting at 2PM

Internally the total kW-Hours I think are held but there may not be a display for it yet.

There are newer MNGP2 firmwares we are working on that may do what you want but just isn't out.

I will ask around.

boB

[Wizbandit]

I just checked in my setup. dev 0x2b is HAWKES BAY and 0x2c is BARCELONA (dual MPPT)
The registers have not been populated yet so there is still some code to be written.
4 Bytes for Watt-hours and 4 bytes for Amp-hours.

0x023 DC Lifetime Cumulative Stream 10s [Wh X10]32 [Ah X10]32

reg_num[0x023] dev_type[0x2b] idx[0x01] bid[0x01] [8] 00 00 00 00 00 00 00 00
reg_num[0x023] dev_type[0x2c] idx[0x01] bid[0x03] [8] 00 00 00 00 00 00 00 00
reg_num[0x023] dev_type[0x2c] idx[0x02] bid[0x03] [8] 00 00 00 00 00 00 00 00

[qrper]

I just checked in my setup. dev 0x2b is HAWKES BAY and 0x2c is BARCELONA (dual MPPT)
The registers have not been populated yet so there is still some code to be written.
4 Bytes for Watt-hours and 4 bytes for Amp-hours.

0x023 DC Lifetime Cumulative Stream 10s [Wh X10]32 [Ah X10]32

reg_num[0x023] dev_type[0x2b] idx[0x01] bid[0x01] [8] 00 00 00 00 00 00 00 00
reg_num[0x023] dev_type[0x2c] idx[0x01] bid[0x03] [8] 00 00 00 00 00 00 00 00
reg_num[0x023] dev_type[0x2c] idx[0x02] bid[0x03] [8] 00 00 00 00 00 00 00 00

I noticed that the counters seem to work for longer than 24 hours. Monday, I had produced 15kWh and tuesday morning, the counter said 20ish kWh. So no rest at midnite. However, this Wednesday morning, I'm back at 4.7kWh. Tuedsay night, the counter was 28.8kWh.

Not that it makes any difference, I wonder if the counter is reset by time or total kWh product or a combination of the two. It will be great to have a running odometer of kWh produced.

Mike

[boB]

I just checked in my setup. dev 0x2b is HAWKES BAY and 0x2c is BARCELONA (dual MPPT)
The registers have not been populated yet so there is still some code to be written.
4 Bytes for Watt-hours and 4 bytes for Amp-hours.

0x023 DC Lifetime Cumulative Stream 10s [Wh X10]32 [Ah X10]32

reg_num[0x023] dev_type[0x2b] idx[0x01] bid[0x01] [8] 00 00 00 00 00 00 00 00
reg_num[0x023] dev_type[0x2c] idx[0x01] bid[0x03] [8] 00 00 00 00 00 00 00 00
reg_num[0x023] dev_type[0x2c] idx[0x02] bid[0x03] [8] 00 00 00 00 00 00 00 00

I noticed that the counters seem to work for longer than 24 hours. Monday, I had produced 15kWh and tuesday morning, the counter said 20ish kWh. So no rest at midnite. However, this Wednesday morning, I'm back at 4.7kWh. Tuedsay night, the counter was 28.8kWh.

Not that it makes any difference, I wonder if the counter is reset by time or total kWh product or a combination of the two. It will be great to have a running odometer of kWh produced.

Mike

Mike,  The kW-Hours are reset at midnight.

Which firmware/software version is your Rosie running ?

There will be newer firmware coming that may fix part of this ?

boB

[qrper]

I just checked in my setup. dev 0x2b is HAWKES BAY and 0x2c is BARCELONA (dual MPPT)
The registers have not been populated yet so there is still some code to be written.
4 Bytes for Watt-hours and 4 bytes for Amp-hours.

0x023 DC Lifetime Cumulative Stream 10s [Wh X10]32 [Ah X10]32

reg_num[0x023] dev_type[0x2b] idx[0x01] bid[0x01] [8] 00 00 00 00 00 00 00 00
reg_num[0x023] dev_type[0x2c] idx[0x01] bid[0x03] [8] 00 00 00 00 00 00 00 00
reg_num[0x023] dev_type[0x2c] idx[0x02] bid[0x03] [8] 00 00 00 00 00 00 00 00

I noticed that the counters seem to work for longer than 24 hours. Monday, I had produced 15kWh and tuesday morning, the counter said 20ish kWh. So no rest at midnite. However, this Wednesday morning, I'm back at 4.7kWh. Tuedsay night, the counter was 28.8kWh.

Not that it makes any difference, I wonder if the counter is reset by time or total kWh product or a combination of the two. It will be great to have a running odometer of kWh produced.

Mike

Mike,  The kW-Hours are reset at midnight.

Which firmware/software version is your Rosie running ?

There will be newer firmware coming that may fix part of this ?

boB

Running the latest and greatest that Ryan uploaded the other day. I did end up bricking my MNGP2, but thank to a second upload with a different file name, was able to recover the display.
Mike

[boB]

Running the latest and greatest that Ryan uploaded the other day. I did end up bricking my MNGP2, but thank to a second upload with a different file name, was able to recover the display.
Mike

Yes, that sucks but at least there was a way around it.

[qrper]

Running the latest and greatest that Ryan uploaded the other day. I did end up bricking my MNGP2, but thank to a second upload with a different file name, was able to recover the display.
Mike

Yes, that sucks but at least there was a way around it.

I sure would like to see a way for the uploader to allow you to retrieve and reload the last firmware update, just for when the code bricks something. For example:

If I uploaded 10.20.01 and it locked my device, I'd like a pathway to download 10.10.00 (the last version) to at least get back on line.

As is it now, you're one and done. I'm no coder, and I know your folks are up to their elbows in software project right now, but that needs to be looked into.

Mike

[ClassicCrazy]

I am sure they are working on it Mike.
At least to let you re-upload the same code which is what the fix was for you and me.
I wouldn't call that bricking a device. It was just a glitch. Bricking in the traditional sense would mean that it was dead for good. Since the MNGP2 had bluetooth communications and accepted upload of firmware it was nowhere near "bricked". It was just stuck on the first MNGP2 screen for whatever reason.
Larry   

[qrper]

I am sure they are working on it Mike.
At least to let you re-upload the same code which is what the fix was for you and me.
I wouldn't call that bricking a device. It was just a glitch. Bricking in the traditional sense would mean that it was dead for good. Since the MNGP2 had bluetooth communications and accepted upload of firmware it was nowhere near "bricked". It was just stuck on the first MNGP2 screen for whatever reason.
Larry   

Yeah, 'bricked' was perhaps a bit much. I wasn't able to tell tech support exactly what happened, other than it was lock up on the splash screen. That's when he said it sounded like it got bricked... so it came home with me.

Were you able to figure out what went fubar? Were we the only two that had issues?

mike

[ClassicCrazy]

Mike,
Far as I know we are the only two who that happened to. Hard to say. Since these new firmwares are beta , we are beta testers and should expect some failures. When I have things like that happen I contact Ryan and he gets back to me quickly. He is the one releasing these so is the one who should know right away. He just said that he had seen that happen and reloading it fixed the issue. But the fact that the beta updater wouldn't allow the same new firmware to be reloaded was the bug. That is the first thing I would have tried after it didnt' work right.
Even when the MNGP2 was stuck on that screen, I checked and my Hawkes Bay controller was still operating okay . All is well that ends well.
Larry

[qrper]

Mike,
Far as I know we are the only two who that happened to. Hard to say. Since these new firmwares are beta , we are beta testers and should expect some failures. When I have things like that happen I contact Ryan and he gets back to me quickly. He is the one releasing these so is the one who should know right away. He just said that he had seen that happen and reloading it fixed the issue. But the fact that the beta updater wouldn't allow the same new firmware to be reloaded was the bug. That is the first thing I would have tried after it didnt' work right.
Even when the MNGP2 was stuck on that screen, I checked and my Hawkes Bay controller was still operating okay . All is well that ends well.
Larry

I agree. Had the uploader allowed me to re-load the current version or the next to last one, would have saved my bacon. Like you, Rosie was online and operating when the MNPG2 froze on upgrade.
I'm always a bit hesitant when upgrading. Hell, I'm still running Word '97 on my ten year old mac... that's running system software three version behind.

I still use pcb cad software that's running on Windows '98.

Mike

[FNG]

I did find out there is a revert to factory image in the MNGP2, This will allow a stuck update to be forced all the way back to factory and allow you to update again.

To do this:
1- Power down the MNGP2 and when screen is dark wait 15 seconds.
2- Hold the back button and power on MNGP2 and continue holding back button for 15 seconds
3- MNGP2 will go through a update process and revert to the stored factory image
4- Update again using the beta app