![]() |
Dead Zones
Greetings,
Can anyone tell me how to change the dead zone that exists by default? That is, I know any input between pretty much 120 and 140 is read as neutral. I don't necessarily want to remove that, but if I did, how would I do so? Also, is anyone else changing their dead zone? |
Re: Dead Zones
The Victor's dead zone can be compensated for in code if you want. Just add 7 or so to the value you're sending to if if it's more than 127, and subtract 7 or so from the value if it's less than 127.
|
Re: Dead Zones
What is the victor's dead zone?
|
Re: Dead Zones
it may be better to expontially map the joysticks so that there is no dead zone but it is less sensitive at lower values
|
Re: Dead Zones
We use a lookup table to "curve" our drive outputs...
I don't remember the syntax for defining tables offhand; if you need it let me know and I'll look it up tomorrow. if you put this in your code... pwm01 = lookuptable[p1_y]; Say you've moved the joystick slightly, and p1_y = 132. This line will define pwm01 as the 133rd value in your lookup table (since lookuptable[0] is the first number in the list). You could make that 133rd value anything you want... indeed, you could make all table values from 90 to 170 equal to 127, making a freaking huge dead zone. Hope that helps |
Re: Dead Zones
Yeah, we do the same thing as the guy in the above post. "Smoothed" lookup table makes the robot move nicer.
|
Re: Dead Zones
Quote:
|
Re: Dead Zones
Quote:
Code:
rom const unsigned char lookTable[XXX] = {x, y, z};Code:
unsigned char lookTable[255];Paul Dennis |
Re: Dead Zones
The main Victor page describes the deadband:
Quote:
|
| All times are GMT -5. The time now is 01:05. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi