..another suggestion

[dgd]

If there are going to be some software development resources coming available soon what about not bothering with further local app updates and just proceeding to sorting out a web interface in the Classic?

dgd

[zoneblue]

Robin said, not that long ago, that this wasnt going to happen after all. (back during Kid release discussion). Something about not enough resources on board the current hardware, and that future hardware (by that i imagined he meant their inverters) would have webservers. But i also heard him mention something about a Classic 3. Thats a mystery?

[dgd]

I must have missed that.
I also heard the insufficient hardware resource argument before but the door was left open that there could be sufficient to permit a web interface - the resource was memory.

Now that the concept of input device targeted firmware has been mentioned for the KID, albeit for commercial and maybe marketing reasons, could the same concept not be applied to the Classic?
I wonder what % of Classics are used only for PV input? I suspect it is very high.
So could the non PV applications have their own version of firmware?
Separating these PV and other functions should not really impact the classic's ability unless there is a future application where hybrid input from perhaps PV and wind is a possibility.

Then the firmware could be slimmed down and perhaps release a significant portion of memory resource to permit some form of web interface to be included?

dgd

[Westbranch]

dgd, I remember vaguely that comment and seems it was on the far back burner as there was/is a lot of development work in play, the wind turbine, Brat, Kid, Inverter, Kid Clipper, etc ... and not enough engineers... or time...

[dgd]

Wb, Yes I think your recall is good, can't help thinking what might have been with Classic data easily accessed by just about any computer, tablet, cellphone etc..
dgd

[zoneblue]

dgd, blackbox is really the here and now solution for this. For 50 odd bucks and couple hours of your time all your dreams come true. Im looking forward to doing some more work on the interface. Now that the newmodus daemon is up and running,  that increases the resolution of the data significantly. Not to mention the stability... Ill have some more code up soon.

[dgd]

Hmmmm, not sure the blackbox is a realistic solution.
I have not had a problem extracting modbus data as I needed it and have my own reporting/monitoring prgram running on an Eeeepc/Linux

I was thinking more from a MN product viewpoint
Web access to an ethernet connected device is now an expectation of every computer user.
Every time I look at the web reporting and setup/config on my Linksys router that is an example of what the Classic should be doing.

dgd

[Westbranch]

Hi dgd, there i only one hiccup with your statement about every user it  includes the assumption that everyone has an internet connection.   Though I would dearly like to have that kind of access, I do not want to  leave on a bunch of parasitic loads just to be able to monitor my system from afar. 

In addition I would have to drive > 250 km from our place in order to get cell service and then lose it as I head for the big smoke.  Too bad that the whole world is not yet covered by cell service.

[Rybren]

I'm in the same boat as Westbranch - no service at the camp.

[dgd]

Wb, you are right in that remote monitoring without internet or cell coverage is near impossible.
I was just thinking that on my LAN, even if it was not on internet, then using my Ipad's browser to connect to Classic would be a neat solution. I never bothered with home computers or notebooks/laptops since the Ipad release. We have several here that seem to do all the computing tasks we need. I had to buy a notebook running W7 then W8 just to deal with the Classic, firmware updates, local app etc..
dgd

[zoneblue]

You wont get much argument from me there. Maybe we'll just have to see what hapens to the next generation of classic. Look at it this way, it will be something to look forward to...