Hello,
I have been working through some haptic updates to introduce a longer delay to allow the motor to spin up - that way short events still trigger a vibration.
In the process I have found a really weird bug that I cant get my head round.
Reproduce as follows:
* power up radio
* move trim stick on left stick 2 clicks left - then 2 clicks right. ; this should fire the haptic - and it does! But at a very very low power.
* move trim stick left all the way... then back to center... then all the way left.. then back to center again. Boom Haptic at full power.
I cant for the life of me get my head round why this would be the case.
Any ideas?
Rob
Haptic Bug - ersky9x
- Rob Thomson
- Site Admin
- Posts: 4543
- Joined: Tue Dec 27, 2011 11:34 am
- Country: United Kingdom
- Location: Albury, Guildford
- Contact:
Haptic Bug - ersky9x
Slope Soaring, FPV, and pretty much anything 'high tech'
...........if you think it should be in the wiki.. ask me for wiki access, then go add it!
...........if you think it should be in the wiki.. ask me for wiki access, then go add it!
- Mechcondrid
- Posts: 222
- Joined: Fri Dec 30, 2011 3:53 am
- Country: -
- Location: ledyard, connecticut, United States
- Contact:
Re: Haptic Bug - ersky9x
ok nevermind the previous comment i was run on empty and no sleep (came back from pax east on that day)
i think that maybe the delay is interfering with the actual signal generation for the haptic; do you put the haptic into a que or do you just delay the signal?
if its just the signal then it might be only activating on the tail end of the signal
i think that maybe the delay is interfering with the actual signal generation for the haptic; do you put the haptic into a que or do you just delay the signal?
if its just the signal then it might be only activating on the tail end of the signal