This forum is preserved as a permanent archive. The community continues at eMedia Press.

Announcement

Collapse
No announcement yet.

My Motors got me to Tap into Radiant Energy

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • machinealive
    replied
    Hi Dana

    The neons were for testing, but like before, if I went to 24 v, we'd have a BBQ. I'm going to play with it a little more tonight, I never used gate resistors up to 50 ohms, maybe that would help. I just want to try relays before I start risking fets. They'll probably be here today or tomorrow.

    @John, I'll make a vid today of the two programs running at 12 v, so you can pick which program you think works best. On pulse packets, neons flickered at increased duty, but still, over 300 v spikes at 12 v.

    I'm on my way to work, Dana I'll send you my pm today after work, I appreciate your offer,

    Machine

    Leave a comment:


  • JohnStone
    replied
    Originally posted by prochiro View Post
    Hello JohnS
    You asked about driver voltage. I use one 12V and one 6V battery. Not sure where you got -18, maybe one of my diagrams labeled too closely to another label.
    Dana
    One of your real photographs shows +18 and -18 labels.
    These two batteries are in series. Do they power driver AND load at same time?

    @ALL: I still wonder on why those dead FETs occure. There MUST be a understandable reason. I would like all setups to start with drivers powerd separately (i.e. simple socket charger) in order to get effects separated. In research state it is not necessary to operate with one single battery like in later practical applications.

    JS

    Leave a comment:


  • prochiro
    replied
    Hello JohnS
    You asked about driver voltage. I use one 12V and one 6V battery. Not sure where you got -18, maybe one of my diagrams labeled too closely to another label.
    Dana

    Leave a comment:


  • JohnStone
    replied
    Originally posted by machinealive View Post
    Hi guys

    Well, no blown fets, but... First I tried the original program 12 v, 3 neons lit instantly across ds, constant, and intense. So then I tried the new program 12 v, way less severe spikes and less often, but still, 3 neons lit. No rotation. I like the second program better. I'm done until my mercury switches arrive.
    I don't know what else to due.

    Machine
    That's why we need a plurality of attempts. In the end we need to know what approach fosters motor turning the best.
    1. Availability of radiant energy without any timing requirements -> pulse packets
    2. Availability of radiant with precise timing for radiant release -> well positioned single pulse

    @ALL: For run in of setups please start with low duty cycle (approach 1. or 2.) and increase it gently while observing spikes and heat . If any abnormal effects do not increase load or duty - search for reason first.
    JS
    Last edited by JohnStone; 07-15-2013, 11:09 AM.

    Leave a comment:


  • prochiro
    replied
    @ Machine
    While reading your last post a question came to me. Are you using the neons at the same time you are trying to run Imperial, if so that will not work. The neons are only a test to check out circuit. I am sure you know that but just a hunch. If you will PM your address I will send you a fet board that will turn your motor.

    Dana

    Leave a comment:


  • machinealive
    replied
    Hi guys

    Well, no blown fets, but... First I tried the original program 12 v, 3 neons lit instantly across ds, constant, and intense. So then I tried the new program 12 v, way less severe spikes and less often, but still, 3 neons lit. No rotation. I like the second program better. I'm done until my mercury switches arrive.
    I don't know what else to due.

    Machine

    Leave a comment:


  • JohnStone
    replied
    Originally posted by prochiro View Post
    Hello All
    I have created a PDF file showing pictures of my QuadPulser and closeups of important views.
    This is a downloadable PDF file.


    Dana
    Looks fine. Some small details are somewhat different from mine setup but if it works - OK.

    From what source do you feed the driver? Battery or other source?
    Is it really -18V or do you refer to GND of 18V power source.
    KS

    Leave a comment:


  • Ufopolitics
    replied
    Still working on Site...

    Hello to All,

    I am still working on the site...and below, is a Direct Link to View On Line, the latest release of the Monster Pulser pdf...That was as per your post on other thread, Dana...

    VIEWER/MONSTER PULSER


    And here it is a link to be Downloaded



    Press on " Download File"

    The pdf file is not small...and I do not have a Private Server...so, it may take a while if too many hits, to fully download...so be patient.

    Let me know if it works ok.


    Regards


    Ufopolitics

    Leave a comment:


  • prochiro
    replied
    QuadPulserConstruction.PDF

    Hello All
    I have created a PDF file showing pictures of my QuadPulser and closeups of important views.
    This is a downloadable PDF file.


    Dana

    Leave a comment:


  • JohnStone
    replied
    I like plurality including your PWM approach Garry. Any attempt gives lots of information and often guids us to solutions we never have thought of. That is a very neat kind of taking options and convert them to success. The high grade is to cherry pick later on those elemts being proved to be successful.

    My concern is to have one Arduino setup with simple pulses in order to have the opportunity to run in our pulsers with simple pulse shape. Once they are known to function heavy duty we can go for complex pulsing of any kind. But with complex pulsing at very start some of us will not detect basic errors in the setup. I feel it to be important to support very beginners.
    The original UFO pulsing gives the opportunity to study cerain effects that might be essential:
    • Release the radiant event at a predefined timing.
    • If that effect holds true we need to play with voltage later on in order to shut off a predefined current at predefined time - at any rpm.
    • It might be important to concentrate the current increase to certain area of max torque
    • ...


    And it might be essential to detect some additional artifacts in PWM scattered pulsing.
    Just now we are mostly in the realm of ISDN (I Still Don't Know). Let's cherry pick later on but before let's add to our reports what type of pulsing was applied.
    JS
    Last edited by JohnStone; 07-14-2013, 06:51 AM.

    Leave a comment:


  • machinealive
    replied
    Hey guys

    Dana i'll give the new program a try, if you tried it and it works. You seemed confident in this program, before reading the last several posts. Some friends just left, and I'm pretty tired, that was a long week, but I may go try it now, it's all set up at 12 v.

    Leave a comment:


  • prochiro
    replied
    Wow, a guy takes a day to pour sidewalks and all heck breaks open. A few weeks ago, when Garry first mentioned this idea I really tried to see how it would work in our system even though this methiod of pulsing is standard in Arduino. I mentioned several times it might not work but after checking it out further, saw that it would work. At this point I will say that if JohnStone said no go then I will go back to previous pulses. I have run this system on several motors and believe that the outcome is the same. As to fet killers, maybe my boards are magic but I see no problem at this point. My boards are just beefed up with vary heavy lines to diodes so as to draw spikes off the fets.
    Here is a link to see the pulse in a pulse.


    If anyone is at this point unsure about this different code, use the previous code until JS has checked it out fully. It does work and motor runs much smoother although I did not check amps on Imperial but on the 4x long motor I showed earlier the amps were down. I will do whatever UFO and JS wants with this issue.
    Dana

    Leave a comment:


  • Ufopolitics
    replied
    Originally posted by machinealive View Post
    I have a feeling Dana has already used this code, and it works, just a hunch. I'll still wait to make sure.
    I agree with you here Machine....sometimes Science is like that...beyond all logic...We "assume" -based on our limited knowledge- something is never gonna work like that...and it happens all the contrary, it is a Great Success...then we find new reasons why it did worked out...

    Just "Hang in There" till Dana tells You...unless you want to "Unleash Your FET's Serial Killer Syndrome"...and destroy them All!!...once and for all!!...


    Warm regards..


    Ufopolitics

    Leave a comment:


  • machinealive
    replied
    I have a feeling Dana has already used this code, and it works, just a hunch. I'll still wait to make sure.

    Leave a comment:


  • Ufopolitics
    replied
    Yes , Correct.

    Originally posted by JohnStone View Post
    confused
    If I understand you right: what we call one single pulse is composed at your setup of a packet of n pulses. The duty cycle of these sub pulses is variable.
    Right? If yes this is definitely NOT what UFO talks of. And additionally it might be a FET killer.
    Hello John,

    Yes , You understood perfectly well, and as a matter of fact, thanks to your observation, I see now what Machine was showing at Scope.

    And, Yes, that was NOT the Design I was originally proposing to drive Imperial.

    If it could be a "FET Killer"...then Machine Alive, you do NOT need this...unless you have developed a "FET'S Serial Killer Syndrome"...LOL...


    I'll tell you what I understood we require to have:
    1st channel emits a SINGLE pulse first (i.e. 1ms) and waits another 3 ms before repetition (5ms for MAG3) in order to allow the other 3 channels (5 fro MAG3) to perform their 1ms pulse each. In this case any channel repeats its pulse 250 times a second (166.6 times for MAG3). UFO showed exactly this in his diagram.
    Overall: any channel is allowed to perform maximum 25% duty cycle in order to not overlap with other channels (16.6% for MAG3). But this duty cycle can be reduced down to 1% i.e. leaving a dead zone in the range of its time slot (24% / 15.6%). Duty below 1% does not make any sense and should be omitted.

    JS
    Yes, that is the way...Dana has already run Imperial smoothly with this set up...however, I see some of the "limitations" as duty cycle concerns...and no option to variate the "Off Times" between Channels...

    That is why Garry offered his design...there is only one Main Problem with this, besides the ones cited above...

    @Garry (GChilders): Your idea is very "interesting" and I think we should keep it in mind as it may be usable on other arrangements...and/or correcting/improve, some design issues with the wave pattern.
    The problem I see: (and I have to admit I do not have full understanding yet of this wave design, so, please, let me know if I show ignorance about it at any point)

    Asymmetrical Motors require that the "Energizing Milli Second Time" per Pair or Coils, meaning, per Interaction when Brush hit their commutator elements...be done at a Steady Rate, in order that coil could develop in the shortest time possible, enough magnetic field strength that would allow to generate the required speed/torque...

    If We look at this Coil Feeding till it develops a full Magnetic Field Strength...it is an "Ascending Mode Curve" through Time...and NOT a Flat Line...parallel to time.

    And as I can see in your design...you are fractionating that already small timing On, for Pairs-Coils, into "Mini Pulses"...This will end up weakening the required strong magnetic field development within the On Time....The responsible Parameter that creates Speed and Torque at same levels...I call it "Throw Out Forces"...those forces are based on "As Similar As Possible", Magnetic Field Strength between Rotor Coils at Interaction and Stators.


    I still like Your design(I see it "pretty darn" interesting, and very different!)...and I am sure we could modify it or arrange it differently, in order that would be very functional and successful to our future development. As I agree with you if we get this to function properly it will definitively be an Ultra Low Wattage consumption for our Machines.


    On the other hand, a FET Killer, I understand it, as it "amplifies" the amount of opened off times/gates for spikes(Our Lady) to reverse back to our "Switchers" Drains...


    Warm Regards Sir John Stone, Garry, Machine and All


    Ufopolitics
    Last edited by Ufopolitics; 07-13-2013, 10:19 PM.

    Leave a comment:

Working...
X