Mantis Bug Tracker
Main | My View | View Issues | Roadmap | Repositories
  

View Issue Details [ Jump to Notes ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000402FirmwareScheduler (Inj/Ign)public2011-11-18 13:192012-09-10 14:20
ReporterFred 
Assigned ToDeuceEFI 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version0.2.0-SNAPSHOT 
Target Version0.2.0Fixed in Version0.2.0 
Summary0000402: Don't Schedule Anything When Desired PW Is 0
DescriptionCurrently we blindly schedule even ridiculously small output pulses regardless of the intent of the earlier code. Change to not schedule if the final pulse width is less than our minimum possible pulse width, whatever that may be at the current time. Right now it's considered to be 100us but is probably quite a bit lower in reality.
TagsNo tags attached.
FirmwareVersion
Issue TypeImprovement
Risk of Breakagemedium
Attached Files

- Relationships

-  Notes
User avatar (0002016)
Fred (administrator)
2012-09-04 10:38

 Fixed in 8de7257 please bench test and confirm that no outputs occur when PW is very low (under 200us).
User avatar (0002082)
DeuceEFI (reporter)
2012-09-10 14:19

 I used 500 RPM as my threshold, with 0% VE, 0* Advance, 0mS Dwell, then at 1000 RPM I used 1% VE, 1* Advance, 1mS Dwell, outputs stayed low until 503 RPM then scheduled outputs could be seen on the Saleae.
User avatar (0002083)
DeuceEFI (reporter)
2012-09-10 14:20

 I have confirmed that in hash 8de725795676188774f70559f4191ab6b1ee4da3 there are no output pulses for injection or ignition advance when below the thresholds listed in the VE, Ignition and RPM-Dwell tables.

Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker