I just had a Classic do something strange. The network switch it was plugged into failed. When I plugged the network cable into the new switch, the Classic restarted and now is stuck on 52.7V overvoltage on a 24v system. The Input Voltage is stuck at 111V whether the solar is on or off. It is nighttime right now. I have tried rebooting the classic and I have checked all the connections.
Any ideas what could be wrong?
I searched the forums and could not find anything with overvoltage on solar.
Is the Classic blown?
Here is the register export:
16385,65535,app_version,65535,
16386,65535,net_version,65535,
16387,1923,app_rev,1923,
16388,0,,
16389,1839,net_rev,1839,
16390,0,,
4101,1224,UNIT_ID,1224,
4102,2014,UNIT_SW_DATE,18.12.2014,
4103,3090,,
4104,13,InfoFlagsBits3,13,
4105,0,,
4106,19143,UNIT_MAC_Address,60:1D:0F:00:4A:C7,
4107,3840,,
4108,24605,,
4109,1,UNIT_IP_Address,0.0.0.1,
4110,0,,
4111,35718,UNIT_Device_ID,-289502330,
4112,61118,,
4113,40960,,
4114,1999,RestartTimerms,1999,
4115,576,Battery Voltage,57.6,
4116,1117,Input Voltage,111.7,
4117,0,Output Current,0,
4118,0,kWh,0,
4119,0,Watts,0,
4120,2304,Charge Stage,9,
4121,0,Input Current,0,
4122,1116,LastVoc,111.6,
4123,1881,,188.1,
4124,0,MatchPointShadow,0,
4125,0,Amp Hours,0,
4126,33183,Total kWh,3318.3,
4127,0,,
4128,57002,Total Amp Hours,122538,
4129,1,,
4130,12288,InfoFlagsBits1,12288,
4131,45568,InfoFlagsBits2,45568,
4132,246,Battery Temperature,24.6,
4133,272,FET Temperature,27.2,
4134,354,PCB Temperature,35.4,
4135,0,NiteMinutesNoPwr,0,
4136,300,,
4137,502,ModbusTCPPort,502,
4138,1,TimeMinutesFloatToday,1,
4139,7183,AbsorbTime,7183,
4140,0,DaysSinceLastFloat,0,
4141,50,PWM,50,
4142,4,SunRiseTodayMsrd,4,
4143,3600,Equalize Time,3600,
4144,0,,
4145,1,,
4146,0,USB Comm Mode,0,
4147,0,NoDoubleClickTimer,0,
4148,780,Battery output Current Limit,78,
4149,294,Absorb Set Point Voltage,29.4,
4150,278,Float Voltage Set Point,27.8,
4151,296,Equalize Voltage Set Point,29.6,
4152,780,Sliding Current Limit,780,
4153,0,Minimum Absorb Time,0,
4154,7200,Maximum Absorb Time,7200,
4155,296,Maximum Battery Temperature Compensation Voltage,29.6,
4156,274,Minimum Battery Temperature Compensation Voltage,27.4,
4157,50,Battery Temp Comp Value for each 2V cell,50,
4158,0,Battery Type,0,
4159,0,Equalize Retry Days,0,
4160,0,Force Flag Bits,0,
4161,0,,
4162,3600,Equalize Time,3600,
4163,0,Equalize Interval Days,0,
4164,10,Mppt Mode,10,
4165,20993,Aux 1 and 2 Function,20993,
4166,293,Aux1VoltsLoAbs,29.3,
4167,1,Aux1DelayT,1,
4168,3000,Aux1HoldT,3000,
4169,1,Aux2PwmVwidth,1,
4170,0,,
4171,0,,
4172,296,Aux1VoltsHiAbs,29.6,
4173,900,Aux2VoltsHiAbs,90,
4174,65516,Aux1VoltsLoRel,-2,
4175,10,Aux1VoltsHiRel,1,
4176,65516,Aux2VoltsLoRel,-2,
4177,50,Aux2VoltsHiRel,5,
4178,587,Aux1VoltsLoPv,58.7,
4179,660,Aux1VoltsHiPv,66,
4180,357,,
4181,1400,Aux2VoltsHiPv,140,
4182,24576,FanSpeed1PwmCompare,24576,
4183,202,ArcFaultSenstvty,202,
4184,95,,
4185,0,,
4186,23244,Enable Flags 2,23244,
4187,64,Enable Flags 1,64,
4188,0,PWM Offset,0,
4189,0,Vbatt Offset,0,
4190,0,Vpv Offset,0,
4191,1116,VpvTargetRd,1116,
4192,1350,VpvTargetWr,135,
4193,0,VbattGainAdj,0,
4194,0,VpvGainAdj,0,
4195,0,IbattGainAdj,0,
4196,0,IpvGainAdj,0,
4197,4,LgcySweepIntervalSecs,4,
4198,100,MinSwpVoltage,10,
4199,990,MaxSwpVocPercentage,99,
4200,8,SweepDepth,8,
4201,8,PrePwmConnectOffsetAdjSS,8,
4202,776,ClipperMaxVoltage,776,
4203,0,WindNumberOfPoles,0,
4204,8,MppPercentVoc,8,
4205,0,WindTableToUse,0,
4206,0,WindTableLearn,0,
4207,3,LED Mode,3,
4208,1117,,
4209,0,,
4210,12851,Unit Name,32141,
4211,13361,,
4212,49,,
4213,0,,
4214,4882,CTIME0,68490002,
4215,1045,,
4216,264,CTIME1,132120840,
4217,2016,,
4218,111,CTIME2,111,
4219,0,BaudRateStopStartEtc,0,
4220,0,RemoteMenuMode,0,
4221,0,RemoteButtons,0,
4222,0,VbatOvrshootSenstvty,0,
4223,0,VpvStartupDeltaSS,0,
4224,1116,PreVoc,1116,
4225,0,Vt2PwmDiff,0,
4226,0,VauxA2Dinput,0,
4227,1,,
4228,1,,
4229,0,,
4230,1116,,
4231,1116,VocRD,1116,
4232,0,,
4233,1117,,
4234,16,,
4235,0,,
4236,7182,AbsorbTime,7182,
4237,50,AntiClickSenstvty,50,
4238,131,SiestaTime,131,
4239,20,SiestaAbortVocAdj,20,
4240,8320,flagsRD,8320,
4241,0,,
4242,0,,
4243,240,,
4244,291,VbattRegSetPTmpComp,291,
4245,24,VbattNominal,24,
4246,12,EndingAmps,1.2,
4247,5,EndingSoc,5,
4248,200,BattCapacityAhrs,200,
4249,262,RebulkVolts,26.2,
4250,88,BattAhrEfficiency,88,
4251,0,BattMonSOC,0,
4252,3,BattMonAmps,3,
4253,0,BattMonAHefficiency,0,
4254,0,,
4255,0,,
4256,0,,
4257,0,RebulkTimerSec,123273216,
4258,1881,,
4259,2,,
4260,0,,
4261,295,,
4262,1,,
4263,41,,
4264,0,Voc_Qualify_Timer_1ms,0,
4265,0,,
4266,0,MinVpvTurnOn,29.3,
4267,41,,
4268,41,,
4269,0,,
4270,0,,
4271,25000,,
4272,41,RestartTimerms,41,
4273,0,Ibatt,0,
4274,224,,
4275,36,ReasonForResting,36,
4276,578,Output Vbatt,57.8,
4277,1116,,
4278,200,Typeint,200,
4279,0,,
4280,75,MinLogZeroNdx,75,
4281,0,LogValueRead,0,
4282,0,PkHoldVdTcapVpvStamp,0,
4283,1118,VpvTargetRd,1118,
4284,0,SwpDeepTimeoutSec,0,
4285,0,TESTSHORT3,0,
4286,20,LowWatts,20,
4287,50,WindLowWatts,50,
4288,17,WindWindowWattsRef,17,
4289,57536,WindowWattsRO,57536,
4290,90,WindTimeOutRef,90,
4291,1800,WindTimeOut2Ref,1800,
4292,0,WindTimeOut,0,
4293,0,WindTimeOut2,0,
4294,750,MinVpvTurnOn,750,
4295,0,VpvB4TurnOff,0,
4296,65474,HydroSwpAmps10Time6,65474,
4297,0,EndingAmpsTimerSec,0,
4298,970,PkAmpsOverLimitHi,970,
4299,850,PkAmpsOverLimitLo,850,
4300,4,FactoryVbattOffset,4,
4301,23386,WindPowerTableV+0,23386,
4302,24156,WindPowerTableV+1,24156,
4303,25184,WindPowerTableV+2,25184,
4304,26212,WindPowerTableV+3,1717829832,
4305,27240,WindPowerTableV+4,27240,
4306,28268,WindPowerTableV+5,28268,
4307,29296,WindPowerTableV+6,29296,
4308,30836,WindPowerTableV+7,30836,
4309,512,WindPowerTableI+0,512,
4310,1796,WindPowerTableI+1,1796,
4311,3338,WindPowerTableI+2,3338,
4312,5393,WindPowerTableI+3,5393,
4313,7705,WindPowerTableI+4,7705,
4314,10275,WindPowerTableI+5,10275,
4315,12589,WindPowerTableI+6,12589,
4316,15159,WindPowerTableI+7,15159,
4317,0,UNIT_Reserved,0,
4318,1297,PkAmpsOverTrip,1297,
4319,0,UNIT_Reserved,0,
4320,0,mnlp_revision,0,
4321,0,ReadRamAddress,0,
4322,0,,
4323,0,ReadRamDataRO,0,
4324,0,,
4325,0,UNIT_Reserved,0,
4326,10,ClassicModbusAddr,10,
4327,32768,BatteryTempPassedT,32768,
4328,128,iFlagsRO,65664,
4329,1,,
4330,0,ModbusControl,0,
4331,0,ClassicFmePassedBits,0,
4332,0,WindSynchA,0,
4333,0,WindSynchV,0,
4334,0,FollowMePassRefS,0,
4335,0,SchedTimer03,0,
4336,0,SchedTimer04,0,
4337,100,SchedTimer05,100,
4338,1000,SchedTimer06,1000,
4339,32669,SchedTimer07,32669,
4340,64,SchedTimer08,64,
4341,10261,DabtU32Debug01,672484381,
4342,19485,,
4343,52156,DabtU32Debug02,-876852030,
4344,19650,,
4345,41296,DabtU32Debug03,-1588552380,
4346,40260,,
4347,41296,DabtU32Debug04,-1588552380,
4348,40260,,
4349,132,SchedTimer17,132,
4350,0,SchedTimer18,0,
4351,0,SchedTimer19,0,
4352,40106,SchedTimer20,40106,
4353,63037,SchedTimer21,63037,
4354,0,SchedTimer22,0,
4355,0,SchedTimer23,0,
4356,43,,
4357,65333,,
4358,19705,,
4359,134,,
4360,134,,
4361,53,,
4362,65529,,
4363,0,,
4364,0,,
4365,31294,WbJr AH(+),31294,
4366,0,,
4367,32790,WbJr AH (-),-32746,
4368,65535,,
4369,1,WbJr AH (net),1,
4370,0,,
4371,8,WbJr Amps,0.8,
4372,34380,WizBangJrRawCrcAndtemp,34380,
4373,99,WBJr SOC,99,
4374,696,WbJrAmpHourChrg,696,
4375,0,WbJrAmpHourChrgadj,0,
4376,1,WbJrAmpHourDisChrgadj,1,
4377,232,WbJr AH Remaing,232,
4378,28323,WbJrAmpHourDisChrg,28323,
4379,190,BatCapacityTrefMBus,19,
4380,30,WbJrBatAhrCompPcntMBus,3,
4381,233,UNIT_Reserved,233,
4382,56,UNIT_Reserved,56,
4383,0,UNIT_Reserved,0,
4384,0,UNIT_Reserved,0,
4385,0,UNIT_Reserved,0,
4386,0,UNIT_Reserved,0,
4387,0,DabtU32Debug05,0,
4388,0,,
20481,2,settings,2,
20482,43200,IP Address,192.168.0.55,
20483,14080,,
20484,43200,Gateway Address,192.168.0.1,
20485,256,,
20486,65535,Subnet,255.255.255.0,
20487,255,,
20488,43200,Primary DNS,192.168.0.1,
20489,256,,
20490,0,Secondary DNS,0.0.0.0,
20491,0,,
see the last post...
http://kb1uas.com/mnsforum/index.php?action=search2
hth
PS search "36" or "RFR 36"
Quote from: Westbranch on January 09, 2016, 12:33:45 AM
see the last post...
http://kb1uas.com/mnsforum/index.php?action=search2
hth
PS search "36" or "RFR 36"
RFR is 22 which seems to point to battery overvoltage. The Classic is reporting 57 v on a 24 v system. Volt meter is reporting 28v. With it being dark, classic is reporting over 100v on the solar input and the volt meter reports 44v. It usually reports anywhere from 22 to 70 v when it is dark. I am guessing that when I plugged the Classic into the replacement network switch, something "shocked" the Classic logic board causing the reboot and the subsequent bad readings.
Time for a new Classic it would seem.
I had one do this after a network anomaly. I let it set off for 45 minutes and it went away. Try that and if not let me know (ryan@midnitesolar.com) I will issue an RMA
Quote from: Halfcrazy on January 09, 2016, 06:05:52 AM
I had one do this after a network anomaly. I let it set off for 45 minutes and it went away. Try that and if not let me know (ryan@midnitesolar.com) I will issue an RMA
It has been off all night long. This morning I turned it on, battery voltage at 57V, Solar reads 158V. It seems it is reading about 30V high on the battery side and about 90v high on the solar side.
Id be inclined to try a VMM, to reset the registers to factory defaults. Just in case some odd packets spewed out of the thing in its dying breath.
Quote from: zoneblue on January 09, 2016, 10:12:12 PM
Id be inclined to try a VMM, to reset the registers to factory defaults. Just in case some odd packets spewed out of the thing in its dying breath.
Did the hardware jumper and soft < > VMM, still no change. I ordered a new one on ebay for $500, will wait for a RMA from Midnite and see how much it is going to cost to repair. Can't be without it for more than a week, that way I will have a spare in case one of the two I own fail again.
If there are several readings displaying too high, it is probably a low-ish 3.3V to the processor.
If it is only the battery voltage, it is possibly an open or high value voltage divider resistor.
If the Ethernet switch problem is related then maybe the Ethernet PHY chip inside the Classic
went bad at the same time, taking the 3.3V down a bit and making the readings high.
Except that temperatures read lower I believe and not higher.
Sounds like this might be a normal warranty covered thing to me.
boB
Quote from: boB on January 10, 2016, 01:37:16 AM
If there are several readings displaying too high, it is probably a low-ish 3.3V to the processor.
If it is only the battery voltage, it is possibly an open or high value voltage divider resistor.
If the Ethernet switch problem is related then maybe the Ethernet PHY chip inside the Classic
went bad at the same time, taking the 3.3V down a bit and making the readings high.
Except that temperatures read lower I believe and not higher.
Sounds like this might be a normal warranty covered thing to me.
boB
I was reading that in another thread where it said the 3.3 v line being low would cause bad readings. I didn't verify the temperature readings, though. It is both the solar and battery voltages that are reading high. Ryan is sending a new unit out Monday with an RMA. I did order a spare to go along with my spare inverter so downtime would be minimal next time.
Thanks a bunch for all the help.
A BIG THANK YOU to Ryan for getting a new Classic out so quickly to replace the one that failed. New one is in and working like a charm!
Just a bit of history, the old one failed when I plugged it into a new ethernet switch.
I will now power down the classic whenever I must remove the ethernet or USB just to be on the safe side.
Again, Ryan, a BIG THANK YOU!!