XGATE PIT based bit bang fuel injection

[SleepyKeys]

Yea sounds like a good idea ttyl

[SleepyKeys]

Getting rid of slag. Calm down code reads easier too

[SleepyKeys]

Each channel with it's own DC with an event scheduled every Clocks.millisToTenths % 10.

[Fred]

Two questions:

1. Are these outputs in any way timed to the ECT input time stamp subsystem?
2. Does your code handle switching multiple pins in one execution?

Cool screen shot none-the-less! :-)

Fred.

[SleepyKeys]

Two answers.

1. No not yet, that's the next step, wanted to make sure everything was mint so far.
2. By Execution do you mean one instructional bang or one ThreadRun? Threadrun yes it's its zero time or past due.

What else ?

[Fred]

OK, so each time your XG code runs it switches something on or off depending on some internal clock such as the PIT clock and stamps/registers/masks, right?

I take it you're running one piece of code for on and off and running it ultra often to make sure that it's high res, rather than timing the execution with the pit timer? You can ignore most of these questions if you want :-)

Is your internal clock scheme 32 bit? And do you handle roll over gracefully?

If it's 32 bit, how did you achieve that? With the Freescale trick? Or manually? Does the PIT stuff have a roll over interrupt? I don't think so, so it must be manually, right?

Curiosity killed the cat!

Fred.

[SleepyKeys]

It takes quite a bit into account I think there are 500 lines of ASM code, so it getting smarter every day But yeah that's the core of it.

"I take it you're running one piece of code for on and off and running it ultra often to make sure that it's high res, rather than timing the execution with the pit timer? You can ignore most of these questions if you want " No the only loop like that is the xgateMetronome which is pretty tight.

Again xgateMetronome

[Fred]

Don't forget that you have to explain this thing to me until I understand it as well as you do :-) Carry on.

[SleepyKeys]

I'll need to go back and comment things more too.

[Fred]

Right, and if you have, and it's good, that should reduce your explanation load to almost nothing. Whatever isn't clear when I start asking and poking can be added to the docs as we go, I guess :-)