We've never seen this before, and search returns almost no instances of this error online.
The problem is, one motor won't spin upon start-up or spin when attempting flight with the RC. It blinks red/yellow on the LED constantly. On the CrystalSky tablet, when we try to fly, it says "ESC ERROR".
The only thing we did different to this motor was unscrewed/screwed a tiny screw on the bottom of the motor.
To fix this, we re-uploaded the firmware to the drone. We also re-uploaded the firmware to the RC. We've also plugged in DJI Assistant, which does not show an error.
Please help, thanks!
This sounds like a hardware issue with the drone itself. I would recommend contacting DJI Customer Support.
Related
I'm using opengl es 3.0 API with the android studio ndk to create apps.
But I've encountered a very huge problem. I've created a demo app, all it does it change the background color of the screen from white to black and vice versa, every frame. And so when I go to minimize this app, I still see it rendering the background, mostly at the edges of the screen, and not in full color but still very strongly apparent. And it doesn't go away when I close the app, when I restart the device, or when I run "kill apps" on it. Only a factory data reset fixes the issue, so it's not easy for me to debug this.
This is the relevant code that I'm using for when the app is minimized and receives the APP_CMD_TERMINATE event:
eglMakeCurrent(engine->display,EGL_NO_SURFACE,EGL_NO_SURFACE,EGL_NO_CONTEXT);
eglDestroySurface(engine->display,engine->surface);
engine->display = EGL_NO_DISPLAY;
engine->surface = EGL_NO_SURFACE;
I've error checked that eglDestroySurface() is successful.
And I've put debugging messages in to make sure that the main draw loop is NOT executing when the app is minimized. But the problem persists and I don't know what to do about it. Thanks for any help.
UPDATE: well, no one has responded, and I still don't know what to do. Could it be related to threads?
UPDATE: Still can't determine what it is, but for some reason it's messing with the System UI. Willing to upload my entire source code somewhere if someone would be willing to go through this with me, as I'd really like to be able to continue working on my game engine.
Is it the "Strict Mode" developer option on the device settings, perhaps?
That one flashes the screen if an app is blocking.
It would explain why a factory reset changes behaviour.
The answer is not a solution here. The above comment by the user columbo was correct.
I've demoed switching from black to white at high framerates on 3 different android devices, and also my Linux Desktop, all via the openGL api, and it has exhibited this issue on all the devices. So what he said must be correct: this is a problem with LCD monitor technology itself. Interestingly, doing completely random colors does not cause this problem.
I set my tango down for a couple of months while busy with other things. I charged it for a bit, turned it on and saw the red battery icon. I charged it overnight and saw the green battery symbol. I clicked the power button The splash screen came up, said it was installing updates and screen turned off. That evening I tried to turn it on and it wouldn't do anything. Next morning it turned on - splash screen - white screen, off. Now it doesn't do anything at all. I've tried - volume button and power, both volume buttons...nothing. Has anyone else had this problem? Any ideas? Thanks.
On the below instruction. it only diagnose your device for hardware and BSP level problem. Tango Core and Apps related is not included.
To diagnose your device problem. First we need reset your device.
Hard Reset device
Press your device power key for around 8-10 secs.
sometimes you will see the backlight of screen is off.
Diagnose what is going on on your tango devices
2.1 Check basic bootloader function.
Plug in device with a charging usb cables.
2.1.1 if your device is out of power.
It will show red battery icon. or green icon which you device still enough battery to boot it up.
2.1.2 if your device is not any icon pop up.
Try 1 step again. or
switch different Usb cables and chargers or charging docks.
If it still doesn't work.It is possible a hardware issues now. you may need to contact project-tango-help#google.com
2.1.3 if you do see the battery icon, but without charging icon on it.
That mean something wrong with your charging cable or devices. Switch different charger and cables. if problem still exists. you may need to contact project-tango-help#google.com
2.2 Check the Software side of the devices
if you can see the icon in 2.1.1, that is good.
Normally on Green icon, you can boot up your device.
2.2.1 after the icon is gone, press the power key are 1-3 secs, device will boot up.
you will see the tango icon and the rolling tango icon as part of booting process.
if you get stuck at this two process forever. it means that there is some problem on booting image on android. please go to section 2.3.
if you can see the Android UI without problem. you are fine.keep a eye on your battery. if it show 50% on charging full. and some weird condition. you may need to contact project-tango-help#google.com for more details.
2.3 Recovery your device by android recovery mode.
if you android system can't boot up successfully, Recovery your device is needed. Remember it will wipe out all your data,and cache. so try to backup your data if possible.
2.3.1 If you device can access by ADB, try : adb reboot recovery
or try below steps:
{ make sure device is off,
press the power key with volume Up and Down key at the same time for around 2-3 seconds, till you see Bootloader menus
you will see
{
Continue
Fastboot protocol
Recovery mode
Reboot
Power off
Force Recovery
}
by using volume Up and Down, and power key you can select the item.
select "Recovery mode"
2.3.2: now you are at Tango android recovery mode.
it will show
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
Using Volume down key for moving, and power key for selecting.
The same step as normal Android recovery step.
1. wipe cache partition
2. wipe data/factory reset
then select reboot system now.
Waiting device to boot up.
2.3.3, If your device is still not good. Google didn't provide the tango image for customer fastbooting the device. you had to contact project-tango-help#google.com for next step.
Today I accidentally upgrade the Yellowstone that I was working on and after the system upgrade, the TangoMapper is not working any more. The app can be launched and you can still choose the specifications for your data collection such as "Enable recording" and "Enable depth", but when you click Live Sensor Data -> [VGA+Depth], only red window will shows up at the place where it use to show the camera recording, and the depth measurement is not shown at all on the right. I wonder has anybody encountered this situation before? I would greatly appreciate any help or suggestion.
Da, You might have a out dated apk. However, Tango Mapper is a Tango internal tool. I wonder how did you get it.. Even though you have the apk, it won't get updated unless you have internal access to Tango team..
I've seen claims on the net that the newly released iOS 7.1's iBeacon support.
Specifically:
The system is supposed to still notify your app about
didEnterRegion/didExitRegion events, even if the user explicitly
kills your app.
didEnterRegion/didExitRegion notifications are
supposed to be faster from the background and/or with the device
locked.
I have not been able to confirm either of these claims with my own testing. In fact, I seem to be less likely to get didEnterRegion/didExitRegion notifications from a locked device. (more accurately I seem to get didEnterRegion notices, but not didExitRegion notices). That could be because Apple made me remove my BLE background mode entries in my info.plist - I'm not completely sure. I'm still trying to sort this out.
I had trouble setting up my tests at first, but I have witnessed background region entry callbacks after killing an app in iOS 7.1 on both iPhone 4s and iPhone 5s models. See comments below for testing details and instructions to reproduce.
I have also done tests on background detection times on an iPhone 4S, and I still see delays of 15 minutes on iOS 7.1. My full test results and methodology are described here.
Finally, I have also done some tests on the fluctuations on the "accuracy" (distance in meters) measurement on the same device before and after the upgrade to iOS 7.1. I do not see an obvious difference in the noise on the estimate. The graphs below show results before and after the upgrade, with an iBeacon 0.5 meters away for 60 seconds then moved to 3 meters away for 60 seconds. In both cases, the transmitter was a properly calibrated iPhone 4S w/ iOS 7.1 and the receiver was an iPhone 5S.
iOS 7.0.6 Estimated distance
iOS 7.1 Estimated distance
As has been mentioned in several articles circulating around the internet, beacon sensing is available even when you swipe your app away from the multi-tasking view. However in my experiments, a region enter/exit event doesn't call the didDetermineState: directly (Probably because I hadn't been using the AppDelegate to initiate any beacon sensing but instead triggering monitoring based on UI events). Instead if you have registered for Background Location Updates, your AppDelegate's didFinishLaunchingWithOptions: method would get called with the value for key UIApplicationLaunchOptionsLocationKey in the parameter launchOptions set.
You can do a simple check like this to test if this is indeed a location update that has bought your app into the background to perform some task.
if ([launchOptions objectForKey:UIApplicationLaunchOptionsLocationKey])
You can then either register your monitored regions again or start ranging immediately.
P.S. CLLocationManager retains your previously monitoredRegions on app restore but without starting monitoring again using the same UUID and identity, you would not get the enter/exit region event in CLLocationManagerDelegate (which had brought your back up to life)
David has done some wonderful work on this, so I'm writing this cautiously... but I'm seeing something quite different from him in my tests.
I'm using two phones: an iPhone 4S running iOS 7.1 (11D167) and an iPhone 5S running iOS 7.0.6 (11B651). My iBeacons are manufactured and sold by Bluecats (www.bluecats.com), although I'm not yet using their SDK (ie. I'm just using CoreLocation) and I don't think the manufacturer makes much difference.
I'm getting response times of around 1-2 seconds on both devices when the app is running in the foreground and also when running in the background. The only difference is when I remove the app from the app switcher: iOS 7.0.6 never responds (or perhaps will do in 15 minutes), but iOS 7.1 responds in roughly the same time. When I say "respond", I mean that the CLLocationManager's locationManager:didDetermineState:forRegion: delegate is called by iOS.
I'm testing by actually wandering around my office with phones in hand, so I'm physically moving in and out of range. Strangely (?), in my early testing, where I was sitting at my desk and simulating moving in and out of range by removing and reinserting batteries, I was seeing much slower response times. Perhaps this is part of the difference?
In my testing I have seen the presence of a beacon go un-noticed by an app for up to 15 minutes, but I found something that's interesting. I'm using RedBearLabs mini BTLE sensors as ibeacons and their app to program the beacons, http://redbearlab.com/ibeacon/ (http://redbearlab.com/s/MiniBeacon_v1.zip), seems to have an something in it that immediately starts a scan / update of beacons. If I start a beacon up, and in my app it goes unnoticed, by starting then quitting the MiniBeacon app my app immediately notifies me that there are new beacons. This is the same result when entering or exiting. Their app uses CBCentralManager, which my app doesn't, so maybe a mixture between CBCentralManager and CLBeaconRegion is the way to go? I imagine CLBeaconRegion starts / restarts the bluetooth radio, so maybe that is the reason for this. Just taking a stab at it in hopes that someone with a more complete understanding can help resolve this.
Thanks
My testing also reproduces 15 mins to start scanning when my app is in background mode on iOS7.1.1. Just a bit curious, I have seen quite many youtube videos from different companies showing the app has been waken from background mode as soon as they approach their beacons. Is it sales trick?
I am looking for some advice/input on writing a device driver. I have never written one for windows before, let alone for bluetooth.
Can you recommend a book or website or something to get me started? I have the windows driver kit, and the examples therein but with out some place to start I am dead in the water.
The specifics: My friend gave me his mac Magic Mouse. I have a windows 7 machine. With the mouse set up as just a generic HID device it works ok as a two button mouse with no scroll, the motion is smooth and the acceleration what you expect in a windows mouse.
The mouse actually has a fairly good lpi resolution, making it pretty sensitive. There are mac drivers available, extracted from bootcamp. They kind of work. The cursor will randomly freeze or stop responding to the mouse's movement, which is buffered, and then leap once whatever has caused the stall stops. As an added touch the mac drivers make the cursor move like it would on a mac, with that logarithmic acceleration, that will completely throw off any windows user. With the driers you get vertical and horizontal scroll, but that's it. There is no multi touch functionality, and you can't change any of the behaviors, like acceleration. There isn't multiclutch for windows, or other 3rd party software for a multi touch mouse.
So I figured I would endeavor to make my own drivers and multi touch functionality in windows for this thing. I know mac will never support it properly under windows and windows won't write there own drivers until there is a reason.
Also if any one knows of any one else trying to do the same or similar things, point me to them.