- Welcome to A Forum run by Enthusiasts of MidNite Solar .
News:
To visit MidNite Solar click this link www.midnitesolar.com
Recent posts
#41
MNGP2 specific / New updater app
Last post by ClassicCrazy - March 21, 2026, 02:20:28 AMThere is a new MNGP2 , Hawkes Bay , Barcelona, Rosie, and Little Rosie updater app for Iphone and Android.
I didn't get any good results with the Android updater app but maybe because something was too out of date like my android phone ? Not sure because it saw the mngp2 but then when it tried to find updates the app just sort of hung up searching for it . I gave up on that after a few attempts and I have an Iphone so tried that new updater app.
The iphone app didn't find anything but then I thought to shut off the android bluetooth and that must have been the problem because once android was off, the iphone found mngp2 right away. It also saw the HB and for the first time saw the Little Rosie which the old updater app never did.
It updated the MNGP2 right away first try.
I had to make two attempts at the HB update but it went second time no issues. Then I updated the Little Rosie .
It did the usual shutdown of the HB PV and the Little Rosie shut off too. I got both of them started again and everything seemed okay.
This morning I didn't see any watts being produced by the Hawkes Bay. Since I hadn't done the full factory reset after updates yesterday, I did that and put all the settings back in . Either before or after that reset I noticed that one of the MNGP2 screens showed amps being produced which I confirmed with my clamp meter . The HB was charging but didn't show any watts output. I shut off the HB breakers and restarted HB , and when it got going again - it all was okay showing the watts and amps charging as normal.
So better do factory reset and restart the devices too . I am not sure how many updates behind I was so maybe that had something to do with it.
I should check the new Android updater app again sometime to see if it can find the MNGP2 - maybe will be okay now with newest updates all in place. ( my android phone is samsung s5 with lineage OS - so older android model )
Larry
I didn't get any good results with the Android updater app but maybe because something was too out of date like my android phone ? Not sure because it saw the mngp2 but then when it tried to find updates the app just sort of hung up searching for it . I gave up on that after a few attempts and I have an Iphone so tried that new updater app.
The iphone app didn't find anything but then I thought to shut off the android bluetooth and that must have been the problem because once android was off, the iphone found mngp2 right away. It also saw the HB and for the first time saw the Little Rosie which the old updater app never did.
It updated the MNGP2 right away first try.
I had to make two attempts at the HB update but it went second time no issues. Then I updated the Little Rosie .
It did the usual shutdown of the HB PV and the Little Rosie shut off too. I got both of them started again and everything seemed okay.
This morning I didn't see any watts being produced by the Hawkes Bay. Since I hadn't done the full factory reset after updates yesterday, I did that and put all the settings back in . Either before or after that reset I noticed that one of the MNGP2 screens showed amps being produced which I confirmed with my clamp meter . The HB was charging but didn't show any watts output. I shut off the HB breakers and restarted HB , and when it got going again - it all was okay showing the watts and amps charging as normal.
So better do factory reset and restart the devices too . I am not sure how many updates behind I was so maybe that had something to do with it.
I should check the new Android updater app again sometime to see if it can find the MNGP2 - maybe will be okay now with newest updates all in place. ( my android phone is samsung s5 with lineage OS - so older android model )
Larry
#42
Online Training sessions / NABCEP CREDIT Design and Advan...
Last post by Sunshine - March 19, 2026, 02:25:56 PMCouldn't make it to the NABCEP conference this year? No problem! Join us for an all new webinar Thursday March 26th at 8am Pacific! In Design and Advanced Programming of the Midnite Solar Energy System Ryan will discuss system design with real world examples featuring the Rosie and Little Rosie inverters as well as the MidNite charge controller lineup. This 1.5 hour webinar counts for NABCEP continuing education credit!
https://attendee.gotowebinar.com/register/4180827448049316703
https://attendee.gotowebinar.com/register/4180827448049316703
#43
The Rosie / Re: Parallel Rosies not sharin...
Last post by Brucey - March 17, 2026, 10:23:08 AMQuote from: FNG on March 16, 2026, 09:16:07 AMA few things here in no order:To clarify on the parallel threshold setting, this allows you to just have the Master Rosie on and additional slave parallel unit(s) will power up if the threshold is exceeded? Is there a timer before the slaves shutdown after load drops below threshold?
1- I would update firmware on the Rosies, A lot of work was done for generators late in 25/ early in 26
2- Looks like the second Rosie is off maybe, It should wake up if parallel threshold is set but to be sure try turning parallel threshold to off
3- Parallel threshold percentage is on either leg. For example if set to 20% and L1 loads to 700 watts that's 20%
Very cool.
#44
The "Classic" charge controller / Re: ClassicBridge - Classic to...
Last post by ClassicCrazy - March 16, 2026, 10:53:21 AMI would like to get all the various controllers I have talking to each other, but in the end it seems easier to just set the one I want as the lead and then stagger the float voltages so they more equally contribute power when the light levels drop in afternoon. I can do the same thing with absorb voltages and absorb times. In my system I have to tweak it all just right since my common bus bar system is not ideal so voltage drops can be different .
Larry
Larry
#45
The Rosie / Re: Parallel Rosies not sharin...
Last post by FNG - March 16, 2026, 09:16:07 AMA few things here in no order:
1- I would update firmware on the Rosies, A lot of work was done for generators late in 25/ early in 26
2- Looks like the second Rosie is off maybe, It should wake up if parallel threshold is set but to be sure try turning parallel threshold to off
3- Parallel threshold percentage is on either leg. For example if set to 20% and L1 loads to 700 watts that's 20%
1- I would update firmware on the Rosies, A lot of work was done for generators late in 25/ early in 26
2- Looks like the second Rosie is off maybe, It should wake up if parallel threshold is set but to be sure try turning parallel threshold to off
3- Parallel threshold percentage is on either leg. For example if set to 20% and L1 loads to 700 watts that's 20%
#46
The "Classic" charge controller / Re: ClassicBridge - Classic to...
Last post by RJD18 - March 15, 2026, 11:54:12 PMFor the ClassicBridge (Modbus RTU protocol bridge) the software component is now completed and loaded on to my little box. (Pictured in prev post) .
Next step is two isolated tests.
1) physically test the RS485 connection to the ComBox . I have simulation running that will allow the ClassicBridge ,acting as a Modbus slave @ address 30, to publish Classic telemetry to the Schneider Combox.
2) physically test the rs232 connection to the Classic and make sure I have the TX and RX lines correct
I will have to wait a bit to get physical access to my Classic but if anyone reading has any questions please do no t hesitate to ask .
It remains to be seen what or how the Schneider ComBox will react with the Classic data. Fingers crossed
Next step is two isolated tests.
1) physically test the RS485 connection to the ComBox . I have simulation running that will allow the ClassicBridge ,acting as a Modbus slave @ address 30, to publish Classic telemetry to the Schneider Combox.
2) physically test the rs232 connection to the Classic and make sure I have the TX and RX lines correct
I will have to wait a bit to get physical access to my Classic but if anyone reading has any questions please do no t hesitate to ask .
It remains to be seen what or how the Schneider ComBox will react with the Classic data. Fingers crossed
#47
The Rosie / Re: Parallel Rosies not sharin...
Last post by Wirenut - March 14, 2026, 09:02:24 PMThe master has the MNE300Rosie-240P100 breaker panel under it. The slave has the MNE300Rosie-240F panel under it. They are wired together with #6 THHN conductors between the boxes. The generator input connects to the AC input of the 240P100 box with #4 THHN conductors.
#48
The "Classic" charge controller / Re: ClassicBridge - Classic to...
Last post by ClassicCrazy - March 13, 2026, 11:46:31 PMHave you seen Grahams projects for the Classic ?
https://github.com/ClassicDIY
Also I posted info on getting classic data via modbus over ip might help ?
https://midniteftp.com/forum/index.php?topic=9687.0
Larry
https://github.com/ClassicDIY
Also I posted info on getting classic data via modbus over ip might help ?
https://midniteftp.com/forum/index.php?topic=9687.0
Larry
#49
The "Classic" charge controller / Re: ClassicBridge - Classic to...
Last post by RJD18 - March 13, 2026, 06:35:45 PMI am calling this hardware-software project "ClassicBridge".
ClassicBridge is being designed to act as a data broker or translator rather than a one-off solution for just the Schneider Combox. Expect it to be fully shaken out / viability tested using the Schneider Combox as a patient zero as it were.
A few points on the design principles being used as the software is being built. (in 4 distinct modules, System Initialization Module, Classic Polling Module, Translation Module , Target Output Module )
0) Minimum power footprint - goal is less power overhead than the MNGP
1) Adaptability , Maintenance and Scalability : Classic extraction AND Transformation are configuration file driven. To minimize reads from the Classic
2) Separation of Concerns: keeping raw Classic data, translation logic, and ComBox outputs separate. Making it easier to swap or extend any part.
3) As noted ,Table-driven Translation: Using .map files for target-specific logic. I have imagined one .map for Schneider (already created) , one for Victron, one for... anything else. No code changes needed, just a new map.
4) Hardware Resilience: Solidify The RS232/RS485 interfaces and fail-safe mechanisms so the software can stay agnostic about the target — it just reads Classic data and outputs according to the map.
5) Minimal Overhead: The approach will add almost no runtime complexity — the map is just a lookup table applied in memory. The main "extra work" is making sure the map parsing is robust and errors are caught.
6) Scalability: Later, if somebody else wants more registers or a more complicated device, they just make a new .map — the same polling and translation engine handles it. Future-proofing without locking in.
* A note on the failsafe - if for any reason there is an error in any module that renders data unreliable then the destination registers are set to null or default values and we set execute a function that , in the case of the Combox , sets the "Device State " register (#65) to a value of 255 (Data Not Available). This prevent erroneous reporting downstream .
If anyone thinks of anything I missed from a design perspective please let me know as now is the time to think about these things.
ClassicBridge is being designed to act as a data broker or translator rather than a one-off solution for just the Schneider Combox. Expect it to be fully shaken out / viability tested using the Schneider Combox as a patient zero as it were.
A few points on the design principles being used as the software is being built. (in 4 distinct modules, System Initialization Module, Classic Polling Module, Translation Module , Target Output Module )
0) Minimum power footprint - goal is less power overhead than the MNGP
1) Adaptability , Maintenance and Scalability : Classic extraction AND Transformation are configuration file driven. To minimize reads from the Classic
2) Separation of Concerns: keeping raw Classic data, translation logic, and ComBox outputs separate. Making it easier to swap or extend any part.
3) As noted ,Table-driven Translation: Using .map files for target-specific logic. I have imagined one .map for Schneider (already created) , one for Victron, one for... anything else. No code changes needed, just a new map.
4) Hardware Resilience: Solidify The RS232/RS485 interfaces and fail-safe mechanisms so the software can stay agnostic about the target — it just reads Classic data and outputs according to the map.
5) Minimal Overhead: The approach will add almost no runtime complexity — the map is just a lookup table applied in memory. The main "extra work" is making sure the map parsing is robust and errors are caught.
6) Scalability: Later, if somebody else wants more registers or a more complicated device, they just make a new .map — the same polling and translation engine handles it. Future-proofing without locking in.
* A note on the failsafe - if for any reason there is an error in any module that renders data unreliable then the destination registers are set to null or default values and we set execute a function that , in the case of the Combox , sets the "Device State " register (#65) to a value of 255 (Data Not Available). This prevent erroneous reporting downstream .
If anyone thinks of anything I missed from a design perspective please let me know as now is the time to think about these things.
#50
The "Classic" charge controller / Re: ClassicBridge - Classic to...
Last post by RJD18 - March 13, 2026, 04:59:51 PMLarry , Just a thought but have you considered connecting to the grid to power all gear you use to enable such robust monitoring for your renewable energy system ?? You sure do have a veritable bouillabaisse of equipment. 
(this was meant to make you chuckle. If it offended in any way I apologize )
Thank you for your great and useful input .
Russ
(this was meant to make you chuckle. If it offended in any way I apologize )
Thank you for your great and useful input .
Russ