Quote from txqNL on June 5th, 2011, 12:26 PM

Found bug with external pulse trigger (pulse_trigger==2) in all versions to fix search "MCUCR" and replace with "EICRA" so new line looks like;

EICRA |= (1 << ISC01);  // Falling-Edge Triggered INT0

Ok! By the way this is alot better! Lovin it,

Onlything so far is on the night rider...

The end pulses pulse twice... I like that for some reasons but I also would like to see the pulses with out the 2 pulses... You known what I mean?  So both as a choice!

It looks really good! Lovin it thanks for the hard work!

~Russ

Quote from Rwg42985 on June 3rd, 2011, 03:22 AM

Quote

Will check the schematic needs a few changes;
- PB0 & PB1 should goto gnd.
- D0 & D1 are connected internaly to USB so should left open.
- D2 External trigger for pulse needs button or sensor or connector.
- Also D2 when lpm_size > 0 then is output for mosfet for relay valve.
- D5 External clock for pwm needs BNC style connector with gnd.
- Add label D6 with LCD_RS
- Add label D7 with LCD_E
- Add label A0 with LCD_D0
- Typo cpu ATMEL 168/328
- I think backlight needs resistor.

ok, I have updated the schematic and also changed the links in the previous posts
Here it is,
 :

http://open-source-energy.org/rwg42985/russ/Arduino%20Hardware%20schematic%20Simple%20for%20Pulse%20Fire%20v%200.5%20RWGresearch.bmp

enjoy! ~Russ[/quote]Hey Russ,

I found that the external pulse trigger from D2 needs to go to GND instead of +5.  

Nate

Quote from Rwg42985 on June 5th, 2011, 02:42 PM

Ok! By the way this is alot better! Lovin it,

Onlything so far is on the night rider...

The end pulses pulse twice... I like that for some reasons but I also would like to see the pulses with out the 2 pulses... You known what I mean?  So both as a choice!

It looks really good! Lovin it thanks for the hard work!

~Russ

I known the 2 pulses had already tried to get them out for a bit, but then in the other mode it was wrong again but will try again :)

But there is a workaround with the new mode 4, PPMA which shifts the ppm_data out for All output steps in one sequence.

root@pulsefire: ppm_data 1025 0
root@pulsefire: ppm_data 514 1
root@pulsefire: ppm_data 260 2
root@pulsefire: ppm_data 136 3
root@pulsefire: ppm_data 80 4
root@pulsefire: ppm_data 32 5
root@pulsefire: ppm_data_len 10
root@pulsefire: pulse_mode 4
root@pulsefire: pulse_steps 6

See that the ppm_data_len is offset by 1 will fix that also but but now see the bits;
root@pulsefire: info_ppm
ppm_data00==0000010000000001
ppm_data01==0000001000000010
ppm_data02==0000000100000100
ppm_data03==0000000010001000
ppm_data04==0000000001010000
ppm_data05==0000000000100000

Now you see night rider without double pulse.

Quote from firepinto on June 5th, 2011, 02:54 PM

Hey Russ,

I found that the external pulse trigger from D2 needs to go to GND instead of +5.  

Nate

Yes you are very right sir, missed that :blush: changing it to 3 pin connector with Vcc and gnd would be nice to direct connecting sensors which need power.

Here is the start of my mosfet box:

https://www.youtube.com/watch?v=cpMGj6BzPGQ

It's coming together better than I thought so far.  Just hope I don't ruin it with the dremel next weekend!

Nate

Quote from firepinto on June 5th, 2011, 10:02 PM

Here is the start of my mosfet box:

https://www.youtube.com/watch?v=cpMGj6BzPGQ

It's coming together better than I thought so far.  Just hope I don't ruin it with the dremel next weekend!

Nate

It looks grate Nate!

I'll fix the schmatic and add a pin for power/gnd.

Yeah!

Keep up the good work guys!!!

~Russ

Quote from txqNL on June 5th, 2011, 05:05 PM

root@pulsefire: ppm_data 1025 0
root@pulsefire: ppm_data 514 1
root@pulsefire: ppm_data 260 2
root@pulsefire: ppm_data 136 3
root@pulsefire: ppm_data 80 4
root@pulsefire: ppm_data 32 5
root@pulsefire: ppm_data_len 10
root@pulsefire: pulse_mode 4
root@pulsefire: pulse_steps 6

