Unable to transmit deployed science

[fragtzack]

Deployed science on the Mun, silly me put the kit on the far side... 

So now am getting spammed messages that say "Unable to transmit deployed science data from the Mun , deployed science cluster has no CommNet connection to home".

Yet, I deployed a relay satellite that satellite is verified working. The satellite is almost directly over head and still not working.

 

Seems a bug or am i missing something?

Relay satellite "show network" clearly shows a green connected line back to Kerbin when the satellite is overhead of the deployed science.

 

Edit: This is not a bug, just a noob Kerb.. I needed to wait a few more orbits for the deployed science to be in the sunlight. All good now. Relay working!

Edited June 8, 2019 by fragtzack
Discovered issue.

[Aegolius13]

Do you have the deployable antenna with your experiments?  I haven't definitevely figured this out yet, but perhaps you need one to beam back the science.  Even though the experiment controller has an onboard antenna, it may be that it can't be used to transmit results, much like the built-in antennae on the command pods.

[Jan Kerjann]

Same kind of problem here. Deployed stuff on Minmus, surrounded Minmus with relays, but every ten minutes it gives me a message that there is no connection. The problem I have is not the connection that might or might not work. The problem is the spamming with the messages. If I do something else, like fly to Duna or catch some innocent asteroid, the spamming doesn't stop. Time warping for a bit easily gives me around 200 messages. Needs a change so that those "no connection" messages don't spam the message thingie. Lots of important messages have been lost due to clicking away some hundered notifications about having no connection.

 

EDIT: The message spamming stopped once I exchanged the solar panels for RTGs.

Edited June 12, 2019 by Jan Kerjann
new info

[AHHans]

You probably already noticed this, but in case you haven't: the recent patch to KSP 1.7.2 (BG 1.1.0) should have fixed this.