DO_SET_ROI on a Tali H500 not supported in MP 1.3.10?

Does someone try to manage the camera of a TALI H500 with a DO_SET_ROI ? Don’t think is supported with the H500, because when I set it with MP, I can see the red flag on the map. But when I upload the mission on the H500, I tried to download the mission again from H500 to MP and the ROI dissapeared on the map. I mean the DO_SET_ROI line always exist in MP but Lat and Long are set to “0”. As if this function was not supported by the H500. I do not know it it’s a H500 bug or MP. Did you try it? If you have the same bug, where to report this bug?

The file before writing to the H500:

2 0 3 16 0.000000 0.000000 0.000000 0.000000 40.247590 5.371515 30.000000 1
3 0 3 201 0.000000 0.000000 0.000000 0.000000 40.248027 5.371875 30.000000 1

The file after reading from the H500:
2 0 3 16 0.000000 0.000000 0.000000 0.000000 40.247589 5.371514 30.000000 1
3 0 3 201 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 1

Thanks,

chris

Ok, will be supported in 1.3.5 like seen in this video, right? youtube.com/watch?v=W8NCFHrEjfU
So will wait for the final release, better for my money :wink:

Camera support in the TALI is connected via the receiver. The APM can’t point or fire the camera from what I’ve seen, as TALI comes from the factory, although I’m sure more hacks could be done.

Getting support for a “proprietary” (Walkera) version of the open-source APM autopilot is problematic at best, since the company, by not releasing the source for their version of it, appear to be in breach of the open source license, and I suspect the APM developers could not support it even if they wanted.

If enough people remind Walkera, perhaps that would help. If only we knew what version of APM they use, it would be a starting point.

If Walkera released the source for their FCS, the problem, if it exists, could probably be fixed.

If you want true APM functionality, just install one into the TALI. No harder than any other DIY multirotor to setup, and they are going obsolete, so will be cheap.

I don’t think Walkera makes any compatibility claims at all with missionplanner or APM, do they?

But having said that, specifically walling off features which are common to every other APM drone seems an awful lot of pointless trouble to go to unless they are trying to boost sales of 3DRobotics APM hardware.

So, yeah, TALI has a real nice radio, a fairly nice autopilot, camera, and gimbal, good battery life, and now, (ahem) a groundstation capability, so perhaps they’ll see the value (and their own ill-thought-thru proprietary foot-shooting irony) in open-source soon enough.

Does DO_SET_ROI currently work in the current release of APM and MP on genuine hardware?

You should probably try that. And if you don’t have an APM, you may want to get one. I love mine!
Until I get A 32 bit one, that is.

@sleat, thanks for your answer.

But for me, after 4 or 5 missions, ROI should be managed by “rotating” the drone, pointing to the ROI target (I understand myself, :wink: , but if you do not understand, tell me!). For me the gimbal is used just for stabilisation purpose, except up-down function, no? So don’t need to be piloted.

Hi sleat, there again,

You said:
If you want true APM functionality, just install one into the TALI. No harder than any other DIY multirotor to setup, and they are going obsolete, so will be cheap.

Easy procedure? Just unplugg the Thali controller, plug the APM 2.6, load the firmware 6 rotors and that’s it?