See that the ppm_data_len is offset by 1 will fix that also but but now see the bits;
root@pulsefire: info_ppm
ppm_data00==0000010000000001
ppm_data01==0000001000000010
ppm_data02==0000000100000100
ppm_data03==0000000010001000
ppm_data04==0000000001010000
ppm_data05==0000000000100000

Now you see night rider without double pulse.

Made an error in that it has to be;
root@pulsefire: ppm_data 1 0
root@pulsefire: ppm_data 514 1
root@pulsefire: ppm_data 260 2
root@pulsefire: ppm_data 136 3
root@pulsefire: ppm_data 80 4
root@pulsefire: ppm_data 32 5
root@pulsefire: ppm_data_len 9
root@pulsefire: pulse_mode 4
root@pulsefire: pulse_steps 6
root@pulsefire: info_ppm
ppm_data00==0000000000000001
ppm_data01==0000001000000010
ppm_data02==0000000100000100
ppm_data03==0000000010001000
ppm_data04==0000000001010000
ppm_data05==0000000000100000

Quote from firepinto on June 5th, 2011, 10:02 PM

Here is the start of my mosfet box:

It's coming together better than I thought so far.  Just hope I don't ruin it with the dremel next weekend!

Nate

Nice air flow, for how many outputs you are building ?

Quote from firepinto on June 5th, 2011, 10:02 PM

Here is the start of my mosfet box:

It's coming together better than I thought so far.  Just hope I don't ruin it with the dremel next weekend!

Nate

Nice air flow, for how many outputs you are building ?[/quote]There will be 6 outputs.  Each output will have 4 mosfets in parallel for just under 200 amps per output based on Russ' suggestion on the drawing.  I'm hoping this design makes the mosfet the weak point in the system so that the maximum amp draw can be used safely.  Even the wire leads are going to act as heat sinks to the power bus bars, which are all fan cooled also.  Should be fun, its got the clear top to see the sparks and smoke. :D  

Nate

Quote from firepinto on June 6th, 2011, 05:38 PM

Quote from firepinto on June 5th, 2011, 10:02 PM

Here is the start of my mosfet box:

It's coming together better than I thought so far.  Just hope I don't ruin it with the dremel next weekend!

Nate

Nice air flow, for how many outputs you are building ?

There will be 6 outputs.  Each output will have 4 mosfets in parallel for just under 200 amps per output based on Russ' suggestion on the drawing.  I'm hoping this design makes the mosfet the weak point in the system so that the maximum amp draw can be used safely.  Even the wire leads are going to act as heat sinks to the power bus bars, which are all fan cooled also.  Should be fun, its got the clear top to see the sparks and smoke. :D  

Nate[/quote]Nate, if you get even 50 amps threw a coil I would love to see it! Lol love it! ~Russ

Quote from Rwg42985 on June 6th, 2011, 06:03 PM

Quote from firepinto on June 6th, 2011, 05:38 PM

Quote from firepinto on June 5th, 2011, 10:02 PM

Here is the start of my mosfet box:

It's coming together better than I thought so far.  Just hope I don't ruin it with the dremel next weekend!

Nate

Nice air flow, for how many outputs you are building ?

There will be 6 outputs.  Each output will have 4 mosfets in parallel for just under 200 amps per output based on Russ' suggestion on the drawing.  I'm hoping this design makes the mosfet the weak point in the system so that the maximum amp draw can be used safely.  Even the wire leads are going to act as heat sinks to the power bus bars, which are all fan cooled also.  Should be fun, its got the clear top to see the sparks and smoke. :D  

Nate

Nate, if you get even 50 amps threw a coil I would love to see it! Lol love it! ~Russ[/quote]lol I would too, I don't think the coils I have will do it though!  Would really need a coil that did "something" to push it that hard. lol  Gonna need a ceramic core. :-)

Quote from firepinto on June 6th, 2011, 05:38 PM

There will be 6 outputs.  Each output will have 4 mosfets in parallel for just under 200 amps per output based on Russ' suggestion on the drawing.  I'm hoping this design makes the mosfet the weak point in the system so that the maximum amp draw can be used safely.  Even the wire leads are going to act as heat sinks to the power bus bars, which are all fan cooled also.  Should be fun, its got the clear top to see the sparks and smoke. :D  

