Local App software

[Halfcrazy]

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

[Treetop]

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

[sbudd]

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

[Halfcrazy]

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

[sbudd]

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?

[sbudd]

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,

[Tinman]

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.

[Ctran]

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!     

[Halfcrazy]

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

[Ctran]

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!

[WizBandit]

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.

[boB]

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

[ChrisOlson]

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

[boB]

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

[thooker]

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