Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Also, the error tooltip on the microcontroller just tells you when the PID is attempting to output a value outside the 0-1 range for the throttle. The reason you see a short flicker is because there is a 1 tick delay between each of the components of a microcontroller so it takes a couple ticks for the controller to detect the out of range condition and then clamp it to 0-1.
https://i.gyazo.com/1d6250f83f8e5add1150c4a95975be57.mp4
This is a video, although it did flicker the negative number on every bang for me (I think at 30fps it won't 'capture' every tick on the recording software).
Ultimately it will spend a lot of time backfiring, usually, when close to the speed it's trying to achieve.
shut down or have any issues. It's not something that occurs when using the throttle manually.
I tried monitoring the microcontroller and the Error YES flashes when this occurs, but the throttle value seems to remain at least the idle if not slightly higher throttle setting. I've had a play with the coef and it doesn't seem to make much difference.
If you didn't have audio you wouldn't notice anything out of ordinary. Any thoughts?