Open MorfinWendel opened 4 years ago
Hiya - a few questions 1) How does the device appear under Device Manager (look for the serial COM port)? What's the name/text describing it? 2) In USB Game Controllers, does an EDTracker "joystick" device show up at all?
Hi, Before I managed to install proper drivers it was showing up as EdTracker2 unknown device. I had to manually point windows to treat it as Arduino Leonardo (Or Pro Micro, both act the same), so now it shows up as COMX Arduino Leonardo, but it doesn't show up as a joystick at all. On second PC, where windows could get drivers without pointing it at a specific device, it showed up as COMX Arduino Leonardo, and did show up also as a game controller, although still not working at all, and unable to connect with 9250 firmware. Both PCs used Windows 7. Additionally I've tried to calibrate it as 6050 only, but coulnd't get it to calibrate at all (2-3 values calibrated at most, then completely lost after next button press), so there is a possibility that there is also something wrong with the chip itself, although it does connect and show some values, so i guess that would be a separate issue to the one above.
So let's focus on the 2nd PC where it shows up as a joystick (this shows that at least the firmware is up and running as an EDTracker; the first PC doesn't even see the joystick so it cannot be initialising correctly). Load up the Arduino IDE, enable debugging (uncomment the debug line), compile, flash and then use the Arduino serial monitor to connect to the device and read what's happening. Ignore the EDTracker GUI for now, just use the serial monitor - with debugging, it might tell us a bit more info about what's going on ;)
So, I finally found some time and opportunity to access second PC (It's not mine), I did uncomment #define DEBUG line, it gives me #warning "** DEBUG defined **" in uploading console, but on both PCs, serial monitor is completely blank, no matter what sketch i upload. Any ideas why what's happening? I've tried pluggin in, unplugging, pressing the reset button, waiting some time, nothing shows up in serial monitor. It did work when i uploaded some random 9250 test sketch.(like it did print some hello message and sensor values)
That's got me beat! With debug enabled, you should get some debug output to the serial port when the device starts up... if you're not getting any serial output, I can only thing something is wrong with your Arduino build environment (incorrect libraries/etc). I'd say PC/driver or cable issues but since it flashes, and you've proven it works with other Arduino sketches, that doesn't really make sense. You're happy that the Arduino IDE is a clean install, the libraries are the right ones, you've selected the right device and so forth? Arduino 1.8.5? Maybe turn on the IDE debugging and upload the entirety of the compile/upload log just to verify?
Could you help me build a wireless Edtracker? Which device should I use for wireless connection without losing transmission quality?
Hi I have the same problem as MorfinWendel but using the MPU 9150 board. made my first Edtrackers over 4 years ago and have just come back to play Elite again. Lost my original but had lots of version 3 boards and parts from then. I have built a new board on pasteboard to check, have flashed the 9150 Sketch as per Github instructions. Fresh install of Arduino software and drivers and its recognised on COM4, also as a Game Controller. But when I launch the Edtracker 404 GUI , I cant see magnetometer tab. There is no Sketch info and GUI reports "NOT CONNECTED" I can click to connect to Tracker but thats it. No calibration. My soldering is pretty good, Arduino red power light is on, Orange flashes if I use GUI and press connect. Green light is on on the MPU 9150.
Hope this helps, problem is duplicated using different MPU 9150
I am including compile verify text file with output as there were warnings but compile and upload completed. CompileVerify.txt
I have had similar issues to AcidCloud, struggling to find a solution after I assumed it had compiled acceptably and it bricked a promicro chinese clone. I have been unable to recover the clone using a USBasp bootloader. I have paired the promicro with a MPU9250. I get the following file, it has been a long time since I did much programming in C and its my first time using the Arduino eco system. CompileWarnings.txt
Hi, same probleme here with a 9250. It is recognized by W10 as a joystick (EDTracker). But nothing happens when I press the CONNECT TO TRACKER button. However, it is written "connected" next to the head (but not above the button) and if I try to connect to the COM port with Docklight, it says that this COM port is already in use (so it's connected to the GUI).
Hi, I've built my own EDtracker out of Arduino Pro Micro clone and this MPU 9250 board: https://www.hotmcu.com/gy91-10dof-mpu9250-and-bmp280-multisensor-module-p-341.html?cPath=7_37 (It's the version with BMP280, so that might be somewhat causing the issue, maybe it's a bit different than the regular one?) Most of the issues, I've eventually managed to solve on my own, but this is the one that I can't figure out.
My problem is that it works perfectly fine when I flash it with calibration firmware, or 6050 firmware, but when I flash it with 9250 firmware (both through the GUI app, and Arduino IDE app) It doesn't work at all. The GUI app doesn't connect, serial port monitor doesn't show anything. Only thing that happens when I press "CONNECT TO TRACKER" button is the red LED flashes once, and then nothing (although it does keep the serial port busy and unable to access from Arduino IDE for example).
I believe it's not hardware or wiring problem, as I managed to make it work with libraries from this repo: (https://github.com/Snowda/MPU9250), and it did give me all 9 values, therefore the magnetometer seems to be working properly.
I believe I could just use it as 6050 only (could I?), but it seems like a bit of a waste. Could you please guide me in some direction to fix this problem? Maybe it is a matter of this particular MPU board, and it just requires a few changes in code to work, or is a somewhat known issue? Thank you for your support.