Nate

Wow 200Amps, you need very big wire coils and big power :)
I have wound a 63A 1.7mH coil to try and that is a heavy thing.
You can driver a motor on that, mmm maybe that is something for
pulse_mode=5 special H-bridge drive mode.

With the 4 mosfets in parallel you will lower the rds(on)==resistance
which is good for sharp pulses, but do use a mosfet driver with powerfull push/pull output so you not kill your mosfets when the switch time delay between mosfets in parallel is to big so all current goes true one mosfet.

If that happens than you mosfets will turn to fire see example in this 200Amp build;

https://www.youtube.com/watch?v=Pw1SkRleReo

Quote from txqNL on June 7th, 2011, 08:16 AM

Wow 200Amps, you need very big wire coils and big power :)
I have wound a 63A 1.7mH coil to try and that is a heavy thing.
You can driver a motor on that, mmm maybe that is something for
pulse_mode=5 special H-bridge drive mode.

With the 4 mosfets in parallel you will lower the rds(on)==resistance
which is good for sharp pulses, but do use a mosfet driver with powerfull push/pull output so you not kill your mosfets when the switch time delay between mosfets in parallel is to big so all current goes true one mosfet.

If that happens than you mosfets will turn to fire see example in this 200Amp build;

https://www.youtube.com/watch?v=Pw1SkRleReo

I would probably have more chance of running multiple coils at the same time, rather than one big one.  Also an HHO cell would be another possibility.  I kind of doubt I'll ever use much past 150 amps, lol but who knows.  

I really have no idea what the push pull output of the chip is. :s  I'll have to research that, I've never really got into solid state electronics much.  

The unit in the video don't look like much thought was put into cooling it?  He said the heat sinks only measured 90 degrees, but that could mean they weren't actually pulling heat off the mosfets.  I've thought about putting in some DIP switches to disable any mosfet I wanted.  Then I could test if any are burned up with out major surgery.

If anything its gonna be a great learning experience.:D
Nate

Have been working hard on rewriting the config variable handing in the code so it has more options and is cleaner and smaller.
It not finished yet so next release will be coming when it all works again.

Looks like the next release will have these changes;
- Rewrite of config variable handling so smaller and more options
- Wrote small lcd display driver for size and extended mode support
- Fixed trigger bug
- Fixed soft startup + added LCD keyword
- Fixed one off in ppm_data_len cmd
- Moved sys_conn_mode to multiple compiler flags.
- Moved sys_*_time and sys_input_delay to defines to save space in eeprom
- WIP RealTinyBasic language support for small scripts
- WIP sys_dic_map 2-8 digital inputs in extended mode

Hope also to fix the auto reverse duel step bug and add the simple version of req_auto_lpm_tune loop code.
So not that much functional changes but a lot of internal changes, also
new features can always be requested because I'm almost done with todos for arduino code and then have to build hardware to use it :)

Quote from txqNL on June 22nd, 2011, 09:35 AM

Have been working hard on rewriting the config variable handing in the code so it has more options and is cleaner and smaller.
It not finished yet so next release will be coming when it all works again.

Looks like the next release will have these changes;
- Rewrite of config variable handling so smaller and more options
- Wrote small lcd display driver for size and extended mode support
- Fixed trigger bug
- Fixed soft startup + added LCD keyword
- Fixed one off in ppm_data_len cmd
- Moved sys_conn_mode to multiple compiler flags.
- Moved sys_*_time and sys_input_delay to defines to save space in eeprom
- WIP RealTinyBasic language support for small scripts
- WIP sys_dic_map 2-8 digital inputs in extended mode

Hope also to fix the auto reverse duel step bug and add the simple version of req_auto_lpm_tune loop code.
So not that much functional changes but a lot of internal changes, also
new features can always be requested because I'm almost done with todos for arduino code and then have to build hardware to use it :)

Sweet! I can't wait!

Thanks again for your efforts! Alot of work you have in to this and alot of people will get good use out of it!

God bless!

~Russ

Quote from txqNL on June 22nd, 2011, 09:35 AM

Have been working hard on rewriting the config variable handing in the code so it has more options and is cleaner and smaller.
It not finished yet so next release will be coming when it all works again.

