i have scooter tachometer (was by oem) but controller chip has been broken .
Tachometr is mA meter , it can controlling with PWM help .
I want use it in multi modes . (you can see it in patch)
I wrote some code , but it doesn't work . (compiling without errors)
Andrey , can you help me?
i didn't know about 122nd ticket .
But i asked about another : i didn't defined "DISPLAY_SWITCH" and code doesn't know what is hw pin . where i can define it ?
Patch have all difference between "clear" code and my code .
Re: mA meter tach
Posted: Wed Jan 07, 2015 8:54 pm
by AndreyB
rus084 wrote:i didn't know about 122nd ticket .
now you know about this defect which might be relevant
rus084 wrote:
But i asked about another : i didn't defined "DISPLAY_SWITCH" and code doesn't know what is hw pin . where i can define it ?
No, you did not really ask about that. As far as I know, you've asked "I wrote some code , but it doesn't work" which is a typical case of http://rusefi.com/wiki/index.php?title=40
rus084 wrote:
Patch have all difference between "clear" code and my code .
this is actually a problem. Your patch has too much stuff which has nothing to do with your question, this makes it harder to respond.
please google "how to ask a good question"
Re: mA meter tach
Posted: Wed Jan 07, 2015 9:18 pm
by AndreyB
there is a bit of a mess around brain_pin enum, output_pin enum and OutputPin struct, I will now try to simplify this.
Re: mA meter tach
Posted: Thu Jan 08, 2015 3:06 am
by AndreyB
russian wrote:there is a bit of a mess around brain_pin enum, output_pin enum and OutputPin struct, I will now try to simplify this.
Done. io_pin_e is not really needed any more, it would probably be eliminated pretty soon.
else i have problem with power supply from laptop ( yersterday usb power in laptop was good ):
problem.png (40 KiB) Viewed 10027 times
2.4V! but i didn't connect any devices to the discovery .
i hear beeping from laptop when discovery is connected . (hsdpa modem have more power consumption , but it work's good )
The general idea - if PWM is below 0.01% or above 99.99% instead of doing the normal scheduling it should just pause PWM for same 10ms. So, somewhere it should set next event invocation to 10ms instead of 0.001% of period which breaks everything