I did two more powered runs this morning. Test 09 is very similar to the results from test 07. Unfortunately test 10 was corrupted. I can see the data, I just can't export it to excel. It looks very similar to test 09 from what I can tell. I may need to shield the dataq to prevent corruption in the future.
As before, by monitoring the spectrum analyser, I could send events to be recorded. This time I captured not only RF on/off, but also 2.46Ghz and 2.45Ghz.
I did two more powered runs this morning. Test 09 is very similar to the results from test 07. Unfortunately test 10 was corrupted. I can see the data, I just can't export it to excel. It looks very similar to test 09 from what I can tell. I may need to shield the dataq to prevent corruption in the future.
As before, by monitoring the spectrum analyser, I could send events to be recorded. This time I captured not only RF on/off, but also 2.46Ghz and 2.45Ghz.Can you explain what the 2.45 and 2.46GHz means in this graph and how it relates to the drive?
Shell
I did two more powered runs this morning. Test 09 is very similar to the results from test 07. Unfortunately test 10 was corrupted. I can see the data, I just can't export it to excel. It looks very similar to test 09 from what I can tell. I may need to shield the dataq to prevent corruption in the future.
As before, by monitoring the spectrum analyser, I could send events to be recorded. This time I captured not only RF on/off, but also 2.46Ghz and 2.45Ghz.Can you explain what the 2.45 and 2.46GHz means in this graph and how it relates to the drive?
Shell
I watched the spectrum analyser in real-time and as the frequency drifted due to magnetron heating, I clicked when center frequency was 2.46Ghz and then again at 2.45Ghz. This gives me vertical lines on another channel that represent separate events.
Here is a video of the spectrum analyser. This is from an earlier run though. https://www.youtube.com/watch?v=sKsV3qTStyE?t=168
I did two more powered runs this morning. Test 09 is very similar to the results from test 07. Unfortunately test 10 was corrupted. I can see the data, I just can't export it to excel. It looks very similar to test 09 from what I can tell. I may need to shield the dataq to prevent corruption in the future.
As before, by monitoring the spectrum analyser, I could send events to be recorded. This time I captured not only RF on/off, but also 2.46Ghz and 2.45Ghz.Can you explain what the 2.45 and 2.46GHz means in this graph and how it relates to the drive?
Shell
I watched the spectrum analyser in real-time and as the frequency drifted due to magnetron heating, I clicked when center frequency was 2.46Ghz and then again at 2.45Ghz. This gives me vertical lines on another channel that represent separate events.
Here is a video of the spectrum analyser. This is from an earlier run though. https://www.youtube.com/watch?v=sKsV3qTStyE?t=168From your FEKO runs, are there well-defined mode shapes associated with the flat (constant force) portions of the response curve during power on?
Particularly just before it went below 2.45 GHz ? (long portion of flat response)
Particularly just before it went below 2.45 GHz ? (long portion of flat response)
...
Sigh...there was not 900 watts, it was a null test on a magnetron without rf output. The temp rise on both the mag and the harness was minimal. That experimenter probably knows what they are observing.The power was going into the wire harness instead of going into RF thus producing a thermal effect on the wire. Similar to what Prof Yang experienced prior to nullifying her tests by running with a battery.
The long time delay to coming back to the original position being due to the wire taking a long time coming back to its original length (due to the long time constant involved in thermal diffusion).
Thus from this mistake (the experimenter at the time thought that he was running the magnetron: he only realized that the magnetron was broken after the fact) one can learn a valuable lesson as how to identify such an effect.
Suffice it to say that at the time that this experimental artifact was being presented here it was being argued by some as being the real thing. It wasn't. We can learn from experimental mistakes such as this how to distinguish such an experimental artifact from the real thing.
ADDENDUM: The experimenter (rfmwguy) proposes elsewhereQuote from: rfmwguy-EMDrive Builder an hour agowas actually a slow dissipation of a magnetic charge, not of the frustum cavity, but of the wires themselves
...
I did two more powered runs this morning. Test 09 is very similar to the results from test 07. Unfortunately test 10 was corrupted. I can see the data, I just can't export it to excel. It looks very similar to test 09 from what I can tell. I may need to shield the dataq to prevent corruption in the future.
As before, by monitoring the spectrum analyser, I could send events to be recorded. This time I captured not only RF on/off, but also 2.46Ghz and 2.45Ghz.
I did two more powered runs this morning. Test 09 is very similar to the results from test 07. Unfortunately test 10 was corrupted. I can see the data, I just can't export it to excel. It looks very similar to test 09 from what I can tell. I may need to shield the dataq to prevent corruption in the future.
As before, by monitoring the spectrum analyser, I could send events to be recorded. This time I captured not only RF on/off, but also 2.46Ghz and 2.45Ghz.
Why doesn't it return to it's starting place? Is the test rig sticky now or is there some heating/thermal effect that is causing the offset to persist after RF is off?
I did two more powered runs this morning. Test 09 is very similar to the results from test 07. Unfortunately test 10 was corrupted. I can see the data, I just can't export it to excel. It looks very similar to test 09 from what I can tell. I may need to shield the dataq to prevent corruption in the future.
As before, by monitoring the spectrum analyser, I could send events to be recorded. This time I captured not only RF on/off, but also 2.46Ghz and 2.45Ghz.
Why doesn't it return to it's starting place? Is the test rig sticky now or is there some heating/thermal effect that is causing the offset to persist after RF is off?
We are dealing with a much smaller force than the tap test so it takes much longer to return to center. I've truncated the data to be centered on the RF portion. I also agree that it may be a little sticky at this level and there are probably thermal effects too. I'm looking into that now.
Edit: I might try the 3 inch dampening paddle again.
I did two more powered runs this morning. Test 09 is very similar to the results from test 07. Unfortunately test 10 was corrupted. I can see the data, I just can't export it to excel. It looks very similar to test 09 from what I can tell. I may need to shield the dataq to prevent corruption in the future.
As before, by monitoring the spectrum analyser, I could send events to be recorded. This time I captured not only RF on/off, but also 2.46Ghz and 2.45Ghz.
Why doesn't it return to it's starting place? Is the test rig sticky now or is there some heating/thermal effect that is causing the offset to persist after RF is off?
We are dealing with a much smaller force than the tap test so it takes much longer to return to center. I've truncated the data to be centered on the RF portion. I also agree that it may be a little sticky at this level and there are probably thermal effects too. I'm looking into that now.
Edit: I might try the 3 inch dampening paddle again.Have you thought about centering your oil damper to the center of the beam like Dave did. As the beam tries to move back to zero it will cause the beam to tip a little dragging in the oil, giving you asymmetrical movements from the drag. This also could show up in how your measurement records beam movements.
Shell
Particularly just before it went below 2.45 GHz ? (long portion of flat response)
Just to be clear, the flat portions represent no movement of the beam. Time is horizontal, displacement is vertical. When the graph line drops, the frustum is moving in reverse direction (large end leading), when the graph line goes up, it is moving in forward direction (small end leading). So it would seem the the portions where the beam moved down quickly are the most interesting.
Particularly just before it went below 2.45 GHz ? (long portion of flat response)
Just to be clear, the flat portions represent no movement of the beam. Time is horizontal, displacement is vertical. When the graph line drops, the frustum is moving in reverse direction (large end leading), when the graph line goes up, it is moving in forward direction (small end leading). So it would seem the the portions where the beam moved down quickly are the most interesting.I disagree.
The figure of merit in all discussions about the EM Drive have been force/InputPower.
With constant input power, you should get a constant force on the torsional pendulum: it should settle down to a flat line. Constant input power = constant rotation of the torsional pendulum. Flat.
As we discussed several times, even this, if larger than thrust/inputPower of a photon rocket leads to a problem with conservation of energy.
Having increasing force with constant input power can trivially be shown to be a free-energy machine.
I doubt that the strongest advocate for the EM Drive as a source of space propulsion would seriously advocate for the EM Drive to result in increasing force at constant power. That would be a runaway free-energy machine.
Hence increasing force at constant power is clearly a transient or an artifact.
NASA Eagleworks plots were showing fairly good looking pulses with the force settling down at constant power. Not increasing force at constant power. That is a no-no.
It must be related to the fact that you are doing frequency sweeps and therefore the mode shapes are changing.
It must be due to the fact that they are transients and not steady-state.
If you want to understand what is going on, you better go for the simpler things: the steady-state.
Transients are always more complicated.
Transients for mechanical oscillations are more complicated than the steady-state solution: for example a mechanical system excited with a mechanical force oscillating harmonically will display a transient with a damped frequency different from the excitation frequency, and the shape of the transient will very much depend on the amount of damping and the shape of the transient excitation including initial conditions.
Therefore you should be looking for flat portions of the curve at constant power at constant frequency.
The worst thing to have, which was shown to be an experimental artifact is something like this, with the measured force increasing, apparently without bounds, at on/off pulsing of constant power in each on segment:

I've superimposed the rate of change in beam displacement.
...
Ah okay, I see what you're talking about and that does make sense. Thank you!
I have almost everything I need to go solid state and that is next on the list. Solid state will also be vastly easier to run on batteries.
Wow
If you run this experiment on batteries you will be making history.
Only Prof. Yang, and if my memory is correct our esteemed DIY at NSF, RFPlumber, run the EM Drive with batteries, both with null results.
Nobody else...