Looks like the next release will have these changes;
- Rewrite of config variable handling so smaller and more options
- Wrote small lcd display driver for size and extended mode support
- Fixed trigger bug
- Fixed soft startup + added LCD keyword
- Fixed one off in ppm_data_len cmd
- Moved sys_conn_mode to multiple compiler flags.
- Moved sys_*_time and sys_input_delay to defines to save space in eeprom
- WIP RealTinyBasic language support for small scripts
- WIP sys_dic_map 2-8 digital inputs in extended mode

Hope also to fix the auto reverse duel step bug and add the simple version of req_auto_lpm_tune loop code.
So not that much functional changes but a lot of internal changes, also
new features can always be requested because I'm almost done with todos for arduino code and then have to build hardware to use it :)

Is there a way to have two groups of pulsing outputs?  I don't really have any specific ideas of how many outputs in each group.  An example I was thinking of is if you used an arduino to control Stans gas processor.  One group of outputs could be for the lasing and the other for the high voltage.  Each group would have it's own frequency.  Not sure if that is needed for the processor or not, could be that the HV pulse should be the same as the LED pulses?

Nate

Quote from firepinto on June 22nd, 2011, 10:31 AM

Is there a way to have two groups of pulsing outputs?  I don't really have any specific ideas of how many outputs in each group.  An example I was thinking of is if you used an arduino to control Stans gas processor.  One group of outputs could be for the lasing and the other for the high voltage.  Each group would have it's own frequency.  Not sure if that is needed for the processor or not, could be that the HV pulse should be the same as the LED pulses?

Nate

To have each group it's own total independent frequency is best realized with two arduino boards :)
But there are some settings that could simulate two groups, lets see some examples with two groups of 3 outputs.

Simple train with extra output bits looks funny;
root@pulsefire: pulse_steps 6
root@pulsefire: pulse_mode 2
root@pulsefire: pulse_data_init 9
root@pulsefire: pulse_dir 2

PPMA data for 2 groups;
root@pulsefire: pulse_dir 0
root@pulsefire: pulse_mode 4
root@pulsefire: ppm_data 3 0
root@pulsefire: ppm_data 12 1
root@pulsefire: ppm_data 48 2
root@pulsefire: ppm_data 3 3
root@pulsefire: ppm_data 12 4
root@pulsefire: ppm_data 48 5
root@pulsefire: ppm_data_len 6 (in version 0.6 this is 5)

PPMA data for 2 groups with dubbel speed;
root@pulsefire: pulse_mode 4
root@pulsefire: ppm_data 195 0
root@pulsefire: ppm_data 780 1
root@pulsefire: ppm_data 3120 2
root@pulsefire: ppm_data 15 3 (=1+2+4+8)
root@pulsefire: ppm_data 240 4 (=16+32+64+128)
root@pulsefire: ppm_data 3840 5 (=256+512+1024+2048)
root@pulsefire: ppm_data_len 12 (in version 0.6 this is 11)
root@pulsefire: info_ppm
ppm_data00==0000000011000011
ppm_data01==0000001100001100
ppm_data02==0000110000110000
ppm_data03==0000000000001111
ppm_data04==0000000011110000
ppm_data05==0000111100000000

Hope that helps, gr Willem

[attachment=92]

Here is version 0.7 with mostly internal changes and a lot of fixes;

- Rewrite of config variable handeling so smaller and more options
- Wrote small lcd display driver for size and extended mode support
- Fixed external trigger bug
- Fixed soft warmup + added LCD keyword
- Fixed one off ppm_data_len cmd
- Changed sys_conn_mode to compiler flags
- Moved sys_*_time and sys_input_delay to defines to save space in eeprom
- WIP Added MicroAssemblyLanguage support for small scripts
- Added sys_dic_map 2-8 digital inputs in extended mode
- Added all fields to info_data to see internal pulse data.
- Added info_prog command to see internal prog data.
- Split source to multiple files phase1.
- Renamed sys_start_* to sys_warmup_*.
- Added sys_warmup_delay for startup predelay with all outputs off.
- Added sys_warmup_mode to use diffent pulse mode in sys_warmup_secs warmup mode.
- Added index printing argument to help command
- Added pulse_mode 5 Interleaved ppm data
- Made sys_adc/dic_map also work on indexed variables
- Made sys_adc/dic_map work with variable names instead of numbers
- Added more support for 16 column lcd and 4 row display
- Added debug flag which print more info to serial
- Moved sys_push_mode from eeprom into pf_prog with new name: req_auto_push
- Fixed offset of pwm_compa,pwm_compb and pwm_wait so now pwm_compa 0 is step 0.
- Fixed missed interrupt of compbX>0 so there was a loop of timer why result was stange.
- Fixed duel step bug/wait in auto reveral pulse_dir mode.

