The Local Application software is now available to everyone. See Andrews post below for links to the software and the manual. Let us know what you think and if there is any odd behavior.
[attachment deleted by admin]
Okay, it's ready to go.
Sorry everyone for the delay. There will be updates moving forward. Please feel free to post all your comments in this thread.
Software
http://mymidnite.com/?q=node/7 (http://mymidnite.com/?q=node/7)
Manual
http://dl.dropbox.com/u/31975941/Local%20App%20manual.pdf (http://dl.dropbox.com/u/31975941/Local%20App%20manual.pdf)
H/C, what is the minimum Operating System needed to run this app?
thanks,
ej
:-X I downloaded the first version and it worked awesome!!!
I will load the " real Version " lol when I get home and see how it works
Hope you can have a version to run on macs so I don't have to run out to the gen room to look at it. :P
( my wife already thinks I have a mistress out in the shed ;D )
I did set up using VNC so I can log into my laptop at home and see how the system is working. Keeps it secure over the internet until mymidnite is up and running.
Will be setting up the other 2 Classics this weekend on line so I can see all the units working, ( solar, wind and Lister )
Nice to have a software that works very well to see how the system is when I am not home.
You guys are doing a excellent job .... Keep up the great work.
Cheers
Danny
Danny this app does run on a Mac. I cant help you with the Wife I do understand the want to set in the shed and watch I have my Lister Clone running into a Classic now although it is no where as elegant a set up as yours.
Glad to hear you got your Lister up and running. How is it working?
I did load the new version and it does work on my mac as well. ( but I am still spending time in the shed ;D lol )
I noticed the "pre-release version" I had loaded, automatically updated when the new version was available, nice !!
Midnite,
I am having some issues. For the past 24hrs I have been unable to connect with my two classics. I have reset the router, the switch and the computer to no avail. In the status panel it says synchronizing and does not go any further. All of the indicator diodes on the switch and router are on. I will try resetting the controller and see what that does.
Cheers...
Damani
Ok, I reset both classic and it has synchronised. So problem solved. No worries.
Cheers...
Damani
Yes this is a known bug and it is in the Classic. The Classic will lose connection to the router and requires a reboot. Andrew is working on it as we speak. It only seems to happen on a very limited number of networks though. Can you give us some specs on the network like Router make and model and how many devices ar on the network etc?
Ryan
1/2,
Model number of router:
Siemens gigaset SE587 wlan dsl
I current have 2 Computers, 2 Classics and one doogle router on my network.
Anymore info required just let me know.
Cheers...
Damani
Can I Hook directly to the cassic and run the software
I can't connect. Using a Cadlepoint MBR 1000 as follows:
No WAN only using as LAN router. User login requirements are disabled so it is just a connect without prompts.
Router is 192.168.10.1
Mask: 255.255.255.0
Classic 150 was set as static: 192.168.10.100
Mask: 255.255.255.0
Gateway: 192.168.10.1
DNS: 192.168.10.1
Also tried as DHCP since I reserved the address for the classic. Under DHCP address shows the same.
In the local app I get: "Reading..." and in smaller letters to the right "Connection Closed"
Network cable tests good.
Other devices can connect to router.
I reset Classic - No Joy.
I configured port forwarding to insure port 502 is open. No Joy
Rebooted router- nothing
Deselected auto detect Classics - nothing.
Shut down and restarted everything. - Nothing.
I've now tried another router - nothing except the time it took to display "Connection Closed" took longer. I can see tx and rx data stats in the router for the Lan port the Classic is connected to.
There doesn't appear to be a way to verify what IP address the Classic really has. The menu is a configuration item' not one that shows the configuration summary unless I'm not seeing it. That would sure help since you could see if the Classic was getting an IP address and loading it. While routers will show the DHCP leases, if one doesn't exist it could be because the Classic isn't releasing an address and accepting a new lease.
Okay UPDATE:
Finally got an IP address via DHCP. For some reason the Classic will not get an IP from that router. JFYI, these are very popular 3/4G Routers. Hint hint.
The Classic got the IP:
192.168.1.3
255.255.255.0
The Local App still cannot find nor display anything from the Classic. So I rebooted everything including the Classic (last) and nothing.
I then uninstalled and reinstalled the Local App. Zilch.
And now a comment. I'm not sure why the ethernet connections on the board are placed in such a way that it takes a miracle of tool fabrication to change the cables but really. Behind the ethernet connection are jumpers, tiny, small and easily dislodged. Unless you uninstall the Classic and rip it out, getting the ethernet cables (and temp sensor cable) out is nearly impossible. Some of us do not have huge spaces to work with and in this case when you are changing cables to test...so pleeeease.
I'm going to try 2 or 3 different computers now since I have access to them. Hopefully something will work. The one I tried first is a Windows 7 machine. I also tried running the Local app as admin and in compatibility mode, no workie.
Ah, before I go deeper, tried the various compatibility modes from Win2000 all the way through Vista SP2. Nope. Windows 7 does report this as an incompatile application though. Often that means very little but since it isn't working...
Help.
Quote from: Gyroman on October 28, 2011, 09:36:35 PM
Can I Hook directly to the cassic and run the software
There is no reason why not. there would be a sample configuration:
PC side:
IP 192.168.0.1
Subnet mask: 255.255.255.0
Gateway is not needed. DNS is not needed unless Midnight is resolving names (doesn't appear so)
Classic:
IP 192.168.0.2
Subnet mask 255.255.255.0
IMPORTANT: You need to use a cross-over cable, not a regular one. Since you don't have a router or switch in between your devices, the cross-over cable is a must. While you can make them up, its just easier to buy one, they come in handy.
Quote from: Tinman on October 29, 2011, 05:34:45 PM
I can't connect. Using a Cadlepoint MBR 1000 as follows:
No WAN only using as LAN router. User login requirements are disabled so it is just a connect without prompts.
Router is 192.168.10.1
Mask: 255.255.255.0
Classic 150 was set as static: 192.168.10.100
Mask: 255.255.255.0
Gateway: 192.168.10.1
DNS: 192.168.10.1
Also tried as DHCP since I reserved the address for the classic. Under DHCP address shows the same.
In the local app I get: "Reading..." and in smaller letters to the right "Connection Closed"
Network cable tests good.
Other devices can connect to router.
I reset Classic - No Joy.
I configured port forwarding to insure port 502 is open. No Joy
Rebooted router- nothing
Deselected auto detect Classics - nothing.
Shut down and restarted everything. - Nothing.
I've now tried another router - nothing except the time it took to display "Connection Closed" took longer. I can see tx and rx data stats in the router for the Lan port the Classic is connected to.
There doesn't appear to be a way to verify what IP address the Classic really has. The menu is a configuration item' not one that shows the configuration summary unless I'm not seeing it. That would sure help since you could see if the Classic was getting an IP address and loading it. While routers will show the DHCP leases, if one doesn't exist it could be because the Classic isn't releasing an address and accepting a new lease.
Okay UPDATE:
Finally got an IP address via DHCP. For some reason the Classic will not get an IP from that router. JFYI, these are very popular 3/4G Routers. Hint hint.
The Classic got the IP:
192.168.1.3
255.255.255.0
The Local App still cannot find nor display anything from the Classic. So I rebooted everything including the Classic (last) and nothing.
I then uninstalled and reinstalled the Local App. Zilch.
And now a comment. I'm not sure why the ethernet connections on the board are placed in such a way that it takes a miracle of tool fabrication to change the cables but really. Behind the ethernet connection are jumpers, tiny, small and easily dislodged. Unless you uninstall the Classic and rip it out, getting the ethernet cables (and temp sensor cable) out is nearly impossible. Some of us do not have huge spaces to work with and in this case when you are changing cables to test...so pleeeease.
I'm going to try 2 or 3 different computers now since I have access to them. Hopefully something will work. The one I tried first is a Windows 7 machine. I also tried running the Local app as admin and in compatibility mode, no workie.
Ah, before I go deeper, tried the various compatibility modes from Win2000 all the way through Vista SP2. Nope. Windows 7 does report this as an incompatile application though. Often that means very little but since it isn't working...
Help.
TinMan
One thing to look at is how old is the firmware? Try going into the Local application and adding the Classics IP address manually and add port 3900. Or just download the latest firmware of our website.
Port forwarding and what not should not matter if you are on the local area network with the Classic.
Ryan
Quote from: Tinman on October 29, 2011, 05:34:45 PM
And now a comment. I'm not sure why the ethernet connections on the board are placed in such a way that it takes a miracle of tool fabrication to change the cables but really. Behind the ethernet connection are jumpers, tiny, small and easily dislodged. Unless you uninstall the Classic and rip it out, getting the ethernet cables (and temp sensor cable) out is nearly impossible. Some of us do not have huge spaces to work with so pleeeease.
I'm going to try 2 or 3 different computers now since I have access to them. Hopefully something will work. The one I tried first is a Windows 7 machine. I also tried running the Local app as admin and in compatibility mode, no workie.
Help.
I am surprised you are having so much trouble here but that may be a router that just has some weird way about its protocol.
So, the local app can't see the Classic on your local intranet ? I see you are pretty knowledgeable about IT stuff and still having problems so it may very well be an incompatibility with the router. Looks like you have made a bit of progress though.
I have connected a Classic directly with a PC Ethernet port so I know that it ~can~ work... It might be like you say, a crossover cable
problem, depending on the computers' ability to swap the RX-TX lines. I thought that most newer computers could do this but
I'm not sure ?
About that upside down Ethernet jack.... Sorry about that. I totally agree ! We are getting different jacks that will eventually
be used that have the the tab on the top side. What I do to get the cable out though is to use a small screwdriver to pry the tab up
on the bottom. In the office here, I just break the tab off since I'm always plugging and unplugging it.
Sorry about the problems with that, but emails have been sent and help should hopefully on the way soon. Check back in a little bit or possibly tomorrow and we'll see if we can't shed some light on this on this forum.
Thanks,
boB
PS.... I see Ryan mentioned that port 3900 thing... The Classic firmware did used to be port 3900 instead of 502. The latest firmware is on port 502 though. 3900 is a non standard modbus over IP port of course.
The Local app only auto detects Classics on port 502 so if you had an older one the app will not see it automatically.
I haven't loaded up the latest firmware yet. I get very hesitant about such things if something isn't broken. I posted some of my configuration in the Intro section. I'm using a solar panel tracker on a motorhome. Harvesting some crazy amounts thorugh the Classic. 1.7/2.0 kw and more, so it says.
I'll try the other port. That might do it. I'll report back.
Update: Port 3900 worked for a few minutes. On the status I got a Battey Temp not installed although it is there.
I will try the new firmware tomorrow. Since I just turned on the Classic 3 days ago, I guess why not.
BTW, the Classic reports over 7 kw in the last 4 days using my 3 100 watt Mono panels on my motorhome tracking system. Yeowzzzzahhhh.
Quote from: Tinman on October 29, 2011, 09:27:13 PM
Update: Port 3900 worked for a few minutes. On the status I got a Battey Temp not installed although it is there.
I will try the new firmware tomorrow. Since I just turned on the Classic 3 days ago, I guess why not.
Did you get the direct Ethernet connection to work ?
Quote from: Tinman on October 29, 2011, 09:27:13 PM
BTW, the Classic reports over 7 kw in the last 4 days using my 3 100 watt Mono panels on my motorhome tracking system. Yeowzzzzahhhh.
Well, it ~IS~ a pretty good controller ya know.... ;D
But really, that IS a bit higher than one might think. How much peak power have you seen from that array ??
If you really saw 300 Watts, then, ~maybe~... But that would be sorta rare. How long are your solar days ?
Are you in the south ??
boB
Thanks for all the help. Okay, I can connect to the Classic via Local App. It was the port 3900 for my current version of firmware (as shipped-purchase about 2 months ago). I'll update the firmware today after my batteries hit float mode which should be before noon today.
In end, so far so good then and no harm in checking and re-checking everything. I have access to a huge inventory of networking equipment from thin client, tablets (Windows Xp/7, Android, Apple,HP WebOS) routers (enterprise class stuff) so I'll run the Classic through most of it just to see and report back here about any tweaks necessary.
Bob: Don't forget, I am using a panel tracker so I get direct exposure from sunrise to sunset. It is a two way tracker. I ran my panels in series and using 1/0 wire from junction box (on the roof since only one array) to controller and the same size from controller to batteries. I have very little line loss.
I silver plated all my electrical mechanical connections (everything but my slip ring). My inverter/charge bay is very well ventilated as is the battery bay. I have absolutely no shadowing at any time of the day/year. I might make a gift of tree pruning if some start to interfere with my harvest.
There is one thing that would really come in handy for those of us with "small" installations: Allow for different scales on the gauge displays, especially watts. More of an aesthetic thing than functional.
The one thing I did was to use a separate wireless router that I subnet off my main switch so it can't be bridged to my production network. My production AP has the ability to broadcast 7 different SSIDs at either 2.4 or 5 gig range. A tablet running Windows Server will find it's way to a wall mount to display the local app along with camera feeds and some other home automation things as well as being the multi-media distribution server.
So all is good now. After I update the firmware I'll report back again and re-test the Cradlepoint. I'm sure that will work now too.
The main meter "Power" or watts is scalable in 1kw increments. Go to the "Config" tab on the top of the status window under the power meter. Then at the bottom of the window click "Classic". In the top of the status screen is a drop down box labeled "Power Meter Scale" select the scale you want and the power meter will change.
Quote from: Tinman on October 29, 2011, 09:27:13 PM
BTW, the Classic reports over 7 kw in the last 4 days using my 3 100 watt Mono panels on my motorhome tracking system. Yeowzzzzahhhh.
Well, it ~IS~ a pretty good controller ya know.... ;D
But really, that IS a bit higher than one might think. How much peak power have you seen from that array ??
If you really saw 300 Watts, then, ~maybe~... But that would be sorta rare. How long are your solar days ?
Are you in the south ??
I am a little north of San Francisco. In bulk mode I routinely see 295-297 watts from the array. Below is a screen shot of what the Classic is reporting as of about 12:30 PST so I have until the sunset to harvest. Right now in absorb so watts are down a bit.
I really like the retro style gauges. Today when everything is digital and looks sanitized it's nice to see something with design. I hope they continue to use the retro style because it is after all, a Classic. Just my 2 cents.
boB
[/quote]
[attachment deleted by admin]
I updated the firmware for both Classic and the monitor. That went just fine. I insured I had removed any config for port 3900. App can find the Classic and will stay connected for about 30 seconds, the "Connection Closed" is the message.
I'll try again tomorrow as the Classic is "resting" and thus can't be reached via the local app. That might be a good enhancement although it might use some power. Usually, I'd want to see the results of the day after the day is done or at least cumulative until the point there was no more harvest. As it is, once the Classic goes to rest the local app never finds it.
Tomorrow I'll run through this step by step once more from application install to end. I'll use a computer with a fresh install of Windows 7, no firewall, local area network only-wired, no anti-virus, running as admin and see how that goes. I'll try the cross-over cable as well if going through any of my routers doesn't work.
Quote from: Tinman on October 30, 2011, 09:27:30 PM
I'll try again tomorrow as the Classic is "resting" and thus can't be reached via the local app. That might be a good enhancement although it might use some power. Usually, I'd want to see the results of the day after the day is done or at least cumulative until the point there was no more harvest. As it is, once the Classic goes to rest the local app never finds it.
That's interesting. The local app should see the Classic whether it's running or resting.
Not sure what's going on there.
Hmmmmm....
boB
Hi, Guys,
Just some insight into Tinman's issue connecting to the Classic which might help in general:
- The Classic advertises its IP address on UDP port 0x1212 (4626) so if you've got your Classic and Monitoring Computer on different routers (or UDP port 4626 blocked) then the auto-detect won't work.
- The Classic will automatically close any open connections after 30 seconds of inactivity. Under normal conditions (using the Local App) this shouldn't happen because the Local app is constantly requesting modbus registers from the Classic. If you see the Classic disconnecting (from the local app) after 30 seconds it means that somehow data is not getting back and forth to/from the Classic. This may be an issue if you've got QOS or port triggering set up on your router/switch, or if port 502 is blocked on your firewall (although if this is the case it shouldn't connect at all).
- The Classic should always accept TCP connections despite the charge control mode (including resting).
- The Classic will only accept one TCP connection at a time so if you're running the Local app on one machine, you won't be able to connect to it from another.
- The Classic does use name resolution (DNS) when trying to connect to the MyMidNite server so if you'd like to use that feature (when I finally finish the website...sorry, no rocks, please) then that will be something that will need to be configured (manually for static or via DHCP).
Now this is all the way things _should_ work. There are bound to be some bugs to squash or some configurations to configure to make everything play nice on different networks (which are hideously complex beasts). I'm glad to try to fix as many bugs as possible so we can get the Classic working on everybody's network so please complain if it's not working!
I'm going to see if we can get a Cadlepoint MBR in house so I can debug your DHCP issue, Tinman, because that is probably a problem on my end. DHCP is an UGLY protocol.
Thanks,
-Andrew
The local app has now been running for hours ;D
The battery sensor indicator shows it is not installed but oh well, I know it is.
I went completely through everything, brand new cat5 cabling, different routers, wired/unwired, different computers and so on. I also took a look at the flow between the Classic and the local app (via router). Not knowing much about these things it could be a latency issue, especially on wifi. I have seen this before with some databases and since the local app is storing data locally that is where the database resides. When I've run across this in my applications usually accounting for increased latency corrects the problem.
It will not run on two of my machines, both of those are Windows 7 patched but not running SP1. I upgraded one to SP1 and then the app worked. On the machine I was working with mostly, SP1 had tried to install but failed, a pretty common thing. You need to look to see if SP1 actually installed correctly if you have auto-updates configured. Otherwise it is easy to let it slip by. The other machines do work with it. All are name brand (Lenovo/Dell/Motion Computing). It will not work with my Airlink WiFi router, wired or unwired. It does work with a Cisco RVS4000 gig router and through to a Ruckus 2.4/5 gig N band AP back to the computer.
The one thing I did notice was that after uninstalling the local app, Windows 7 may not clear the registery so the next time you reinstall it, additional entries are created. These show up in Windows 7 Firewall and you need to manually set them to allow access. If not, the application will not connect to the Classic. It went through that several times to verify it, you might want to do the same.
The registry entries can be cleaned up manually but most people probably shouldn't touch it, bad joojoo can happen quite easily. CCLeaner also know as crap cleaner seems to find the extra entries and removes them. If you uninstall the local app I highly recommend you run something to insure any entries are flushed from the registry. That way the reinstall is clean.
It could have been a combination of things that prevented the local app from working.
Some other things I noticed. If you happen to set port 3900 as the port to be used, sometimes port 502 will appear as a second classic even though it doesn't exist. After a while it appears to time out. That has gone away now that I'm using port 502 but I'll run some other configurations after a while to see if I can duplicate it. Some folks might want to use a different port and if it is repeatable, might be something to check.
Windows Embedded is a no go even with write filter off. Most people won't have such a thing so no big deal.
2.5 hours uptime and all appears to be good with the local app. Thanks for the suggestions and patience.
TinMan
If you go to the Charge menu and go to T Comp make sure there is a number for the temperature compensation adjustment if it is set to 0 or disabled it will just show as the temp sensor not being there.
Ryan
Quote from: Halfcrazy on October 31, 2011, 08:01:33 PM
TinMan
If you go to the Charge menu and go to T Comp make sure there is a number for the temperature compensation adjustment if it is set to 0 or disabled it will just show as the temp sensor not being there.
Ryan
My value is currently: -5.0 mV. under Temps I see N/A 25c for the battery. The sensor is installed correctly as best as I can determine. I'll take it off and see if that changes anything. I have it near center top of the #4 battery (4 batteries in parallel with 1 being top left, 2 top right, 3 bottom left 4 bottom left looking down.)
Maybe the sensor is bad? Let me know in a pm your shipping address and I can send you a new one.
If you happen to have an extra telephone cable that you can cut one end off of, and you
short ALL of the wires together, Plugging it into the battery temperature sensor phone jack
should make all the fans turn on and the display should show 100 degrees C.
As long as you cut the unused end of that cable off, cut off the locking tab from the
test plug end so you don't have to use a screw-driver to un-plug it, or just to make
it easier to pull back out again.
boB
Quote from: boB on November 01, 2011, 07:59:29 PM
If you happen to have an extra telephone cable that you can cut one end off of, and you
short ALL of the wires together, Plugging it into the battery temperature sensor phone jack
should make all the fans turn on and the display should show 100 degrees C.
As long as you cut the unused end of that cable off, cut off the locking tab from the
test plug end so you don't have to use a screw-driver to un-plug it, or just to make
it easier to pull back out again.
boB
I have enough cabling to re-wire New York. ;)
I PM'd Halfcrazy about the display and not remembering the time/date between reboots. Everytime thing. Goes to 00/00/2000 and time of battery breaker disconnect.
Tinman, you rock! Thanks for trying out so many configurations. You probably just saved Ryan hundreds of hours of service calls with folks who are running Win7 without SP1.
Here is some more general info for folks who are trying to connect directly to the Classic either with a crossover cable or through a switch on a dedicated network/subnet. (Note that if you use a ROUTER with DHCP capabilities on this private network then you can skip the rest of this).
The Classic has DHCP enabled by default. If you plug it straight into your PC chances are it will NOT work unless you are running a Linux or Windows server on your machine. The following is the recommended way to handle this case:
First setup your PC:
Set your LAN IP address to your desired subnet. I recommend something like 192.168.13.1. Set your subnet mask to 255.255.255.0. Gateway and DNS are not required in this case.
Now on the Classic set the NET series of menus set the following:
MODE: STATIC
IP: 192.168.13.100
SN: 255.255.255.0
GW: 192.168.13.1 (same as your PC)
You can skip D1 and D2. If you are on a private network/subnet you can also disable web access to reduce the traffic on your network.
Now you and the Local App should be able to access the Classic using a crossover/private network.
To test, open a console window (Windows Start->run->cmd, Mac Applications>terminal, Linux -- really?) and run:
ping 192.168.13.100
You should see the pings returning with a time value in the millisecond range otherwise you will see an error indicating that the IP address could not be reached.
Note that before you go mucking about changing LAN IP settings on your machine, at the very least write down all the settings that where there BEFORE you changed them. I am unable to guide you in re-setting up your personal network if you change it according to these instructions.
Quote from: Tinman on November 01, 2011, 10:28:36 PM
Quote from: boB on November 01, 2011, 07:59:29 PM
I PM'd Halfcrazy about the display and not remembering the time/date between reboots. Everytime thing. Goes to 00/00/2000 and time of battery breaker disconnect.
I just realized that you are talking about the time and date in the MNGP/Remote itself where the main time and date should be held,
even when the power goes down. I would check the clock battery (3V coin cell) in the MNGP. Maybe it is dead or there is
still an insulator between it and the battery holder ?? It should be higher than about 2.0 volts to keep the internal clock/calendar running
when the power goes out. You can measure POSITIVE at the TOP of the battery holder with respect to GND or NEGATIVE. Battery negative is one place for the multi-meter reference, or, if you have a steady hand, the left most pin on the LCD connector of 20 pins (pin 1) is GND.
We put the insulator on every MNGP battery so that if the Classic is sitting on some distributers' shelf for a year, it doesn't run the
battery down. When the Classic is powered up, the coin cell battery in the MNGP ~should~ not have to power the clock.
Now, here is my explanation for the Classic (control board PCB) and how its internal clock works without an internal battery which was my
first response to your question, Tin Man..........
The time is held in the MNGP itself which has the battery. When the Classic boots up, or re-boots, it tells the MNGP that it needs its time set.
The MNGP responds but only when the MNGP is in the MAIN STATUS menu (this will be able to be done in other places eventually).
It may be that if the Classic is unsuccessful that it gets set to year 2000 maybe. Also make sure the time and date is set correctly in the MNGP.
You can also set the time and date in the Classic to the MNGP's time/date by going to the MNGP's MISC menu, time,
and pressing ENTER from the MNGP time/date setup screen. That sends the time/date to the Classic itself.
If the Classic's power did NOT go off during the reboot, then the time and date ~should~ be still good, as the processors'
internal clock and calender were still powered up in that case. The Classic booting will still request the time and date from the
MNGP though, so it may be that the MNGP isn't responding.
Another thing may be that this is older software where time and date issues were not handled as well as they are now.
The next release, coming up in a few days will be better. What the Classic will do is to set its internal date to 05/04/2003 so we
know that it just didn't get initialized. Otherwise, the Classic will be all 00000s and would show 00/00/2000 like you are seeing
now I think.
It's a lot to remember, but I figure its as good a place as any for me to write this down so I know where to copy this info from as well.
boB
Thanks. The controller is handling solar harvest just fine and verified by the condition of my batteries. These little things aren't show stoppers and knowing there is continued work everything is stellar.
We have rain tomorrow and Friday, possibly Friday so that is inside work time, getting the remote mounted properly, ordering new batteries and so on.
The Classic 150 is tops in my book and glad I have it.
The issue of the Date/Time not carrying over after a reboot/power off is resolved. It was the grunge on the back of the battery, the battery was fine.
As I said in another post, it is the residue from packaging or that insultaor pull strip that caused the problem. It sorta burned onto the back of the battery, forgot to take pictures. Anyway, all is well with date time now.
Now the Local App isn't retaining the scale for power (watts). I had set it to the lowest value since I have a smaller system. Today, fired up the tablet and after the sync, that scale is back to the maximum (5 kw). Strange. The Classic hasn't been rebooted. It went to rest last night but that is all.
I still have no readings for amps on the status either for daily or lifetime. Is that not functional? It would be really nice to know what I'm putting into the batteries or my harvest without running calculations. When I chart it the values presented are exactly the same if I choose hourly. There is no way the same amount of amps are going into the battery or coming down from the panels every hour, just not possible.
Let me know if those measurements are not yet working, I'll stop looking for them to show up until a future application release.
[attachment deleted by admin]
TinMan
The Power scale is remembered on the PC but if the Local App is Updated it loses that setting. I will mention to Andrew that user settings need to be retained during an upgrade.
As for the Amp Hours I understand that is not functional in the Classic yet so the Local App does not have that Data I will ask boB today when we should expect that to be functional.
Ryan
No worries. Completely understandable that not all features will work on a first out application (ask me how I know). It isn't critical and the app is pretty stable. It's one of those things, you get a taste of the goodies and then you get the wants. You should have seen me begging and badgering ASW to get the 150 Classics. Gotta have the best you know. ;D
Local app starting to be unstable. Several days in a row now, the local app simply stops working. The remote monitor works as it should but the local app freezes and even after close and restart (the app) the data is not maintained.
Pictures attached. For example, today at around 1pm the local app stopped functioning. You can see the flatline of data in the chart and all the gauges also freeze. Until a few days ago it was running ok. This is a closed network, just the router, the Classic and a TabletPC running Windows Xp are on it, no internet connection, no other clients. The next two posts will have the other pics showing nearly identical timed pics of the remote and the local app.
Not sure what is going on. Not messing with the settings or charts at the time. This has happened both when displaying a chart for extended periods and just showing gauges.
[attachment deleted by admin]
Here is a pic of the remote monitor, next is the local app, frozen. Notice the difference in information even though the pics are taken at the same time (within seconds). The difference is not attributable to actual panel/system performance as the local app stayed that way until it was restarted.
No data is logged when the local app freezes. The data is then missing completely from the local app.
[attachment deleted by admin]
And now the local app. The remote monitor operates normally, the local app stop recording/displaying data.
This seems pretty consistent now. The result are some pretty significant gaps in recorded data.
[attachment deleted by admin]
I will bring this to Andrews attention today.
Ryan
I can concur with everything that tinman has said about the local app locking up. I just chalked it up to bugs in the app and I am waiting patiently for you guys to sort it out, for now I have to reset classic when the app locks up. I would love to see the internet version up and running so I can visit my classic via a smart phone.
Cheers...
Damani
Instead of rebooting the Classic try closing the application, dropping your connection to the client (PC) and then connecting and running the application. I found that works well instead of re-booting the Classic.
My comments on Internet access to the Classic.
While I would welcome an Internet app for accessing data via Smartphone (I do this for a number of my own applications) I wouldn't use a cloud service based application host, no matter who runs it. Having gone that route for Enterprise class services the complexity and reource demands are very significant. Even if the solution is hosted via third party, no one has been able to get it right yet, Apple, Google, RIM you name it. Much rather have a rock solid local app that can be accessed via a VPN or a native one just pulling or getting pushed data right from the Classic or even an application running on the LAN. I ran the data center for a statewide government agency having a whole team of sys and net admins working for me and maintaining even 3 9s of service is a huge undertaking. Just my 2 cents but I can deal with my connection and solid applications running locally but accessible remotely. Connecting to cloud services for access to my Classic will create a huge resource drain for Midnight when it doesn't work. When the whole "all eggs in one basket" is really figured out I'm all in but until then, even a small glitch in that infra structure can bring a company to it's knees in short order. Let the remote smartphone app call home, not a cloud service. My solar install is now mission critical. No way am I going to sit there wondering if someone else got through a data center or server sitting somewhere. Realistically, cloud services for mission critical applications are off 5 years and anything else is marketing.
Temporary solution. If you set a task to run once an hour then close and restart you can most likely avoid the application hang. Use task Scheduler to do this. You can probably set it to run/close/run more frequently but I don't know if that will make any difference or add benefit. Unknown is if this will corrupt any data stores for the local app. Perhaps someone can answer that?
If no data corruption is likely then this is a quick fix. The question then is: are the data stores closed at commit or do they remain open? If the application is closed via task scheduler, does the application roll back for any reason? If the answer is no then using Task Scheduler is a nice quick fix for us.
I've tried it and so far no issues but it will take a day or so to prove this all out.
As for the smart phone running the local app, it just requires a re-compile of the local app to make that work, at least on an Android.
That will also be a direct connection to the Classic ~OR~ the cloud server... Whichever is doable for the customer. If the customer
has a hard time port forwarding, then they can use the slower cloud which can work OK but not nearly as fast as the direct
connection (which I prefer).
We'll get your immediate concerns fixed first though.
Thanks and sorry for the hangups !
boB
Hi, everyone,
It looks like what you guys are experiencing is the App trying to process a lot of logged data. There is tons of it and while I tested it with REALLY BIG data sets it is possible that with extended data logging it gets bogged down. I'm going to have to fix this one and get a fix up for you guys.
Sorry about that!
Quote from: atop8918 on November 10, 2011, 05:46:43 PM
Hi, everyone,
It looks like what you guys are experiencing is the App trying to process a lot of logged data. There is tons of it and while I tested it with REALLY BIG data sets it is possible that with extended data logging it gets bogged down. I'm going to have to fix this one and get a fix up for you guys.
Sorry about that!
I think that a temporary work around for this may be to DISABLE data logging in the Configure/Classic menu.
In fact, give that a try and see if it stays up longer ??
Thanks,
boB
No sweat here (speaking for myself), I know you folks are on it. For me the application is icing on the cake. The Classic is wringing power out of the panels. ;)
BTW, using Warpia's Ultra Wireless USB the ability to send the applications display to larger format panel display is nice and works very well. Sending it over allows a simple botton push to change modes and display the Classic's info.
A pic of my growing info center. Midnight's stuff is a perfect fit in the space provided.
[attachment deleted by admin]
Nice Tinman, I like.
Cheers...
Damani
Quote from: atop8918 on November 10, 2011, 05:46:43 PM
Hi, everyone,
It looks like what you guys are experiencing is the App trying to process a lot of logged data. There is tons of it and while I tested it with REALLY BIG data sets it is possible that with extended data logging it gets bogged down. I'm going to have to fix this one and get a fix up for you guys.
Sorry about that!
Just happen to re-read that. Not sure what extended data logging means but my Classic has been up only about 10 days or so. The benhavior gets progressively worse as I tried starting/stopping the application, closing it after rest and now it rarely syncs up without a reboot of the Classic. I can get a few hours out of it but noticed that on days with clouds the time is shorter that the app doesn't freeze.
Freezes are usually corrected with a close and restart of the application after 5 minutes or so, sometimes less. Failures to sync always require a reboot of the classic. Hope that info help track down the culprit.
Quote from: Tinman on November 13, 2011, 11:00:26 AM
Freezes are usually corrected with a close and restart of the application after 5 minutes or so, sometimes less. Failures to sync always require a reboot of the classic. Hope that info help track down the culprit.
Interesting observation. Might just help...
Thanks !
boB
Can't connect via Local App at all now. Get error 2002 frequently. Even reboots of the Classic no longer do much to help so I'll leave it be. I might try a complete uninstall and reinstall of the local app. Since the last time I did that all the data was wiped I'll see if a connection comes back. Not sure, guessing on this but I do know it is application related and at this point not my network (everything else works).
Quote from: Tinman on November 14, 2011, 10:49:21 PM
Can't connect via Local App at all now. Get error 2002 frequently. Even reboots of the Classic no longer do much to help so I'll leave it be. I might try a complete uninstall and reinstall of the local app. Since the last time I did that all the data was wiped I'll see if a connection comes back. Not sure, guessing on this but I do know it is application related and at this point not my network (everything else works).
A complete un-install may include deleting the directory ( this is in my Documents and Settings)....
C:\Documents and Settings\boB\Application Data\com.midnitesolar.LocalStatusPanel\Local Store
boB
All,
Since I unchecked the "enable data logging" things seem to running smoother with less drop out and disconnecting. I have been able to consistently open the app and connect to all three of my classic "knock on wood".
Cheers...
Damani
I believe the issue with the local app and logging is related to latency as the application aquires data from the controller. Just my seat of the pants testing indicates that if the application requests data and it can't get it immediately the application hangs.
You can probably replicate this by running updates to graph parameters and watching data requests.
Perhaps running the data transfer requests as a service?
I've been wrong before and this is as good a time for another example.
Finally got my Midnite Classic connected to my network. I'm installing SP1 on my windows 7. Hoping that will get the local app working.
My main computer is running Ubuntu 11.10. I can not install the Local App. The Adobe Air installer will not work. Is there anyway to install with out using Adobe Air?
As far as I know the Local App requires Adobe AIR. Andrew will chime in I am sure or you can PM him he is Atop8918 here on the forum he should be able to help with AIR.
Hi, I am new to Midnite and just got the local app running on W7sp1 (using port 3900 as mentioned in an earlier post).
Very nice to have connectivity but wondering where is the history logged? Does it only store history while the application is running?
Will the web service have continuous history?
Thanks,
Al
Quote from: Treetop on November 28, 2011, 04:40:05 PM
Hi, I am new to Midnite and just got the local app running on W7sp1 (using port 3900 as mentioned in an earlier post).
Very nice to have connectivity but wondering where is the history logged? Does it only store history while the application is running?
Will the web service have continuous history?
Thanks,
Al
The local app logs while you are connected to the Classic. The Classic logs all the time it is running and our Local App
software guru is working now to be able to access that logging information through the app you are running through
the Ethernet. Not sure exactly of when this will be done but I know he's working feverishly to get it going.
We'll definitely keep you all posted.
Thanks !
boB
Also to add to boB's post the Classics are only logging data if they have newer firmware 11-7-11 or newer. This firmware will also switch the Classic to port 502.
Ryan
Quote from: Halfcrazy on November 28, 2011, 05:45:36 PM
Also to add to boB's post the Classics are only logging data if they have newer firmware 11-7-11 or newer. This firmware will also switch the Classic to port 502.
Ryan
Thanks for the info. Will look into updating firmware
Eureka! it works,
The Classic 150 is up and running. Used the Wizard and all is good, as far as I can see.
It took a few days to get the local App. going, but when I stopped tweaking my router it worked.
Using the DHCP on the CC and the DHCP on the router....it worked. The port forwarding stuff did not make the trip for a beginner.
couple of questions:
Why does the app screen display turn yellow and green? communication problems? I am using Linux
The graphing seems hard to manipulate? could be me? or do I need a firmware upgrade?
lots of fun,
thanks guys,
steve
When everything is normal the screen will have a green background. When there is an alert the background goes yellow. If there is an error the background will go red. Here is a link to the manual for the Local app you will find all the Alerts and Errors with there icons and description in there starting on page 8: http://dl.dropbox.com/u/31975941/Local%20App%20manual.pdf
little update....
I loaded the latest firmware and the graphs work much better.
Had to cycle the power on the cc before the improvements were picked up by the App.....more luck than good management, but it is working great.
thanks guys
steve (Linux amateur)
ps: Down the road it would be fun to bring the values into an RRDtool graph, not sure exactly how to accomplish this, but learning is part of the fun. "Mymidnite" may be a better method?
spoke too soon...
The 150 works great in the charging role. One anomaly ...once in a while, the input voltage drops down for a second, then bounces right back? Cold up here ~0 F, pushing 66 volts into 12volts.
The App seems to be having the same challenges that Tinman described. Something glitchy in the app graphing? It was fantastic for a day or so after the firmware upgrade, then lost it's time precision/functionality. I am using Linux on a low power ITX as a pc and to run the MS App. The ITX is not blazing fast, but should be OK?
Meanwhile, reading a lot of forum posts on Modbus. Has anyone tried this with Linux? The documentation "warning" makes me a little cautious. Good winter project.
thanks,
Wondering if we're getting closer to a new dot version of bug fix release, sure would make things easier on the monitoring end. While I don't watch the CC all the time, not being able to use the local app for logged data graphing is real void. While the remote display can do things, that tiny display is a PITA and good for numerical data only. Even so, running through menus on that small display using the buttons isn't the hot ticket for sure.
If the local app just wouldn't hang that would do the trick for quite a while. Seems it doesn't take much data for it to hang (a few days). Disabling data logging defeats the purpose because then all you have is real time.
I downloaded and installed the latest version 0.2.4 MidNite Solar Classic Local Application on Windows XP, then connected the PC to the Classic 200 directly using cross-over Ethernet cable. I was able to ping and got ping reply from the Classic 200. However, when I launched the Classic Local Application, it did not detect the Classic 200. I verified the "Auto-detect Classic" checkbox is checked. What am I missing ?
I captured the Ethernet packets using Wireshark tool, the Classic 200 was broadcasting (255.255.255.255) its IP address (192.168.13.100) on UDP destination port 4626. Does the Classic Local Application (version 0.2.4) listening on port 4626 ?
Is it a mismatch between the Firmware version and the application version ? Does not seem like there is way for me to check the Classic 200 Firmeware version from its front panel display.
Thanks!
To check the Classics firmware version repeatedly push the "Status" button until the screen shows up with a couple dates. These are the Firmware dates for the Classic and MNGP. Most older Classics where on port 3900 I think and newer ones all default to 502.
First thing I would try is to shut off the Classic for 1 minute and also close the App. Now turn the Classic back on and try the app again.
Ryan
The factory ship Firmware on the unit is version dated 09/23/2011.
I have update the firmware to version to:
Classic revision 1043, release date 06/29/2012
MNGP revision 1056, release date 06/29/2012
Network revision 1024
And it is working fine with the Classic Local Application version 0.2.4.
Thanks!
I just installed 3 Classic Charge Controllers here and have the Local App up and running fine. All three were on their own static IP on port 502 stock. I moved the port on #2 & #3 to 503 and 504. The app found them no problem but now it says #2 & #3 formally on port 502 are "not found" and I can't seem to clear out the old entries. Any one know how to clean up the list? They are not really hurting anything but just looks ugly.
Quote from: WizBandit on August 17, 2012, 04:25:13 PM
I just installed 3 Classic Charge Controllers here and have the Local App up and running fine. All three were on their own static IP on port 502 stock. I moved the port on #2 & #3 to 503 and 504. The app found them no problem but now it says #2 & #3 formally on port 502 are "not found" and I can't seem to clear out the old entries. Any one know how to clean up the list? They are not really hurting anything but just looks ugly.
Are those phantom Classics IP's listed in the list of addresses in the configuration menu ?
If so, you can just delete those. Or maybe just delete everything, turn off Auto-Detect and add your static IP classics again.
That ~should~ take get rid of the unwanted addresses in the list.
If that does not work, delete the directory where the info is stored which, for my windows 7 computer is here....
C:\Users\boBWin7\AppData\Roaming\com.midnitesolar.LocalStatusPanel
.... and re-install the local app with the satic IP addresses and their ports.
boB
Can someone tell me, with the latest version of the Local App, how you change the name of your controllers? With the old Lacal App I had named them "Solar", "Wind1" and "Wind2". But I can't seem to find a way to change their names in the new version of the Local App.
--
Chris
Does your new version of the local app have a spot for a password in the config screen ?? If so, that means that
you need to enter the password, which is just the serial number (No "CL" or leading zeros) and then it
should allow you to adjust most items in the Classic, including the name.
We have been working on this lately, but I believe the latest released classic firmware has the code in it
to make this work. If the local app sees that the classic is not new enough with that capability, then it
won't let you adjust things. You could of course revert to an older version of local app if your classic code
doesn't allow that.
Also, the next release of Classic code will use the Lock Jumper on the Classic control board to bypass the
password for those that don't want to bother with having to enter that for adjusting the Classic parameters.
There were some that are using the modbus programming extensively on a local network and it would have
been much more difficult for them to have to enter that password.
The latest local app also lets you adjust the wind power curves and import/export those from/to a CSV file.
And, almost ready is the local app that reads the Classic's internal logging data.
boB
I got a Classic 150 about 6 months ago, and tried the controller with the local app, and everything work OK. The project got put on hold, and today I pulled it back out. I upgraded all the firmware in the CC, and downloaded the new local app. No workie. On computer #1, windows XP laptop, the local app sees it, knows the address but not the name, but shows ' BUSY'. I can ping the controller. On computer #2, a windows XP desktop, the local app connected for about 5 seconds. I clicked a couple of tabs, then it lost contact, and it now shows 'BUSY'.
I will reset everything and see if it helps.
Any ideas?
Tracy
Two days ago, I installed the local app, plugged the 150 classic into the router and bingo: had data.
Now it doesn't read the classic at all. I've checked cables, rebooted the router, tried loading the program anew onto the Xp side of my XP/Ubuntu dual-boot laptop, tried using static rather than DCHP: nottin'
The ONLY thing I did was on the main computer (Vista machine), was change the name of the 150. However, that "took" and ran without an issue for 20 minutes, until I shut the 'pooter down and went to bed.
Next morning: nada.
Also, I have had ZERO success using the given instructions for installing the USB driver. (So no, I can't upgrade firmware, because I can't connect the classic to the computer by USB.)
Vern
Try rebooting the Classic, we have a known bug that causes this to happen.
Ryan
Quote from: Halfcrazy on October 24, 2012, 06:37:28 PM
Vern
Try rebooting the Classic, we have a known bug that causes this to happen.
Ryan
Doesn't stay working for long - I'm loathe to reboot the classic every 12 hours. Does a firmware upgrade fix this? I've got something six months outta date (at the office, can't recall what I have accurately.)
As of now the bug is still there. Andrew is working feverishly to fix this and may have already. I will talk to him today and see how it is going.
Ryan
My Midnite Solar Status Panel Data tab is reporting Lifetime Values of 12.1Kwh which is about correct for the little over 3+ days since install but it is reporting Ah of 3,284,197.2 which seems just a bit high :o .
Thurmond
Quote from: Tritium on November 24, 2012, 01:50:52 AM
My Midnite Solar Status Panel Data tab is reporting Lifetime Values of 12.1Kwh which is about correct for the little over 3+ days since install but it is reporting Ah of 3,284,197.2 which seems just a bit high :o .
Thurmond
Thurmond;
My Amp Hours says 429,494,369.8 which is kind of insanely high.
And here is a screen shot:
(http://pics.ww.com/d/461930-1/C150-1.png)
This was going on before I upgraded it last night so not "new".
Tom
Hi Tom, Yes that is what is happening to mine. The Ah on the daily values Increments about 1000 amp hours per click of the float time clock to about 32,000 Ah then goes -32,000 and begins to count up again. ??? I did a power up reset of the Classic last night and today the Lifetime Values Ah reads 843.6 which seems about correct. The daily Ah remain very strange.
Thurmond
Since the Classic did not have a properly working Amp-Hour function early on, (it does now),
some older Classics may show very large life-time amp-hour values.
I think we better make a way to reset that ! OK, coming up soon then !
bob
Quote from: boB on November 24, 2012, 04:43:13 PM
Since the Classic did not have a properly working Amp-Hour function early on, (it does now),
some older Classics may show very large life-time amp-hour values.
I think we better make a way to reset that ! OK, coming up soon then !
bob
Figured it was something of the sort.
Hind sight is 20/20 they say.
Sorry to pick apart your work but I figure you want to know about "issues"
Tom
I only received my unit from Arizona Wind and Sun Last week and presumably it was new. Is it New old stock then?
Thurmond
Quote from: Tritium on November 24, 2012, 07:57:31 PM
I only received my unit from Arizona Wind and Sun Last week and presumably it was new. Is it New old stock then?
Thurmond
Thurmond;
If you look at the serial number and pass it on they probably can tell exactly when it was built and maybe even by who? ;D
Tom
Classic 150V (rev 4)
Serial # CL04253
Firmware:
Classic Rev: 1070
Network Rev: 1024
Thurmond
Quote from: Tritium on November 24, 2012, 11:27:08 PM
Classic 150V (rev 4)
Serial # CL04253
Firmware:
Classic Rev: 1070
Network Rev: 1024
Thurmond
Hmmm... That is a pretty new Classic. I'm pretty sure that it (rev 1070) is good to go on the Amp-Hours so
should not have large A-hour values. You should be able to see daily amp-hours on the MNGP (LCD)
screen. Just press the STATUS button and it will roll over to a status screen where kW-hours changes
to amp-hours, and of course, other status screens.
So, let's see if it is the Classic itself or the Local App status panel reading the wrong register maybe.
boB
Amp hours is not functional in the production code as of yet I do not believe? Try clicking the Status buton once and see if KWH changes to Amp Hours on the MNGP
Ryan
Quote from: TomW on November 24, 2012, 11:53:56 AM
My Amp Hours says 429,494,369.8 which is kind of insanely high.
Tom
Tom,
My amp hours yesterday showed almost the exact number as yours, this morning it says KWH 2534.1 and AH 6559.3
Quote from: dbcollen on November 25, 2012, 10:46:18 AM
Quote from: TomW on November 24, 2012, 11:53:56 AM
My Amp Hours says 429,494,369.8 which is kind of insanely high.
Tom
Tom,
My amp hours yesterday showed almost the exact number as yours, this morning it says KWH 2534.1 and AH 6559.3
Dustin;
Today it says
Amp Hours: 429,496,605.5Tom
Quote from: boB on November 25, 2012, 01:04:35 AM
Quote from: Tritium on November 24, 2012, 11:27:08 PM
Classic 150V (rev 4)
Serial # CL04253
Firmware:
Classic Rev: 1070
Network Rev: 1024
Thurmond
Hmmm... That is a pretty new Classic. I'm pretty sure that it (rev 1070) is good to go on the Amp-Hours so
should not have large A-hour values. You should be able to see daily amp-hours on the MNGP (LCD)
screen. Just press the STATUS button and it will roll over to a status screen where kW-hours changes
to amp-hours, and of course, other status screens.
So, let's see if it is the Classic itself or the Local App status panel reading the wrong register maybe.
boB
Here are the 4 screens presented by pressing the status button on my classic in order 1 thru 4:
Yes that explains it. The Amp Hour software is not in the production units. There would be a screen (The second one) that would be identical to the first except KWH would be AH. To get AH going a firmware update will be in order. I would give it a few days as I plan to put up some new Beta firmware first of the week that has a lot of stuff in it (Even some network reliability stuff)
Ryan
So the Daily Amp Hours on the PC Application are just free running from -32,448 to 32,646 endlessly since there is no input from the Classic then whatever that value happens to land at end of day is written to the Lifetime Values? That is how it appears to me.
Thurmond
I'm showing 6,900Ah for one today's production (not bad for 10:00AM) My lifetime values for the last 28 days are high enough to charge a 1000 strong fleet of submarines at 429,495,098.7AH :o
I'm running 1070 on the classic and monitoring with 03.10 remote software.
(http://i1105.photobucket.com/albums/h352/kurtthrun/Ah.jpg?t=1353890188)
Seriously though It isn't a big Issue for now I just use KWH as a guide as they look to be correct for both daily and total:)
Look forward to the update though.
Kurt
Quote from: boB on November 24, 2012, 04:43:13 PM
Since the Classic did not have a properly working Amp-Hour function early on, (it does now),
some older Classics may show very large life-time amp-hour values.
I think we better make a way to reset that ! OK, coming up soon then !
bob
So, do I understand that to mean that in a future Classic firmware update there will be a fix for older Classics (ca. CL00330) so that the AH functionality of the local software is enabled accurately? Thanks, boB.
-Dave
Beware :
Be precise when you speak about the 1070 version, because this name is used with the Production version AND the Beta version !!!
As I understand from the announcements made on this forum, for the last two months, the Amps information is only OK with the 1070 Beta version.
Associated with this 1070 Beta Version, came an OCP problem.
As of my known, this problem isn't corrected.
Weeks are going, without new Beta Release.
Yann
We have officially released Rev 1166 for Beta. We will be moving it to production very soon. Maybe Friday?
QuoteAssociated with this 1070 Beta Version, came an OCP problem.
As of my known, this problem isn't corrected.
Yann,
You just have to do a VMM to solve OCP problem with rev 1070 and it will work fine.
Turn the battery and solar power to the Classic off. Next, turn the battery power back on while holding the Left and Right arrows. Hold the arrows until the first "Solar, Wind or Hydro" screen pops up. Follow the on screen prompts and continue setup. Note: This will reset all settings to factory defaults. You will need to reset any custom settings such as Aux 1 and 2. You may want to write these settings down for reference prior to resetting the Classic.
Erik
Hi Ryan,
On the forum, at the end of last week, i saw your post on the forum, about a Beta Release, but all the associated documents were relating to the Follow-me feature, and i was afraid that this version was dedicated to guys having networked Classics.
On the Midnite website, as the top menus are made with Flash, they are not visible with Safari on the IPad !!
So, when I will go back on my PC, It Will be OK.
Thanks!!
Hi Erik,
A lot of Thanks for the VMM explanation.
After forum reading, for me, it was Vulcan Meld Mind (An American Joke ??) without more explanation.
So, I will install this new Beta, at night.
Have a good day.
Yann
QuoteSo, I will install this new Beta, at night.
Great, I'm sure you will have fun with varimax to end your absorb time.
Erik
Quote from: TomW on November 25, 2012, 11:01:01 AM
Quote from: dbcollen on November 25, 2012, 10:46:18 AM
Quote from: TomW on November 24, 2012, 11:53:56 AM
My Amp Hours says 429,494,369.8 which is kind of insanely high.
Tom
Tom,
My amp hours yesterday showed almost the exact number as yours, this morning it says KWH 2534.1 and AH 6559.3
Dustin;
Today it says Amp Hours: 429,496,605.5
Tom
I powered it off and back on and now it says 33.6AH
Any idea when the Lifetime Amp hours divide by 10 issue will be fixed?
Thurmond
now mine says 0....... Oh yea, I did just install the new one. :D
LocalApp questions :
1°) Where are stored the LocalApp Logs Data on the hard Drive ?
Is it possible to configure this location on a specific disk ?
2°) Is it possible to concatenate Logs datas from differents Computers ?
3°) When the LocalApp is started and no Classic is selected, is the LocalApp already logging all the Classic's viewed ?
The idea is to automatically wake-up a computer from sleep mode on the first hours of the morning to start logging without being present.
4°) Is it possible to connect a Raspberry PI on the USB port and a PC via Ethernet and have the two simultaneously requesting Modbus datas ?
That's all for today :P
Yann
Quote from: Lya72 on February 25, 2013, 06:09:20 PM
4°) Is it possible to connect a Raspberry PI on the USB port and a PC via Ethernet and have the two simultaneously requesting Modbus datas ?
That's all for today :P
Yann
Yann;
I am logging data from 2 Classics from USB on one Pi with a couple perl scripts. You can export the log file many ways, NFS, http, ftp, etc. I would use a USB thumb drive or stick to record the files to because the root file system will fill up fast on the SDHC card otherwise.
Not sure about 2 devices reading the same USB stream from the same Classic, however.
Just gather the data on the Pi and share it out from there to other computers.
In my method you do not "request" modbus data from thte Classic, you simply monitor the continuous stream of data it spits out when you set the comm tab to dump data to USB
More than one way to defur a feline!
Good luck with it.
I do use the Local App at the same time I harvest the USB data stream.
Tom
Quote from: TomW on February 25, 2013, 06:46:30 PM
I am logging data from 2 Classics from USB on one Pi with a couple perl scripts. You can export the log file many ways, NFS, http, ftp, etc. I would use a USB thumb drive or stick to record the files to because the root file system will fill up fast on the SDHC card otherwise.
I do the same except I also installed a lightweight web server on my pi. I can web into it and using a few simple html pages, show what is happening with both Classics.
I was using BOA server but am now moving to monkey or more likely lighttpd
see http://www.penguintutor.com/linux/light-webserver (http://www.penguintutor.com/linux/light-webserver)
Can't wait to get a Clipper and get a cpu into it with some shunts and sensors..
I'm still thinking about Pi'ing the 500A shunt via a/d into another pi for BM for LifeYPO4 cells - and of course reporting to the webserver pi
dgd
Quote from: dgd on February 25, 2013, 10:55:46 PM
Can't wait to get a Clipper and get a cpu into it with some shunts and sensors..
I'm still thinking about Pi'ing the 500A shunt via a/d into another pi for BM for LifeYPO4 cells - and of course reporting to the webserver pi
dgd
dgd;
Have you see the CAI Networks Webcontrol boards?
Built in ethernet, A/D, 1 wire temperature probe bus, Honeywell Humidity sensor support, counter and frequency input, as well as digital I/O programmable logic controller. Another project(s) I have going. Monitoring temps, driving my small soalar array tracker, running lights in my hen house. Can also interface to X10 stuff. They were like $35 when I got mine. There is a handy little break out board for them, too.
I have way too many irons in the fire.
Tom
Tom,
Im looking at the CAI Networks stuff, they look like stand alone network processors with interesting sensor inputs.
I have been buying various pi and arduino interface cards from low cost ebay sellers. Most seem to originate from China but cost just a few $ with free postage. The current sensors with digital serial output are excellent, pwm generators too that could drive SSRs etc..
dgd
OK, Thanks for this fourth question, well responded.
Any idea for the others ? :
Quote
LocalApp questions :
1°) Where are stored the LocalApp Logs Data on the hard Drive ?
Is it possible to configure this location on a specific disk ?
2°) Is it possible to concatenate Logs datas from differents Computers ?
3°) When the LocalApp is started and no Classic is selected, is the LocalApp already logging all the Classic's viewed ?
The idea is to automatically wake-up a computer from sleep mode on the first hours of the morning to start logging without being present.
Yann
Yann;
Sorry, not sure on the other other 2 questions. However, to concatenate files should simply be a copy / paste operation. or a "cat file.1>>file.2" in a *nix environment.
My guess is the local app keeps data as it sits waiting for you to select a Classic to view. But I really never checked or wondered about it.
Tom
Quote from: Lya72 on February 26, 2013, 12:44:38 AM
OK, Thanks for this fourth question, well responded.
Any idea for the others ? :
Quote
LocalApp questions :
1°) Where are stored the LocalApp Logs Data on the hard Drive ?
Is it possible to configure this location on a specific disk ?
2°) Is it possible to concatenate Logs datas from differents Computers ?
3°) When the LocalApp is started and no Classic is selected, is the LocalApp already logging all the Classic's viewed ?
The idea is to automatically wake-up a computer from sleep mode on the first hours of the morning to start logging without being present.
Yann
On 1 the data files all live in /Users/<username>/appData/com.midnitesolar.LocalStatusPanel
On 2 Combining data will probably result in some strange behavior. Andrew says in theory it could be done but would probably be tough
On 3 yes the App is logging anytime it is open Minimized view or not.
Ryan
QuoteOn 3, yes the App is logging anytime it is open Minimized view or not.
Even, being on the first screen whithout a Classic selected ?
So, if you have three Classic's, just by starting the LocalApp, all three are logged ?
Yann
they have to bee seen as the little green dot in the minimized view
Ryan
Quote from: Halfcrazy on February 26, 2013, 11:07:55 AM
On 1 the data files all live in /Users/<username>/appData/com.midnitesolar.LocalStatusPanel
Ryan
Ryan;
Not to pick nits but..
Do the data files live in /Users/<username>/
.appData/com.midnitesolar.LocalStatusPanel?
That dot before "appData" hides it from the common "ls" command in *nix unless you use "ls -a".
Probably a "hidden" file in M$, too? They are not human readable files, either. ;D
On my Ubuntu system they are in: /home/tomw/.appdata/com.midnitesolar.LocalStatusPanel
Just for clarity.
Tom
Tom
Good question? I assume you are correct but have posed this to Andrew and will report back
Ryan
Here is what Andrew had to say about the DOT in front of App Data
No.
If you are navigating windows remotely with a Linux machine, maybe, but no, there is no dot before appData if you are navigating windows using windows as long as you turn off file hiding.
Ryan,
Just tried to load the new version of Local App and got the attached message. Firefox on a Mac. Thoughts?
Quote from: sunstroke on June 08, 2013, 05:39:13 PM
Ryan,
Just tried to load the new version of Local App and got the attached message. Firefox on a Mac. Thoughts?
You may have to uninstall the previous version first if it is on your Mac. This is not always the
case but does show up some times.
Do you have Adobe AIR installed on your Mac ?
boB
I have entered the serial number as the unlock code, but additional config options are still grayed out. Is there a secret to unlocking those features other than entering the serial number?
Running latest app on xp machine with midnite 150. 3.6 kw of panels, twin golf cart batteries for storage and a magnasine 4448 inverter as well. I would love to be able to modify some of the more esoteric features of this controller from my computer.
Quote from: stuman on June 14, 2013, 05:00:00 PM
I have entered the serial number as the unlock code, but additional config options are still grayed out. Is there a secret to unlocking those features other than entering the serial number?
Running latest app on xp machine with midnite 150. 3.6 kw of panels, twin golf cart batteries for storage and a magnasine 4448 inverter as well. I would love to be able to modify some of the more esoteric features of this controller from my computer.
Be sure to click that little blue "enter arrow" to the right lower corner of that pane to send the data to the Classic.
That one got me in the beginning
Tom
You can also install the "LOCK" jumper located behind the main power terminal block to
unlock the Classic from needing the local app serial number password.
boB
I finally uninstalled the update utility program and reinstalled it and it worked fine.
So I went to connect to local status Panel and the first one went fine and the 2nd can't be found.... very frustrating... I've changed the IP address of the original Classic but can't connect to the 2nd one at all on any of 192.168. addresses, yes I've bounce the laptops address around as well, and re connected the original and it's recognized right away.
I've set it up the first for Follow me and have it wired. I don't suppose that's creating a problem?
They actually are more in sync than they have been, so I guess some sharing is going on... I get one short blue blip then one long one... Kinda a one sided conversation....lol.
Do you have 2 ethernet cables, one to each Classic?
Ryan
No, I'm just using one cable, I don't intend(for a while at least) monitoring the classics, I just want to get them on the same page. I haven't connected to the 2nd classic, via software, I am moving the cable to the 2nd unit. I directly connected to my laptop, which worked fine 1st try on the first unit.
I really haven't worked on it, other projects going on. I hope to ping the 2nd in the morning to see if the computer 'sees' it and it's just a software problem. Then I might uninstall and reinstall the program as I did for the firmware install.
I am moving the cable to the 2nd classic, I do have the 'FollowMe' cabling installed. I have taken the 1st CL(classic Lite) and changed the IP to ...1.220(I think with out checking) and setup my parameters, including FollowMe.
I have also removed the BTS from the 2nd CL, anticipating setting up Follow Me. Surprisingly they are pretty much using the parameters I setup, I have it set for EQ every 30 days, or is that cycles? since I can't set the time on the CL. Or will that not work with the CLs connected in FollowMe with out at least borrowing a regular display to set the time?
I think someone said that the CL could acquire the time from an attached computer, but I can't recall how to do this.
Pw,
I think I may see the problem here - or maybe not.. :)
You ethernet connect the first Lite and change its IP to ..1.200
You then connect the second Lite which will be at one of the IPs set by dip switches either ..1.223 or ..1.224 using the ethernet cable that was connected to the first Lite.
This won't work as the local app is trying to talk to the ..1.220 IP number which it expects to see at the end of the ethernet cable.
It will work if you restart the local app because then the app will look for and find the second Lite.
The proper solution to this is to have each Lite separately connected via its own ethernet cable to your ethernet hub/switch. Maybe a good solution would be a small 4 or 5 port powered ethernet hub inside that box that contains the two Classics, fusebox and inverter
The hub will probably have a plugback power unit that could be plugged to a socket next your inverter. You could use two real short ethernet cables to connect hub to each Classic. You could even look at an ethernet radio bridge like Cisco/Linksys WET54G in the same box and its radio link would connect to radio router/laptop etc in the main dwelling.
Anyways just sort of thinking out loud here ::)
dgd
Quote from: dgd on July 07, 2013, 04:07:21 AM
Pw,
I think I may see the problem here - or maybe not.. :)
You ethernet connect the first Lite and change its IP to ..1.200
You then connect the second Lite which will be at one of the IPs set by dip switches either ..1.223 or ..1.224 using the ethernet cable that was connected to the first Lite.
This won't work as the local app is trying to talk to the ..1.220 IP number which it expects to see at the end of the ethernet cable.
It will work if you restart the local app because then the app will look for and find the second Lite....
My understanding from watching the nice install video Ryan produced is that the program would address multiple addresses?
I have added the correct address for the second CL(Classic Lite) and I have the network cable connected to the 2nd CL. I also changed the static IP address for the laptop. Will the program not talk with the 2nd CL. I have turned the program on and off, and I will 'ping' the 2nd CL next chance I get, hopefully this week. I don't have the door hinged yet and it's a bit of a production to open the power center. We reached 96 here today and I really didn't want to sit out in the heat.
I did not get that you had to have a hub or needed a hub unless you intended to monitor the CLs at the same time. I just want to set them and let them work. If the 'Follow Me' cabling is messing something up, like I shouldn't have them connected until both CLs are set for 'Follow Me' I'd be glad to disconnect them.
I don't think "...This won't work as the local app is trying to talk to the ..1.220 IP number which it expects to see at the end of the ethernet cable...." is true of the program, I think you can select what CL address you want it to talk to, changing the static IP only puts you in the correct group to talk to, so as long as your CL is using an unused 192.168.1.xyz address you should be able to communicate with either CL, one at a time by selecting the configuration you wish to address.
Perhaps I'm wrong, thanks for trying to help me out, I'll direct Ryan to this thread and perhaps he can straighten me out.
The local app only does network device discovery at startup.Once the link layer tcp/ip is established to a Classic then the local app will expect to find that Classic at the end of the physical link it discovered it at.
Break that link and insert a different device, Classic, and the local app will fail to find it unless the local app is restarted so that it goes through the network device discovery stage again.
Thats why what you are doing does not work. Nothing at all to do with follow-me wiring, ethernet does not use or take account of follow me wiring between Classics.
The easiest and cheapest solution is to get a hub for a few dollars (ebay) and wire up both the h Classics (one on 192.168.1.223 and the other on 192.168.1.224 as set by the LITEs dip switches).
dgd
Thanks for the help, I really have a pet peeve about people needing to constantly monitor their systems.
I must have missed that it only looks for devices at startup, pretty sure I just typed in the configuration and it started looking, but I could be wrong (it won't be the first time!) Well I opened the Program and that is what it appears to do...
I have a half doz 10/100 hubs around at the cabin, but they are hubs not switches, I had a friend who changed them out for gigabit in her business, just don't want or need to see both CLs, I'm sure I have restarted the program a few times. Though I guess it could be like the firmware problem and hanging in some manner, I also restarted my computer though a couple times. I'll ping the CL if it is seen by the computer, I'll uninstall and reinstall the LocalStausPanel software.
Someday I'll setup a wireless hub and be able to monitor from inside, one of the reasons for the outlet in the power center.
I've always been amazed by people who constantly monitor their systems, that is the reason you have charge controllers. I like to check from time to time to see what stage they are in, but more for running opportunity loads, which I'll let the CL's start at some point.
Quote from: Photowhit on July 07, 2013, 10:01:46 PM
I've always been amazed by people who constantly monitor their systems, that is the reason you have charge controllers. I like to check from time to time to see what stage they are in, but more for running opportunity loads, which I'll let the CL's start at some point.
There's a difference between MONITORING them and obsessing with them.
I monitor and log lots of stuff.
I don't look at it very often while I'm here UNLESS something goes screwy. THEN I want to know what, and what led up to it.
When I'm away, it's REALLY good to be able to look at things and tell the wife if she's going to have to let the generator run or not, or how long for, so she can work out washing etc.
I'll have to look for that. I'm still not able to unlock after numerous updates to the software.
Quote from: boB on June 14, 2013, 11:10:16 PM
You can also install the "LOCK" jumper located behind the main power terminal block to
unlock the Classic from needing the local app serial number password.
boB