Go-ob ED lost connection with control station after collecting all science

[a2soup]

So I deployed a small experiment station on the Mun in my first breaking ground career mode to fulfill a contract. Was working pretty great for a while. I checked in on it after a while, however, and found that it had apparently gotten disconnected from the control station, but only after collecting 100% science. The problem is that only 10% of this science ended up getting transmitted for some reason. What's up with that?!

None of the modules seem to have moved around at all, and it is definitely still in range of the control station, which is still receiving power from the solar panel. Screenshot with context menus is at the link, it won't let me insert the image for some reason.

How can I fix this, and how can I stop it from happening again?

https://imgur.com/a/Nr1joPS

EDIT: On second look, maybe the connection with the control station isn't lost, but it's not receiving power for some reason? I don't know, man.

Edited March 1, 2020 by a2soup

[AHHans]

Well, the Go-ob ED didn't loose connection as such, but it shut itself down after it thought that it did its job. The deployed science works in the way, that while they are working every now and then (every 10% of science gained?) they try to connect to the KSC and transmit their science. If they cannot transmit at that moment - either because there is no commnet connection (at that moment!) or no power (e.g. because the solar panels are in darkness) - then they keep the data and continue on. If they have a connection at a later try then they transmit all data that has been accumulated up to then. But once they reach 100% researched science they do another try to transmit data and then shut themselves down, even if they couldn't transmit their data. So if you have a setup with spotty commnet connectivity or are just unlucky then it can happen that whenever the experiments try to transmit their data this fails for some reason or another. And when they reach 100% researched science they give it a final try, fail again, and then stop trying altogether.

The only way to "fix" this that I know of is to go there with a Kerbal - preferably a scientist - pick up the experiment, and place it again. This resets the experiment and it can try from scratch.

Yes, this sucks. Welcome to the club.

Edited May 13, 2020 by AHHans
fixed typo

[a2soup]

Wow, is there a bug report on that? Seems like an unintended behavior, given that spotty power and signal work up until it reaches 100%. At the least there should be a button in the context menu to attempt transmission or something.

Anyways, looks like I have some commnet work to do before I reset it to try again. Thanks so much for your help!

Edited March 1, 2020 by a2soup

[a2soup]

To anyone who may find this in the future: The fix described above worked great, but it was actually unnecessary to set the experiment back up since it turns out that when a Kerbal picks up an experiment with 100% complete but untransmitted science, they hold that science just like any other science result and can take it back to Kerbin with them. They may even be able to transmit it after putting it in a commnet-connected craft, but I didn't test that unfortunately.

I hope this helps someone out there, since I was unable to find any documentation of these mechanics anywhere online.

Edited March 3, 2020 by a2soup

[StrandedonEarth]

I just ran into this bug, since I guess my relay wasn't in the right position above Eeloo when the Goo tried to transmit. I was able pick up and put away the goobered monitor, then board the minerefinery and transmit the data home, which completed the contract.

It would be nice to be able to force transmission though, whenever someone feels inclined to add it to the bugtracker.... Maybe it's fixed for 1.10?