Huh, mine took about a week for it to arrive here in Los Angeles.
DIY Head Tracker For A Tenner
- Thread starter Dead Fred
- Start date
Huh, mine took about a week for it to arrive here in Los Angeles.
9150DMPTest4 4.0.0 seems to be overcorrecting a bit much in some situations. I can play fine for a couple of minutes, but when I then need to look right and up the view turns back to the left a bit. It's okay if I try that same movement again right after, but a couple minutes later the overcorrecting is back.
It's probably not limited to right & up, but that's where the effect seems most noticeable.
PS:
The 3.0.0 sketch seems to have the same problem. Strange, I never noticed it with 3.0.0 before. Gonna recalibrate tomorrow.
It's probably not limited to right & up, but that's where the effect seems most noticeable.
PS:
The 3.0.0 sketch seems to have the same problem. Strange, I never noticed it with 3.0.0 before. Gonna recalibrate tomorrow.
Last edited:
Do you use Opentrack? I noticed this in 2.3 RC8 and reverted to 2.2 stable.
http://tysoes.com/Elite/OpentrackINI.zip
My 2.2 and RC8 ini files are in the above zip. Might help people struggling (assuming the configs are transferable).
It happened with and without OpenTrack. It turned out to be a calibration issue. After a couple more calibration attempts I have now found settings I can play with. But really just play. If I take off the EDTracker and move it with my hands, which results in faster and more extensive movements, I'm running into overcorrecting issues again.
Wanted to do calibration tests tomorrow, but I just couldn't wait
Wanted to do calibration tests tomorrow, but I just couldn't wait
Last edited:
If someone have knowledge of Arduino coding, I found this: https://github.com/kriswiner/MPU-9250 . Overview of several different 9DOF seonsor is here: https://github.com/kriswiner/MPU-6050/wiki/Affordable-9-DoF-Sensor-Fusion .
I cheered too soon. I let the EDTracker rest over night and just now wanted to give it a spin, and I get overcorrections all over the place. I turn my head to the left, the head in the GUI follows, stops, then does a quick correction a bit further to the left. I turn my head to the right, the head in the GUI does also, stops, then corrects a bit further to the right. I move my head left again, GUI head movement and overcorrection happens as before, I move my head to the right, the head in the GUI follows but then corrects movement to the left. I lower my head while keeping it turned right, the head on the GUI follows but also turns a bit towards the center.
I tried flashing the old Test3 3.0.0 sketch after following the old calibration guide, but that one is now totally out of whack, bouncing all over the place as if I still had the ferrite core attached to the cable. Makes me wish I never tried test 4. No matter what I try, I always get overcorrection that makes it unusable.
DMP Calibration always looks like this:
PS:
Flashed back to test 4.0.0. Overcorrections all over the place. Reattached the ferrite core. Unit now acts as innocent as a lamb, doing all movements without any overcorrections.
I'll report back in 15 minutes when I expect the behavior to change again.
I tried flashing the old Test3 3.0.0 sketch after following the old calibration guide, but that one is now totally out of whack, bouncing all over the place as if I still had the ferrite core attached to the cable. Makes me wish I never tried test 4. No matter what I try, I always get overcorrection that makes it unusable.
DMP Calibration always looks like this:
PS:
Flashed back to test 4.0.0. Overcorrections all over the place. Reattached the ferrite core. Unit now acts as innocent as a lamb, doing all movements without any overcorrections.
I'll report back in 15 minutes when I expect the behavior to change again.
Last edited:
How very curious :-S so this ferrite core is definitely an interesting development. Can't explain why it's just a concern for you. Quick check - on the Pro Micro, there are two resistors in the USB data lines, just below and to the left of the USB connector (if you're looking at the device with the USB connector coming out to the right). Do they both have 220 written on them? Or is one of them 331? Real stab in the dark and unlikely, but worth a check, I'll ellaborate why if it does indeed turn out one of them is a 330 ohm res.
Slightly rough picture
of OT v2.2 curves.But this is my yaw graph. Yours may need to be different depending on your screen etc. On the tab at the top you can also set up pitch (up/down) and roll curves. You can invert all axes in options.
First set EDtracker Ui scale x and y to 1, linear. Set OT protocol to TrackIR, put accela filter on if you get any jittering in game.
A - If you wear your tracker and switch it on with 'start' in OT, you get live feedback. A is the current point. It helps for visual tuning.
B - is a control point. You can modify them by clicking/Rclicking on points, add them by clicking on the curve. Play around.
C- normally unchecked, but if you want different responses on each side of the axis, check this and set up the curve in area D. Leave this unchecked usually, so one graph for both sides of the axis..
E - this graph axis shows actual angle the tracker has moved in yaw only.
F - this graph axis shows the angle your viewpoint moves in the game in yaw only.
So here, a 35ish degree head yaw movement is amplified to about 160 degrees in the game.
At bottom L corner of the graph is a flat area of curve. This provides a sort of detente, so the front middle view feels slightly sticky and it's easy to tell where it is.
Last edited:
@Brumster
They're both 220 Ohms.
Current settings seem stable and work rather well. I'm beginning to think that maybe I just have to repeat the 9150DMPCal calibration process until I find settings that work, even if it takes 20 attempts or so. Magnetometer seems to be working because I see drift compensation changing.
If only someone could explain to me why my EDTracker behaves as unpredictably as it does. Before, the ferrite core was causing issues, now it seems it fixes them. It doesn't make sense.
They're both 220 Ohms.
Current settings seem stable and work rather well. I'm beginning to think that maybe I just have to repeat the 9150DMPCal calibration process until I find settings that work, even if it takes 20 attempts or so. Magnetometer seems to be working because I see drift compensation changing.
If only someone could explain to me why my EDTracker behaves as unpredictably as it does. Before, the ferrite core was causing issues, now it seems it fixes them. It doesn't make sense.
A previous poster mentioned that somebody 'upgraded' his 6050 to a 9150, who actually did that for him, is that a resource known to the community or was that just something he did through private means?
Also, is there a way to bind a joystick button to the EDTracker re-center button? I'm trying Opentrack but can't seem to get it to work. I also still can't "see" my EDTracker when I hook it up to the software it's "supposed" to use. The top right section doesn't list the name, just says "connecting" or "disconnected" ... can't recall, at work now.
Also, is there a way to bind a joystick button to the EDTracker re-center button? I'm trying Opentrack but can't seem to get it to work. I also still can't "see" my EDTracker when I hook it up to the software it's "supposed" to use. The top right section doesn't list the name, just says "connecting" or "disconnected" ... can't recall, at work now.
Indeed. I am at a loss to explain, in all fairness. You're not a daft chap, so I think telling you all the obvious stuff about calibration and keeping it still at the important moments isn't needed...
It's the PIXIES. It's always the pixies.
Ok, I'll admit, I did it for him
but I can see where this is going and to be honest I don't want a flood of requests from the internet asking to upgrade their 6050s for them So I'd really not want to put up an expectation that I can do these. The problem is I'm flat out with so many other things with EDTracker, mainly trying to keep up with demand for new ones, that getting dragged into a sideline of upgrading existing ones might be the straw the breaks the camels back
View attachment 9463
Slightly rough picture
But this is my yaw graph. Yours may need to be different depending on your screen etc. On the tab at the top you can also set up pitch (up/down) and roll curves. You can invert all axes in options.
First set EDtracker Ui scale x and y to 1, linear. Set OT protocol to TrackIR, put accela filter on if you get any jittering in game.
A - If you wear your tracker and switch it on with 'start' in OT, you get live feedback. A is the current point. It helps for visual tuning.
B - is a control point. You can modify them by clicking/Rclicking on points, add them by clicking on the curve. Play around.
C- normally unchecked, but if you want different responses on each side of the axis, check this and set up the curve in area D. Leave this unchecked usually, so one graph for both sides of the axis..
E - this graph axis shows actual angle the tracker has moved in yaw only.
F - this graph axis shows the angle your viewpoint moves in the game in yaw only.
So here, a 35ish degree head yaw movement is amplified to about 160 degrees in the game.
At bottom L corner of the graph is a flat area of curve. This provides a sort of detente, so the front middle view feels slightly sticky and it's easy to tell where it is.
Thanks man, that'll help!
So I'd really not want to put up an expectation that I can do these. The problem is I'm flat out with so many other things with EDTracker, mainly trying to keep up with demand for new ones, that getting dragged into a sideline of upgrading existing ones might be the straw the breaks the camels back
maybe it's time to get an apprentice to do your soldering for you ?
Ferrite core will change the distortion of the magnetic field so if you add or remove it then I would expect you would need to perform mag calibration. But if it's working - don't change it
[edit] There are a couple of bugs in the latest (v4) 9150 test sketch which may be effecting you.
The start-up calibration can product odd results. Manifests as magnetometer struggling to keep yaw drift in check (head wobbles a bit). Workaround is to press the button again.
The 'recentre view' code doesn't clear magnetometer readings so pressing multiple times results in a build up of mag compensation errors.
The code which calculates the transformation matrix which "un-distorts" the magnetometer readings can fail if the raw data is too far off centre ( the red sphere is way off).
All are fixed in the production release
(... soon)Rob
Last edited:
All are fixed in the production release
Rob
Sorry Rob, i may have to report you to the apropriate authorities.
The word 'soon' is definately a micheal Brookes exclusive copyright
My EDTacker (9150) arrived this morning, so far i;ve only had time to get it working, strapped to my headset and make sure its basically doing what it should in ED, will be giving it a more in depth run this evening. My initial impressions are that its great, definately worth the 38 quid I paid for it (assembled and enclosed), my expectations are that it will not be perfect and that software updates will keep improving it (and breaking it now and then) but that it will provide a ton(ne) of additional fun in ED, so thanks to the ED team