Fredk, you are right - the weight of twitter-evidence today points at seconds, rather than minutes, of connect time. Perhaps he meant the time of the total comm session incl. listening in when he mentioned "minutes".
Anyway, I posted a comment to the Philae awake blog post from ESA, respectfully asking for a daily status update. Even "no news today" would be most welcome to contain my excitement and interest for a next 24 hrs!

This is a good update, in German, sorry.

http://www.dw.de/rosetta-muss-ihre-antenne...hten/a-18518860

and an update from DLR in English
http://www.dlr.de/dlr/en/desktopdefault.as...#/gallery/16734

More news from ESA here: http://www.esa.int/Our_Activities/Operatio...ntense_planning

The kind of stories we all love to read here: http://blogs.esa.int/rosetta/2015/06/15/ho...rd-from-philae/

Looks like real Philae data. According to the ESA Rosetta glossary ESS refers to the Electrical Support System of the lander. It's temperature value was updated 16.06.2015 07:37:30 and shows an increase to 21.43 °C.

From the Rosetta lander user manual:

Just look at the top image on:
http://isee3.p3s.nl/philae/

The system locations are indicated on Roseta and Philae.

The webmaster at http://isee3.p3s.nl/philae/ confirms that these are old data. Notice the other readings, which relate to pre-delivery status. S/he says: "....I've been meaning to update....."

Rosetta blog: http://blogs.esa.int/rosetta/2015/06/16/pr...etta_to_listen/
I would expect science from the surface as early as next week when Rosetta will reach the right "orbit".

Interview with Philippe Gaudon, project head at CNES about first re-contact with Philae (in french):

https://rosetta.cnes.fr/fr/jai-eu-la-chance...eveil-de-philae

Regarding the Philae telemetry page:
while it is correct that the webmaster of that site mentioned that he should probably update it he did also mention that it is showing the latest data on twitter. The only parameters that are currently updated correctly for Philae are PSSH_C_SBat_CH as well as PSSH_C_SBat_DCH which are solar panel current and rechargable battery current. Most data is from the 13th but there are also a few measurments from the 14th.

Interesting comment from Gaudon about the battery recharging, not seen that before. If true that's brilliant as that was previously mentioned as one of the possible failure points from the low temperatures.

They've been prepared to operate without the battery, directly with power from the solar panels.
But now there seems to be a chance, that the battery can be charged, and operated as initially planned.

Press conference coming up in half an hour:

http://www.esa.int/spaceinvideos/esalive

I'm on site at le Bourget! i will try to record it on my phone

if you have any question for the press conference let me know!

Lot's of interesting data being shown, including a landing site model, camera field of view and orientation, etc.
Very interesting.

They are being so thorough in their presenting that I'm struggling to find anything to ask!


Archive should be here once it's done.

http://www.esa.int/spaceinvideos/Keywords/...By%29/published

I have at least one question Paolo.
How about MUPUS PEN (the hammering penetrator), are they going to run that again? They didn't list it in their risky instrument suite (they did mention MUPUS as one of the first experiments to be run, but then they were referring to the thermal sensors). Obviously you can't redeploy the penetrator, so I suppose it depends on how it lies.

Edit: My questions aren't that important, but here is another one anyway.

Perhaps a way too soon to speculate, but any chance they will try to move (hop) Philae when winter starts approaching again on its side of the comet hemisphere for an of chance of sampling yet another location?

Looks like they're confident that they can turn Philae in the right direct to (eventually) drill the surface!

Also great preview of science results; carbon-rich materials cementing the ice grains, rather than the reverse. Papers getting published in a few weeks.

sorry, I was not able to record with the mobile and read the forum at the same time

They didn't take that many questions anyway. The most interesting part to me was probably what Explorer1 mentioned, although I suppose that's a long way off.

Looks like the next opportunity for contact with Philae will be on Friday.

http://spaceflightnow.com/2015/06/15/scien...h-comet-lander/

Here is the revised Philae position from the article in Spaceflight Now .

That revised Philae position image was released last week (always best to cite the original).

...and we got more contact.

https://twitter.com/esaoperations/status/611894877417291776

Slightly more data on today's contacts. There were two contacts, each 2-minutes long. 185 packets of data were collected.

They didn't say when the next contact would be, but they ended with this:

"The Rosetta and Philae teams will be closely monitoring subsequent transmissions between the spacecraft, not only to better determine the health of the lander, but also to understand the length and frequency of available communication timeslots. This information is needed to determine when to upload new commands in order to restart science operations and, similarly, when the data can be downloaded."