Errata:
- Serial/io on high freq output.
- Soft warmup and pulse_mode 3,4,5 is not oke.
- MAL support is WorkInProgress.
- req_auto_lpm_tune/pulse_delay_pre are not yet implemented.

Let pick out some of the changes by example;

- Fixed soft warmup
root@pulsefire: sys_warmup_delay 10 (wait 10 secords before going on)
root@pulsefire: sys_warmup_mode 2   (use mode 2 in soft warmup instread of pulse_mode, 0=use pulse_mode)
root@pulsefire: sys_warmup_secs 20  (after delay we use 20secs to do soft warmup)
root@pulsefire: sys_warmup_duty 5   (some multiply factor for wait duty calc)

- Made sys_adc/dic_map work with variable names instead of numbers
root@pulsefire: sys_adc_map 4 pulse_steps 1 6 (Maps adc4 to pulse_steps with the range 1 to 6)
root@pulsefire: sys_adc_map 5 pwm_compb 0 65535 3 (Maps adc5 to pwm_compb3 !!)
root@pulsefire: sys_adc_map 5 pwm_compb 0 65535 (Maps adc5 to all pwm_compb vars, note; use 255 as magic index)
root@pulsefire: sys_adc_map (It print now also the name of variable)
sys_adc_map00==65535 0 0 0
sys_adc_map01==65535 0 0 0
sys_adc_map02==65535 0 0 0
sys_adc_map03==65535 0 0 0
sys_adc_map04==pulse_steps 1 6 255
sys_adc_map05==req_pwm_freq 100 2000 255
root@pulsefire: help index (Use to list all mappable variables with number which is needed for MAL programs)
.....
sys_warmup_duty==29
req_pwm_freq==40
lpm_level==46
mal_trigger==60
(And use info_conf and info_data to see if variable has indexed data)

- Fixed offset of pwm_compa/b
root@pulsefire: req_auto_push 1
root@pulsefire: pulse_mode 2
root@pulsefire: pulse_steps 6
root@pulsefire: req_pwm_freq 60
root@pulsefire: pwm_compa 333 0
root@pulsefire: pwm_compa 333 1
root@pulsefire: pwm_compa 333 2
root@pulsefire: pwm_compb 65000 3
root@pulsefire: pwm_compb 65000 4
root@pulsefire: pwm_compb 65000 5
root@pulsefire: pulse_mode 1
root@pulsefire: pulse_mode 3
root@pulsefire: ppm_data 65535
root@pulsefire: pulse_mode 4
root@pulsefire: pulse_mode 5
(Having diffent outputs in diffent speeds looks working in all modes)

- Added more support for 16 column lcd and 4 row display
To use change these flags to match your lcd display;
LCD_SIZE_ROW 4 or LCD_SIZE_COL 16

- Changed sys_conn_mode to compiler flags
It looks like extended output is working, only have not yet tested it all at once, now there are 4 compiler flags to extends the arduino.
SF_ENABLE_EXT_OUT        // enable extended output for 8 outputs
SF_ENABLE_EXT_OUT_16BIT  // enable extended output for 16 outputs (with: EXT_OUT !!)
SF_ENABLE_EXT_LCD        // enable extended connection mode lcd.
SF_ENABLE_EXT_LCD_DIC    // enable multiplexing DIC inputs (with: EXT_LCD !!)

When using SF_ENABLE_EXT_LCD you get 6 analog inputs and 2 digital inputs to play with. (and only 3 outputs if not extented)
For MEGA arduino owners its on my todo to add a flag so you don't need chips for extension because of the extra io pins on the chip/board.

I have a new avr chip and some 74xx595 chips and 4 row display in order now.
So hope to test soon with working chip and all extensions connected to see if it works :)

Quote from txqNL on June 28th, 2011, 04:39 PM

