Successful TPU-ECD replication !

[Jon]

Feynman

RE: We should collaborate so we can standardize things a bit... did you write  a protocol to speak to the Atmel?   Maybe we should all write a common protocol.

I would really like to work on a communications standard that we can all share. Getting the computer talking to the microcontroler was a bit tricky. I would also like to make a standard board schematic that would use a micro controller and several oscillators.

I can post the micro controller code as well as the client Java application on my website but it is still in progress and won't be exactly the same as yours because I will be controlling digital resistors instead of the oscillators directly.

I will post the code here today: http://freeenergygroup.com/?page_id=13

As a quick overview the computer communicates with the atmel through the serial port. There are several commands like set channel a,b,c pulse width/frequency, set mode, get voltage and more. The mode allows the micro controller to perform a specific task. I have some modes that set io lines output frequency and pulse width for example.

[Feynman]

@Jon

Okay, that sounds perfect.  My draft protocol was also set / get based.   Don't worry, I'm sure your code is fine!  We can always revise things.  Oh also is your protocol binary or ASCII?

@Marco

Thanks for the info.  I just noticed what you mentioned today... the oscillation frequency on the high efficiency LED driver fluctuates wildly if bump the circuit or toroid, then it settles back to +- 3% of 20khz over the time domain (take 30 sec to a couple of mins to settle into a new oscillator orbit).

[Jon]

Feynman

The protocol is ASCI. Here are some examples:

getinfo;  returns the values of internal variables.
setfreq[char]; where [char (unsigned) is a number between 0-255] returns value as a confirmation. Not used any more.
setmul[char]; where [char (unsigned) is a number between 0-255] returns value as a confirmation. Multiplier value used to multiply variables to use values larger than 8bits.
set1offset[char]; is really for adjusting the first channel in different ways depending on the mode.
getvolts; returns an ascii numeric value from the internal ADC.
setmode[char]; sets the mode value. there are predefined modes like 8,16 and 32 bit frequency wave generators.

Perhaps a better approach would be to add commands for the variable size i.e.
setChannel1_8[char];
setChannel1_16[word];
setChannel1_32[int];
setChannel2_8[char];
...

then there could be a mode for the LTC6904 that would use the values assigned by setChannel1_32 for example.

[sparks]

       
           I'm thinking that the 7.3hz beat freq. is coming in at high freq. phase displacement.  So the kick pulse can go radiant real easy.  We got lots of microwave ovens around.     I would think that the ionized gas tube oscillator or even a spark gap would respond in phase to the beat freq.  I'm a 60hz tech so what do I know?

[slapper]

I'm a 60hz tech so what do I know?

That is quite alright sparks. Your still learning just like the majority of us.

Could a physical displacement of a conductor, in a vibrational sense, allow for this phase displacement for setting up for the 7.3 beat.

The materials used and the structural shape of the TPUs have been curious to me. It's almost another way for him to tune his coil(s) if we throw in physical vibration.
So not only do we need to consider the L and C configurations but we have to consider tension on the coils if we were to include displacement of the wire. It seems to me that the construction of (the non-open ones at least) the TPUs allowed for the conductor coils to dimensionally vibrate and he could adjust this.

Please continue sparks. Thanks for good insights.

Take care.

nap