So we have some software that was written by an individual. It basically allows you to program your outback gear and classic as well as monitor it. I understand the next move is to port it over to Linux so it will run on something like a Beagle Bone black. The software requires the Outback AXS and at least one Classic in the system.
It can be found here http://www.kb1uas.com/pics/MidniteClassic3PlusObAXS-V1Setup.exe (http://www.kb1uas.com/pics/MidniteClassic3PlusObAXS-V1Setup.exe)
I will start throwing some screen shots up as well as a you tube video of it in operation.
Monitoring of a Classic and FX
Monitoring 3 Classics
Setting up the software for monitoring
Programming the Outback
Programming the Outback
Programming the Classic
Programming the Classic
Programming the Classic
Device control to allow automation of the FX and Classic
YouTube video tour http://www.youtube.com/watch?v=sxQo9Tab9M0&feature=youtu.be (http://www.youtube.com/watch?v=sxQo9Tab9M0&feature=youtu.be)
Modbus reader tool thats included
Looks tasty. Not really familiar with AXS, you using an Outback product or a generic box?
If I had Winders here I might be ordering one today. When the Linux version arrives my monitoring and control addiction will force me to get one, I am sure.
Looks sweet.
Tom
Yes the AXS is an Outback product they made but never offered any software ::)
"Someone" has clearly devoted considerable time to this, and looks like they had some midnite help as well. Im judging that by not being filed under open source, that this is a closed source intiative?
Are we destined to have 45 half projects? Its a reality unfortunately that most every developer has their own pet language and ways of doing things. And thats the diversity you get in the software world.
If we are to specify this though i would say that there are at least 2 distinct target markets.
1. client, portable device, "status monitor"
- whats up with my system right now.
- super easy to install from app store
- windows/mac/etc versions that can be installed on a computer
(so far: local app; local app for android; grahams android app; N1GNN)
2. server , combox /blackbox, the above plus datalogging
- track daily, monthly, yearly data
- higher resolution
- datapoint agregation
- provide access to multiple clients
(so far: mymidnite, green monitor, blackbox, various home brew)
Personally what i would like to see is the community and the kind of energy present with the openenergymonitor project. If we could do that then we could make something awsome.
OK Just to be clear this is NOT MIDNITE Speaking it is me personally. Midnite in no way endorses or agrees with what I am about to say!!
This software was written by a single individual who simply enjoys writing code. He had no help from Midnite on this he did it simply because he wanted to control of his system and I wanted to control mine. This is not a Midnite project. And I am so sorry you consider it 50% done and welcome you to not bother to use it. If I sound frustrated I am, I feel like the harder I try the more I get beaten. This program works 100% for what he wanted it for and what I wanted it for. I am sorry if it does not do what you need but it does do what we wanted it for. And I felt it may benefit some others as well.
With all that said I welcome an open source movement and will do anything I can to support that. There are a ton of people out there doing there own thing and I think that's great. I however am not a programmer and can not write the code for anyone.
I will now put my Midnite hat back on and sign in and move this thread to a new place.
Ryan
Sorry Ryan, i didnt mean to sound critical. Like i say he or she has obviously invested some energy into it, and it looks great, and no one wants that energy put down, so im certainly not doing that.
Would "he" be willing to work with us? Im only saying this becasue there are only so many hours in the day and to see all of us all repeating each others work just seems such a waste of those hours.
Nor am i saying that there should only be one project. But sharing ideas, source, and documentation allows us to improve all of the projects.
This is the whole point of open source, that we each can stand on the shoulders of giants, as newton said.
I understand what you mean about all the hours - I see some of those open source projects show accumulated hours put in and I have been amazed at how much effort goes into some of those things. But I always thought people who do coding don't sleep !
We don't -- we collapse.
Quote from: Halfcrazy on March 19, 2014, 08:45:10 AM
Modbus reader tool thats included
Ryan.. I was looking for the location of the Modbus reader tool but can't seem to locate it in the download you provided. Can you point me to its install location?
Hm looks like that was in an older version. I will see if I can get it added back into the new version as I find it a very handy tool
Ryan
Quote from: Halfcrazy on March 22, 2014, 12:59:39 PM
Hm looks like that was in an older version. I will see if I can get it added back into the new version as I find it a very handy tool
Ryan
Thanks Ryan.. I was thinking it would be a handy too also.
Try here:
http://www.n1gnn.com/StatusMonitor/StatusMonitor.html
Quote from: zoneblue on March 22, 2014, 10:44:17 PM
Try here:
http://www.n1gnn.com/StatusMonitor/StatusMonitor.html
Thanks zoneblue
I got an AXS Port from Alt E Store. It was a bit less than intuitive to set it up for my LAN IP block. I used the application from N1GNN on my beater XP home laptop I only keep for these M$ only applications.
Toughest bit was getting XP to use the ethernet connection set up for the 192.168.0.xxx network. They really should have made it use DHCP and some form of broadcast identifying itself.
I just set it up and it found both my FX inverters and both Classics no problem.
I poked around some, set up the devices and the IP for the AXS itself.
Tried to get it logging but when I ftp in it shows no files. I had hoped I could at least pull the log file(s) to parse for my logging and local web pages.
Anyway, an early adopter playing with it. It looks like it will be great for monitoring and control of a mixed system like we have here with OB and MN gear.
Can't wait to see where this goes.
Big thanks to the coder (N1GNN).
Can't wait to try the Linux port of this handy tool.
Tom
Been trying to enable the AXS logging with this and it simply will not let me change the values in Outback_SD_Card_Log... fields, except the logging_Mode which I set to 1 for "excell mode". I also set the IP and Gateway with this App.
I have enabled the time server, changed the timezone and changed the logging mode so I can definitely write to the AXS.
I must be missing something that needs to be set before I can set the logging values?
Any help appreciated.
Tom
Excellent. I've been out of the loop lately - so just now seeing this. I've been hoping someone would develop an application that makes use of the AXS port. The fact that it incorporates monitoring of Classics is a bonus!
Now I just have to get an AXS port and try it out. :D
Shouldnt be too hard to add a blackbox module for AXS or mate3 , but as i dont have any outback gear ill need some help.
After a couple days of messing with this...
Not intended as a complaint just where I am at.
It "sees" my inverters but does not recognize them as FX inverters and does not show any writable fields. (a clue?)
It will not let me add the AXS Port to the monitor window.
I get zero length log files on the hour every hour generally. Probably because I cannot change any logging settings other than logfile format.
I am fairly certain I am missing something silly and simple. Maybe it can't write to the inverters because you need to enter that 141 password someplace I am missing?
I have reset the AXS Port multiple times and started from scratch and have had no luck getting past these issues.
I read the AXS Port "Manual" several times and it is absolutely no help on this or I am too dense to see the answer.
I tried to update the firmware but it does NOT seem to update despite following the instructions in the Manual.
If anyone can actually offer some help I would truly appreciate it. I never had much hair but may be bald soon at this rate.
Thanks.
Tom
Hey Tom. I hope you get it figured out and if so post it here since I have ordered an AXS port and hope to be setting this up myself soon.
Quote from: mtdoc on April 18, 2014, 06:49:48 PM
Hey Tom. I hope you get it figured out and if so post it here since I have ordered an AXS port and hope to be setting this up myself soon.
I certainly will. I had to walk away from it as it was making me crazy searching and trying things and not getting anywhere.
I will get back at it but had hoped someone would say "you gotta set this to that" but so far nobody seems to have the answer.
The Classic bit works treat it is the Outback inverters and the Outback AXS port that are twitchy and apparently OB has not devoted (m)any resources to product support on the AXS Port.
Tom
Did you ever get this working for you Tom?
I have my AXS Port now and am hoping to find time soon to install it. Wondering what the pitfalls are to look out for....
Quote from: mtdoc on May 02, 2014, 05:59:21 PM
Did you ever get this working for you Tom?
I have my AXS Port now and am hoping to find time soon to install it. Wondering what the pitfalls are to look out for....
Nope, never had any luck with it recognizing the inverters as FX inverters just generic inverter and could not program them with it.
I got an error once about "wrong version" but it never said of what. Maybe it is my FX's they are not exactly new inverters?
I had to give up on it when my laptop committed suicide on me a couple weeks back and haven't got back to it but got the laptop replaced now so will get at it again.
Tom
Ryan,
This is a neat piece of software. It took me just a minute to get it displaying two Classic's data.
I can get the AXS port configured for it too but the second hand 230V 3048 I bought locally has decided to do weird cracking noises then let smoke escape. Seems it was in a flood zone two owners ago and I am first to use it since. Should have bought one from naws instead of being a cheapskate.
The display boxes look pretty, good for those preferring a text type display instead of the analogue dash type of the local app. The 1 minute shortest time refresh is a tad too long for me.
It sorta reminded me of the original mymidnite text list display (node 14??) or at least one line of it.
( I don't use MyMidnite due to its potential security/hacking issues BUT did it ever get the node14 type text display back as an option?)
Now instead of, or additional to, the screen refreshing, this program were to were to have a configurable number of time stamped display lines for each device then that would be a nice visual immediate record of how the device was performing.
Also got me thinking what could have been and now we see another variation of reporting from the Classic. I suppose the great advantage of this is the ability to see the AXS port and for Outback inverter (and controller?) info to be integrated in one display.
After re-reading ZBs comments I can appreciate his frustration at the seemingly non cooperative efforts of developers in making these reporting applications. But then thats the way things go, no critisism of these package developers as they produce some excellent stuff but each tends to go his/her own way.
dgd
This is frustrating.
Maybe I got a bad AXS Port?
I have tried it on XP home,Win 8 and under Wine on different computers..
I cannot get it to function properly on any of them. Does not seem to retain settings.
Maybe I will see if i can send it to Ryan and see if it works for him? So far not much use here.
Tom
Well that sucks Tom... :-[
I have my AXS port - now I just have to find the time to get it installed and play with the software. I also need to update my utility room router/wifi. -Life is just too busy... maybe this weekend. I have both XP and Win 7 machines available to try it with. Will report back after I try in it out.
Quote from: mtdoc on May 07, 2014, 02:48:53 PM
Well that sucks Tom... :-[
I have my AXS port - now I just have to find the time to get it installed and play with the software. I also need to update my utility room router/wifi. -Life is just too busy... maybe this weekend. I have both XP and Win 7 machines available to try it with. Will report back after I try in it out.
In the slow process of getting an RMA out of AltEStore and / or Outback. It is obviously a brick now only lights up the green LED now.
Kind of getting the run around that AltEStore needs to get an approval from OB to RMA it.
Considering it took nearly 3 weeks to get it the first time I expect it may be months before I have one to use again.
Felt like a run around but we will see.
Won't be buying from AES again, that is for certain.
And that is where it is now.
Just an update.
Tom
Tom,
Since my OB smoked I have seen that this Classic/AXS port software will not start up the AXS port. I think it may actually require the AXS port to see a recognised OB inverter.
Just thinking since you said your OBs were not recognised that this may be an issue.
Or maybe not, but just an idea. I hope my AXS is not bricked :o
dgd
Quote from: Halfcrazy on March 19, 2014, 08:35:48 AM
So we have some software that was written by an individual. It basically allows you to program your outback gear and classic as well as monitor it. I understand the next move is to port it over to Linux so it will run on something like a Beagle Bone black. The software requires the Outback AXS and at least one Classic in the system.
It can be found here http://www.kb1uas.com/pics/MidniteClassic3PlusObAXS-V1Setup.exe (http://www.kb1uas.com/pics/MidniteClassic3PlusObAXS-V1Setup.exe)
I will start throwing some screen shots up as well as a you tube video of it in operation.
Can the monitoring part be configured to add the daily kWh usage to provide cumulative power generation as a function of time in days?
Very excited to hear that this is possible. I've got several sites that would really benefit from remote monitoring/control. Does anyone know if this can be used with the Radian inverters as well? Any way to run the Mate 3 at the same time, or is it one or the other?
Quote from: ID Solar on July 01, 2014, 05:26:38 PM
Any way to run the Mate 3 at the same time, or is it one or the other?
Unfortunately only one or the other.
I finally found the time to get this software up and running. A bit buggy with the tendency to crash once in a while when asking it to "update block/tab fields". Also, attempts to write to the inverter fields sometimes return an error code but retrying eventually works.
But overall it's a very useful bit of software. Nice to be able to change the settings of my Outback Inverter from computer screen instead of wading through the convoluted Mate menu tree. Thank you! :) Of course with the Local App I could already do this with my Classics!
My biggest complaint is not an issue with this software but with the physical connection of the AXS Port. I guess I didn't look at the Outback info close enough since I did not realize that the AXS needs to replace the Mate in the Hub. I had thought it would plug into one of the other empty Ports on the Hub.
So as Bob states above you cannot have an AXS port plugged in at the same time as the Mate. The issue I have with this is that I am very happy with using WattPlot for monitoring and logging my Inverter and FNDC data. But WattPlot requires serial data from the Mate
I'd really like to be able to have my Wattplot and this software both running at the same time. Wattplot does not allow the control of the system that this does and this software does not work very well for monitoring! >:(
I tried a simple ethernet hub to see if that would allow both connections - but no joy. Both devices rely on PoE for their power.
Bob or other network guru's: Is there any other 10 BASE-T type hardware switch/router that might allow this? Even a physical switch witch would allow me to change from one to the other would be better than having to open up my Epanel to change connections on my Hub.
Quote from: mtdoc on July 03, 2014, 12:36:46 AM
I tried a simple ethernet hub to see if that would allow both connections - but no joy. Both devices rely on PoE for their power.
Bob or other network guru's: Is there any other 10 BASE-T type hardware switch/router that might allow this? Even a physical switch witch would allow me to change from one to the other would be better than having to open up my Epanel to change connections on my Hub.
The problem is likely because the OB device only allows one network connection at any time. So its either OB hub or AXS device but not both.
dgd
Quote from: mtdoc on July 03, 2014, 12:36:46 AM
I tried a simple ethernet hub to see if that would allow both connections - but no joy. Both devices rely on PoE for their power.
Bob or other network guru's: Is there any other 10 BASE-T type hardware switch/router that might allow this? Even a physical switch witch would allow me to change from one to the other would be better than having to open up my Epanel to change connections on my Hub.
mtdoc;
I think you are lucky if that hub still works and you did no damage to the other components.
Some time ago I asked on the OB forum about using an ethernet hub to extend the range / break out the Hub ports.
I was warned it would damage the OB hub and possibly the ethernet hub.
I never tried it but remember the warning.
I ended up with multiple DOA AXS ports and no joy getting a functioning unit so I cannot say for sure but logging should be possible by collecting the ftp logs and parsing them for the data.
It always annoyed me that OB never offered any real customer options for logging / control via the network and a PC.
Tom
mtdoc;
I meant to mention that you could wire a couple ethernet bulkhead jacks as direct feed through and plug one into the OB Hub and the other into whichever device you wish to use.
Even an ethernet in-line coupler would work.
Like this:
http://www.amazon.com/Britta-Products-271710-Coupler-Straight/dp/B000BSLW8U/ref=sr_1_2?ie=UTF8&qid=1404388367&sr=8-2&keywords=ethernet++coupler (http://www.amazon.com/Britta-Products-271710-Coupler-Straight/dp/B000BSLW8U/ref=sr_1_2?ie=UTF8&qid=1404388367&sr=8-2&keywords=ethernet++coupler)
Not a switch but would work to use the AXS or the Mate.
Tom
Thanks Tom.
Hub still working - so far...
Yeah, I thought about using RF45 couplers or splitters to at least pull the connections out of my ePanel. Not as good as a physical switch but workable.
Still - I wish there was some way to have both the Mate and AXS port connected at the same time and at least remotely switch between input from either. Seems like this sort of a software controlled Ethernet switch must exist since it would have applications elswhere.
If I have to go to my utility room to physically make the switch then it takes away a lot of the utility of this software for me...
BTW - I've had no luck using Filezilla to log on to the AXS port for FTP server purposes. It makes an initial connection then times out.
But even if I could do that and have access to logged data - it would not be a good substitute for WattPlot without some serious time spent coding GUI - something I have neither the talent or inclination to attempt.
It really is too bad Outback seems to drop the ball when it comes to software control and monitoring solutions for their equipment
Perhaps their new initiative will be better but it relies on the expensive Mate3 which I have no desire to purchase.
Ethernet hubs and switchs are extremely robust, with something 3kV isolation. Outback probably not so much.
On the monitoring, i guess it depends on how involved your setup is. Using WBjr covers the load side of it, thats the most interesting. Subtracting WbJr from classic(s) amps, gives you dc load amps. That just leaves genset run time and a few other more minor things.
We are bringing, fingers crossed, a vfx back with us on our trip stateside next week, so it is possible that ill write a blackbox module for either AXS, serial, or mate3. I doubt we will get a mate as we have no genset, so that leaves one of the other two.
Well as far as monitoring goes - with the Local App and My Midnite I'm covered on the CC side.
Wattplot is really pretty good for inverter and load monitoring. But it does not allow much control at all - Only AC grid use/drop and Aux on/off. This is due to Outbacks limtation on the Mate's serial interface. Also - monitoring Wattplot remotely involves using a VNC setup which can be a bit finicky at times.
The great thing about this AXS software is the ability to control all the settings. It also provides basic monitoring but no graphing or built in logging.
It really would be nice to have one application for remote monitoring and control.
Short of that some sort of software controlled switch to allow changing the HUB input/output between the Mate and the AXS port would be the bee's knees....
Quote from: TomW on April 16, 2014, 08:47:41 AM
I got an AXS Port from Alt E Store. It was a bit less than intuitive to set it up for my LAN IP block. I used the application from N1GNN on my beater XP home laptop I only keep for these M$ only applications.
Toughest bit was getting XP to use the ethernet connection set up for the 192.168.0.xxx network. They really should have made it use DHCP and some form of broadcast identifying itself.
I just set it up and it found both my FX inverters and both Classics no problem.
I poked around some, set up the devices and the IP for the AXS itself.
Tried to get it logging but when I ftp in it shows no files. I had hoped I could at least pull the log file(s) to parse for my logging and local web pages.
Anyway, an early adopter playing with it. It looks like it will be great for monitoring and control of a mixed system like we have here with OB and MN gear.
Can't wait to see where this goes.
Big thanks to the coder (N1GNN).
Can't wait to try the Linux port of this handy tool.
Tom
Hi Tom,
I bought an AXS. What is the physical setup of the AXS? In other words, how is it connected to the ports of the OB and classics?
Thanks!
Quote from: Nashville on August 29, 2014, 07:44:47 AM
Hi Tom,
I bought an AXS. What is the physical setup of the AXS? In other words, how is it connected to the ports of the OB and classics?
Thanks!
Well, I got stuck with 2 bad units in a row and no luck getting either AlteStore or Outback to RMA #2 so I am going by memory here. One connection to the OB hub and one to your network hub or router. As I recall they are marked well enough. It gets power from the OB HUB and uses the ethernet to access other devices not on the OB HUB. It uses CAT5 for both connections.
Frankly, I gave up on it considering my 100% failure rate on it and lack of customer support from the retailer and manufacturer and the fact I spent $1000 worth of my time on trying to get a $150 part warranted.
Neither company will see my business again
Sorry for the rant but there you go.
Tom
Ok, I got the AXS and plugged it in. Cabling is correct. When I plug in 192.168.0.64 in my browser, it cannot find the AXS. I reset the AXS to default settings. No go....
Any ideas? Firewall? Maybe add a port number?
Thanks!
Quote from: Nashville on August 30, 2014, 09:03:48 AM
Ok, I got the AXS and plugged it in. Cabling is correct. When I plug in 192.168.0.64 in my browser, it cannot find the AXS. I reset the AXS to default settings. No go....
Any ideas? Firewall? Maybe add a port number?
Thanks!
The AXS does not have a web server in it... It is a Modbus over TCP/IP device.
To see what it is doing, you will need to download our software that lets you see it and the Classic charge controller.
The link for that software is in the first posting in this forum thread.
BTW, it is ~usually~ port 502 for modbus over TCP/IP.
It certainly won't hurt for me to re-post that here right now...
boB
Quote from: Halfcrazy on March 19, 2014, 08:35:48 AM
So we have some software that was written by an individual. It basically allows you to program your outback gear and classic as well as monitor it. I understand the next move is to port it over to Linux so it will run on something like a Beagle Bone black. The software requires the Outback AXS and at least one Classic in the system.
It can be found here http://www.kb1uas.com/pics/MidniteClassic3PlusObAXS-V1Setup.exe (http://www.kb1uas.com/pics/MidniteClassic3PlusObAXS-V1Setup.exe)
I will start throwing some screen shots up as well as a you tube video of it in operation.
Three years since this topic was last discussed...
As of about a year ago, WattPlot 5 (http://wattplot.com) can now monitor the AXS Port and MATE3 via Modbus over TCP/IP. :) However it was still limited to OutBack equipment. :(
I have been working on a new tool called WattPlot ACKcess - a Modbus-based monitoring, control, and reactive* software, intended for ANY manufacturer. It obviously started with OutBack, but I have recently started adding support for the MidNite Solar Classic as my first non-OutBack device. Of course, not owning or having access to a Classic, my testing options are limited, so I am seeking helpful (patient) parties who might have an interest in seeing this become a reality.
True, WattPlot has always been a fee-for-lifetime-license product. (I think it ended up being a pittance for what clients received in terms of features, documentation, support, professionalism, and a years of free updates and responses to requests for new functionality.) I don't know if ACKcess will follow the same model or not. Frankly no-one wants to pay for software anymore. If I had a need for this software myself (as most open-source developers do), it might be a different story, but I only do this to help pay the bills. (I tried CareWare for one of my earlier tools - WattPlot VisualMATE - but practically no-one respected that and the charity received no real benefit from it.) I guess if there is any chance of getting ACKcess installed out there with a license fee, it would have to be pretty cheap to compete with all the excellent open-source software that is available.
That being said, WattPlot ACKcess uses an entirely new software architecture, designed and written from square one, to be data-driven, open to new manufacturers, graphic-more-then-textual, and possibly portable to smaller handheld devices. More than any other WattPlot tool, I can see a day when it might become open source. (The chances of anyone following the code of the original tools, started in 2005, is practically zero. ;) )
* Reactive software means that you can easily program the tool (i.e. in plain English) to monitor multiple conditions and to automatically react to those conditions, changing settings, issuing commands, texting you, running a Windows program, etc. etc. 8)
Just seeing this now Andrew. I have been a happy user of Wattplot for years now. It's an excellent tool!.
I would love an all in one solution for monitor and control of my Outback and Midnite equipment and if high quality, would happily pay for it. Based on my Wattplot experience, I'm sure anything you do will be very good.
I'd be happy to help in any way I can. I'm generally technically literate (but with minimal coding skills).
Excellent! If you'd like to try out the new tool, head over to http://WattPlot.com/fieldtest.htm, download a copy and give it a trial.
The main thing I need to do right now is see if it can connect to the Midnite Classic via Modbus. After that, things will speed up a lot.
Andrew, I'd like to give it a try if I can be of help. Looks promising. I will follow the link above to the DL page.
Ok - great. I should have some time this weekend to try it out.
Quote from: Matrix on November 28, 2017, 10:52:47 PM
Andrew, I'd like to give it a try if I can be of help. Looks promising. I will follow the link above to the DL page.
I look forward to receiving your activation request as well. Be warned - I have an extremely busy weekend coming up, so if you want to try things out at that time, I may be slow in getting you up and running. I recommend downloading and activating ahead of time! ;)
The latest version that went out today (WattPlot ACKcess 6.0.3.1) has full monitoring (MATE3/MATE3S/AXS Port), data logging (MATE3 CSV file format), direct access to just about any setting (with helpful guidance), graphing and summary screens, a powerful event log, and a brand new Generator Control function which has some very cool capabilities (including a safe start function for remote starts so the generator won't keep running on, even if your network goes down. 8))
I have been stuck for a long time in the OutBack world, and I look forward to spending some time adding Classic connectivity!
Hi Matrix and mtdoc:
'Tis a busy season for sure, but I was a little disappointed not to hear back from either of you on trying out the monitoring of a MidNite Classic with OutBack components. Since neither of you have asked for an ACKcess activation, I worry that perhaps there is a program problem that I wasn't hearing about....? Or perhaps you are both just busy. :) (Me too!)
No problems here. So sorry. I've been bogged down with work and on the side still trying to get my diversion load working correctly.
Plan to move forward soon.
Quote from: intellact on December 16, 2017, 02:05:37 PM
Hi Matrix and mtdoc:
'Tis a busy season for sure, but I was a little disappointed not to hear back from either of you on trying out the monitoring of a MidNite Classic with OutBack components. Since neither of you have asked for an ACKcess activation, I worry that perhaps there is a program problem that I wasn't hearing about....? Or perhaps you are both just busy. :) (Me too!)
Sorry Andrew. I had some family issues arise and that along with the holidays has kept me out of the lab. I'll have some free time later this week and early next week so I should get to it then. I'll post here if I'm having any issues..
Thanks for checking!
Okay, so it's now March... ;)
WattPlot ACKcess has taken great leaps forward in the last few months, but still no word (and therefore no progress) on that MidNite Solar Classic testing... :(
I will test it for you, I have a classic 250 on a 620w array on my battery back up in the new house. I really enjoyed wattplot as a system monitor on the house we sold. Send me a private message and I will give you my new email.
Thanks,
Dustin Collen
I am willing to test for you. I have 4.5KW array and Classic 150.
One important component that may not have been emphasized enough in this thread... Testers should really have an OutBack MATE3 or AXS Port at this stage of the game. I'm trying to test that combination right now. I hope to have a straight Midnite Solar version soon. :)
Is it too soon still for the "Mate3s"?
Quote from: bee88man on March 11, 2018, 10:12:27 AM
Is it too soon still for the "Mate3s"?
It depends what you mean by that question! ;) Are you asking about OutBack's network connectivity challenges or WattPlot compatibility? ;D
WattPlot can talk to the MATE3S, but there are still a few issues that I am tracking down in Version 5. For example, Modbus can pull the model name directly from the device, but other (earlier) parts of the program were asking the user to select from a menu that had "MATE3" but not "MATE3S", so things didn't match up nicely.
For the purposes of this test, it is WattPlot version 6, so the MATE3S has been designed in from the beginning - no problem.
I have run up against a very tricky technical challenge. Any and all help would be appreciated...
Challenge #1 - My VB.Net code, which maintains very robust connections to OutBack's MATE3 and AXS Port device via Modbus/TCP, is unable to connect to a MidNiteSolar Classic at all.
Challenge #2 - A reminder that I don't have a MidNite Solar Classic, so I am not actually in front of the device I'm trying to talk to or able to easily experiment with code. Everything runs through my volunteer field tester.
Here are the technical details:
User is able to access Classic via local status panel and Grahams classic status 4 plus.
My code is VB.Net and seems to be dying at the socket Connect method (but is not generating an error message !? - I know, I'm double-checking this):
Try
ModbusSocket = New Socket(ResolvedIpAddress.AddressFamily, SocketType.Stream, ProtocolType.Tcp)
With ModbusSocket
.Connect(New IPEndPoint(ResolvedIpAddress, 502)) ' << appears to fail here
.SetSocketOption(SocketOptionLevel.Socket, SocketOptionName.SendTimeout, 500)
.SetSocketOption(SocketOptionLevel.Socket, SocketOptionName.ReceiveTimeout, 500)
.SetSocketOption(SocketOptionLevel.Socket, SocketOptionName.NoDelay, 1)
.SetSocketOption(SocketOptionLevel.Socket, SocketOptionName.DontLinger, 0)
End With
Catch ex As Exception
MsgBox(ex.Message)
End Try
Any thoughts? Special settings to be enabled on the Classic? Tricks to try?
Thanks in advance (and a free software activation to the person that solves the issue! ;D)
Problem solved! I expect to have full MidNite Solar Classic compatibility within the week. ;D
Quote from: intellact on March 16, 2018, 05:37:51 PM
Thanks in advance (and a free software activation to the person that solves the issue! ;D)
Is that Me? ;)
Quote from: intellact on March 06, 2018, 11:35:45 AM
Okay, so it's now March... ;)
WattPlot ACKcess has taken great leaps forward in the last few months, but still no word (and therefore no progress) on that MidNite Solar Classic testing... :(
Sorry Andrew. I did try to get it working back in January but had no luck. I spent about half a day trying to sort out possible network and/or AXS port issues on my end then gave up.
Because my current set up using my Mate 2 with Wattplot 5 works so well I went back to that and have not taken the time to revisit the issue - even though it means no integration with my Midnite classic monitoring.
Good news that you are making progress and eventually I will get back to it. Priorities, priorities... If my current set up wasn't "good enough" already I might move it to the top of the list..
I appreciate your efforts and your great products :)
Any updates? Definitely interested in control software for my Midnite Classics.