Where on Earth did you guys get the information that it was running and hydrogen was purged?
"Early in the day with a glitch showing up, Rossi said that they had to make a decision about whether to go for 1 MW output, not in self-sustain mode, or with self-sustain mode at a lower power level. The customer opted to go for the self-sustain mode." There was never additional information provided as to how this power cut was achieved. I would love to hear any ideas as to why it would be 1MW "driven" or half-that in "self sustaining". Still, look at the numbers. If it were filled before hand, the tank would have dropped between September and Oct 28th: September 7th: before filling: 13613.4 grams - after filling: 13610.7 grams Total loaded: 2.7 grams October 6th: before filling: 13606.4 grams - after filling: 13604.9 grams Total loaded: 1.5 grams October 28th: Before filling: 13604.5 grams After filling: 13602.8 grams Total loaded: 1.7 grams Or are you assuming that the E-Cat was filled from a different bottle, then mostly purged, then the same bottle from all of the other tests was used for the demo? Again, this is a non-issue. It looks like some numbers were "fudged," but that shouldn't surprise anyone. _________________ > Date: Wed, 23 Nov 2011 09:43:54 -0800 > To: [email protected] > From: [email protected] > Subject: Re: [Vo]:hydrogen refill > > At 04:38 AM 11/23/2011, Gigi DiMarco wrote: > >I don't know if it was already reported but I found some oddies in > >the hydrogen consumption > >October 28th test, from Fioravanti/Rossi's report > > For Oct 28, don't forget the "restart" -- they started the eCat, it > was unstable, so they lowered the hydrogen pressure. > > Did they completely discharge it? Maybe they just let some out, and > then reconnected the hydrogen bottle to measure the 55 Bar, (or whatever). > > The actual hydrogen consumption is so small that it's trivial > .... the 1MW would run for 25 (wild guess for intentional hyperbole) > milliseconds on a gram of hydrogen. > > This isn't just a picayune problem ... it's a pico-picayune problem. >
