bitfocus / companion-module-birddog-ptz

MIT License
5 stars 5 forks source link

PTZ speed actions fail to apply when sending multiple actions on a single button #78

Open nottooloud opened 2 years ago

nottooloud commented 2 years ago

I made a set of buttons with 3 actions each, setting P, T, and Z speeds all to small, medium, or large values. It never works to push a button just once, need to push it 3 times at least, and often more, before the camera will take all 3 values. I tried 5 ms delays between the actions.

P200 firmware 5.0.059 and companion-mac-arm64-2.4.0+4710-beta-05bf0507.

jmcc94 commented 1 year ago

@nottooloud will take a look, but I don't have any P200 to test with, only P100.

Does the problem still exist on the recent release 5.0.064?

joakyhsf69 commented 1 year ago

Yes, I have several P200 with firmware 5.0.0.64 and I have the same problem

obcocav commented 1 year ago

Can confirm same issue with P200 A2 and A4 revisions on 5.0.0.64 and latest beta Companion.

jmcc94 commented 1 year ago

When you say '...before the camera will take all 3 values...' how do you know?

Are you using variables or checking the BirdUI on the camera?

nottooloud commented 1 year ago

I'm checking BirdUI. Those values don't update dynamically, have to skip out to another section and back to Cam Control to see the new values.

jmcc94 commented 1 year ago

@nottooloud - As BirdUI / CamControl and Companion all poll the API to get the information, there can be a delay between setting a value, and having that value represented in the visualization.. and, as you say, the BirdUI doesn't auto-refresh.

From what I'm seeing with my testing, the speed changes are behaving similarly to what I would expect ... I'm seeing almost instant change in the companion variables... which polls the camera API

BBrazner commented 1 year ago

I'm having success with minimum 100ms delay between actions involving p/t/z speed. Also, once the camera accepts a speed command, the feedback variables update right away.

bryce-seifert commented 1 year ago

This has been narrowed down to an issue with the BirdDog firmware itself, as it is reproducible outside of Companion. We have informed BirdDog of the issue.

The temporary solution is to add a relative delay between each action.