Here is version 0.7 with mostly internal changes and a lot of fixes;

dude! you are freekin amazing!

I must ask, i have some people that would really like to build and use one of these but they are not inclined enuff to understand some of the technical input to make changes and what not. (I have my hard times)

so, i'm going to ask if it would be possible (or how much time it will take) to make a simple PC GUI that allows you to change some basic parameters. (number of outputs, I/O, different pulse train sequencing) i have some people that could really use this in there research but sense its in R&D mode it is really hard for them to use, ? just wondering,

Ill be playing with it soon! yeah!

Thanks again for all your hard work and open sourcing this wonderful PULSER!

~Russ
 

Quote from Rwg42985 on June 28th, 2011, 07:29 PM

I must ask, i have some people that would really like to build and use one of these but they are not inclined enuff to understand some of the technical input to make changes and what not. (I have my hard times)

so, i'm going to ask if it would be possible (or how much time it will take) to make a simple PC GUI that allows you to change some basic parameters. (number of outputs, I/O, different pulse train sequencing) i have some people that could really use this in there research but sense its in R&D mode it is really hard for them to use, ? just wondering,

The Arduino is almost fully calc_struct==445 we got max 512 bytes which are savable.
So want to get a few features in before starting on gui like;
hho MMW calc, amp regulated pwm, rpm/freq input for pwm/pll function.

I think around release 1.0 gui development could be started, I can already start building but I really need first to decide for a nice location where to host the source repro for all files,sch,docs.(like code.google or SF or github)
The gui is probably as much work as PulseFire itself something about 8-10 weeks 1 FTE to get near 1.0 release.
Some parts of the PulseFire code are now 1 year old already see the first auto lpm test last summer;

https://www.youtube.com/watch?v=dDV5ZLy5rGo
I have a option to work on this full time in august if there is bounty to have it asp else I need to go find myself some 'normal' work.

Quote from txqNL on June 29th, 2011, 10:47 AM

Quote from Rwg42985 on June 28th, 2011, 07:29 PM

I must ask, i have some people that would really like to build and use one of these but they are not inclined enuff to understand some of the technical input to make changes and what not. (I have my hard times)

so, i'm going to ask if it would be possible (or how much time it will take) to make a simple PC GUI that allows you to change some basic parameters. (number of outputs, I/O, different pulse train sequencing) i have some people that could really use this in there research but sense its in R&D mode it is really hard for them to use, ? just wondering,

The Arduino is almost fully calc_struct==445 we got max 512 bytes which are savable.
So want to get a few features in before starting on gui like;
hho MMW calc, amp regulated pwm, rpm/freq input for pwm/pll function.

I think around release 1.0 gui development could be started, I can already start building but I really need first to decide for a nice location where to host the source repro for all files,sch,docs.(like code.google or SF or github)
The gui is probably as much work as PulseFire itself something about 8-10 weeks 1 FTE to get near 1.0 release.
Some parts of the PulseFire code are now 1 year old already see the first auto lpm test last summer;

https://www.youtube.com/watch?v=dDV5ZLy5rGo
I have a option to work on this full time in august if there is bounty to have it asp else I need to go find myself some 'normal' work.

Maybe we could just start a Wiki page for now that is divided into set up options.  Each option could be outlined with descriptions and what line of code to modify.  It wouldn't need to be a completely technical description, just stuff like if you want to use your POTs to control some variable, have a list of numbers to use and descriptions of each number.  Things like that in plain english.  Most people don't need to know what the numbers mean in code, but which ones they need to use to accomplish the action they want.  

Nate

Any recommendations for a certain type of Wiki that is recommended.  I'll install anything that will further progress.  

I have narrowed it down to these choices.

bitweaver, BusinessWiki, MediaWiki, Midgard Wiki, PhpWiki, SMW plus, Tiki Wiki CMS Groupware, WackoWiki and WikkaWiki.

Any idea's guys?

Quote from firepinto on June 29th, 2011, 02:56 PM

Quote from txqNL on June 29th, 2011, 10:47 AM

Quote from Rwg42985 on June 28th, 2011, 07:29 PM

I must ask, i have some people that would really like to build and use one of these but they are not inclined enuff to understand some of the technical input to make changes and what not. (I have my hard times)

