If it is working in everything except ED that must be where the problem lies. I occasionally have a problem where ED forgets my very expensive Warthog HOTAS. I have to go into the controls section and select a different config, then apply, then re-select my own config, apply and all is well again. Try that first.
if that doesn't fix it, I would install Opentrack 2.2 stable and ED will use it as a TrackIR device with no additional input from you.
First off apologies if this has been covered, i didn't want to search through 300+ pages.
Recently bought myself an EDTracker DIY with the 9250 board, got it assembled and arduino drivers installed without issue. Installed the EDtracker GUI and ran it, received this screen, mostly functional but some elements seem out of place.
(appologies for link and not inline, invalid filetype error even though it's a relatively small jpg)
It recognises the device however, so i attempted to flash the 4.05 firmware for the 250 board. First attempt throws up this error message. (Error text in spoiler just in case it's useful)
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.UnauthorizedAccessException: Access to the port 'COM8' is denied.
at System.IO.Ports.InternalResources.WinIOError(Int32 errorCode, String str)
at System.IO.Ports.SerialStream..ctor(String portName, Int32 baudRate, Parity parity, Int32 dataBits, StopBits stopBits, Int32 readTimeout, Int32 writeTimeout, Handshake handshake, Boolean dtrEnable, Boolean rtsEnable, Boolean discardNull, Byte parityReplace)
at System.IO.Ports.SerialPort.Open()
at EDTrackerUI3.flashDialog.touchPort(String port, Int32 baud)
at EDTrackerUI3.flashDialog.ProgressForm_Shown(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnShown(EventArgs e)
at System.Windows.Forms.Form.CallShownEvent()
at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Unplug everything, restart software and attempt again, everything worked. Still seem to have the wrong UI, restore factory settings is unclickable and other items appear to be covered. Clicked the edge of one of the covered clickable buttons and gives me the calibration progress bar. once it completed the ui changed to the one shown in the tutorial pdf and videos. Slightly confused, but so far so good. Calibrated the mag no problems, rebiased the gyros, and everything was working fine, head was moving in unison to the EDtracker. Yay!
Hopped in game, and it was amazing, worked better than expected, for about half an hour. While i was fiddling with other settings (also acquired a new joystick and an axis was also bound to pitch vision giving some interesting results). at some point during fixing and setting up the joystick, the edtracker stopped controlling the vision. Rebinding did nothing, and recentering was having no effect. Tabed back to the GUI and saw there were no inputs being registered. Maybe the program crashed, so i closed and re opened it. Back to the first screen. Since then i have never been able to return to the 'Proper' GUI, have not been able to receive any inputs from the EDtracker. Opentracker also does not receive any input from the EDtracker, so it isn't dodgy game settings. I have tried flashing every version of the firmware available, with no success. It always recognises the device as an arduino leonardo, but only sometimes completes the flash, sometimes giving a port error, either closed, missing or no access. There does not seem to be any pattern to this. After successful flashing sometimes the gyro balance button gives a progress bar, sometimes it causes a crash, but never takes me back to the 'proper' GUI.
Flashing the debug firmware results in flashing LEDs on the controller as described in a previous post. (if the sequence is important then green emits a short flash roughly once a second, orange toggles on and off with the green flash, and red is continuous).
so yeah, anyone got any ideas? for the 20 mins game time i got it working was amazing and i don't feel like giving up, i'm just out of ideas how to fix it.
If it is working in everything except ED that must be where the problem lies. I occasionally have a problem where ED forgets my very expensive Warthog HOTAS. I have to go into the controls section and select a different config, then apply, then re-select my own config, apply and all is well again. Try that first.
if that doesn't fix it, I would install Opentrack 2.2 stable and ED will use it as a TrackIR device with no additional input from you.
Has anyone had any issues with EDTracker and a Logitech G430 (or any other make/model) not cooperating? I have searched as much as I could, but there are so many posts out there it's almost impossible to go through them all.
I have been having this problem that when EDTracker is plugged in it causes my G430 to cut out momentarily, then recover. It does this several times and I can't for the life figure out why it's doing that. With EDTracker plugged out it functions normally. I have the EDTracker mounted ontop of the headset and both are plugged into USB 2 ports. I have also tried different ports, thinking it was a power issue, but to no avail. The same problem keeps occurring. All my drivers and patches are up to date. I checked EventViewer, but saw no messages about this.
Has anyone else been going through this, and is there a solution?
Have you tried moving the EDTracker away from the headset to see if the problem persists. That would tell you if there is localised interference that the G430 is picking up. I've had every version of Edtracker including the beta wireless version and never seen this behaviour with my wired Plantronics or Corsair wireless headphones. Which version of EDTracker are you having the problem with?
Did a quick search through our support emails; never had a report of the G430 being an issue I'm afraid
Would just pass on the usual suggestions of trying different ports/cables, which you've done, but maybe also try on a different PC if you can, just to confirm whether it's a software/OS/driver issue on that particular PC...
I'm currently working on a DIY EDTracker with an MPU-9250 and pro micro both sourced from china via ebay. I've read through this forum, used google, watched Brumsters videos including the debugging one, and I'm stuck. When I flash the 9250 sketch (4.0.5), i never get past "not connected" and my device manager doesn't show the device. I am able to flash the calibration sketch, but its buggy as hell.
I tested some simple sketches on the arduino that had no issues.
I tested some sketches for the 9250 that had no issues. I did this testing with both the leonardo and a uno
I unsoldered from the PCB bought from EDTracker and have tried on a breadboard
I have tried flashing using the command prompt (with admin rights) and the GUI (4.0.4.0)
During flashing, I never receive errors but its as if the program doesn't take. I have yet to see Windows recognize the device as a joystick.
I am running Windows 10 x64. I tried on both a desktop and a laptop. I tried disabling the other com device on the desktop, the laptop did not have either. The device manager sees the device and recognizes it as a leonardo under COM devices.
Any help, including better search phrases to find the answer if it already has been answered elsewhere where I did not locate it, would be greatly appreciated.
it is a 16mhz according to the Ebay posting and no I'm in the US. For what it is worth, during the calibration sketch it reports the temperature around 41.4 (i'm assuming Celsius). I also tried to leverage linux to use the java command line but it panicked when it was /dev/ttys0 instead of COM(1-5). I'm going nuts!
I'm currently working on a DIY EDTracker with an MPU-9250 and pro micro both sourced from china via ebay. I've read through this forum, used google, watched Brumsters videos including the debugging one, and I'm stuck. When I flash the 9250 sketch (4.0.5), i never get past "not connected" and my device manager doesn't show the device. I am able to flash the calibration sketch, but its buggy as hell.
I tested some simple sketches on the arduino that had no issues.
I tested some sketches for the 9250 that had no issues. I did this testing with both the leonardo and a uno
I unsoldered from the PCB bought from EDTracker and have tried on a breadboard
I have tried flashing using the command prompt (with admin rights) and the GUI (4.0.4.0)
During flashing, I never receive errors but its as if the program doesn't take. I have yet to see Windows recognize the device as a joystick.
I am running Windows 10 x64. I tried on both a desktop and a laptop. I tried disabling the other com device on the desktop, the laptop did not have either. The device manager sees the device and recognizes it as a leonardo under COM devices.
Any help, including better search phrases to find the answer if it already has been answered elsewhere where I did not locate it, would be greatly appreciated.
Only thing i could suggest is try a program called USB Deview
It uninstalls usb devices and drivers, i usually find if something isnt being recognised the drivers are not working corrrectly.
This util allows you to uninstall and disconnect any usb device then when you plug it back in it reinstalls drivers.
Interesting, I hadn't tried that because I wasn't having an issue with the leonardo connecting but found that with USBDeview it was recognized as EDTracker both with the calibration sketch and the 9250 sketch. I should have expanded earlier when I said the calib sketch was buggy, I have clicked the "Calculate Bias" button 15 times at the time of this screenshot. I am posting a screenshot of the calibration sketch (with usbdeview in the back), the flash message from flashing 9250, and than a screenshot of usbdeview after the 9250 flash which shows it being identified as EDTracker, but no axis data received either on the EDTracker GUI or OpenTrack.
