Re: [EVGRAY] Triple thick BiTT

Database ID: 105916
2018-01-22T17:55:49+00:00
Douglas Konzen <[email protected]>

← View thread

Message-ID
In-Reply-To: <CAD7GjUQh+iO3HKia-AWiNbUjS6KWMvbPk+FofidE+s9SgK8O4A@mail.gmail.com>

Body

Hi Gerry'
 Thanks for the advice and ideas again - I agree with the AC swing analogy...when I was in Germany the engineer there (HD) described just the same thing in AC in his MEG and timing things just right in analogy with swing...
 I understand your idea with my ORBOI motor maybe the shielding of the steel to the rotor magnets will be better more efficient rather than copper torroid surround a ferrite core and then the primary inside  of the copper wire would be creating power each pulse too - I can imagine coils sticking out from stators 15cm long with that thick copper wire jammed up the middle....
 

 What I was trying to get at about the BiTT and the backemf forces, is just what is it that creates that "split" of the backemf force from the forward-current magnetic force, and for that backemf force to run along those extra transformer legs leading back to the opposite secondary, and not route itself back to primary??? 
 There being thicker core material is "giving it" the path to follow, but what is is that make the backemf go that way?   
 This is the only way to make a BiTT really work scuh as X3 OU  in my measly opinion, and that is for the backemf (and backemf only) to take that route and add power to opposite secondary......if it does not, it is just a fairly efficient transformer design....So my idea of how it works and why it works is that there is a bucking-collision of forward and the inherent back emf  and the bucking collision causes the intitial split, and once split, the backemf goes over to the opposite secondary....so what causes this split?? My idea is it an inherent thing such as Leedskalin saying there is always in magnetism a forward and an opposite magnetic force, and perhaps the primary's magnetic force is what creates the smashing event to the secondary, and this secondary and primary must share the exact same time flow  in first place, but when the primary brick wall oif magnetism gets in the way, there is the bucking event....if there is time delay, perhaps now there will not be a bucking event because either the primary or the secondary will not have the exact same collision force and one will dominate (whichever is stronger) and the backemf flux will not be "dislodged" from the forward magnetic force rather they will continue together locked tight and just go back to primary causing the extra draw there...
 ciaoKone

References

<BLUPR11MB0658BF73BB5954BA292091B4C2EE0@BLUPR11MB0658.namprd11.prod.outlook.com>
<[email protected]>
<[email protected]>
<CAD7GjUSjOFdCOHQ==U1O4QcwV-i7M9xXf0PNXY0vKJ40FhdGCg@mail.gmail.com>
<CAD7GjUTppcudi7q6Lj7e1=M5M_M6o1s3u5GFE=bbj7HmZdh9Pw@mail.gmail.com>
<[email protected]>
<CAD7GjUQh+iO3HKia-AWiNbUjS6KWMvbPk+FofidE+s9SgK8O4A@mail.gmail.com>

Headers

