This message is telling you that the MNGP "Display" is not able to communicate with the Classic. The most common cause of this would be that the address the MNGP is looking at got changed to one that is not on the network. When at the Home screen or main status screen there will be a word in the middle at the top. On a single Classic this should say Classic if it does not say this then you need to use the up and down arrows to find Classic. The MNGP should regain communications when this is set correctly.
Halfcrazy.....I use a MNGP to set up and change parameters on a couple of Classic Lites I have installed for 2 of my of customers..... when I plug it into the classic Lites (after powering down) I am getting a "Got Comm? message on the MNGP with a "01" instead of "Classic" in the upper middle portion of the MNGP.....there are no battery voltage or pv voltage showing (00).....I used the up arrow and down arrows on the MNGP but did not change.....any thoughts?
Hm so are you saying there is physically no PV or battery power to the classic and the MNGP is still lighting up? Are the Classics networked to each other in follow me?
Ryan
there is physically batt and pv power to the classic but it shows "0" volts........2 different Classic Lites.....no networking.
Ah ok. So you say it says 01 instead of classic. Sounds like it got off the address somehow. Try holding the left arrow and tapping the up arrow until you get to 10 and see if it fixes the issue.
Ryan
Ryan
That worked.....This happened on both of the Classic Lites...I hooked up the same MNGP to my Regular Classic at home and it displayed everything I would expect it to.....I'm sorry I failed to mention that I had just uploaded firmware 1370 to the 2 blind Classics (without the MNGP attached)...could this have been the cause? Thanks for the help.
Need to bring this thread back to life. I'm seeing this "Got Comm?" message on my display every once and a while as well. It's only there for a second and goes away. Things seem to be working fine, just curious why it's happening? Firmwares are all the latest.
I installed the MNGP a few months ago on a Lite 150 I've had in service for a few years. The name in the middle of the display is "Lite".
Glen
I've see it come momentarily also but since it goes back to normal just suspect it is a timing issue of some sort.
I was just wondering if it "might" be related in some way to the "network" communication issues some have, me included. I was just away from my system for a few days, and was unable to access the Classic remotely, after probably a 24hr period. I had to come home and physically power off, power on, for it to communicate again on my network. Maybe this "Got Comm?"is not related in any way, just throwing it out there.
From what I'm reading, the "Got Comm?" message is referring to MNGP to Classic, but perhaps it's affecting network connectivity as well?
Glen
Quote from: Muskoka on January 03, 2015, 10:15:01 AM
I was just wondering if it "might" be related in some way to the "network" communication issues some have, me included. I was just away from my system for a few days, and was unable to access the Classic remotely, after probably a 24hr period. I had to come home and physically power off, power on, for it to communicate again on my network. Maybe this "Got Comm?"is not related in any way, just throwing it out there.
From what I'm reading, the "Got Comm?" message is referring to MNGP to Classic, but perhaps it's affecting network connectivity as well?
Glen
Glen,
In the world of software & hardware I guess anything is possible. However, it's my guess that the Ethernet issue is separate although it may be a timing issue of sorts because we know from others that have researched this if the Classic is asked to dump data too fast it stops communicating. Some of the folks working on blackbox data access have run across this.
I'm sure Ryan has the correct info on the "Got Com ?" display and that it is between the Classic and the MNGP. Since even the Classic Lite without the MNGP communicate by Ethernet to the Local App and MyMidnite. I think the MNGP can be ruled out of the Ethernet communication issue. For the local app it could come down to the fact that it was written with Adobe Air and maybe the Adobe Air Network code is not robust enough for real time applications. Although, I used Wireshark to capture the Network communication a while back with older firmware and at that time the Local App sent out it's request and it was the Classic that did not respond back. The big question is WHY? And why in some cases does it require a Classic reboot to get it working again.
The "Got Comm ?" message is separate from the Ethernet issue.... However, the Got Comm messages should be lessened in
this new beta code, among some other changes.
http://fusion.midnitesolar.com/MidNiteSolarUpdate_1923_12-18-2014_v4.60.exe
Try it if you like to. Update the MNGP too, or maybe just the MNGP code for the Got Comm message.
boB
Here is a list of changes from the Readme-Changes.txt file...
12-18-2014
Classic build 1923
Lifetime kW-Hours and Lifetime Amp-Hours will now accumulate and
not be limited to just 16 bits worth. (long time bug) 65535
Aux 1 SOC% output will now remember On/Off state through an auto-restart cycle
Whizbang Junior accumulations will save periodically throughout the day to non-volatile memory every 90 minutes
Classic will go to Resting for 8 seconds when MPPT mode and power output stays below 50 watts for 15 minutes in Legacy, Hydro or Dynamic tracking mode if Insomnia is On. (night charging sanity check)
Removed VariMax Absorb mode
MNGP build 1922
Added menu LIMITS---MORE--- High battery temperature charger shut off
Fixed Daily Hi-Power graphs log numerical readout. Was only
showing 3 digits
Increased time required to show "Got Comm ?" message by 2 seconds
Might be unrelated, but my Classic had the message Got comm ? Displayed on the screen yesterday when I first discovered it had overheated and had shorted unregulated panel output to the battery, pumping it up to ~74v (48v system) and causing permanent damage.
This disappeared when it cooled down. Maybe this is a sign of yours approaching that point, then the fans saving it, check FET temps when this happens again.
Quote from: wrt on January 03, 2015, 11:54:28 PM
Might be unrelated, but my Classic had the message Got comm ? Displayed on the screen yesterday when I first discovered it had overheated and had shorted unregulated panel output to the battery, pumping it up to ~74v (48v system) and causing permanent damage.
This disappeared when it cooled down. Maybe this is a sign of yours approaching that point, then the fans saving it, check FET temps when this happens again.
The Classic itself may have crashed and then it was reset or re-powered ? That may have brought communications back to life.
Quote from: Resthome on January 03, 2015, 01:10:27 AM
I've see it come momentarily also but since it goes back to normal just suspect it is a timing issue of some sort.
Well, that's 2 of us that see it briefly and it resolves on it's own. Another posting for other issues later.
(and I was looking at it with the local app 2 feet away, and saw the blink on the MNGP)
Quote from: Halfcrazy on March 05, 2011, 11:18:38 AM
This message is telling you that the MNGP "Display" is not able to communicate with the Classic. The most common cause of this would be that the address the MNGP is looking at got changed to one that is not on the network. When at the Home screen or main status screen there will be a word in the middle at the top. On a single Classic this should say Classic if it does not say this then you need to use the up and down arrows to find Classic. The MNGP should regain communications when this is set correctly.
am having the same issue with my midnite classic 200 4 days now i notice it . any solution would be deeply appreciated screen shot is below
Janoy876
if this issue happens randomly and will not clear itself then it could be an issue with the hardware. If it just pops up every now and then for a few seconds that is considered normal.
I would suggest if it is a hard fault and requires you to reboot the controller that you contact tech support and let them know you may need a new control board and MNGP per Ryan they can be contacted at support@midnitesolar.com
Today my new Classic 150 showed "GOT COMM?" for the first time, immediately after I installed my new Wizbang Jr. Soon after wiring the Jr. I figured I was home free--the Jr.'s LED was flashing to indicate good communication with the Classic. Then suddenly the Jr'.s status info just stopped updating in the front panel, and I got "GOT COMM?" on the Classic main menu. A check of all the wiring and several power cycles later, the problem mysteriously disappeared and has not recurred.
I did have to extend the length of the Jr.'s data cable by several feet (I crimped on some 20 AWG solid copper).
Could "GOT COMM?" be in any way related to addition of the Wizbang Jr.?
Could "GOT COMM"? be induced by noise caused by my extension of the data cable?
JohnZ
Hi JohnZ,
The Got Comm? Message used to be fairly commonly seen with earlier FirmWare (FW) versions. Generally it was meaningless.
What is the FW version that is running on the Classic and MNGP?
Am not an expert on these things, but would expect that the extension of the WbJr's Violet wire would have no direct effect on that message.
Have noticed with earlier FW versions, that going to the Network pages on the MNGP, that any key entry other than the left or right arrow, seemed to generate the Got Comm? message for some minutes, but later, the appearance of that message would stop, seemingly on its own ...
FWIW, Vic
Local app shows these firmware versions for my Classic 150:
Classic Rev: 2096
Network Rev: 2097
The unit was purchased in August, 2016--so it's new. Not sure how to find the firmware rev of the MNGP. I've never flashed new firmware.
Again, today's "GOT COMM?" event feels related to my wiring the Wizbang Jr. today. It's also the case that I visited a lot of MNGP menus today that I normally don't touch. I had set the mode to "OFF" for a while.
In any case, system has been working normally since this event.
JohnZ
JohnZ you are up to date on the FW... to find it go to WWW. Midnitesolar .com and
in the choices bar at the top of the page choose Software
If it comes back you can always try a Factory Reset ( Vulcan Mind Meld).... and if you do not use the local App to save the settings you may have to reset them by hand...
Quote from: Jszuckerman on October 29, 2016, 06:27:17 PM
Local app shows these firmware versions for my Classic 150:
Classic Rev: 2096
Network Rev: 2097
The unit was purchased in August, 2016--so it's new. Not sure how to find the firmware rev of the MNGP. I've never flashed new firmware.
Again, today's "GOT COMM?" event feels related to my wiring the Wizbang Jr. today. It's also the case that I visited a lot of MNGP menus today that I normally don't touch. I had set the mode to "OFF" for a while.
In any case, system has been working normally since this event.
JohnZ
Hi John,
Thanks for the info on the FW version. Your up to date with Production FW.
Assume that you have not set up any of the Network configuration stuff on that Classic...
You do know that when the Classic and the WBjr are communicating, that the green LED on the WB flashes about every five seconds -- this should be quite consistent.
Extending that Violet WB interface cable by "several feet" should not affect the communication on most systems. To me, several feet, is essentially two feet.
I did need to extend this cable on several systems, and used shielded control type cable. The shield was grounded only on one end of that cable. And, this cable was run in EMT (metal) conduit that has only BTS and shielded Aux control cables inside.
With some systems, there could be NOISE induced into that WB Violet interface cable. And with no communication between the WB and the Classic, the green WB LED would not be flashing, OR, it would be flashing frequently, and seemingly randomly.
Is the WB interface cable run with, or in parallel with any power conductors (AC, PV, or battery)?
Thanks, Vic
>>> Extending that Violet WB interface cable by "several feet" should not affect the communication on most systems. To me, several feet, is essentially two feet.
I added between 2 and 3 feet of unshielded wire to the interface cable.
>>> I did need to extend this cable on several systems, and used shielded control type cable. The shield was grounded only on one end of that cable. And, this cable was run in EMT (metal) conduit that has only BTS and shielded Aux control cables inside.
>>> With some systems, there could be NOISE induced into that WB Violet interface cable. And with no communication between the WB and the Classic, the green WB LED would not be flashing, OR, it would be flashing frequently, and seemingly randomly.
I am now getting consistent flashing at the 5 second rate.
>>> Is the WB interface cable run with, or in parallel with any power conductors (AC, PV, or battery)?
Yes, unfortunately I did run the WB interface cable in parallel with the power conductors. While troubleshooting yesterday, I did wiggle the interface cable, changing its orientation to the power cables significantly.
I'd be happy to change to shielded cable. Can you recommend a type of shielded cable? (How would it be specified?)
Would the violet interface cable need to be replaced all the way back to the WB Jr?
Hi John,
Why not wait to see is the issue repeats.
If you see this issue again, at this point, it is probably easiest to just make a Twisted Pair -- the signal conductor, twisted with a ground wire of about the same size as the signal wire.
Ground one end of that added wire, twisted with the Violet wire. This should be about as effective as would be a shielded cable, and would be easier.
Opinions, Good Luck, Vic
Problem hasn't recurred so far.
Twisted pair: that's a great idea--I was wondering if a twisted pair would do as well--but being a software guy, I just wasn't sure. Many thanks, JohnZ
So a new 150 was installed and running great in a remote cell tower in NewMexico. I came up to do some work and clean up wiring. I had a DC GFP alert and the red, yellow,and green leds came on. I turned off PV and DC to the unit to do a reset and when I added DC power back I get this GOT COMM? So, I did a reset to factory default but it returns. Im not getting any charging out of the unit at all.. Any help here. Im supposed to fly back to FL Monday morning.
With all the LEDs lit that tells me there is a failure on the main board int he processor, two of the 3 LEDs are driven from the main board. And with the issue a factory restore will not help as the two are not talking. You could try the jumper reset but I am afraid you need to call tech support tomorrow (or open a ticket today) for some repair help
Hi FishH20,
When someone posts, "tower" and "New Mexico", some of us think about LIGHTNING, and the often rocky "soil", which can create problems in getting a fairly solid ground, to dissipate energy from nearby strikes.
You, too, may have considered possible lightning damage to your electronics, etc, and you may have Surge Protection Devices already installed.
Assume that this is a personal Cell Phone Repeater (or similar).
I know nothing of the exact workings of the Classic internals, but am sure that FNG, does.
This situation may well not have been related to any lightning, but, it might not hurt to review good practices for lightning protection, if you are not too well versed in that.
There are many, many variables is designing and implementing effective lightning protection measures, but this art is fairly well-known in the Communication business, although there are many site variables.
FWIW, Good luck, Vic
Thanks for getting back Vic.
The site was not hit and we are running gas surge protectors and all is grounded good. I ended up pulling the unit and flying back with it to work with support. Luckily I had a back up controller for the site and all is up I just don't know what the heck happened yet to this unit. Could have been a mistake I made or something else.
Quote from: Vic on June 03, 2018, 11:18:21 PM
Hi FishH20,
When someone posts, "tower" and "New Mexico", some of us think about LIGHTNING, and the often rocky "soil", which can create problems in getting a fairly solid ground, to dissipate energy from nearby strikes.
You, too, may have considered possible lightning damage to your electronics, etc, and you may have Surge Protection Devices already installed.
Assume that this is a personal Cell Phone Repeater (or similar).
I know nothing of the exact workings of the Classic internals, but am sure that FNG, does.
This situation may well not have been related to any lightning, but, it might not hurt to review good practices for lightning protection, if you are not too well versed in that.
There are many, many variables is designing and implementing effective lightning protection measures, but this art is fairly well-known in the Communication business, although there are many site variables.
FWIW, Good luck, Vic