Theres the files for a 3D printable enclosure linked to on the site;
https://edtracker.org.uk
https://edtracker.org.uk
DIY Head Tracker For A Tenner
- Thread starter Dead Fred
- Start date
Sorry, been a long weekend at Lavecon, but back now
Yes, prime candidate if the device just "sticks" after powering-on is that it thinks the button is held down - often because it's connected the wrong waySounds like you've sorted it now anyway....
Glad you had a good time at Lavecon, really wished I could have made it and caught up with you all again, but Silverstone the weekend before was way better
Will be looking to go to the 2016 one
Last edited:
Announcement on the website about the new EDTracker Pro, but I thought I'd just pop in here and give a lighter-hearted update
.jpg)
So we released EDTracker Pro at Lavecon, and it's now on the webshop for sale, replacing the previous hand-built MPU-9150 equipped models that we did on a voluntary basis. We won't be building any more DIY EDTrackers for people, short of fulfilling outstanding orders (anyone in the queue will be offered the option to cancel their order and go for the Pro instead, of course). When we've closed all the outstanding old orders off, we'll offer the remaining stock of MPU-9150 devices at a knock-down price to get clear (people in the queue will get first refusal at the lower price first - emails will go out in due course so bear with us).
I figure there may be some common questions, which we will do our best to answer, but just to be clear about what I am guessing will be people's main concerns....
1. We're not stopping anything related to "DIY" EDTracker. It carries on and it still remains the cheapest way to EDTracker ownership. We'll continue to support and develop the open-source code (mind you, it's pretty stable now to be honest). You'll still be able to get the custom PCBs if you don't want to make it all yourself. So don't worry, it's all good, we still want to encourage people to make it themselves!
2. Your previous MPU-9150 or MPU-6050 DIY EDTracker isn't defunct and isn't worth throwing in the bin in a fit of tears, don't worry. EDTracker Pro is mainly about one thing - we (Rob, Dor and myself) just can't keep hand-soldering these things indefinitely any more. The order numbers are just too high now, and it eats into our personal time and also the time we could be spending doing other EDTracker stuff, like developing the software side. Pro is all factory-built, freeing up our time from doing the construction. It just wasn't sustainable long term. But functionally, Pro doesn't do anything that the magnetometer-enabled MPU-9150 didn't. Sure, it's lighter, it's got a stronger USB connector design, it's not hand-dremelled (!) and it's now completely driverless - but in terms of how it plays in-game, there's very little difference at all.
3. So no-one thinks there is anything underhand going on, I will clarify that we are now trading as a limited company, EDTracker Ltd. This is just common sense given how 'serious' things are getting. We will honour all previous commitments via the company too, so it's not just a "Pro only" thing.
Do people have any questions or concerns that they think it might be worth clarifying/answering? Something I've forgotten?
So we released EDTracker Pro at Lavecon, and it's now on the webshop for sale, replacing the previous hand-built MPU-9150 equipped models that we did on a voluntary basis. We won't be building any more DIY EDTrackers for people, short of fulfilling outstanding orders (anyone in the queue will be offered the option to cancel their order and go for the Pro instead, of course). When we've closed all the outstanding old orders off, we'll offer the remaining stock of MPU-9150 devices at a knock-down price to get clear (people in the queue will get first refusal at the lower price first - emails will go out in due course so bear with us).
I figure there may be some common questions, which we will do our best to answer, but just to be clear about what I am guessing will be people's main concerns....
1. We're not stopping anything related to "DIY" EDTracker. It carries on and it still remains the cheapest way to EDTracker ownership. We'll continue to support and develop the open-source code (mind you, it's pretty stable now to be honest). You'll still be able to get the custom PCBs if you don't want to make it all yourself. So don't worry, it's all good, we still want to encourage people to make it themselves!
2. Your previous MPU-9150 or MPU-6050 DIY EDTracker isn't defunct and isn't worth throwing in the bin in a fit of tears, don't worry
. EDTracker Pro is mainly about one thing - we (Rob, Dor and myself) just can't keep hand-soldering these things indefinitely any more. The order numbers are just too high now, and it eats into our personal time and also the time we could be spending doing other EDTracker stuff, like developing the software side. Pro is all factory-built, freeing up our time from doing the construction. It just wasn't sustainable long term. But functionally, Pro doesn't do anything that the magnetometer-enabled MPU-9150 didn't. Sure, it's lighter, it's got a stronger USB connector design, it's not hand-dremelled (!) and it's now completely driverless - but in terms of how it plays in-game, there's very little difference at all.3. So no-one thinks there is anything underhand going on, I will clarify that we are now trading as a limited company, EDTracker Ltd. This is just common sense given how 'serious' things are getting. We will honour all previous commitments via the company too, so it's not just a "Pro only" thing.
Do people have any questions or concerns that they think it might be worth clarifying/answering? Something I've forgotten?
Last edited:
Really pleased you've incorporated Brumster mate, I hope everything goes really well. Must be exciting times
I am still confused about the Mac compatibility of the EDTracker. I do have a Windows VM available ... would it be possible for me to run the Windows calibration utility in the VM to calibrate the EDTracker, and then shut down the VM and go back to the Mac desktop in order to play E and have the unit remain calibrated? But this wouldn't allow me any way to recalibrate the EDTracker if/when it starts to drift, correct? Better still, are there any plans or thoughts of making a Mac version of the calibration utility?
and have the unit remain calibrated? But this wouldn't allow me any way to recalibrate the EDTracker if/when it starts to drift, correct? Better still, are there any plans or thoughts of making a Mac version of the calibration utility?
I am still confused about the Mac compatibility of the EDTracker. I do have a Windows VM available ... would it be possible for me to run the Windows calibration utility in the VM to calibrate the EDTracker, and then shut down the VM and go back to the Mac desktop in order to play E
I do know that the software is not required after calibration, (only for the shortcut to work for recentering, or the auto centering, both mainly on the 6050), as the 9150 doesn't drift much if at all, you should not need it at all after calibrating. Now as to this working on the mac, i am sure there are wiser men than me to answer that.
Last edited:
I am still confused about the Mac compatibility of the EDTracker. I do have a Windows VM available ... would it be possible for me to run the Windows calibration utility in the VM to calibrate the EDTracker, and then shut down the VM and go back to the Mac desktop in order to play E
As Noscar said, the GUI software itself is .NET so needs windows, but I've heard of people running it in boot camp/VM just to get it calibrated. Once done, it plays in-game on a Mac just as a joystick.
A Mac version of the GUI would be wonderful, but I have no experience of Mac development so I would have to defer to Rob on that one, who's our resident GUI/.NET guru.... hopefully he'll pop in and reply...
i had the 9150 version, as Brumster will remember, it just would not work for me, he kindly refunded me and i returned it. I had the problem a few others on this thread had, where it would not connect, although showed in the devices, i always thought it was some sort of driver incompatibility or similar, but never found the actual cause.
Now i see the edtracker pro released, driverless and factory produced, i am really tempted to give this a try as the 6050 temp and drift problems is so annoying i hardly use it now.
Worth a try maybe. Or i might wait for the wireless model, will that be a long time off yet.
On a side note, does anyone know if this is working in Star citizen yet. As i am pledged to that game and want to try it when the game is better fleshed out.
Now i see the edtracker pro released, driverless and factory produced, i am really tempted to give this a try as the 6050 temp and drift problems is so annoying i hardly use it now.
Worth a try maybe. Or i might wait for the wireless model, will that be a long time off yet.
On a side note, does anyone know if this is working in Star citizen yet. As i am pledged to that game and want to try it when the game is better fleshed out.
Last edited:
Wireless one will be a while yet - technically it's working but there's a lot more to selling wireless devices than just punting them out without approval bit of antenna tuning to do yet. So wouldn't want to promise anything, but it won't be for a few months yet at least. Very much a Michael Brookes approach from me on that one.... "soon (tm)"...
bit of antenna tuning to do yet. So wouldn't want to promise anything, but it won't be for a few months yet at least. Very much a Michael Brookes approach from me on that one.... "soon (tm)"... Wireless one will be a while yet - technically it's working but there's a lot more to selling wireless devices than just punting them out without approval
thanks brumster, i really like the sound of the wireless one, might wait a bit to see how it develops.
Just out of interest... So the "pro" version will be using a 16MHz clock (instead of the previous 8MHz clock). Is this simply because this is what's available generally now, so that's what's being used? Or another reason?
And, does it have any benefits/issues? ie:-
- Is it more responsive now as it's taking measurements quicker so can react to them quicker?
- As all the previous code and testing was done on something running at half the speed, is it possible some of the code now might mis-behave? eg: Wait 1000 cycles before checking again, might not be long enough now?
Just thought it would be interesting to know/discuss...
And, does it have any benefits/issues? ie:-
- Is it more responsive now as it's taking measurements quicker so can react to them quicker?
- As all the previous code and testing was done on something running at half the speed, is it possible some of the code now might mis-behave? eg: Wait 1000 cycles before checking again, might not be long enough now?
Just thought it would be interesting to know/discuss...
Just out of interest... So the "pro" version will be using a 16MHz clock (instead of the previous 8MHz clock). Is this simply because this is what's available generally now, so that's what's being used? Or another reason?
And, does it have any benefits/issues? ie:-
- Is it more responsive now as it's taking measurements quicker so can react to them quicker?
- As all the previous code and testing was done on something running at half the speed, is it possible some of the code now might mis-behave? eg: Wait 1000 cycles before checking again, might not be long enough now?
Just thought it would be interesting to know/discuss...
You're mixing up models - my email to you was basically saying the prototype EDTracker Pro that YOU (specifically) had would have been running at 8MHz. All the DIY EDTrackers (Arduino Pro Micro based) run at 16MHz
Last edited:
You're mixing up models - my email to you was basically saying the prototype EDTracker Pro that YOU (specifically) had would have been running at 8MHz. All the DIY EDTrackers (Arduino Pro Micro based) run at 16MHz
Ahhhh! So the Pro prototypes are running at 8mhz, but the final EDTracker Pro versions will be running (back) up at 16mhz again... And is that due to a slightly difference processor or just something more subtle being changed on the board to move it up from 8mhz to 16mhz?
Sorry for the questions, but I am interested! If only maybe to ask slightly less dumb questions next time
Last edited:
EDTracker Pro Set-up: Here's how to do it.
After picking up an EDTracker Pro at Lavecon and being confused by some of the set-up instructions on the EDTracker website plus a few people on Twitter having set-up problems I wrote a blog post last night which should help:
http://www.lingula.org.uk/wordpress/2015/07/16/edtracker-setting-up-and-use-with-elite-dangerous/
It's a step by step walk through of the set-up, along with configuring opentrack and includes a sample opentrack configuration file, which is the one I use and doesn't give me motion sickness. It also direct links to the files to download for both EDTRackerPro GUI and opentrack. I found deciding which GUI program to use on the EDTracker web site to be confusing and the release version of opentrack is about three pages down from the landing page.
Basically, if you follow the steps methodically you'll be up and running is less than a quarter of an hour (assuming reasonable download speeds).
After picking up an EDTracker Pro at Lavecon and being confused by some of the set-up instructions on the EDTracker website plus a few people on Twitter having set-up problems I wrote a blog post last night which should help:
http://www.lingula.org.uk/wordpress/2015/07/16/edtracker-setting-up-and-use-with-elite-dangerous/
It's a step by step walk through of the set-up, along with configuring opentrack and includes a sample opentrack configuration file, which is the one I use and doesn't give me motion sickness. It also direct links to the files to download for both EDTRackerPro GUI and opentrack. I found deciding which GUI program to use on the EDTracker web site to be confusing and the release version of opentrack is about three pages down from the landing page.
Basically, if you follow the steps methodically you'll be up and running is less than a quarter of an hour (assuming reasonable download speeds).