??? 10/14/09 16:47 Read: times |
#169704 - timing requirements Responding to: ???'s previous message |
Ofcourse yes this is a massive consideration, however I am a little microncontroller illiterate, so perhaps you could help me here.
Critical operation: here it is the speed at which it responds to the driver requesting a gear change. there are h two inputs (flappy paddles) I was considering having some electronics that would generate an interrupt request signal here to make sure this is always done instantly. The outputs are then simply two control signals which are connected to the Other outputs: Flashing LED to let me know the system is alive, so this only needs to change state twice a second, is that correct ? LCD screen I have read is fairly easy to incorporate, is this true? Output to ignition pause request is simply a control signal of a square wave triggering the ECU to invoke some function that is programmed during the ECU mapping. Other inputs: The only thing I do not know about yet is the input data from the ECU, I do know this is sent serially but the information I have requested from the manufacturer has not arrived. ECU data: I am not datalogging it, And only plan to display the revs via LCD currently so perhaps you could comment on this suitability, I assumed it would involve seperating the data sent serially and simply displaying the data that I will have saved in the RAM memmory that corresponds to the revs? Or is this probably not how it would work? Questions: What do you mean by different ratio of clocks to cycles? Do tell me if this asking a bit to much and the information is available elsewhere for me to read. cheers again guys. |