Wat can happen into a testrig.....
The electric motor produce a magneticfeeld - the plastic (?) disk makes a static (magnetic) feeld.
At high rpm the testrig don't / can't make (magnetic) feelds anymore, current is lower / magneticfeeld is lower.

I agree. Electric motors make a lot of electrical noise as well.

I don't say anything, you've to find out by yourself.
http://www.electronics.gompy.net/completecdi/

I'm just going to keep building them Rob.. So far they all work to run the engines. I can live with it for now. I am building a CDI trigger board which I am adding to the timer board and my CDI. So far, it looks like an easy task. Should work fine. I can experiment now with settings and timing which is really great.. Thanks for this project.. A job well done.!!

John

It's beautiful Rob !!!
This makes my whole week worthwhile! I feel honored!
Started etching the new board already. Thank You.


John

I make a change of software I use, maybe also intrest for others.
Cheap, easy to use, multi language and free print / show program.
http://www.abacom-online.de/uk/html/produkte.html

Rob,

It appears that the link to your site has changed. Can you post a new link to where the CDI board is? Thanks.

I'm sorry but I've to cleanup the server,there are a lot of old files and pictures who take a lot of space.

http://www.electronics.gompy.net/cdi/
http://www.electronics.gompy.net/completecdi/
http://www.electronics.gompy.net/cdiscoot/
http://www.electronics.gompy.net/cditci/
http://www.electronics.gompy.net/strobe01/
http://www.electronics.gompy.net/strobe02/
http://www.electronics.gompy.net/strobe03/

Thanks Rob.

Charlie... I missed making 4 small holes on the HV side..compare to the website board layouts and you should see them.
Etched two boards and am in the process of drilling. Should finish one tomorrow, the other tomorrow night ready for parts.

John

Thanks John. I will take a look.

If you can't see anything wrong or missing Charlie, then I sent you the correct edited layout.
So far, I think the small .1 uf cap across the hall leads has solved my misfires at low speed. If we could only change the firing to after the magnet passes, it would be great. Alot must be changed for my hall mounts to accomodate the early firing.
I've been doing a work-around on that and it seems to be ok. Maybe the pickup point can take care of that? Not sure yet.

John

Hi John,

The Layout looks good. You should be able to fudge a few degrees. Have you asked Rob about talking the Programmer about that?

Hello Guys!

Has anybody tried this unit on a 2T scooter with success?

Thanks!

Charlie.. I was under the assumption that as this was presented, it was a "what you see is what you get" project. No changes no special requests..so I haven't asked.


John

OK. Well I think you can play with the pick up point in the ignition controll software and do what you want.

We can't change anything into the pic.

1e, the pic is out of memory.
2e, the compiler is out of free use.
3e, you can change the pickup point (hard-and software).
4e, every detection in industry isl make on a ricing point.

Not sure why you want to change to after magnet passes but just a thought, you could put a simple inverter on the input from the hall effect switch.

Jeff

This will of course, change the whole pulse structure and the program may well not like it.

Rob,

What compiler did he use? It won't take any more program space to change the way the pic operates. All you have to do a logical AND on the input. Just as Nemey did. know I misspelled his name.

Why change the program for one person if everyone is / can changing the POP ?
BTW, wat do you thinking about the time left to calculate the advange ?
It's not only to change a bit, the complete calculation will be wrong or to short.

I don't know wat compiler he was using, even I don't have the source code (or compiler)

Rob, I can take care of the early trigger point. What I have experimented with was to set my low rpm timing to zero degrees and the total advance to only 17 degrees for top rpm. It works that way and I don't have to really move the hall mount much.
When I ran the engine that way, it still started easily and gives me the same top rpm and power as before.
The oscillation I was getting at slow speeds was fixed mostly by adding the .1 cap on the hall leads. It only does it now at starting speeds and then goes away. One odd thing though was that it takes 2 passes with the magnet after power up to produce the first spark. Charlie mentioned that also in his testing..kind of like it tests the speed first to make sure the engine is rotating or something..not sure what it does there.

John

How did the electronic know wat rpm the engine makes if there is no information befor he is started ?
The CDI needs ONE rotation befor it can calulate with the timetablevalues.
The second rotation the CDI knows the time of one rotation and can use the timetable.

Switch the CDI on (NOT the HV-board), rotate the prop ones (to get petrol into the carburator), switch the HV-board on, start the engine.
Now the CDI gets his first puls and can calculate thet ignitiontime for the second rotation.

BTW, there is no early triggerpoint into the picprogram (HEX).
If you place the hallsensor for example at 70 degrees, into the table you can start and end with any degrees you want.
The pic must only know where you have placed the hallsensor.

Comment from the programmer

This image is a snapshot from some output of a logic analyzer hooked up to the CDI.
The topmost row (RB0/yellow) is attached to the Hall-sensor.
It shows the actual pulse coming in from the pick-up.
In this case the pulse itself has a length of 82.5 usec and there is a period of 4.823 msec between two consecutive pulses.
So the actual laptime is 4.906 msecs.
This is also reflected in the row one up from the bottom (RA3/orange).
For testing purposes I used this port to toggle whenever a pulse comes in and it is
therefore effectively giving me the laptime: 4.906 msecs which equals 12230 rpm if I am correct.
As soon a the incoming signal (on RB0) changes from high to low, i.e. on the falling edge, the actual calculation of the laptime and desired delay starts.
This is reflected in the output of pin RA2 (2nd row from the top/green).
Again, for testing purposes I set this pin up in such a way that it goes high when a pulse has come in and goes low as soon as the ignition needs to fire.
The calculation uses the time difference between this pulse and the previous pulse to determine the actual laptime.
This is why you need at least two pulses before an actual calculation can be made.
This laptime is then used to retrieve the angle from a table. Which in turn is then used to calculate the delay needed.
The program then basically waits until the time has come to fire and fires the ignition pulse.
This can be seen in the middle row (SCR/purple).
Some 277 usecs after the last pulse from the sensor the ignition is fired, i.e. SCR goes high.
It stays high for 77.7 usecs which is more or less exactly the ignition duration set through the PC program.
And finally, the last row (RB3/red) shows the output of the PWM that can be used to generate the intermediate voltage.

Note that the actual row names (RB0, etc.) in this picture are the pins used on the PIC.

Hi Rob.
Some questions about output:
RB0: is 82.5us is a standard timing of a hall sens or it depends on a time that magnet going thru the hall?
RA3: don’t understand that is it end when it goes from low to high?
RB3: we need to stop the PWM during the SCR is high to prevent the SCR damage.
My be better to see the output between 2 pulses of a hall?

BR IURA