Return-Path <[email protected]>
X-Sender [email protected]
X-Apparently-To [email protected]
X-Received (qmail 59484 invoked by uid 102); 22 Jan 2018 18:01:28 -0000
X-Received from unknown (HELO mtaq2.grp.bf1.yahoo.com) (10.193.84.33) by m14.grp.bf1.yahoo.com with SMTP; 22 Jan 2018 18:01:28 -0000
X-Received (qmail 16637 invoked from network); 22 Jan 2018 18:01:28 -0000
X-Received from unknown (HELO mta1004.groups.mail.ne1.yahoo.com) (98.138.100.119) by mtaq2.grp.bf1.yahoo.com with SMTP; 22 Jan 2018 18:01:28 -0000
X-Original-Return-Path <[email protected]>
X-Received-SPF pass (domain of yahoogroups.com designates 98.137.70.156 as permitted sender)
X-YMailISG IfZ6QyoWLDueadgOUZep4pXx2vocIzkmoPl5hGxPdLiLWy5a WcVMc0QLa99m8qaQg4_QCqX05hwzcIJ8IMJoCSWgNeZgI.tUp5n_x8.g5f83 j4WjyFsCUw3srEuJllyH.KEN8_xw.2_aFm_v8nZ8DkPOeYZOTRfaB_xUiLM7 YdRJ7PD45TUoZO3JeZyr.TH2ymryCg0cV0Ky7PooO26y00yVh8FZEwZ2gpDk MJTPj.71ofZSu6PiQfF9OAvx45HAp_au3IlzUbK1IfmN9fXCf0fYAfNxTBD8 QHLQwYYRSFqgJpHTbjR_usZJM7zxck6J8l9oLuBwO7SnLIpdlK4lXvEXHQaH vWEb5RQxnfL7RWVpNJR2FM5WfhoOnjgXYPXWHjGIcEqlUPLCKQhH2cG_CNmM 0wFCHI.S4Gpyr.Oo70mJ1pB6smFgIhB5Id8c7rwOsHFJV3Wi4HIeM5n8Soog Fl7P8_OMMtsJb6LMAQOD2elL6ILA9aQo7PM5c2iy1L2HedVmL_A6xwDupRKt Ve5h41Y06.wQq_dspinfrUOy5Pd1sHoatleYZl67RkbEUtLtmy5et2Oas4lJ nHtwcGHzeGJbB8zYNJ4SGZw.ka3u21hm4cUz_ccToAoXvCeXZ6n4Dme6eUQm FzkKZin5Qzh6EuxdRfGVph9C3l.1XAcO4jtXS2DdPLi2upIJ9jrk9xFug6p3 tVrNjcZw7L1aJKTIS4c.d0RaJjHGZbA4T1DE1j7KeI1axnKJdbue.VgH2B3g 9oZpLq1dJRm2V5GzAY5ixAqomMvjC0Lq_sHmO8xR9DV2PlX9ti6zjE36nDVT y6Yw3CM9DIPotqJ0ftWzSqdhuBaQEK81qxxXaDTLTvWSMIjSp271T6D4nYLR FjpnfSRanGPitASwrf3n.hyMHcsvK2q83yW06kaKTAP4zpVWZUr3TWIC0VG7 inMd6FUZQ9YruaLR4zcHB5z1nHZIj4DkLXiD6ctnAoy1O2deYKW7dVMf_xzI 2dAGbi3io_0TKjpEtraAvd85L0cLYAQSgNyiy8Wqs5yOJn8cT20qjUtbAWiZ cOUa4qP4VNgDCWzslG31yhkfSRzkHS.b9cnUlj33RZJRhB14IotmDU1wrOjW oairYUmSNcJgcINOuLJUSTKu43B.d50zaPuQ75T5lBbO6B.rntoM.wSaZX2T jpZHE.VejYMFfHuzTMp8hLjBlTwpbXJM7T5m1BTBcexscz7vpEM-
Authentication-Results mta1004.groups.mail.ne1.yahoo.com from=yahoogroups.com; domainkeys=neutral (no sig); from=yahoogroups.com; dkim=permerror (bad sig)
X-Received from 127.0.0.1 (EHLO sonic318-30.consmr.mail.gq1.yahoo.com) (98.137.70.156) by mta1004.groups.mail.ne1.yahoo.com with SMTPS; Mon, 22 Jan 2018 18:01:28 +0000
X-Received from sonic.gate.mail.ne1.yahoo.com by sonic318.consmr.mail.gq1.yahoo.com with HTTP; Mon, 22 Jan 2018 18:01:27 +0000
Date Mon, 22 Jan 2018 17:55:49 +0000
X-Received from [127.0.0.1] by gapi2.grp.bf1.yahoo.com with NNFMP; 22 Jan 2018 17:55:49 -0000
To [email protected]
X-Original-Return-Path [email protected]
X-Original-From [email protected]
X-Mailer Yahoo Groups Message Poster
References <BLUPR11MB0658BF73BB5954BA292091B4C2EE0@BLUPR11MB0658.namprd11.prod.outlook.com> <[email protected]> <[email protected]> <CAD7GjUSjOFdCOHQ==U1O4QcwV-i7M9xXf0PNXY0vKJ40FhdGCg@mail.gmail.com> <CAD7GjUTppcudi7q6Lj7e1=M5M_M6o1s3u5GFE=bbj7HmZdh9Pw@mail.gmail.com> <[email protected]> <CAD7GjUQh+iO3HKia-AWiNbUjS6KWMvbPk+FofidE+s9SgK8O4A@mail.gmail.com>
X-Yahoo-Newman-Property groups-compose
Message-ID <[email protected]>
In-Reply-To <CAD7GjUQh+iO3HKia-AWiNbUjS6KWMvbPk+FofidE+s9SgK8O4A@mail.gmail.com>
MIME-Version 1.0
Content-Type multipart/alternative; boundary="9nlWnTS9ocNmxdhsK3FKVLWiM6a5jwOaA8HvrLV"
X-Originating-IP 134.17.169.243
X-Yahoo-Post-IP 134.17.169.243
Reply-To [email protected]
Subject Re: [EVGRAY] Triple thick BiTT
X-Yahoo-Group-Post member; u=1305424; y=_uLruAHeQp2NPumMTCPn5lQifDu2tkQ6BUxHyIfCNH4eUnX6
X-Yahoo-Profile koneheadx
From [email protected]