Camera Mode Failed when changing from video to photo
Got this message when shooting an on the fly panorama last night, hit the play button again and everything worked ok, prior to shooting the panorama I'd manually shot a short video clip, so maybe something to do with switching from video to stills when initiating the mission
Comments
11 comments
this happened again today using 258, same recipe, I'd been shooting video manually then ran the photo mission, with exactly the same result, first attempt to take photo fails and halts the mission, restart it and all fine, if I get a chance I'll put together a mission that has video followed b a photo component and see what happens, here's a link to the mission https://app.dronelink.com/martin-reading/congleton/plan/FgNUEToiSAKqejmq1ehU
Had this happen again last night, mission consisted of video being filmed on a waypoints component, then swapping to photos on a hover at a checkpoint
Here's the mission https://app.dronelink.com/martin-reading/my-first-project/plan/agYubaRaa7rXILs79IqQ/NLEJ8M1LmfTJxf8BtR0Z
This has me stumped as none of those commands should fail, and tapping the play button restarts the mission no problem
This is a video that shows the fault, Changing photo mode to video works as it should
https://youtu.be/1F4RfQC-X-k
Mike (Arizona Wyldwest), try this mission https://app.dronelink.com/martin-reading/my-first-project/plan/xoVnnmlePzSh05mq3ZwV if you run 2 second photo interval list by itself(drone isn't physically capturing video) ten it completes no problem, however if the camera is actually capturing video and you then run 2 second interval list then it crashes
Hi Martin. A couple things I noticed at least on that shared component. You may have just overlooked this because you forgot a start capture on the photo component. Also once you put that in you will need to add “Camera Photo Type” set to Interval or the warning will come up at the top advising to add the photo type. I’ve always set mine up this way and no I don’t remember having issues.
Hi Mike (Arizona Wyldwest), on the original mission that this happened in I had auto capture set for the 10 minute hover, the interval command and associated commands was just put in to make sure I was capturing every 2 seconds rather than what I might have been capturing previously.
Thanks for checking it out👍
Ok Martin. I was just going by the component list you shared which must have both commands or it will fail when testing them as in your video. As I mentioned I don’t remember having and Issue. I may try a mission which switch’s back and forth a few times just to see if it works for me. Interesting..l
Cheers Mike (Arizona Wyldwest), let us know how it goes, I might get a chance to play a bit more with it over the next couple of days
Hey Martin. I haven’t been able to run an actual mission but really doesn’t matter since it’s just commands we’re testing. I actively ran your camera component list and got the same error. I added just the Photo Type “Interval” and it works. I then duplicated the video and photo list twice and set it up to switch between video and photo three times. I ran it again and it switched back and forth between both without any issue. If the camera Photo Type is not set to “Interval” first then usually the Interval time won’t work because it needs to know what photo type as well. Your screen shot of the error does indicates “Camera Mode/ Photo /Undefined.”
I’d did create a couple plans with auto capture to test the issue indicator with a hover and an Orbit then ran the mission preview. When using the auto capture on each it does not indicate the error like it does when added at end of a list. I’m guessing it’s because they are separate components but only DL could explain why they don’t indicate the error when set up this way. Bottom line, just add the Photo Type so it works every time. Maybe give it a try several ways and see for yourself. Enjoy.
The issue seems to be when in video mode between the Stop Capture Command and Camera Mode Command (switching to photo). Because this problem is only reproducible for me on the android/mini 2 combo, combined with the fact we are spending limited time and resources on MSDK v4 bugs and fixes, we are asking users that encounter this to, for now, add a Wait Command between the two commands to avoid this error.
Cheers Nicolas Roberts, understand you spending limited time on things like this
Please sign in to leave a comment.