DIY Head Tracker For A Tenner

I'm really impressed, tihee, that was it! The EDTracker is identified in USBView as having product id 8036, while ED thinks it's 8037. Changed the DeviceSettings.xml file and the game picked it right up! You certainly have an eye for detail.

Thanks!
 
I'm really impressed, tihee, that was it! The EDTracker is identified in USBView as having product id 8036, while ED thinks it's 8037. Changed the DeviceSettings.xml file and the game picked it right up! You certainly have an eye for detail.

Thanks!

Glad to be of assistance. Just be warned, you will have to edit this file, everytime(!) they update the game. At least, untill FD decides to add the second device to the "official" DeviceMappings.xml file!

Now, if someone have an idea what I need to do, to get my 9150 to work with the newer EDTracker2 sketches released? I don't get any axis movement with the sketches newer than v1.0.1. I e, with v4 I see Yaw drift registered in the EDTracker GUI, but no movement of the axis, nor in the USB Game Controller aplet
 
So I have extreme left drift. I can't even go 2 minutes without it pulling that way. So basically I need to get the 9150 but I am terrible at soldering. Any videos or options I may have?
 
I'm doing a 9150 video at some point to show the differences with the 6050. I'll try to do a little section on de-soldering your old 6050 and dropping a 9150 in place.

But drift that severe really should be fixable, assuming you've not fried a component on the board. Check calibration, keep flat/still, let warm up, ensure you've got auto-centering enabled, minimise/close the GUI, etc....
 
Now, if someone have an idea what I need to do, to get my 9150 to work with the newer EDTracker2 sketches released? I don't get any axis movement with the sketches newer than v1.0.1. I e, with v4 I see Yaw drift registered in the EDTracker GUI, but no movement of the axis, nor in the USB Game Controller aplet

I updated the UI and calibrated my new 9150 last night to the latest firmware without issues, so this is probably not going to help, but is it definitely not registering movement in the the game?

The only reason I mention it that there was a moment when I thought the it wasn't working, but it turned out that it was just rock solid and locked in place, I was just used to a bit of drift :)

You sound like your understanding of this is way ahead of mine, so sorry if this is entirely useless!
 
I'm doing a 9150 video at some point to show the differences with the 6050. I'll try to do a little section on de-soldering your old 6050 and dropping a 9150 in place.

But drift that severe really should be fixable, assuming you've not fried a component on the board. Check calibration, keep flat/still, let warm up, ensure you've got auto-centering enabled, minimise/close the GUI, etc....

I've just had mine through the post.... Housework can wait :p

Splendid job and fast turnaround on the upgrade from 6050 to 9150.

Sent on wednesday, back on saturday.
 
Hi All,

Hope someone can help me out here.

Just got my ED tracker, and I have been using the user guide PDF, the guide says go to device manager to and the tracker is under "other devices" (and it was initially), so I got the software, it then disappeared from "other devices" but I can still see it connected under ports. I tried switching ports, another cable, rebooting etc but no change.

Now I am following Brumsters youtube on setting up the GUI, I have calculated the bias values & flashed EDTracker2 2.20.7, everything was the same for me as the video as far as I can tell, in the first drop down its on EDTracker 2.20.7, the second says com4 - Arduino Leonardo(com4), the top box (on Brumsters has now changed to EDTracker11 V 2.20.7) mine is still on not connected, the box below says not connected, Brumsters says monitoring.

Does anyone know what the problem might be, I have tried everything I can think of, its not something I know much about.

Thanks for any advice or ideas.
 
Hi - looking for some advice/help.

I've got EDTracker setup and configured with OpenTrack (2.3 rc8), and the sensitivity is set VERY high - e.g. yaw/pitch are set to 180 at 20 - and the octopus responds accordingly.

Alas Elite does not - it responds, but with a very very slow/soft centre, and seems less than 1:1 until I get into the extreme of movement.

Can anyone advise where I may have gone wrong - in the game options the headlook mode is direct, and there are no deadzones set (e.g. sliders to the left).

EDIT: Everything works well using EDTrack...

Many thanks.
H
 
Last edited:
Does anyone know what the problem might be, I have tried everything I can think of, its not something I know much about.

