To find the "LAST Reason For Resting"
From the main status screen hold the left arrow and tap Enter. The top middle number is the "Last" RFR
Remember this is over written the next time it goes to resting
This table was stolen from a post by boB - hope to make it easier to find:
Reason For Resting:
... "
ReasonForResting = 1 Wake state, (Vpv < PreVoc AntiClickSenstvty (MB Addr. 4236)
ReasonForResting = 2 Insane Ibatt on WakeUp state (offset changed from off state)
ReasonForResting = 3 Negative current on WakeUp state
ReasonForResting = 4 dispavgVpv < (dispavgVbatt - 10) Now -25 (RestartTimerms = 1500)
ReasonForResting = 5 Too low power and Vbatt below set point for 90 seconds
ReasonForResting = 6 FETtemperature >= 100C Hot
ReasonForResting = 7 Ground Fault
ReasonForResting = 8 Arc Fault
ReasonForResting = 9 (IbattDisplaySi < -15) (negative current) (MB 4200)
ReasonForResting = 10 (dispavgVbatt < LBDlowV) Battery less than 8 Volts
ReasonForResting = 11 Vpv >= 90% of Voc but slow. Low Light #1
ReasonForResting = 12 Vpv < 90% of Voc Low Light #2
ReasonForResting = 13 Vpv > (Voc + 10V) in PV_Uset || Solar1_OandP
ReasonForResting = 14 Vpv >= 90% of Voc but slow. Low Light #3
ReasonForResting = 15 Vpv < 90% of Voc and taking too long. Low Light #4
ReasonForResting = 16 Normally because user turned MODE OFF... Disabled
ReasonForResting = 17 Vpv > 150V (classic 150)
ReasonForResting = 18 Vpv > 200V (classic 200)
ReasonForResting = 19 Vpv > 250V (classic 250)
ReasonForResting = 22 Average Battery Voltage is too high above set point (RestartTimerms = 2 sec)
ReasonForResting = 25 Battery breaker tripped (Vbatt shot up high)
(If RFR = 25 on Wakeup, check modbus register 4200)
ReasonForResting = 26 Mode changed while running, Vabsorb raised more than
10.0 Volts or Nominal Vbatt changed by modbus command
AND MpptMode was ON when changed...
ReasonForResting = 27 bridge center == 1023 (R132 might have been stuffed old units)
ReasonForResting = 28 NOT Resting but RELAY is not engaged for some reason
ReasonForResting = 29 ON/OFF stays off because WIND GRAPH is insane
ReasonForResting = 30 PkAmpsOverLimit (will change somewhat 1-23-2013)
ReasonForResting = 31 AD1CH.IbattMinus > 900 (peak negative battery current)
ReasonForResting = 32 Aux 2 Logic input is high. Aux2Function 15 (external disable/enable)
ReasonForResting = 33 OCP in a mode other than Solar or PV-Uset (1-10-2013)
ReasonForResting = 34 AD1CH.IbattMinus > 900 Classic 150,200 newer than 1-23-2013
ReasonForResting = 35 Vbatt < 8.6 V (LOW LOW battery)
ReasonForResting = 36 Battery temperature is Greater than reg address 4161 specified
ReasonForResting = 38, is the new sleep because "other charging sources appear to be active"
ReasonForResting = 136 Battery temperature fell below MB reg. 4161 - 10 C (Classic turned back on)
ReasonForResting greater than 100... 100 + PowerOnReset, WDT, etc...
ReasonForResting = 104 Watchdog WDT reset (only at boot until first RFR)
ReasonForResting = 111 Normal Power up boot (only at boot until first RFR)
[ 100 + 1 = POR, 2 = Ext. Reset 4 = WDT 8 = Brown Out ]
..."
FWIW. Mods, please change/move this to its rightful place if needed. Thanks, Vic
Can you add to that post how you retrieve that information from the MNGP?
I modified the post
I'm getting a 38:Unknown on a classic 150, anyone know what that one is? I did not see it in the above list. Thanks!
Bob clarified just the other day that 38, is the new sleep because "other charging sources appear to be active" and the classic is no longer required. ie something is holding the bank above teh classic setpoints. You might also see this after a bank transits from EQ back to float.
Quote from: eyeinthesky on December 09, 2015, 05:42:33 PM
I'm getting a 38:Unknown on a classic 150, anyone know what that one is? I did not see it in the above list. Thanks!
ZB is correct. Here's boB post
http://kb1uas.com/mnsforum/index.php?topic=2880.msg27522#msg27522 (http://kb1uas.com/mnsforum/index.php?topic=2880.msg27522#msg27522)
#38 unknown
So, could the table be updated to include #38 ?
That would simplify future searches
(I just started getting #38 this last week, cold temps pushed my other controller into higher voltages)
Thanks
Quote from: mike90045 on December 29, 2016, 03:15:46 AM
#38 unknown
So, could the table be updated to include #38 ?
That would simplify future searches
(I just started getting #38 this last week, cold temps pushed my other controller into higher voltages)
Thanks
I updated the table with
ReasonForResting = 38, is the new sleep because "other charging sources appear to be active" . Hope it helps.
Tom
In the same system, most days, my classic goes to rest with reason #4, but sometimes #5
ReasonForResting = 4 dispavgVpv < (dispavgVbatt - 10) Now -25 (RestartTimerms = 1500)
ReasonForResting = 5 Too low power and Vbatt below set point for 90 seconds
These are readings late evening, sun has been down for several hours.. What is the Vbatt setpoint ? The system battery voltage?
ReasonForResting = 17 Vpv > 150V (classic 150)
ReasonForResting = 18 Vpv > 200V (classic 200)
ReasonForResting = 19 Vpv > 250V (classic 250)
From the descriptions of Hyper VOC it would seem these limits should be the given values plus the battery voltage. My Classic 200 is resting in Hyper VOC mode with a voltage of 201.5 volts (and yes, it's pretty cold this morning). I specifically bought this controller for the advertised Hyper VOC capability. Am I missing something here?
Quote from: ppanish on January 08, 2022, 09:30:56 AM
ReasonForResting = 17 Vpv > 150V (classic 150)
ReasonForResting = 18 Vpv > 200V (classic 200)
ReasonForResting = 19 Vpv > 250V (classic 250)
From the descriptions of Hyper VOC it would seem these limits should be the given values plus the battery voltage. My Classic 200 is resting in Hyper VOC mode with a voltage of 201.5 volts (and yes, it's pretty cold this morning). I specifically bought this controller for the advertised Hyper VOC capability. Am I missing something here?
What HyperVoc means is that the Classic is guaranteed not to blow up with the rated "Voc" plus 12, 24 or 48 volt battery voltages.
If you have a Classic 150 and a 48V battery, it will not run above 150 volts input but will be OK up to 150+48 = 198 volts.
Most other MPPT charge controllers will have their warranties voided if you go over that Voc on too cold of a morning.
I am guessing you have a Classic 200 ? What battery voltage ?
boB
I think the marketing and technical specsmanship from Midnite is very misleading in this case. In the end it's not that important to me since the panels heat up quickly enough (they had a light coating of frozen rain this morning, so it took a bit longer than usual) to come within range. This is my first winter with the Classic and an upgraded array. However, there's nothing outside this forum which would have led me to be aware of this limitation that I'm aware of. Certainly this is not the way Hyper VOC is discussed in the literature I've seen. Perhaps I should have been more careful and that information is there, I don't know and it's not really worth the time to run this down.
Technically speaking, Midnite could have just continued the current limit curve to keep power dissipation in the safe range for the ouput drivers up to the Hyper VOC limit. There doesn't seem to be any reason to just cut power generation off at that voltage since the devices are actually spec'd to work at the higher voltage. I don't believe there would be any code issues since the device has to be rated for proper voltage margins independent of power level.
I'm not sure why you're asking about my battery bank, but at the moment I'm running a 24 Volt nominal bank (usually actual chargine voltage in the range of 25 to 29 volts). I will be upgrading to a 48 volt nominal bank in the next few years at battery replacement time, or when my inverter fails. Batteries are 15 years old and inverter is 25 years old, so you never know when that may happen.
While running at the lower battery bank voltage I need all the current capacity I can get, that's why I didn't want to go to a Classic 250, it would have been that much more clipping due to current limitation compared to the 200. Peak voltage from the panels is well within the range of the 200 at any temperature.
Thanks for your response on this.
Sorry that this was a confusing spec ppanish ! We'll see what we can do to make this clearer in the future.
The reason I asked you what your battery voltage was, is because you can add your battery voltage to the actual Voc limit (150V, 200V, 250V)
For a 150 and 24V bank, the Classic will be able to handle up to around 172 volts open circuit if your PV array should get really cold.
The reason we cannot just run the Classic at above the 150, 200 or 250V rating is because of how the switching circuit operates. If it was to run at all above those voltage limits, we would over-voltage the transistors that are doing the switching.
When it is not switching or running but the PV is at a higher than normal voltage, the battery voltage presents an internal circuit scenario where that battery voltage can, to a certain extent, be subtracted from that too high of PV array voltage and keep the transistors from being over-voltaged.
If the Classic were then to start switching, the transistors would then be exposed to a voltage higher than their specifications.
Some controllers don't even run up to their transistor ratings of 150, 200 or 250 volts DC.
Anyway, we will see if there is some kind of wording we can change in future blurbs to avoid the confusion.
I notice in our paper, whyHyperVOC.pdf, https://www.midnitesolar.com/pdfs/whyHyperVOC.pdf it does say:
Remember the Classic will not turn on when the PV input voltage is above 150V
That fact could be spelled out a bit better. I don't think we have been asked to change that but I am not answering the phones and emails every day.
Thanks !
boB
I peaked that 172V range out the other day when it got down -30F, had to clamber up there and take two panels offline. :o Was 3S2P need to convert it to 2S3P on 24V system.
bOB,
Thanks for the response. I hadn't seen the document you mention, but I thought I had looked over the HyperVOC section of the manual reasonably carefully when I bought the Classic 200. Looking it over again it seems pretty clearly spelled out that the unit won't operate above the rated nominal voltage. I think I probably decided the additional current capability was worth it to me since it may be a few years before I move to a 48 VDC battery bank.
We are currently having what will likely be our coldest days this winter, getting down to -5 around sunrise. The panel voltage never gets above 202 volts, and within an hour of sunrise the panel temperature is at the point where it's no longer in the HyperVOC range, so I can certainly live with it.
However, I do wonder if it's necessary to have total shutdown at nominal voltage. It's been a long time since I designed any power circuitry, and even longer since my classes in circuit design and semiconductor physics. However from what I remember, and have looked up, breakdown voltage in both FET and Bipolar devices doesn't go down with increased current. As long as the devices are kept in the safe operating range you could continue to throttle back operating point until total shutdown at HyperVOC cutoff. This would further improve the HyperVOC feature if it's feasible, and I believe it would be a fairly simple software change.
At any rate, not a significant problem, and with warming temperatures I suspect in another few years I will (unfotunately) see even less of this occurring.
Quote from: Vic on August 11, 2014, 06:08:10 PM
ReasonForResting = 104 Watchdog WDT reset (only at boot until first RFR)
The problem with paying attention to what's going on with your system is that you start seeing scary messages like the one above! Is this something to be concerned about?
Is it something that could be caused by the Classic 150 getting too warm? The fan seems to run almost all the time -- it's noticeable when it stops.
Thanks,
Laura
Quote from: ljane on January 21, 2022, 11:09:12 AM
Quote from: Vic on August 11, 2014, 06:08:10 PM
ReasonForResting = 104 Watchdog WDT reset (only at boot until first RFR)
The problem with paying attention to what's going on with your system is that you start seeing scary messages like the one above! Is this something to be concerned about?
Is it something that could be caused by the Classic 150 getting too warm? The fan seems to run almost all the time -- it's noticeable when it stops.
Thanks,
Laura
Hi Laura
Does your Classic have the A-Rst turned on in the TWEAKS menu ? If so, that might have come from the night before at midnight.
WDT is how it causes the reset to occur in that case.
The Classic should not reset because of getting too warm. When the Classic does get hot like, around 90 degrees C on the FET TEMP, it will just reduce the output power until the temperature falls some. That's what it SHOULD do anyway.
boB