If it's 100% steam, and cooling it would make "100%" water*, then your meter is done: tie a wire to +V because it's always 100%!
(*The volume or pressure will change at the same time, so if you think of the container as being 'less full' because it's under less pressure, that wouldn't be "100%", in a certain sense (an incorrect -- but intuitive -- sense). Hence the quotes, and this note. Another example: air compressors are rated in CFM, which might be ambiguous; what they mean is CFM
at atmospheric. There's information hidden in the definition.)
It sounds like, a dewpoint sensor will determine what you need, give or take a conversion table. If it's saturated steam, then you simply get the condensation point at system pressure; if a carrier gas is present, then the temperature will be lower, corresponding to the condensation temperature and partial pressure of the steam content.
Finding one may be difficult. If you aren't prepared to spend a cool $1k on an industrial sensor, well... maybe you just don't need one that bad?
Ah, and that's another key piece of information: how soon do you need it, and how much are you willing to pay?
Two references:
1.
http://us.magnetrol.com/Literature/1/57-239.0%20Eclipse%20Steam%20White%20Paper.pdfThis looks helpful. Measures steam, electromagnetically, it seems. Pretty awesome! Bet it's like $10k, too...
Note that the dielectric constant increases very, very slightly. You'd be measuring parts per million to get desired accuracy. But the apparatus (likely being made of common metals like steel) will expand on the order of tens ppm, due to temperature fluctuations: so, your proposed solution would be a better thermometer than gas sensor.
It's also not specific, because the dielectric constant of steam (at a given pressure) isn't much different from that of any other gas (at the same pressure).
So we could go back and forth, picking and critiquing approaches, but you'd just end up frustrated, and blame us for the failure to come up with something. Which is true, we weren't able to come up with anything. Hence why I'm writing this...
2. Regarding threads like this...
http://xyproblem.info/Consider the situation we have here. You come to us, providing very little information about your intended application (and perhaps, personally having little knowledge about the subject -- this might be some random thing that's been thrust upon you; we have no idea!).
And you propose solutions to us. (Well heck, if the problem is solved, what are you coming here for?
) But it's clear you aren't an expert in that field, so, I hope you aren't getting too fixed on a particular solution or anything! Just a basic idea to get things rolling, right?
But since you're not an expert, for us to discuss those solutions, we need to convey quite a lot of information to you, about a particular approach may or may not work, so that you can make an informed decision about what is best for your application.
So by hiding your background information, you leave us to speculate wildly, and the discussion really just goes nowhere.
Since, frankly, we're a bunch of lazy engineers, who have better things to do than teach the intricacies of sensor design. Sorry. (It's even more likely, most of us are not sensor design experts, either! Sensor design is tricky business, and, accordingly, commands a pretty penny for services rendered...)
And, yeah, this may be a proprietary situation, that you
can't tell us much about -- but in that case, you should be searching all the more earnestly, either to increase your knowledge of the subject, or to find someone who can solve your problems under suitable controls -- such as a contract with NDA, stated work, and compensation. These things aren't free, after all! (And that's why buying a cool $1k industrial sensor is, very often, a darned good idea!)
Tim