Open Source Android App available on Google Play

Started by Graham, October 19, 2014, 11:29:58 AM

Previous topic - Next topic

Graham

Quote from: Muskoka on January 06, 2015, 11:27:51 AM
I'm not seeing any of the issues Kurt is. SOC screen works just fine, in Amps, or Watts. The readings are correct. Amp readings are in whole numbers, fine with me. Are we supposed to see 10th's?

Glen

It's because I was not using the absolute value to set the gauge scale, since Kurt's reading was minus 142 W, it didn't bump up the scale,
I wish the connection issue was as easy to fix!



Off-Grid Island cottage, Lac Simon QC Canada
370 Ahrs @ 24V (4 8L16 batteries)
4 x 250watt panels on dual axis trackers http://tinyurl.com/hfpkgr5
Classic 150, Whizbang Jr.
Android Monitor: http://tinyurl.com/lomzq3s

Graham

I put another update in the dropbox folder with a few more fixes

fixed SOC power/current gauge auto scale when value is negative
SOC power/current gauge now has 1 decimal precision
Power tab Battery current is the current coming out of the classic, SOC tab current is the whizbang +/- current to the battery
Updated modbus TCPTransaction to resync TXID


Graham.
Off-Grid Island cottage, Lac Simon QC Canada
370 Ahrs @ 24V (4 8L16 batteries)
4 x 250watt panels on dual axis trackers http://tinyurl.com/hfpkgr5
Classic 150, Whizbang Jr.
Android Monitor: http://tinyurl.com/lomzq3s

offgridQLD

#32
This  latest update fixed all the  small soc/power current tab display issues. :)

Though for me anyhow after trying this latest update . It went back to the old issue of not showing the classics name just dispays (demo) where the classics name should be.Edit: just reloaded the app and gave it 5 min now it is showing the classics name :)

Dropout issue still the same . I need to try the app on the local network at the location.

Kurt
Off grid system: 48v 16x400ah Calb lithium, Pv array one  NE facing  24 x 165w 3960w, Array two NW facing 21 x 200w 4200w total PV 8200w. Two x Classic 150,  Selectronic PS1 6000w inverter charger, Kubota J108 8kw diesel generator.

Graham

Quote from: offgridQLD on January 06, 2015, 04:57:40 PM
This  latest update fixed all the  small soc/power current tab display issues. :)

Though for me anyhow after trying this latest update . It went back to the old issue of not showing the classics name just dispays (demo) where the classics name should be.Edit: just reloaded the app and gave it 5 min now it is showing the classics name :)

Dropout issue still the same . I need to try the app on the local network at the location.

Kurt

I put another update in dropbox, could you let me know if it's better, the same or worse?

In this latest build I updated the modbus library to the latest version that is supposed to better handle transaction Id's out of sequence. Plus I'm now caching the day and hour logs when you first connect, you should see a 'toast' popup saying the logs have been read several seconds after connecting. The cache expires after an hour for the hour log and at midnight for the day log.

+ when a new device is detected in the nav bar, it is not clickable until the entry gets updated with the controllers name, this should avoid you getting the 'Demo' mode which is the default when it can't figure out what kind of controller it is (like when I'm using my modbus simulator on a pc)

Using wireshark to monitor the tcp traffic, I find the classic to be less forgiving than the modbus simulator on a pc. The android O/S will favour the UI thread over the background threads as to give the user a smooth rendering of the display, normally the background modbus service thread will send out a modbus Register read request, get a reg reply from the classic, then it sends back an acknowledgment and repeats...
when you slide the tabs around the O/S puts more priority on the UI thread and that's when i sometimes see a delay in the final acknowledgement then things can go wrong. most of the time the classic will resend the last reply and get another ack and things are back to normal but once in a while the classic stops accepting any new requests, my app will try 3 more times then will close the tcp socket and attempt to reconnect which may work but sometimes gets refused for 30 seconds then finally reconnects.

+ if you see a big sine wave in the hour chart, that's the test pattern due the the logs transfer failing to complete, not sure if it's related to the issue above or something else but I'll keep looking...


thanks for the help
Graham.
Off-Grid Island cottage, Lac Simon QC Canada
370 Ahrs @ 24V (4 8L16 batteries)
4 x 250watt panels on dual axis trackers http://tinyurl.com/hfpkgr5
Classic 150, Whizbang Jr.
Android Monitor: http://tinyurl.com/lomzq3s

offgridQLD

#34
Graham,
              I have been using the latest version of your App over the weekend on location over my local network. Reading your last post on this thread + your post on the (More robust Ethernet communication) helped a lot in explaining some behavior.

