[solved] Aux1 SOC% in local app incorrect

[cybermaus]

Hi

so far, I did all the configuring on the Classic Panel itself

I did look at the local app, but had not entered the unlock serial, so it was grayed out. I did noticed the grayed out values were 'funny' set at 9 and 9, but did not worry about it.

Until yesterday the SOC% high on reset itself from 99% to 90%.
Not sure why. Today I set them back to 50% for off and 99% for on. And I wrote down the serial number.

As I now unlock the local app, I see it has values 10 and 10 for SOC% off and on.
That is damn scary. And incorrect. I *definitely* set it back to 50% and 99% on the panel and pressed enter. I sure do hope the local app did not write it to 10%, because that is WAY to low.

I guess I have to drive back to the boat to check, this is not something I can ask of my brother in law.


Using release 1759 BTW

[Halfcrazy]

So did you set the initial settings on the MNGP and pressed Enter to save and then before unlocking the Local App you found it again on the MNGP wrong? Trying to get a handle on the issue so I can try to recreate it

Ryan

[cybermaus]

No I did not yet found it on the MNGP. not wrong or right. I need to drive back to the boat for that.
I set it on the MNGP, definitely pressed enter, drove home, unlocked the local app, and saw it state 10/10

Even if I would have forgot to press enter on the MNGP, it was set to 50/90 before (which is also already incorrect) and I would never have put 10/10 in there. And I am 100% sure I did press enter.

I did not press any up or down button in the local app, did not enter a single value in there other then the unlock code.

I'll step into the car now.

[Halfcrazy]

Ok my guess is it is a bug in the local app and it is not reading it correct. Keep us poste

[cybermaus]

Well, the good news is the actual setting on the actual midnite is still 50/99
So I do not need to worry about batt going down to 10%

The less good news is, now the classic is not reachable anymore from local app. It still pings on the IP, but the local app cannot find it.
This was normal all through last year when we were running firmware about february 2013. Normal resolution is completely power down the classic (disconnect both PV and Batt) I did not even bother to always do that.

But I had sort of hoped it would have been solved with the update, as some updates last year were about the network stack.
But it seems that the locking up of the TCP stack and/or modbus stack is still there.

[TomW]

The less good news is, now the classic is not reachable anymore from local app. It still pings on the IP, but the local app cannot find it.
But I had sort of hoped it would have been solved with the update, as some updates last year were about the network stack.
But it seems that the locking up of the TCP stack and/or modbus stack is still there.

That is curious. I thought that was fixed awhile back. I used to see that regularly but not for a couple updates?

Might be back to odd hardware combinations causing it. That was a thought in the early days of this issue.

Hope you get it sorted. Using 1758 here.

Tom

[Resthome]

While I have not seen the local app / Classic network lock up with 1779. The continuing network disconnect are still there for me and have never been resolved as far as I know they were blamed on the Adobe Air network stack that was was being used by the local app.

[TomW]

While I have not seen the local app / Classic network lock up with 1779. The continuing network disconnect are still there for me and have never been resolved as far as I know they were blamed on the Adobe Air network stack that was was being used by the local app.

John;

Frankly, I only use the Local App to occassionally reconfigure the Classic and check things when folks post questions. I exclusively use RossW's application to read Classic data. So that bypasses Adobe problems.

Just from here.

Tom

[Resthome]

John;

Frankly, I only use the Local App to occassionally reconfigure the Classic and check things when folks post questions. I exclusively use RossW's application to read Classic data. So that bypasses Adobe problems.

Just from here.

Tom

It is more a nuance that a major problem as it auto goes back and connects, but the disconnect message is there to let you know the disconnect occurred and you have to go back and click on the connect to reopen the app and then go back to the where ever you were at the time of the disconnect. It appears to be short lived and does not lock up.

I guess RossW's solution would be a alternative.

[zoneblue]

I doubt the network stack timeout issue has been fixed. Andrew said it was on a long list, last i heard.  Here, ive worked around it by maintaining a single open newmodbusd connection, where the symptoms dont manifest. So sadly im no longer a canary for the issue.

[cybermaus]

Well, I played a bit, have a theory of what happened, but could not reproduce it.

First the important bit: Local app vs Aux1 SOC% settings (as in the title of this thread): The actual settings remained 50%/99% on the NMGP. They also remained 10/10 on the local app trhoughout all my further testing. That means I do not trust the local app for *any* settings, so I even removed the unlock code from the local app to avoid mistakes.


Then the TCP/IP monitoring lockup, which I consider annoying but less critical:

I made the Classic powerless, and restarted. The local app connected again. HOWEVER, it seems you can only connect one local app at the time. If the PC had it, the Android app did not connect. If the Android app had it, the PC did not connect.

And this I think is a hint as to why it locked up: at home the local app was running on my own PC when I jumped into the car and drove to the boat. From where I connected using my brother-in-law's PC.

The PC at home did not close the local app, but it did go to sleep after 30 minutes or so. I suspect that somehow because it did not properly close the TCP socket but became unresponsive from the PC side (PC went to sleep) the Classic was stuck to that one link, and would not accept another link.

[TomW]

Then the TCP/IP monitoring lockup, which I consider annoying but less critical:

I made the Classic powerless, and restarted. The local app connected again. HOWEVER, it seems you can only connect one local app at the time. If the PC had it, the Android app did not connect. If the Android app had it, the PC did not connect.

And this I think is a hint as to why it locked up: at home the local app was running on my own PC when I jumped into the car and drove to the boat. From where I connected using my brother-in-law's PC.

The PC at home did not close the local app, but it did go to sleep after 30 minutes or so. I suspect that somehow because it did not properly close the TCP socket but became unresponsive from the PC side (PC went to sleep) the Classic was stuck to that one link, and would not accept another link.

This "one device access at a time" issue is known limitation for the Classic. That is why I read the Classic data and feed that to my own display pages.

Bottom line is you can only access a Classic directly with one device at a time.

Tom

[cybermaus]

Yes, but that is not the point I am making. The point is, it may provide a clue as to why it locked up.

[Resthome]

Yes, but that is not the point I am making. The point is, it may provide a clue as to why it locked up.

Could be a clue. As I only access the Classic with one device using the Local App and I do not ever remember having a lockup where I had to power down the Classic to get Ethernet communication going again. Just my $.02

[TomW]

Yes, but that is not the point I am making. The point is, it may provide a clue as to why it locked up.

Could be a clue. As I only access the Classic with one device using the Local App and I do not ever remember having a lockup where I had to power down the Classic to get Ethernet communication going again. Just my $.02

Which seems to show that we are often not comparing apples to apples and more information is always better than less.

I think multiple, back to back attempts to connect to the Classic appear to be a big factor in the past lockups.

Anyway, All I know is what I observe and those lockups have pretty much gone away as near as I can tell here. They used to be daily.

Sorry to the original poster but we seem to have gone on a topic drift here.

I'm done.

Tom