http://blogs.esa.int/rosetta/2015/06/19/ro...-contact-again/

A bit more info,

http://www.dlr.de/dlr/en/desktopdefault.as...#/gallery/17198

The two previous transmissions contained status information from early May showing Philae was at least awake by then.

"In the meantime, new commands have been uploaded to Rosetta to further adjust its trajectory and distance from the comet to improve the radio visibility between the two spacecraft, with the first sets of thruster burns having taken place this past Wednesday and the next set planned for Saturday morning. The goal is to bring Rosetta to about 177 km from the comet nucleus and keep it in a range of latitudes that maximise opportunities for lander communication."

rosetta-and-philae-in-contact-again

Looks like contact was made today as well, although I haven't seen any reports about it.

Yes, http://isee3.p3s.nl/philae/ again has been updated with new data from Saturday. Quite a bit more than on previous contacts so i would assume that the connection got more stable. Another interesting thing is that some kind of periodicity becomes apparent when looking at the data... i wonder what that is about. Anyways, it will be interesting to see whether they really can start to use for example the MUPUS PEN sensors next week.

Periodicity, huh? Could be a great many things. I'd assume that the lander-orbiter link is the highest priority right now, so I'm not sure what would interrupt it except for Rosetta downlinking that data to Earth. Does it perhaps correlate to Rosetta's orbital period around the comet at this time?

Really hard to say what the source is since i dont think the time axis in that chart always corresponds to the actual time the data was recorded (the DLR blog mentioned that some data was from May...). Instead it seems like it is the time it was received on the ground. Anyways it nearly looks like a heartbeat

Click to view attachment

The reported time between those spikes in current is really short (around five seconds).

Could it be that the time stamp is the receiving at the rosetta orbiter?

I think at -135°C temperature and no energy at all the internal time keeping of Philae became bogous anyway.
There was no downlink to Philae so were should the timing come from?

I do believe the timestamps originate on the ground, or on Rosetta, and are not based on the data from the lander. There are multiple reasons to think this is true, but the most telling reason is that this data is supposed to be from much earlier, perhaps even May, from what I've heard, but the timestamps appear to correspond with the days the data were received.

I've been working from the assumption that the cyclical nature of the battery data reflects the day/night cycle from Philae's location.
I dump the raw data from that server to a CSV file and play with it in Excel.
I like to imagine that Philae is trying to describe the surrounding terrain to me with its battery data as the shadows move across the panels.
Click to view attachment
That's just multiple cycles of one of the data series since Philae woke up, lined up side-by-side to form a surface, in case you're curious. Interestingly (to me), that particular data series doesn't seem to show up in the charts on the telemetry page, and the series aren't labeled in the raw data from the server, so I have no idea what it even represents.
(I dug through the javascript of that page once, back in November, to figure out what was what and what it was doing to the data before displaying it, but I've forgotten all of that and don't feel like doing it again right now.)

Here's a graph of the time (in milliseconds) between data points over the span of the new data (since the 14th or whenever):
Click to view attachment
Vertical axis is logarithmic. The highest peak corresponds to a gap of 4 days 16 hours. Assuming the timestamps are added by Rosetta, I'd like to think the relatively flat, long stretch is indicative of a more stable connection. If they're added on the ground, they could just represent different downlink modes on DSN or something; who knows; I really lack the context and background to draw any informed conclusions from any of this.

Edit/Update:
There were a few tweets from @DutchSpace over the weekend about the telemetry.

https://twitter.com/DutchSpace/status/612163178101907456 (includes chart)


https://twitter.com/DutchSpace/status/612167466211495936 (includes chart)


https://twitter.com/DutchSpace/status/612539793386401792 (includes chart)


I noticed that the label for the bottom chart has been updated so it looks like there is/was some work being done to improve the telemetry page.

As long as I'm editing, I might as well throw out more wild speculation. If the number of data points is correlated with the number of packets received, then, given the 300 packets reported for the first communication session, and the 84 data points for the first block of new telemetry data, one could guess that the current total of 336 data points received since wake-up indicates about 1200 packets (actually, the math of 336 * 300 / 84 comes out to exactly 1200) have been received so far out of the I-forget-how-many packets they said were stored on Philae.

Interesting, if not entirely positive, article from Le Point (in French) apparently regarding conversations with Gaudon,

http://www.lepoint.fr/astronomie/mission-r...938939_1925.php

Gist is it says there were two further contacts over the weekend on Saturday and Sunday, but none with uninterrupted communication windows longer than 2 minutes. They need at least 15 minute windows apparrently to upload commands to Philae. Says they'll try to get Rosetta down to 160km around Wednesday.