Particularly how  3 tabs or views in memory at any time and any more requires a small break while the data is loaded (Good to know that's normal behavior) :)

Identifying classics by name (shed) (house) is working great now. Though I do have a question. What is the little yellow triangle with a explanation mark in the center? I see it some times in the Network tab to the right of the classic names.

I have turned off/disabled (NET access) at the classic. Just to prove (Mymidnite) requests wasn't contributing to any issues regarding the resets, not that I thought it was but just to satiny others concerns.

Personally I don't mind the odd loss off connection or brief break for data to load or reload. As long as it can recover by it's self shortly after. Though triggering the classics to reset and start out in bulk charge again as if it's a new day again. Along with loosing the tally of KWH's for the day is something I am concerned about. As it's a little more serious and a pain messing up your logged logged for the day.....Not blaming this app for this as I know it's a wide spread classic issue I experience the same issue on  local App to if I mess about viewing the offline data windows.

I will keep playing around and see what I find. Thanks for a great app.

Kurt

Off grid system: 48v 16x400ah Calb lithium, Pv array one  NE facing  24 x 165w 3960w, Array two NW facing 21 x 200w 4200w total PV 8200w. Two x Classic 150,  Selectronic PS1 6000w inverter charger, Kubota J108 8kw diesel generator.

ClassicCrazy

#35
Graham 
Was just checking out the latest version that was updated from the Play Store. Looks great -  I  really like all the dial gauges and how you sweep from one screen to the other. Only thing I had to remember was to shut Local Status App off since only one device can work at a time . After I did that my android phone connected right up. Will give this a look tomorrow in the day light when there is some action from the panels ( hopefully ) .

My FET reads 6553.2 C on gauge needle pegged at 100  and Battery temperatures are reading 6542.7 degrees needle pegged at 100 also. Readings on MNGP are FET -0.4 and Battery -10.9 .  PCB temp looks reasonable though same as on MNGP  12.8.  Do you think the negative temps mess  up something in your software and that is why it reads 6500+ C ?

I also like the power meter switch with a tap from amps to watts .

You did a great job on this  Thank you for your efforts!
system 1
Classic 150 , 5s3p  Kyocera 135watt , 12s Soneil 2v 540amp lead crystal for 24v pack , Outback 3524 inverter
system 2
 5s 135w Kyocero , 3s3p 270w Kyocera  to Classic 150 ,   8s Kyocera 225w to Hawkes Bay Jakiper 48v 15kwh LiFePO4 , Outback VFX 3648 inverter
system 3
KID / Brat portable

Halfcrazy

Changing the way wind turbines operate one smoke filled box at a time

Graham

Quote from: offgridQLD on January 10, 2015, 07:34:57 PM

Identifying classics by name (shed) (house) is working great now. Though I do have a question. What is the little yellow triangle with a explanation mark in the center? I see it some times in the Network tab to the right of the classic names.


The triangle next to the device name will indicate that the controller is not reachable, as an example, when you are out of wifi range but for now it turns on a soon as the app gets a connection drop/reconnect and remains on until you restart the app. Once this issue gets resolved, I'll put it back to indicating 'reachable/ pingable'.
+ you can slide the item to the right to delete it, this will erase the stored log cache files for the controller, a new entry should appear a few seconds later, the logs will reload the next time you open it


I've been running a bunch of test with the service thread set at different priority levels to see if that had any affect on the connection dropout but, so far, I still see some reconnects regardless of the priority levels. I put the .pcap wireshark files in the dropbox area if anyone is interested. https://www.dropbox.com/sh/4ruj40a3ztcsyw6/AADlPafYWZ-PV5VtBoQdCohUa?dl=0


Graham.
Off-Grid Island cottage, Lac Simon QC Canada
370 Ahrs @ 24V (4 8L16 batteries)
4 x 250watt panels on dual axis trackers http://tinyurl.com/hfpkgr5
Classic 150, Whizbang Jr.
Android Monitor: http://tinyurl.com/lomzq3s

Graham

Quote from: ClassicCrazy on January 11, 2015, 02:05:00 AM
Graham 

My FET reads 6553.2 C on gauge needle pegged at 100  and Battery temperatures are reading 6542.7 degrees needle pegged at 100 also. Readings on MNGP are FET -0.4 and Battery -10.9 .  PCB temp looks reasonable though same as on MNGP  12.8.  Do you think the negative temps mess  up something in your software and that is why it reads 6500+ C ?



You would think I could have found that bug early on given the fact I'm from Canada ;)
thanks for finding it, I'll post an update soon.
Off-Grid Island cottage, Lac Simon QC Canada
370 Ahrs @ 24V (4 8L16 batteries)
4 x 250watt panels on dual axis trackers http://tinyurl.com/hfpkgr5
Classic 150, Whizbang Jr.
Android Monitor: http://tinyurl.com/lomzq3s

Graham

Quote from: Halfcrazy on January 11, 2015, 09:26:52 AM
Where is the current app? Can I download it?

I published version 2.0.2 to google play yesterday, it can take up to 24 hrs to propagate to google's servers

I have 3 apk files in my dropbox folder https://www.dropbox.com/sh/4ruj40a3ztcsyw6/AADlPafYWZ-PV5VtBoQdCohUa?dl=0

the only difference with each file is the modbus service thread priority level, the 'normal_priority' one is what is in google play.
Off-Grid Island cottage, Lac Simon QC Canada
370 Ahrs @ 24V (4 8L16 batteries)
4 x 250watt panels on dual axis trackers http://tinyurl.com/hfpkgr5
Classic 150, Whizbang Jr.
Android Monitor: http://tinyurl.com/lomzq3s

ClassicCrazy

Quote from: Graham on January 11, 2015, 09:42:46 AM
Quote from: ClassicCrazy on January 11, 2015, 02:05:00 AM
Graham 

My FET reads 6553.2 C on gauge needle pegged at 100  and Battery temperatures are reading 6542.7 degrees needle pegged at 100 also. Readings on MNGP are FET -0.4 and Battery -10.9 .  PCB temp looks reasonable though same as on MNGP  12.8.  Do you think the negative temps mess  up something in your software and that is why it reads 6500+ C ?



You would think I could have found that bug early on given the fact I'm from Canada ;)
thanks for finding it, I'll post an update soon.

Yes - pretty sure it is caused by negative temperature since this morning one temperature was above zero and the app and MNGP temperature were the same but the other temperature that was negative was still goofy .
system 1
Classic 150 , 5s3p  Kyocera 135watt , 12s Soneil 2v 540amp lead crystal for 24v pack , Outback 3524 inverter
system 2
 5s 135w Kyocero , 3s3p 270w Kyocera  to Classic 150 ,   8s Kyocera 225w to Hawkes Bay Jakiper 48v 15kwh LiFePO4 , Outback VFX 3648 inverter
system 3
KID / Brat portable

ClassicCrazy

Graham
Playstore had a new version it sent down to me yesterday . I have my settings so Playstore doesn't automatically update apps so I know when new ones come in - notifies me they are available first.

I can't find anywhere in your app that tells what version it is . Am I missing that somewhere ?
Larry
system 1
Classic 150 , 5s3p  Kyocera 135watt , 12s Soneil 2v 540amp lead crystal for 24v pack , Outback 3524 inverter
system 2
 5s 135w Kyocero , 3s3p 270w Kyocera  to Classic 150 ,   8s Kyocera 225w to Hawkes Bay Jakiper 48v 15kwh LiFePO4 , Outback VFX 3648 inverter
system 3
KID / Brat portable

ClassicCrazy

I also like how the dial gauges automatically scale - that is great.
system 1
Classic 150 , 5s3p  Kyocera 135watt , 12s Soneil 2v 540amp lead crystal for 24v pack , Outback 3524 inverter
system 2
 5s 135w Kyocero , 3s3p 270w Kyocera  to Classic 150 ,   8s Kyocera 225w to Hawkes Bay Jakiper 48v 15kwh LiFePO4 , Outback VFX 3648 inverter
system 3
KID / Brat portable

Graham

Quote from: ClassicCrazy on January 11, 2015, 02:11:46 PM
Graham
Playstore had a new version it sent down to me yesterday . I have my settings so Playstore doesn't automatically update apps so I know when new ones come in - notifies me they are available first.

I can't find anywhere in your app that tells what version it is . Am I missing that somewhere ?
Larry


I will be adding the release version info in the about area starting at 2.0.3, the latest on google play is 2.0.2
for now you can go the android settings under apps find the classic, click it and you should get the App Info, the version is under the title of the app


Graham.
Off-Grid Island cottage, Lac Simon QC Canada
370 Ahrs @ 24V (4 8L16 batteries)
4 x 250watt panels on dual axis trackers http://tinyurl.com/hfpkgr5
Classic 150, Whizbang Jr.
Android Monitor: http://tinyurl.com/lomzq3s

ClassicCrazy

Updated my Android phone to 5.0 Lollipop and Cyangenmod 12 and the app is working great ! I turned on some big loads and see how much power I could squeeze out of my 2700 watt array on this sunny cold day
Attached is screen shot .

system 1
Classic 150 , 5s3p  Kyocera 135watt , 12s Soneil 2v 540amp lead crystal for 24v pack , Outback 3524 inverter
system 2
 5s 135w Kyocero , 3s3p 270w Kyocera  to Classic 150 ,   8s Kyocera 225w to Hawkes Bay Jakiper 48v 15kwh LiFePO4 , Outback VFX 3648 inverter
system 3
KID / Brat portable