Hi chap. I would try an unplug, close the GUI, replug in, restart GUI - sometimes the COM ports get bound up in the .NET libraries I think (I can't explain it, but a restart of the GUI sorts it). Failing that, flash it again and see if that works.
 
Can anyone advise where I may have gone wrong - in the game options the headlook mode is direct, and there are no deadzones set (e.g. sliders to the left).

Many thanks.
H


first make sure scale in edtrackerUI is set to 1 on both axis.

Then in mapping, make sure you have the spline graph axis set the right way around.

Horizontal is physical head angle, vertical is virtual head angle. (if back to front you will have to move your head a lot for tiny in game response).

For yaw I set mine to 170 vertical about 25 horizontal
Pitch 90 vertical 25 horizontal
Roll about 50 vertical and 25 horizontal

F8 to reset F9 to pause.

I don't use opentrack 2.3 RC8 I find Opentrack 2.2 latest stable version has more control of the accela filters and is more smooth and precise with fast movements that stop suddenly.
 
Last edited:
Hi chap. I would try an unplug, close the GUI, replug in, restart GUI - sometimes the COM ports get bound up in the .NET libraries I think (I can't explain it, but a restart of the GUI sorts it). Failing that, flash it again and see if that works.

Hi Brumster, thanks for the advice, and I liked the EDtracker tutorial (and the silent running one too), nice job +1 rep. I did flash it a couple of times and it did not change, I also unplugged it and plugged in (only the front 2 usb ports on the pc. cant reach the others & they are in use anyway) & restarted GUI (both ways round I think, I will try again to be sure). When I plugged it back in the GUI did not seem to recognise it was connected at all (the temperature displayed zero ,it might have crashed), I think the port did though (still not visible as "other device" in windows though). I will also try wiping the device & software & reinstalling again tomorrow if I have time.

Mmm actually is that a good idea? IDK would that mean if I can't flash it again through "other devices" like i did originally?, will I see it there again now its clean like, can I do it via the com port where I can see it connected to reinstall the arduino software? I have no idea.

Thanks again, I have wanted one for ages, it was not an option for me until you started making them for sale, so thank you to all involved, my PC is decent, 6 core 3.9 ghz, radeon R9 2GB & 8GB ram, its AMD but 9 months old running windows 7 premium, so I doubt its the hardware or software, I have a feeling it might be a "PICNIC" issue.

Problem
In
Chair
Not
In
Computer

I doubt its the cable (I read in FAQ, needs to be data not just power) as I tried 2, and I did see it in "other devices" initially, so the cable has done the job once I doubt that's the the issue.

Will reply when I have tried the above & report back, thanks for pointing me in the right direction.
 
Could be a USB connectivity issue. We have seen a small number of Pro Micro boards with an incorrect resistor on one of the USB data lines. This causes issues with the device not being recognized by the drivers and is especially noticeable with longer cables.

If you get more reliable connections with a short cable then it may be the same problem that causes the random jumps.

I doubt this is that issue tbh, Rob. I've seen the behaviour he describes yonks ago in the very early sketches where the register wrapped because the drift compensation value applied was massive and reaching the 32768 limit and wrapping...

Reminds me, I must put that resistor thing on the website at some point...

Thanks for the feedback.

I know of three people with this issue now which i admit isnt so many but just wondering what the common denominator might be.

I have another tracker here i can test another night and a different cable, will advise of any difference over the course of the week.
 
Will reply when I have tried the above & report back, thanks for pointing me in the right direction.

You can click "Scan Ports" and if it lists an Arduino, you're ok, it can see the device (assuming you've not got any other Arduino's plugged into your PC other than the EDTracker!) so it should be able to flash it. It will also try to connect to the first one it finds with a free port, but as I said this can sometimes fail for an unexplicable reason, I generally only see this when I've been flashing loads of devices with lots of plugging and unplugging, and I unplug one without remembering to click "Disconnect" first (as you can imagine, I sometimes have a batch of loads to flash!)

Thanks for the feedback.

I know of three people with this issue now which i admit isnt so many but just wondering what the common denominator might be.

I have another tracker here i can test another night and a different cable, will advise of any difference over the course of the week.

Rob is working on putting some logging-to-text-file feature into the GUI so that we can debug this sort of thing a bit easier. I'm not sure when it will be ready but hopefully very soon; this will help us understand what's happening a bit better. I know it's a pain, but we'll get there :)
 
I'm little bit confused about the product texts in the shop. At the product page of the Pre-Built EDTracker (Magnetometer) it says that there are some units available. Does that mean that they are already assembled and ready to be sent or do I still have to wait a few weeks if I order one?
 
I'm doing a 9150 video at some point to show the differences with the 6050. I'll try to do a little section on de-soldering your old 6050 and dropping a 9150 in place.

But drift that severe really should be fixable, assuming you've not fried a component on the board. Check calibration, keep flat/still, let warm up, ensure you've got auto-centering enabled, minimise/close the GUI, etc....

OK, I'll try and calibrate it. I'm having trouble getting it connected to the EDTracker software, it shows values moving when I hit "start" but it says "connected" but it doesn't list the device name or anything at the top where it should (in the videos I've watched)

I've just had mine through the post.... Housework can wait :p

Splendid job and fast turnaround on the upgrade from 6050 to 9150.

Sent on wednesday, back on saturday.

Who did this for you and what was the cost?
 
Last edited:
I'm little bit confused about the product texts in the shop. At the product page of the Pre-Built EDTracker (Magnetometer) it says that there are some units available. Does that mean that they are already assembled and ready to be sent or do I still have to wait a few weeks if I order one?

Ah no, I'll fix that. They are always built to order, we always have a backlog I'm afraid :( !!
 
You can click "Scan Ports" and if it lists an Arduino, you're ok, it can see the device (assuming you've not got any other Arduino's plugged into your PC other than the EDTracker!) so it should be able to flash it. It will also try to connect to the first one it finds with a free port, but as I said this can sometimes fail for an unexplicable reason, I generally only see this when I've been flashing loads of devices with lots of plugging and unplugging, and I unplug one without remembering to click "Disconnect" first (as you can imagine, I sometimes have a batch of loads to flash!)



Rob is working on putting some logging-to-text-file feature into the GUI so that we can debug this sort of thing a bit easier. I'm not sure when it will be ready but hopefully very soon; this will help us understand what's happening a bit better. I know it's a pain, but we'll get there :)

Its very much appreciated, the work and achievements you guys have done is truly amazing, i will await the new software and give results from there :)
 
Back
Top Bottom