Interesting they mention uncertainty in the orientation of Philae. I had thought they earlier stated they had a good sense of that. And the mosaic I had made, with the help of Mattias' sun vector also gives some potential information about orientation, with an estimated 80 degree tilt compared with the "local" surface. We can even see the CONSERT antenna in the mosaic. The specification of orientation is better though before the rotation maneuver, though we can get a sense of this by the shift in the ROLIS images before/after.

I suspect the point is Philae might not be in the orientation they left it, if it is tilted more on its head that might explain the communication difficulties.

Makes sense that Philae could have shifted. I believe though the CONSERT antenna projects off the lower part of one of the sides, unless there's another reason the head (top) would be important.

We didnt hear anything form the mission today... i just hope that they dont run into another safe mode. The Startracking failure graph they showed at the last press conference was pretty scary.

Click to view attachment

The blue line represents how many issues there have been with the star trackers and the dotted grey one is the distance to the comet. X-Axis is comet distance to the sun... Even when they kept far away from the nucleus the star trackers now seem to have tons of problems so close to the sun.

I note that people are still commenting on the http://isee3.p3s.nl/philae/ data. My understanding is that this has NO relation to actual Philae data. The webmaster told me as much a week ago. Unless someone can cite a recent confirmation that this is now reliable, I suggest it cannot be relied upon.

Well, I quoted several tweets from @DutchSpace (mentioned at the top of the telemetry page) several posts back in this thread, but maybe seeing is believing.
Click to view attachment
https://twitter.com/DutchSpace

I assume this guy is the web master right?

https://twitter.com/DutchSpace/status/612539793386401792

as far as i understand it there are only a few variables updated properly right now. The whole upper graph is useless (is this what you mean when you said "the webmaster told me as much"? ). The only relevant stuff are some of the current measurements in the lower one ( PSSH_C_SBat_CH and PSSH_C_SBat_DCH are current from the solar panels and the recharchable battery discharging current). If this is not really data from Philae then it at leasts corresponds nicely with the times contact was reported...

Philae communicates through an S band antenna on the head. It has a visibility cone of 60 degrees to the positive z (straight up). So if Philae is pointing to the ground....

For what it's worth, the bottom graph at http://isee3.p3s.nl/philae/ is fed by the same data source as http://www.musc.dlr.de/philae/telemetrie.html (the science sequence graph is the only one that includes the new data), but the isee3 page has a much easier-to-use graph and is being maintained (for example, over the weekend the lower graph was relabeled). The data that feeds the bottom graph on the isee3 page can be accessed at http://www.musc.dlr.de/philae/db_pss-statu...h_v_sbat-c.json and the data that feeds the bottom graph of the DLR page can be accessed at http://www.musc.dlr.de/philae/db_curent_5_...h_v_sbat-c.json (this is the exact same data as the other one, but with the pre-landing data omitted).

If Philae is still pointing as in this mosaic, we can see the top of the lander is aimed generally at (or a bit left of) Perihelion Cliff (green dot in center of yellow solar circle). Thus I wonder if Rosetta is possibly being maneuvered to catch the line of sight pointing just above Perihelion Cliff, thus at a latitude more to the north? This would actually not be at the zenith of Philae's latitude. North is in the center of this mosaic.

Click to view attachment

Is there a way to check Rosetta's current latitude? How much of the 60 degree cone is pointing above Perihelion Cliff? Is alphasam's 60 degree figure an angular radius?

Well, I've tried at multiple points during the day today and every time, I've found that the data sources the isee3 page uses for Philae telemetry ( http://www.musc.dlr.de/philae/db_pss-statu...h_v_sbat-c.json for the power systems) are now 404ing. If you've been watching it to spot new data from Philae, you can still use the URL the DLR telemetry page uses ( http://www.musc.dlr.de/philae/db_curent_5_...h_v_sbat-c.json ). It has contained identical data to the other one, with the exception that the data set doesn't include pre-landing data.

I see 4 new data points in the telemetry (the battery data, specifically), with the following timestamps:
2015-06-24 17:24:11
2015-06-24 17:28:35
2015-06-24 17:33:00
2015-06-24 17:37:24
Prior to these, the last data point had a timestamp of 2015-06-21 02:44:16.
Hopefully, this means we'll be hearing that contact was made today.

The raw data corresponding to the 5 data points I mentioned (including the last one from the contact several days ago):

Thanks for posting this data! Was already wondering whether they disabled the public api completely.
I guess since there are only four new data points they are still struggling to get a stable connection. I wonder if they will consider leaving the terminator plane to get a longer communication window...