so, i'm going to ask if it would be possible (or how much time it will take) to make a simple PC GUI that allows you to change some basic parameters. (number of outputs, I/O, different pulse train sequencing) i have some people that could really use this in there research but sense its in R&D mode it is really hard for them to use, ? just wondering,

The Arduino is almost fully calc_struct==445 we got max 512 bytes which are savable.
So want to get a few features in before starting on gui like;
hho MMW calc, amp regulated pwm, rpm/freq input for pwm/pll function.

I think around release 1.0 gui development could be started, I can already start building but I really need first to decide for a nice location where to host the source repro for all files,sch,docs.(like code.google or SF or github)
The gui is probably as much work as PulseFire itself something about 8-10 weeks 1 FTE to get near 1.0 release.
Some parts of the PulseFire code are now 1 year old already see the first auto lpm test last summer;

https://www.youtube.com/watch?v=dDV5ZLy5rGo
I have a option to work on this full time in august if there is bounty to have it asp else I need to go find myself some 'normal' work.

Maybe we could just start a Wiki page for now that is divided into set up options.  Each option could be outlined with descriptions and what line of code to modify.  It wouldn't need to be a completely technical description, just stuff like if you want to use your POTs to control some variable, have a list of numbers to use and descriptions of each number.  Things like that in plain english.  Most people don't need to know what the numbers mean in code, but which ones they need to use to accomplish the action they want.  

Nate

Quote from txqNL on June 29th, 2011, 10:47 AM

Quote from Rwg42985 on June 28th, 2011, 07:29 PM

I must ask, i have some people that would really like to build and use one of these but they are not inclined enuff to understand some of the technical input to make changes and what not. (I have my hard times)

so, i'm going to ask if it would be possible (or how much time it will take) to make a simple PC GUI that allows you to change some basic parameters. (number of outputs, I/O, different pulse train sequencing) i have some people that could really use this in there research but sense its in R&D mode it is really hard for them to use, ? just wondering,

The Arduino is almost fully calc_struct==445 we got max 512 bytes which are savable.
So want to get a few features in before starting on gui like;
hho MMW calc, amp regulated pwm, rpm/freq input for pwm/pll function.

I think around release 1.0 gui development could be started, I can already start building but I really need first to decide for a nice location where to host the source repro for all files,sch,docs.(like code.google or SF or github)
The gui is probably as much work as PulseFire itself something about 8-10 weeks 1 FTE to get near 1.0 release.
Some parts of the PulseFire code are now 1 year old already see the first auto lpm test last summer;

https://www.youtube.com/watch?v=dDV5ZLy5rGo
I have a option to work on this full time in august if there is bounty to have it asp else I need to go find myself some 'normal' work.

keep doing what your doing and when the time is here, we will be thankfull. i know how these things work and it would be a wast of time to do that and then go back and do it again... keep drainking that coffie! lol thanks my friends!

~Russ

I have here the updated schematic to work with the Pulse Fire 0.7 Software.

Will, please check it again,

Thanks, ~Russ

https://www.youtube.com/watch?v=dDV5ZLy5rGo

will, that is so sweet! some inpressave work! love it!

~Russ

Quote from Rwg42985 on July 1st, 2011, 02:27 AM

I have here the updated schematic to work with the Pulse Fire 0.7 Software.

Will, please check it again,

Thanks, ~Russ

Yep that will work did no changes to default connection mode.
Is that in gEDA made ? I've started to learn that but it has a sharp learning curve, now trying to create a universal 8 port mosfet board for in extented mode, have now access to place where I can etch boards.

I just did a simple mockup of the gui to see how it looked, I think I like it.

[attachment=100]

Quote from txqNL on July 3rd, 2011, 09:46 AM

Quote from Rwg42985 on July 1st, 2011, 02:27 AM

I have here the updated schematic to work with the Pulse Fire 0.7 Software.

Will, please check it again,

Thanks, ~Russ

Yep that will work did no changes to default connection mode.
Is that in gEDA made ? I've started to learn that but it has a sharp learning curve, now trying to create a universal 8 port mosfet board for in extented mode, have now access to place where I can etch boards.

I just did a simple mockup of the gui to see how it looked, I think I like it.

Sweet, it looks great to me!  Looks like PulseFire will be an extremely capable unit. :-)  Does it come with the 50 cal? :P

Nate