Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: PTZ speed broken on BirdDog P200A2_A3 5.5.114 #142

Open
MattRogish opened this issue Nov 7, 2024 · 1 comment
Open

Bug: PTZ speed broken on BirdDog P200A2_A3 5.5.114 #142

MattRogish opened this issue Nov 7, 2024 · 1 comment
Labels
Bug Something isn't working

Comments

@MattRogish
Copy link

We recently upgraded the BirdDog P200 firmware to latest (5.5.114) as well as upgrading Companion from 3.1-ish to 3.4.3. Some - but not all - of our PTZ buttons in Companion 3.4.3 started panning super super slowly (like, 1 pixel per second). However, some were fine.

Looking in the JSON for the buttons I see:

Working Button:

"options": {
	"val": "left",
	"posPan": "0000",
	"posTilt": "0000",
	"override": true,
	**"panSpeed": 11,**
	**"tiltSpeed": 9,**
	"value": 88
},

Not working button:

"options": {
	"val": "right",
	"posPan": "0000",
	"posTilt": "0000",
	"override": true,
	"value": 89
},

I think - but cannot verify - that a "working button" was a button we created at some point in the past?

The non-working button is one created with v3.4.3. I wonder if the "value" parameter is either gone or otherwise doesn't do anything?

Also note in the BirdDog Camera Control UI the Pan Speed is a value from 0-21. In Companion, the "Speed Override" control is a value from 0-255, which seems like a mismatch.

It's also possible it had an issue with the Module Model being set to Auto-Detect, I changed it to P200 A2_A3 but that didn't seem to make difference.

Thanks!

--
Matt

@bryce-seifert bryce-seifert added the Bug Something isn't working label Nov 7, 2024
@bryce-seifert
Copy link
Member

@MattRogish I think I found the issue with the pan/tilt speed override not working, and that should be fixed for new buttons in the latest beta. Let me know if creating a new button still results in issues.

In regards to the speed values, the module should recognize the speed mode (either 0-21 or 0-255) set by the camera but it sounds like it's possibly not doing that. I will look into that more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants